ReadSpeed Release 1

  • Release Candidate 6
    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.
  • 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!



(as in GRC)
Staff member
Feb 1, 2019
Southern CA, USA
Any problems found with this first release of ReadSpeed will be aggregated here. I'll explain the trouble and our plans for dealing with it.
  • So far <<knock on wood>> when ReadSpeed runs, it has run perfectly. The only trouble anyone has had, has been getting their machines to boot from their prepared ReadSpeed USB stick. The typical reason for trouble is lack of system support for BIOS booting. The move to UEFI is well underway, which explains my change in SpinRite's planned Roadmap. I will make SpinRite v6.1 available to everyone as quickly as possible. Then I'm going to immediately move to support for UEFI and liberation from DOS, which is incompatible with UEFI. This will happen ahead of SpinRite's support for USB and NVMe mass storage, which in planned to immediately follow.

  • [RESOLVED] We've encountered our first problem involving an eSATA (external SATA) where it appears that ReadSpeed's drive discovery was powering down and up the drive, and something became confused. ReadSpeed does manage drive power, since we found that Mac drives need to be explicitly awakened and powered up. So something there hiccupped. @Tig77 did come up with a workaround by waiting to plug the drive in until ReadSpeed was initializing. But I want to see whether I can recreate the conditions and come up with a solution. Here's @Tig77 's posting.
    Shawn (aka @Tig77) used a test release of ReadSpeed which simply increased the spin-up wait time from 2 seconds to 10 seconds, and this completely resolved his trouble. So future releases of ReadSpeed (and SpinRite) will incorporate this more patient solution.

  • Second problem found: No drives found on one system that has two: @LeMic has a machine with two AHCI controllers (Intel and ASMedia) and two drives. ReadSpeed r1 starts up, the ASCII characters in the header spin, but nothing else happens. Michael (@LeMic) has joined the GRC newsgroup and we're working to determine what's going on with his machine.