Zippy SystemWorks ...
I have SystemWorks too.
The rescue disk stuff tries to get your system back if some of the 'key' files are damaged. The process requires two things: your system must be able to boot and you must have good copies of the required files.
Floppy based rescue...
One floppy disk is bootable and holds some files useful for doing repair work on your system. To boot, Windows requires many more files than will fit onto a floppy; hence, the floppy boots to DOS, and from within DOS, can control your system. Once running under DOS, you have the tools available to repair or replace damaged Windows files. These files are found on the second and third floppy you made as part of your rescue 'set' with SystemWorks.
Zip based rescue ...
The process is the same except that a Zip disk will hold much more than a floppy; hence, only one disk is needed. Where it gets messy is if you have a system (like mine) where the Zip drive is exchangeable with the floppy drive. I cannot boot from Zip, and if I boot from floppy, my Zip is not connected; therefor, I must use the three disk floppy rescue.
My rescue set is like my fire insurance, it's available, but I've been fortunate enough to have never needed to use it. My impression is that no matter what set you use, you'll be booting to DOS to fix things. After repairing your system, Windows should run.
You can check to see if your Zip contains data using Windows Explorer. Just click on the Zip drive in the left pane and see if anything shows up in the right pane. If so, you can delete what you don't want.
The 'taping over' analogy is partially OK. If you write a file to a disk and there is already a file on that disk with the same name as the file you're writing, the 'old' file will be overwritten by the new file. If the new file's name is unique, it will be added to the disk. Some software issue a warning and ask permission before overwriting, most don't.
Hope this helps, PW.
|
