CompuServe Messages

Hard Disk Crash

    26-Dec-87 00:59:10
Sb: #100045-Hard Disk Crash
Fm: Don Curtis/SYSOP 76703,4321
To: Greg White 72105,1616
Greg, A few ideas…both of which have worked for me during testing: 1. Look for a 0 length file (more than likely, the file you were writting at the time of the crash) and delete it. That may or may not help. 2. Copy the files one at a time until you get a system error on a file and delete that file. Now…I know that #2 sounds like an awful lot of work…depending on how much RAM you have and how your HD is organized…it can be very easy to do. If you have a relatively well organized HD and no huge files on it and at least 1 Meg of RAM, then open a 2nd CLI via the NEWCLI command. In that new CLI, cd to ram: and do likewise in your original CLI. Ok, now from one of the CLI's (it doesn't matter which) type the following: COPY DH0: RAM: ALL This will go thru and attempt to copy the HD into RAM: and create subdirectories as it goes. MAKE NOTE of which directories and subdirectories are being created…it's important! Obviously, soon, you'll get a system requester telling your that ram: is full. Not to worry….go to the other CLI and delete the directores that have already been copied using the DELETE <directory> ALL command. The reason you need to keep track of which directories and/or sub-directories are being copied is that you won't be able to delete the directory that it is presently trying to write to when ram: filled up and the DIR command won't work once RAM: gets full! There is no RAM left for DIR to use to sort. Ok, once you've deleted some directories and/or subdirectories (get as many as you can) then hit the RETRY gadget in the system requester telling your RAM: is full (it's not now). Also click on the CLI window that is doing the copies. As long as you have no individual files that are bigger than RAM can hold…this will work. At some point, you'll come across a file that can't be copied due to the bad extension….that's the file you want to delete. Once you delete that file…and after waiting a reasonable amount of time for the drive to quit doing it's thing….re-boot and the drive should now validate. Don