CrossDOS V4.00
12 messages in this thread
Is anyone having problems with V4.0 of CrossDOS? The V3.07 patch appears to
work okay, but not the V4.0 patch.
Cheers, Paul (WA1OMM)
>Is anyone having problems with V4.0 of CrossDOS?
Yes. The script SEEMED to update my CrossDos disk, but when I tried to use
the resultant mfm.device and MSDOSFileSystem files (manually copied to my
hard drive) I got nothing but errors and "Not a Dos disk in unit X", etc.
I've switched back to V3.06.
I don't know what version I have (I'll check, if anyone wants to know), but
I have gotten some VERY strange results. I put in an MS-DOS disk, open the
CLI and do a DIR DI0:. The directory comes up fine. *Then* I get a
"Workbench Message" (not a "System Message"!) requesting that I insert
volume EMPTY in any drive!
The folks at Consultron believe that the disk must have been formatted for
AmigaDOS at one point (with the default name EMPTY), and that the Workbench
is somehow picking up the EMPTY volume label from the old format.
My wife has Norton Utilities at her office, and she was going to use the
special DOD formating tool, which should wipe the disk superclean. She
hasn't gotten around to it yet, however, so I don't know if it will work.
Chris -)—–
whats new in CrossDOS 4.0?
Nick Murray
>whats new in CrossDOS 4.0?
Well, according to the supplied READ.ME file in the update…
The major feature enhancements for Version 4.00a of CrossDOS are: – faster
floppy data access; improvements to "mfm.device" – AmigaDOS V2.0 compatible
– better error reporting
However, I was unsuccessful in getting my 4.0 upgrade to recognize MS/DOS
disks, so I'm back to 3.06.
I never got any sort of notice for CD 4, but when I need to use CD the old
one works well enough for me.
Ron
I didn't get any notice either, despite being a registered user. Makes me
wonder why I waste my time filling in those cards.
daniel
You cannot use any "noclick" utilities with CROSSDOS V4 except for that
whicjh is part of SETCPU V1.5. It works fine for me now.
Cheers, Paul (WA1OMM)
>You cannot use any "noclick" utilities with CROSSDOS V4 except for that
>which is part of SETCPU V1.5. It works fine for me now.
That may be my problem. I am using a no-click. Since I have four floppies
and neighbors who like to sleep at night, it is a requirement. But you say
that the noclick flag in SETCPU 1.5 _is_ compatible with CrossDos 4.0? If
so, maybe I'll try that combo. I can't give up noclicking, I'd go nuts.
> But you say > that the noclick flag in SETCPU 1.5 _is_ compatible with
CrossDos 4.0?
That is correct.
Cheers, Paul (WA1OMM)
A simple way to keep the drives from clicking is to just put a disk in
them. Simpler and safer than "noclick".
-tc