FreeDOS: Bad or Missing Command Interpreter Error

  • SpinRite v6.1 Release #3
    Guest:
    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.
    /Steve.
  • 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.)

rando

New member
Aug 6, 2023
4
1
Hello Everyone.

This is my first time posting here, so I apologize if there is a more appropriate place to ask this. I am having issues getting Spinrite to boot. I keep getting the following error:

"Bad or missing Command Interpreter: - /P /E:256
Please enter the correct location (for example C:\COMMAND.COM):"

I have tried reinstalling Spinrite on the USB drive, and it says that it installed successfully. Has anyone else ran into this or have any advice on how to fix this?

1691338527702.png
 
Last edited:
How did you make the USB drive? It seems like it's missing COMMAND.COM. You can try using the GRC utility InitDisk ( https://www.grc.com/initdisk.htm ) and supplying the FREEDOS command line option to install a bootable FreeDOS environment on the USB stick. Then just copy your SpinRite.exe onto that disk.

Thanks. I'll give that a shot. I used the SpinRite program to make the USB drive. Is that not the correct way to do it? It seems to be letting me attach screenshots now, so I've added them to this reply.


1691338330315.png

1691338417116.png
 
Well I suspect that should work, BUT SpinRite 6 is from 2003 or so, and PC's have moved on a fair ways since then. Perhaps there's some sort of weird incompatibility you've run into. Certainly SpinRite 6.1 will have newer tech, as it will have the functionality of the utility I linked above (InitDisk) built it. (InitDisk was actually built as a test of that new tech with the intention to include it into SpinRite 6.1.)
 
Well I suspect that should work, BUT SpinRite 6 is from 2003 or so, and PC's have moved on a fair ways since then. Perhaps there's some sort of weird incompatibility you've run into. Certainly SpinRite 6.1 will have newer tech, as it will have the functionality of the utility I linked above (InitDisk) built it. (InitDisk was actually built as a test of that new tech with the intention to include it into SpinRite 6.1.)
Is there a trick to adding the freedos token when using InitDisk? The only thing it will let me type is NUKE.
 
freedos token
You need to invoke it from the command line. Bring up a CMD window, then invoke InitDisk FREEDOS on the command line. (You may need to CD (change directory) to where the InitDisk command is first so it is found in the current directory/path.) You will need to invoke the CMD Window with administrative rights or else you will see the error message I show below. If you need help elevating the CMD prompt, press and release the Windows key on your keyboard, type the letters C M D and then it should look like what I depicted in the attached picture, and click on the highlighted option.
 

Attachments

  • PHolder_2023Aug08_InitDiskFromCommandLine.png
    PHolder_2023Aug08_InitDiskFromCommandLine.png
    10.6 KB · Views: 200
  • PHolder_2023Aug08_HowToElevateACommandPrompt.png
    PHolder_2023Aug08_HowToElevateACommandPrompt.png
    96 KB · Views: 204
You need to invoke it from the command line. Bring up a CMD window, then invoke InitDisk FREEDOS on the command line. (You may need to CD (change directory) to where the InitDisk command is first so it is found in the current directory/path.) You will need to invoke the CMD Window with administrative rights or else you will see the error message I show below. If you need help elevating the CMD prompt, press and release the Windows key on your keyboard, type the letters C M D and then it should look like what I depicted in the attached picture, and click on the highlighted option.
That did the trick. Thank you!
 
  • Done!
Reactions: PHolder