#CrossDOS and 2.0 help
16 messages in this thread
I've just installed OS 2.04 and CrossDos no longer works. DI0: is not
recognized. Here is the mountlist I'm going from. Any noticable problems?
Thanks.
* Using: MSDOSFileSystem V4.02a Copyright 1991 Consultron */ DI0:
Device = mfm.device
Unit = 0
Flags = 1 /* Allow 5 1/4" drives */
Surfaces = 2
BlocksPerTrack = 9
Reserved = 1
Interleave = 0 * SecOrg = 1 */
LowCyl = 0; HighCyl = 79 /* 80 track drive */
FileSystem = L:MSDOSFileSystem
Buffers = 5
BufMemType = 0
Stacksize = 4000
Priority = 5
GlobVec = -1
DosType = 0x4D534400
Mount = 1; #
— Art via Amiga Whap!
Well, I just compared it to mine and found 3 differences.
1) I have a / before the * on secOrg in order to comment it out.
2 The # at the end occurs on a new line by itself
3. I have mount = 0 instead of mount = 1.
1 and 2 may be CIS formatting issues, the last one really shouldn't matter.
I would check to be sure that MSDOSFileSystem is in L: as well as
mfm.device is in devs: You might also consider booting from the Consultron
distribution disk to make sure that it still works.
John A. Toebes, VIII – via Whap!
Art,
To confirm what John said in his reply, I checked my mountlist also, and
it matches yours (with the CIS formatting exceptions that John noted).
CrossDOS definitely works on my system under 2.04, so I would suspect that
you've missed copying one of the needed files to either your Devs: or L:
directories.
Good luck!
– BobR
I have MOUNT=1 because I was told it would allow the MS-DOS disk to appear
immediately on the WB without an explicit call to that disk (e.g. a DIR
DI0: command). MOUNT=0 doesn't change matters.
Since disk reformatting is indicated I used the 2.0 install as an
opportunity to rebuild my system from scratch. Much of my c: drawer was PD
hacks to add functionality to 1.3 so I got rid of it all and we'll see as
time goes on what I want to add back. DMouse is already back since I like
its autopoint and WindowToFront operation better than C='s. But I digress.
🙂
Anyway… I popped in my Consultron disk and reinstalled CrossDOS from
scratch so all the files better be there.
I've had some flakiness in the past I attribute to my GVP '030 card. SETCPU
NOFASTROM was required on my system before CrossDOS would work. Doesn't
help now. I see that 2.0 includes a CPU command which I have not tried.
I'll will try booting with the CrossDOS disk. Thanks everyone. — Art
turn off your data cache, too.
Ben
Art:
I'm using Cross-Dos under 2.04 on an A3000 without problems. The only
difference between my mounlist and yours is that you have mount = 1; # and
both my drive (internal 3.5 & external 5.25) are set to mount = 0; #
Hope that helps.
– Whapp!ng from the North Coast Michael
Art,
You have Interleave and secorg on the same line. If your mountlist is
like this then it would not work as you have a "*/" between interleave and
secorg. The secorg value would be ignored. I also have mount =0. I just
used CrossDos on my A2000HD with 2.04 only a few minutes ago. TDPatch13 is
no longer needed with 2.04. Other values look OK. Be sure that mfm.device
is in Devs: and that MSDosFileSystem is in L:.
….Mark 74335,1677
On a related note, I've been wondering about getting an update to
CrossDOS… they have a BBS, right? What's the latest version? They're
still active, I assume they had to update for 2.04 compatability.
The current version is 4.02a. I was on their BBS the other night and it is
there in a few archives depending on the version you are updating from.
Fred
Have you got Consultron's BBS number handy? I'm still at version 3.06.
Must I be validated to grab these updates, or something like that?
I don't have the number handy, but the BBS is on the normal support phone
number after business hours. The number is in the rear of the manual and
no validation is necessary. Unfortunately, you'll have to grab most of the
files they have to get up to 4.02a!
Fred
They didn't have to update – my copy worked 100% first time, nothing
changed at all.
Ben
Never mind – I found that the regular support number is also the BBS, after
hours.
User stupidity error. The first MS-DOS disk in my grasp after I
reinstalled CrossDOS was a high density disk. Like, duh!
All is fine now. Under 1.3 I had to drop back to XDOS v. 4.00 and turn off
FASTROM to get a reasonably stable setup. Now, it seems v. 4.02a is more
stable than before. I have FASTROM and all caches turned on. — Art
Don't sweat it. It was clearly the handling of the MS-DOS disk that
temporarily reduced your IQ to a minus number. Gotta watch that stuff. :^)
Ben
You know, if I just had an Amiga laptop I wouldn't have this problem. -Art