ingoldsby@calgary.UUCP (04/03/87)
I seem to recall someone else complaining about the fact that the 80 Track
device descriptor causes problems with the CC3Disk driver. I am also
experiencing difficulties.
A disk may be formatted using the 80 track double sided descriptor. The
first DIR (or CHD or whatever) seems to work OK. After reading or writing
to the disk once or twice, the whole thing goes off the deep end and
Error #244 (read errors) are generated. Does anyone (ahem Microware)
know what is going on?
Terry Ingoldsby
ihnp4!alberta!calgary!ingoldsbyjimomura@lsuc.UUCP (04/09/87)
As yet, I've had a lot of suggested solutions to the 96 tpi problem
but nothing has worked as yet. So far I've found that if you use 80 tracks
single sided everything is fine. I have heard that if you use 40 track
double sided, likewise everything is fine (I've never tried it myself).
However, if you use 80 tracks double sided, then things go wrong. I have
not yet been able to make a double sided 80 track system disk. In fact,
I've pretty much given up for now. I'm going to wait for the SDisk patch
and try SDisk.
My best guess is that data space allocated by CC3Disk is insufficient
for 80 track usage and something is getting overwritten by a FAT entry.
That's assuming CC3Disk copies the FAT into memory to speed up disk access.
I've heard that D.P. Johnson is going to try to have the SDisk patch
ready for the Chicago Rainbowfest, so after this weekend I should have SDisk
up. I'm unhappy about CC3Disk in one other respect anyway: if you don't
have a drive attached to use a descriptor number (I have /d0, /d1 and /d2
descriptors loaded but often do not have a /d1 or /d2 drive) the system
locks with the drives running. Not fun that.
Cheers! -- Jim O.
--
Jim Omura, 2A King George's Drive, Toronto, (416) 652-3880
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomura