FXDDR@ALASKA.BITNET (01/09/88)
I would like to know if somebody can explain this one. I was copying C to the hard disk (3 single sided disks). The first disk gave me the "data on drive A may be corrupted" message. Trial and error turned up 3 files on it that wouldn't copy. The rest of the files and the other two disks copied okay. Two of the "corrupted" files were text, so I double clicked on them to see what was salvageable...and got the whole file. The third, a program, wouldn't load. So I fired up Disk Doctor and checked the directory and FAT (including the duplicate). All okay, and no bad sectors in the files. At this point I turned everything off and rebooted without the hard disk or any desk accessories and tried to copy the files to another floppy. Still got the "data on drive A may be corrupted." I tried the disk in B: drive...same error. Tried various copying utilities...no go. So I cranked up my floppy version of C and wrote some copyer programs. The open function didn't like the files, so I went to Rwabs and used the FAT to trace the file. Reading the file by cluster bombed with status -1 (general error...thank you DRI). I put in a gets(str) before the Rwabs so I could step through...still bombed. Finally, I had it read sector by sector with a gets() before each Rwabs, and it worked! So now I've got all the files copied, but I'd like to know why they had to be read a sector at a time with pauses. It makes me wonder how many other corrupted files I might have been able to save if I'd worked at it a bit more... Don Rice FXDDR@ALASKA.bitnet =================== Imagine the amateurs in Minnesota and North Dakota arguing over which is colder...when it's springtime in Alaska, it's 40 below!