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

SD Card and Spinrite




Apologies for my ignorance, but from following Spinrite information over the years it is my understanding that Spinrite 6 (which I have) cannot access SD cards via USB card readers.

That said, I have a 16gig micro SD card with a strange problem that might be of interest to someone here.

The card has zero value to me, so I am either going to trash it or I will mail it to anyone who might want to look at the problem.

The card is a 16gig micro SD used in a game camera, formatted fat32, and is about 75% full with around 16,000 jpegs.

Using file explorer to delete files and folders appears to work (no error messages) but, when the SD card is re-inserted all original folders and files are sill there.

Both quick and full formatting options in Win10 & Win8.1 complete without errors, but, again, when the card is re-inserted, all original folders and files are sill there.

Same with Chkdsk using /F & /R options

Anyone interested in looking at the card? If so, give me a snailmail address and it's yours, no return necessary ...I would be interested in knowing the "why" if there.

fwiw, life and old age has me swamped at the moment and I don't have time to pursue this on my own.

Beverly Howard





I will take a guess that this is an older card, and the erase is failed on the cells, so the card cannot erase the blocks to write new data. The reason the format and delete work is because Windows caches the data for the directory, using it instead of the card content to minimise reads to the card. Thus the delete and such appears to work, as the card does not return an error for the write failing most probably, and thus the cached data is the visible one. Remove and reinsert, and you get the original data, though I will guess that some of the blocks of data have very likely been overwritten in the process of the erase voltage multiplier failing, so you will get parts of the images erased, but the FAT and the backup copy could not get erased.

There format appearing to work is that the quick format only writes a new FAT and backup, and then does a quick sanity check using the reported size to see if the reported matches actual, by reading the last block and getting a valid read. Same with full format, the write does not work but the valid data from reading each block is there, no checksum error so format assumes valid, and thus pass, with the new FAT in cache appearing to be valid, but not being written.