rhuebner@cup.portal.com (Rick Allen Huebner) (11/05/88)
[ Insert cutesy line-eater comment here ] I recently upgraded my A500 to AmigaDos 1.3, C Ltd. SCSI Dos 3.0 w/ controller, and a Seagate ST157N drive. Last night whilst coding, I discovered a problem with Blitzdisk... it seems that files which are written to disk through the Blitzdisk cache get their cache images scrambled together in some strange fashion. Namely, if I edit 3 or 4 files, and then try to compile, the compiler has good odds (it doesn't ALWAYS happen, but pretty often) of seeing one of the files magically transform into another of the saved files in mid line. The file also appears munged when Typed. If I reboot, the file turns out to actually be good on the disk; it was just the cached image that was garbled. Files which are only read, like the compiler or editor, are fine. If I remove Blitzdisk, the problems go away. I suspect that Blitzdisk is being confused by attempting to cache a FFS drive, but if that's so, I would've expected to hear about it by now. Or perhaps it's the Blitzdisk/SCSI Dos 3.0 combination that fails? I dunno. Has anybody else been having any similar strange problems with the Blitzdisk, SCSI Dos 3.0, FFS combo? For the time being, I've been forced to drop back to using (gag) AmigaDos buffers (via the mountlist). This has dropped the read speed of my drive by about 20% from what it used to be using my nice big 256K Blitzdisk cache. Any suggestions/comments, anyone? P.S.: I really doubt it matters, but for those of you who might wish to try and research/duplicate this problem: Blitzdisk 512 also CLtd.device clip 50 nochip 1.5MB ram (maxxed A500 + .5MB Byte Box) C Ltd. controller w/ SCSI Dos 3.0 Seagate ST157N, 2:1 interleave, 6 heads, 26 bpt, cyl 0-607 AmigaDos 1.3, using 48MB Fast File System partition Editing w/ TxEd Plus, compiling w/ Manx 3.6A Drinking Diet Coke B-)