MHDD bypasses DOS and BIOS and talks directly from controller to the drive. You eliminate OS/driver issues in this scenario. In windows, there are too many factors to consider to single out a problem. For example, my jmicron controller driver is buggy. They were listing PATA drives as removable storage in windows till just a few weeks ago! It bails out every once in a while and windows test results get screwed. In this scenario, i drop to DOS and test drive fitness from there. Almost all the time problems are not arising from the drive. In fact, I never had any drive fail after running stress tests for a day on it. If it did not fail, or if it was not a defective drive, i do not get problems with it later on [except when i really fiddle with a drive quite a lot].
HDDScan... has some bugs... For example, when chosen READ test, it is supposed to transfer the data through the controller. But it does not. I think it just does verify when READ is chosen.
SOLUTION: Run Victoria for Windows 4.3 for READ tests.
It also does not create proper MHT reports for archival purposes. I was shocked to find the graph for one of my drives was replaced with the current scan. Apparently, it does not include the image in the MHT file but makes a reference to its location in hddscan folder. This is not good. By the time i found this out, i lost many reports. Because after you run the test, the report works fine even if you move it elsewhere. So you think it is done with, and move it and run another drive. Only to find out in the future that none of your graphs are present!
SOLUTION: Open the hddscan report file in IE. Save it as html. Open the html, save as MHT.
thanks for your many advices.
Okay, I will use MHDD in DOS to scan the drives, instead of HDDScan in Windows. In the hddguru forum, I have received the same advice from several posters. Now I have just realized, that this would be particularly useful when you need to scan the boot, primary drive.
I only use "verify" in HDDScan. I didn't know the difference between read and verify. I decided to use "verify" long ago, I don't remember why I guess I tried both and I chose verify as giving more meaningful results. Now, reading your post, I understand that if you choose "verify", then the data is read by the disk, and verified, and you don't get the data, but only the result of the verification made by the disk. And if you choose "read" then the data should be read by the controller, and the program.
Ok, I will try Victoria and the READ test.
Yes, the MHT files lose the images. I noticed it very quickly. I tried to open the mht files in another computer and instead of images, there were little crosses. And, as you say, if I open the mht file in the same PC, then the images are shown, because it finds the image in the HDDScan folder.
What I was doing to keep the result, was simply copying image captures into a text file (.rtf). and I copy the log too (I highlight the slow sector list, copy and paste).
But now I see your technique, and it is better: open the MHT file in IE, and resave it.
I have tried to save it directly in MHT format, and the images are kept. You don't need the extra step of saving in HTML first, unless you really want to keep both formats.