Export thread

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

Performance — MB/s better than microseconds




It would be more useful to display the transfer speed in MB/second. Microseconds? Is that for a 1kb read/write or 4GB?
In other words, better to display the performance of the drive rather than the performance of Validrive.





The reason I don't for ValiDrive v1.x is that ValiDrive's rapid back and forth switching between reading and writing is actually measuring the drive's worse-case "switching" performance rather than its transfer speed. Writing to NAND flash media requires the generation of a high internal voltage which is used to break through (tunnel electrons) an insulation boundary. And reading requires that voltage to be dumped. The generation of that high voltage takes time (to pump up)... So there's nothing more time consuming than switching back and forth between reading and writing as ValiDrive does. This means that it's really not a fair measure of performance.

Having learned many lessons from this first ValiDrive v1.x release, I plan to take a bit of time once SpinRite v6.1 is published to update it to v2.0, which will (a) run MUCH faster and (b) produce some more useful metrics. (y)




There's quite a few factors affecting write speed and all operations require "charge pumping" and they're usually measured in us (microseconds).
I suspect that ValiDrive v2.0 will teach us quite a lot. (y)