CompuServe Thread

Daniel – there are basicly two ways in which using BlitzDisk increases your risk of getting damaged files on a disk. First is when used with programs which access the disk in non-standard ways, such as some HD backup programs. BlitzDisk is designed to work and has been tested with the AmigaDOS filesystem handlers (the original filesystem and FastFileSystem); any program which goes direct to the device which uses the same conventions as the filesystems should work with BlitzDisk, but unless a non-standard-access program has been thoroughly tested and found to be compatible there is some risk. The second added risk is with memory corruption due to buggy programs. BlitzDisk buffers are stored in RAM, hence if another application is buggy and zaps random memory locations there's a pretty good chance that the zapped location will be in a cached buffer, which means the next time that buffer is accessed the data will be corrupt – and the failure will appear to be in BlitzDisk, whereas it is actually in the buggy application. My opinion is that you'll get this kind of risk using any cache program, on any computer … most would not choose to state the risks as explicitly, but I prefer to let the user know what the risks are so they can choose either not to use the cache, or to make sure they have backup up their work and to turn off caching when using backup programs, disk optimizers, etc. Regarding the JANUS drive, lots of people have reported good results using BlitzDisk on the HD which supports the BridgeBoard drive. Though it is possible the corruption occured due to BlitzDisk, my guess is it is more likely the problem you've described was caused by a crash during an update to the JANUS drive. I'm not an expert on the BridgeBoard so you'll probably get a better idea of what likely failures are and how to fix them elsewhere- …cheath