From:	jdashiel AT eagle1 DOT eaglenet DOT com
Date:	Fri, 14 Mar 1997 04:10:02 -0500 (EST)
To:	opendos AT mail DOT tacoma DOT net
Subject:	[opendos] floppy disk problem details
Message-Id:	<Pine.NXT.3.95.970314040143.12234A-100000@eagle1>
Mime-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

I decided to test opendos a bit when I ran into another of the
i/o errors on my 1.44 mb drive with floppy disks.
This drive is also hooked up to a colorado jumbo cms250
tape drive, so that may have something to do with it.
No hardware detection package beyond what was written by colorado memory
systems
itself has ever been able to detect my tape drive.
The test I did came about because of the way things happened.
I check the first disk and all is fine.
I check the second disk and get i/o error.
I figure at this point if I put the first disk that was fine
before back into my floppy drive and check that disk the error
will clear.
WRONG!  I put the first disk back in the drive twice once after an abort
and
being told invalid drive and the second time after a fail and being given
invalid drive message.
The i/o error stays there even with the first disk put back in the drive.
Have to reboot or power down to clear it.
Since the disks in question weren't missing serial numbers or labels and
in fact were two of the opendos installation disks with their
write protect tabs in read/only mode, this was a bit surprising.



jude <jdashiel AT eagle1 DOT eaglenet DOT com>

- Raw text -