scan disk 2984
Sure. But it vastly more true about MS. Back in the good old days, when computer suppliers actually cared about the customer more than the bottom line, if you had trouble you could call...
David Wade
Hmm. I don't see any option for 'slow areas'. Please tell me where you found this on the web via GOOGLE. i.e. your search arguements and the url for the page where you found this info.
When you are doing a surface scan, I believe that the protocol is 1. Find an unallocated area (sector or possibly whole track) 2. Test it by writing and reading back several special test patterns. Then loop on 3. Read a sector-track and save the contents to the scratch area 4. Read back the saved data and compare with the data on the original area. 5. Write test the original area. 6. Copy back the saved data. And back to 3. If the original area fails the write, read back testing, then the good, recoverable (recovered) data is saved on a good area and the bad spot is marked unuseable. Perhaps by creating or adding it to a love.bad file. So that it is no longer in use by the file system. On some drives there may be hidden bad sector map.
On old IBM drives: 2314, 2319, 3330, 3380 types if the disk checking program found a bad track if would first try to reformat it by shifting the sectors on the track around (left,right) so as to miss the bad spot. If that didn't work then the track was marked bad and an alternate track was buttigned from a reserved pool and renamed to take the place of the bad track. On some older PC floppy drives it was possible to write tracks 'in between' track positions. This was the basis for some copy prevention schemes, and or read protection schemes for games. I remember it for Apple s. I suppose that the drive manufacturers have some hardware & software that allows them to test the whole disk surface before selling the drives. -- Rostyk
Alt Folklore Computers from Newsgroups