Closed Pre-Release 5.01

  • SpinRite v6.1 Release #3
    Guest:
    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.
    /Steve.
  • 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!

    /Steve.
  • 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.)

Steve

(as in GRC)
Staff member
Feb 1, 2019
909
1,257
69
Southern CA, USA
www.grc.com
Fixes: “This drive has taken itself OFFLINE and cannot be used”

This improvement to SpinRite will hopefully resolve “false positive” occurrences of those big red “This drive has taken itself OFFLINE and cannot be used” messages. This could still happen, but now it should be much more rare and only when the drive has really dropped offline.

Tests performed over the weekend revealed that for some drives, SpinRite's patient wait of 10 seconds was not long enough. So SpinRite was declaring that a drive had gone offline just before it came back online. I found some drives that needed more than 10 seconds following a reset to get ready to continue. So from now on, SpinRite will wait up to 60 seconds after resetting a drive following an error before it gives up and decides that the drive is never going to return to use.

Since 60 seconds is a Loooooooong time to wait with nothing apparently happening, after SpinRite has waited for just one second, it will now post a "countdown" in the upper left corner of the screen while it's patiently waiting for the drive to come back online:

1703127003651.png
And, since it will be interesting to collect some data and to learn how long such drives take, SpinRite now also tracks the longest time that a drive required to get its act back together and logs that at the end of the activity log.

So... I would very much appreciating having all pre-release SpinRite testers who experienced that pop-up, give the improved “SRPR.EXE” release a test and report (a) whether this resolved the trouble and (b) what you found at the end of the log for the longest drive reset recovery time.

You can obtain this update as before by going to GRC's Pre-Release page, entering your SpinRite license serial number or transaction code and clicking the link to obtain your personal pre-release copy. You'll see that this release identifies itself as “pre-release 5.01”. This is meant to signify that it follows release candidate #5, but that it is not yet another release candidate since I'll be adding additional improvements in the coming days.

Let me/us know whether that solves the trouble you were seeing!

Thanks!