#CrossDos/WB2.1/Problem
9 messages in this thread
Have you checked to see if you can actually boot from floppy (to ensure
that there is not a problem with the drive itself – I know it is far out,
but stranger coincidences have happened). Assuming that this is not the
problem, what is the content of the PC0: icon? Mine has the following
lines at the start:
FileSystem = L:CrossDOSFileSystem
Device = mfm.device
Unit = 0
Flags = 1
You should ensure that yours are similar and that you have the following
files:
L:CrossDOSFileSystem
devs:mfm.device
Without those I could see some problems. Check the versions on those
files also.
The floppy works OK without CrossDOS, so I'm sure there is not a floppy
problem,
even I'm able to read MS-DOS Diskettes with MSH without problems.
The version of L:CrossDOSFileSystem and devs:mfm.device are the ones that came
with the AmigaDOS Ver. 2.1 that I recently buy. I do not know how to check wich
version they are, but are the originals that came with the system.
You can use the version command on the two files to see what it says.
Mine are 38.7 (mfm.device) and 38.16 (l:crossdosfilesystem) with sizes of
6740 and 26420 respectively.
3:24PM L:> version CrossDOSFileSystem
CrossDOSFileSystem 38.9
3:24PM L:> version devs:mfm.device
devs:mfm.device 38.5
Daniel,
That's what I'm using with WB2.1
Christopher
Christopher,
those check with my versions ala WB2.1. Have you checked to make sure
your mountlist does not refer to the floppies using one of the public
domain ibm handlers?
Brian
Brian,
CrossDOS works fine for me. I posted my versions of the files for someone else
to see. Never had any problem with CrossDOS with 2.1 or when I had it on WB
1.3.
Chris
Chris,
ah, misdirected post. <sigh>
Brian
Christopher,
-> version devs:mfm.device
That command never comes back on my system. In fact, version rarely does.
I just wind up with a hung shell.
Things that make you go, "Hmmmm….."
Malcolm
Malcolm,
I would seriously consider doing the upgrade to WB2.1 from scratch.
This sounds like the situation I ran into once on another Amiga where a
couple of DOS/WB versions were intermixed.
Another possibility is that some older version of AmigaDOS is in your
path, so check that as well.
I did try to duplicate your problem by using older forms of version,
but they worked fine here. Perhaps a bad library?
Brian