#Minor A3000 Problems
26 messages in this thread
I'm having a little trouble with some files on my A3000 hard drive. In the
S directory on my 2.0 system partition, there are 2 files with the same
name, neither of which wants to be deleted or renamed (says "file not
found"). Everything else is working OK so far, but I'm a bit concerned.
What can I do (short of formatting) to get rid of them?
Also, I'm ashamed to say, I've forgotten the boot procedure that lets you
choose which partitions you want mounted. I thought it was booting with
one mouse button down, but that isn't working. Can anyone help me out?
Thanks!
Chris,
You say this is the s directory? If so, it's probably assigned as
S: so here's the trick to fixing things:
1. cd to the root of the drive
2. makedir TEMP
3. cd S
4. copy the files you want from s into :temp
5. assign S: :TEMP
6. cd back to the root
7. DELETE :S ALL
8. mkdir :S
9. copy :temp :s all
10. assign S: :S
11. delete :temp all
That should fix things up for you.
The 1.3 vs 2.0 boot MUST be a COLD boot, it doesn't work on a warm
boot. Yes, the mouse buttons must be held down when you power it up.
Don
Don,
Thanks for the reply. I actually did pretty much what you told me
already. The problem I'm having now is that the system won't let me delete
two of the files in the old s directory; when I try, ADOS says "directory
structure corrupt", and SID 1.06 says "object not found". Apparently the
files aren't there, but the directory entries still are. These files, by
the way, are two TxEd backup files, both named, appropriately enough,
"TxEd.Backup". The system won't let me delete, move, rename, or in any way
manipulate those files (or "non-files").
The second part of my question was not how to get 1.3 vs. 2.0, but how
to get the OTHER boot option screen, which lets you choose which partitions
will be mounted, regardless of which OS is running. Do you know how to get
that? I could have sworn it was booting with ONE button down; I'm sure
that worked with the beta 4 release. But since that was undocumented,
maybe beta 5 took it away. Any insight on this?
— CJC —
Chris,
No idea on the boot setup. I haven't played enough with a 3000 so
know all the in's and out's of it.
On those files…I've got a few ideas, but it'd require playing
with the directory structure with a disk sector editor.
Don
Don,
I figured I'd end up with a sector editor, but wanted to be sure I'd
covered all the bases. Can you recommend a good one?
— CJC —
Chris,
I haven't tried any sector editors on the latest release of FFS
(which is what the 3000 runs with). Normally, I use SEC to fix header
blocks and the like.
What I'd do is look in both the directory header block, and it's
hash extension block for entries that hashed to that filename. I'd look at
those file headers and see what names are really on the files.
If they're both the same, I'd use the editor to change the name of
one of them slightly, hash the new name, and move the pointer in the
directory block to the new offset.
Don
Don,
Since I broke out in a cold sweat as I read your last message, I think
I'll just reformat that partition. 😉 If I get up enough nerve to mess
around with the directory structure, I may be back to you on this for some
guidance. Right now, though, I'm fellin' pretty cowardly.
Thanks again for the advice!
— CJC —
I recommend chucking SID … I don't work on a 3000.. I think alot of
programs like SID ansd SuperView will have directory errors.. probably
because of the way the do BPTR clearing in a 32-bit environment or
something gross like that
SID has behaved reasonably well on my 3000. With the exception, that is of
floppy disk access – which it won't do; the system crashes as soon as you
try to access any floppy volume. For that reason alone, I've pretty much
stopped using it. Can you recommend something similar which you think
would be safer on a 3000?
— CJC —
I've gon back to using PP&G's CliMate, which actually sucks. DUDE works,
but is a bit overblown..I haven't tried newer PP&S dir utils or any of the
other PD ones.
Chris,
I had the same problem with a customers A3K (two files in s: with the
same name)… I ended up re-formatting. Let me know if someone tells you
what happened and how to fix it.
Re: booting into wb_2.x: or wb_1.3:, hold down BOTH buttons from a cold
boot.
-John
John,
Temporarily I've creaed a new s directory, moved everything but the bad
files to it, and renamed the old directory until I can figure out how to
get rid of it. The files in question are TxEd backup files; maybe TxEd and
2.0 aren't as friendly as they first appeared?
The other problem was not how to get the 1.3/2.0 option screen, but how
to get the "which volumes to mount" option screen. As I mentioned to Don,
in beta 4, a cold or warm boot with one button down got the volumes
selector; perhaps that's gone away in beta 5. If so, too bad; that was a
nice, if infrequently used, feature.
— CJC —
Chris,
Ah… I'd never seen that "which volume to mount screen", sorry for
the bad advice. re: the bad files in s:… the one I had to deal with was
startup-sequence. Sounds like you've got a good work around going, but, If
you don't have too much customization going right now… you may want to
get the re-format over with. It's not very painful when all you're doing
is re-copying system files.
-John
John,
Yeah, I imagine I'll probably do the format pretty soon – just being
stubborn!
— CJC —
Chris,
BTW, which versions of KickStart/WorkBench are you running?
-John
The problem is under ADOS 2.0 beta 5. The 1.3 side of things is working
without a hitch.
— CJC —
WARM boot with BOTH mouse buttons held down Chris. Hope that is where you
are trying to get to.
Yup, that's it. Of course, now two more questions arise…
1) Can you get that screen from a 1.3 warm boot? I can only get it from
2.0.
2) Are all volumes available (i.e., Work:, WB_2.x:, AND WB_1.3:), or only
Work: and the current OS's partition?
— CJC —
Glad that was the sequence you were looking for. No, warm boot will not
allow you to change dos versions. There is supposed to be a software
program ,KICKRE.LZH, that will allow dos changes on the fly, but it doesn't
work for me going from 2.0 to 1.3. It will allow me to go the other way on
the fly though. I don't know if the program is bad, if I installed it
wrong or if my version of kickstart and dos are incompatible with the
program. I have version 34.5 ks and 34.32 wb (dos 2.3) and vesions 36.141
ks and 36.68 wb (dos 3.0). What are your versions?
As far as I can tell you can only access the version of dos you are running
in. i.e. if you are booted in 2.0 you can access only wb_2x etc.
I've been playing with KICKRE.LZH, and it's working fine for me both ways.
It basically mimics a cold boot, so if you want to go from 2.0 to 1.3, you
need to run Reboot (or choose the menu selection, if you used KickMenu),
and then immediately hold down both mouse buttons. If no buttons, it'll
bring you to 2.0 every time. The only problem I had was that I had to set
the Wait statement in my startup-sequence to 4, instead of the 3 the
documentation recommends. My versions are 34.5 and 34.28 (1.3), and 36.65
and 36.10 (2.0). It looks like you've got a slightly more recent WB 2.0;
does your Clock work right? Mine initially opens OK, but the two digital
modes don't behave right; Digital 2 is bigger than it's supposed to be, and
Digital 1 just doesn't look right. A small matter, but I used to keep
Digital 1 in the menu bar all the time, and now it doesn't fit.
By the way, I think you missed part of my last question. Can you get to
that volume-selection screen from a warm boot in 1.3? It only works for me
in 2.0.
— CJC —
I'll try extending the wait time a couple seconds and see if that is the
problem. I get a lemon yellow screen and the system hard boot loops for
ever every time I try to REBOOT from 2.0. I haven't noticed if I can warm
start into the volume selection screen or not, from 1.3, I'll check that
out too. Yes I have a problem with my clock! My software clock runs at
+290.33 % realtime. The damn thing really cooks! I haven't found anyone
yet that can help me with it. The hardware clock is fine, a setclock load
loads the software clock with the proper time but from that second on it
runs in triple time. I haven't looked at the digital 1 and 2 programs yet,
I'll check them out.
Dan,
The fast clock sounds like an 8520 problem, or perhaps the signal that
clocks it (tick).
-larry
Larry: Good to hear, now I have two of you that have the same fix for my
problem. DOn Curtis was kind enough to answer my plea too.
Chris, I just read several message back that only the dos partition you are
booted in mounts, you could edit the mountlist and startup-sequence of dos
to include the other version, I suspect.
Yeah, I never thought of that. That should work, I guess. I'm really
persuing this issue not out of need, but because I had accidentally come
across that screen quite a while ago, and then couldn't remember how to get
to it again. I was afraid something evil was going on in my machine!
— CJC —
John,
Read my reply (or give me a call) on how to fix it….it should
work.
Don