AWCTTYPA@UIAMVS.BITNET ("David A. Lyons") (02/03/89)
>Date: Wed, 1 Feb 89 20:12:56 GMT >From: Andy McFadden > <agate!e260-3f.berkeley.edu!labc-3dc@UCBVAX.BERKELEY.EDU> >I was using an older P16 shell under GS/OS when I noticed that >somebody failed to inform GS/OS that I had switched disks. If you >think about it for a minute, you realize that two volumes with the >same name will appear to be the same volume; if you switch them then >GS/OS will use the cached directory. > >I managed to trash a disk in this manner; the directory of the first >disk was written onto the second. I bet you aren't using the device drivers provided: either UNIDISK3.5 or APPLEDISK3.5, as appropriate. Without the UNIDISK3.5 driver, GS/OS can't necessarily tell the difference between two volumes with the same name in a UniDisk. The same _may_ be true of the Apple 3.5 drive, but I'm not sure about that. USE THE DRIVERS! DON'T DISABLE THEM JUST BECAUSE IT MAKES THE FINDER QUIETER! The drivers are provided for a reason. >I've also heard reports of people who update their files, only to >have GS/OS read from the cache. I don't have first-hand experience >of this, but it shouldn't be that hard to test (although logically it >shouldn't happen if the cache was implemented correctly). I don't understand what you mean by "update their files." The only halfway reasonable thing I can think of is, again, failing to use the drivers, and then taking the disk out and modifying it on another machine. In that case, you could bring the disk back and try to read from it, and you'd get something outdated from the cache. >labc-3dc@widow.berkeley.edu (Andy McFadden) >c60c-3aw@widow.berkeley.edu (expiring soon) --David A. Lyons bitnet: awcttypa@uiamvs DAL Systems CompuServe: 72177,3233 P.O. Box 287 GEnie mail: D.LYONS2 North Liberty, IA 52317 AppleLinkPE: Dave Lyons
labc-3dc@e260-3f.berkeley.edu (Andy McFadden) (02/03/89)
In article <8902021325.aa21966@SMOKE.BRL.MIL> AWCTTYPA@UIAMVS.BITNET ("David A. Lyons") writes: >>I managed to trash a disk in this manner; the directory of the first >>disk was written onto the second. > >I bet you aren't using the device drivers provided: either >UNIDISK3.5 or APPLEDISK3.5, as appropriate. Without the UNIDISK3.5 >driver, GS/OS can't necessarily tell the difference between two >volumes with the same name in a UniDisk. The same _may_ be true of >the Apple 3.5 drive, but I'm not sure about that. I have *both* the UniDisk 3.5 and AppleDisk 3.5 drivers installed. Perhaps GS/OS can't tell the difference and is using the wrong one (although I find that hard to believe) or maybe the Universal Drive Controller doesn't resemble a UniDisk closely enough (probably). >--David A. Lyons bitnet: awcttypa@uiamvs > DAL Systems CompuServe: 72177,3233 > P.O. Box 287 GEnie mail: D.LYONS2 > North Liberty, IA 52317 AppleLinkPE: Dave Lyons -- labc-3dc@widow.berkeley.edu (Andy McFadden) c60c-3aw@widow.berkeley.edu (expiring soon)