Guest: We are at a “proposed final” true release candidate with nothing known remaining to be changed or fixed. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum. /Steve.
Be sure to checkout “Tips & Tricks”
Dear Guest Visitor → Once you register and log-in:
This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!
James: During development and testing I built a hashing function into SpinRite. Since it's doing serious work on typically large 16MB buffers, using it slows SpinRite way down. But if you give SpinRite the "hash" term on the command-line it will, when finished, dump a hash to the DOS command prompt.
What I and many others were doing was doing a Level 1 or 2 read pass over some smaller region of the drive with the "hash" parameter to get the "before" hash. Then do whatever you want with a higher level with the hash term, and then confirm that the hashes match. (I should note that as Joep (above) has said, there's really not a lot of point to that since this has already been done extensively during testing and I used it when I was deliberately inducing huge numbers of read and write errors into drives to verify that all of SpinRite's logic was always doing the right thing. We would not be at release candidate stage if it did not always pass that testing! : )