-
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.)
It sounds too easy?
I presume if you make one of each, you can copy the EFI files from the UEFI device to the legacy one.
This is Steve's first attempt at this. It needs more development
before it is ready to become an essential component of SpinRite 7.Run it as a Windows utility to create a dual bootable USB that - in theory - will boot in either a UEFI or a BIOS /CSM environment.
My understanding is that UEFI booting does not work very well. I do not have a UEFI booting system to experiment with.
I have observed that BIOS/CSM booting works, and displays the proper message on the screen, but then always leaves the machine locked up.
Tip: Use a 32 GB (or larger?) USB flash drive for best results.
It's been awhile, Dan... but I suspect this was by design. My only goal was to "get there" -- but after that “my work there was done.” We as know, the December 2022 date was driven by the total and permanent end of RTOS-32 licensing at the end of that month. So I needed to quickly verify that I was willing (or not) to spent $34,000 on its source code.I have observed that BIOS/CSM booting works, and displays the proper message on the screen, but then always leaves the machine locked up.
Right! As a "proof of concept" it was successful. It just needed more work, which was not appropriate at that time. That time will come, and this concept will become a thing of robust beauty!
Of that I have no doubt!