>I did check to make sure that the files were on the floppy, but don't >know how to check to see if they are good. I know just enough about >this to be dangerous. I guess there is some good from any bad >situation if we learn from it! >I have attached both zip files from my floppy to an e-mail and have >sent them to Margaret, who is going to try to restore them to an old >FO 6.0 that she has. I am keeping my fingers crossed. I definitely would not give up without a fight. For example: 1. Try to copy the floppy on another computer. Sometimes one floppy drive will read a diskette when another will not. 2. Test the zip file with WINZIP or equivalent. For example, if the bad file is one of the index files (CDX extension), then restore everything but the index files. FO can rebuild them for you. 3. Using WINZIP or equivalent, try restoring one file at a time time. I have had experiences where a restore operation would restore all but one or two files. Doing it again would restore all but one or two files, but it might be a different one or two than the first time. If all but one or two files are good, be persistent and restore just that one or two over and over again until they work. 4. Take your backup floppy out, put a different one in, then put the backup floppy in again, to give the read/write heads a chance to realign slightly (especially useful in combination with #3, for example in the event that your first try restores all the files but one). 5. Turn your computer off overnight, try again first thing in the morning (when floppy drive is still cool -- temperature changes can mess up read/write head alignment). This is also especially useful if you can restore all but one or two files. Try the other one or two again the next morning. 6. Etc. that I haven't thought of yet. Good luck. Jerry Bryan _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail