Validrive report test date and time

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


New member
Sep 25, 2020
I've noticed that the report shows a 'test date and time' which appears to be when the user clicked to acknowledge the end of a test run, rather than be either the 'start of' or 'end of' a test run. A small thing, but slightly annoying, as I often leave a USB stick test running and walk away or leave it overnight. It would be nice to know when it finished.
  • Like
Reactions: CSPea
Sounds like a bug to me. I always assumed "test date and time" was when the test finished, but I never verified that until now.

I started a test at 18:35, and it finished at 18:37. I clicked "Close" at 18:39. "test date and time" shows 18:39.


I have multiple drives that take a long time to run. One even takes so long that "total write time" becomes "=overflowed=". I think it took around 1.5 hours.