Out with the old..... [SpinRite]

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


What could possibly go wrong?
Nov 7, 2020
I cannot agree more with Steve's direction to pull the old, backward-compatible code from SR and push 6.x into an area where modern mass storage is the target of the tool. While it is all very interesting and nostalgic, the telemetry, if Steve could pull it, would likely give a clear story as to the targets being rescued by SR.

The main reason for this would actually be those needing the backwards compatibility would be able to use the 6.0 release to achieve their goal and I am sure the speed/performance gains are not as important to them given the drive capacity they are likely running with.

The performance will make SR more of a preventive maintenance tool rather than a tool to try to rescue a drive with this performance 👍
I am positive that SpinRite does not include any telemetry.
As Steve enjoys occasionally discussing on SN, there are ways to use hardware to send messages... maybe SpinRite could be modified to speed up and slow down its drive accesses in specific ways so that it sends out "All your bits are belong to you!" :D (This was meant as humour if that is at all unclear.)
  • Haha
Reactions: Barry Wallis
I am positive that SpinRite does not include any telemetry.
Using a limited form of telemetry wherein drives' Spinrite-obtained statistics are stored locally could be valuable over time. I think that was discussed in these forums or on Security Now! recently.
@Steve With such a large change to SpinRite 6.1 by pulling out all of the code to support legacy technology should you bump the Version number as well... Maybe to ver 7.0... pushing whatever you intended 7.0 to be to 8.0 or maybe follow what many software companies are doing now days by naming the version the year / Q... (SpinRite21Q4).
That would effectively mean that a change would be necessary every quarter I don't think @Steve could keep up to that schedule. No let us leave it the way @Steve put forward in the roadmap.