ltf@killer.DALLAS.TX.US (Lance Franklin) (11/12/88)
In article <16869@agate.BERKELEY.EDU> c60a-2bn@web-2d.berkeley.edu (Lawrence Y. Chiu) writes: > >Of course, the program must be able to back up to a different disk, since it >makes no sense to back up to the same disk. If the FAT on that disk becomes >corrupted, chances are, the backup will also be affected. >Lawrence Y. Chiu; University of California, Berkeley. Not necessarily, Lawrence...a disaster that destroys the FAT (which is at the low end of the disk) is not likely to also take out a file at the very top end of the disk, where the FAT backup would be...however, since the FAT backup is given a filename, it should be possible to copy the file to a second disk every so often, and have an option on the restore program to take the file from another source, rather than the fixed sector locations on the bunged disk. Another option might be to allow the user to specify a second disk to write the FAT/Dir backup file to, either at the fixed location (useful if you have two drives...send C's backup to D and D's to C) or just as another file (on the theory that both disks probably won't be bunged at the same time, and the alternate drive's file system will remain usable...personally, I wouldn't want to take the chance, especially if the cause might be a destructive virus or the sort). Lance -- +-------------------------+ +-----------------------------------------------+ | Lance T Franklin | | I never said that! It must be some kind of a | | ltf@killer.DALLAS.TX.US | | forgery...I gotta change that password again. | +-------------------------+ +-----------------------------------------------+