Yeah, you need to make sure there's a copy of command.com in that
directory before you try rebooting. If it's there, then everything
should work, if it isn't, then you'll get that error.
Probably not needed, but you might want to put a copy of command.com in
the root of the drive too, because that's usually where the system looks
for it if it doesn't have any directives to look elsewhere. If that
works, and the other directory doesn't, it might point to a problem with
the environment you're trying to setup, basically, it would mean your
startup files aren't being read properly (if at all).
On 3/19/2026 12:24 AM, Ray Davison via Freedos-user wrote:
tsiegel--- via Freedos-user wrote:
If you boot from the USB drive, all you need do is run the sys
command, and give it the drive letter of the hd, then remove the usb
thumb drive, and the hd should boot just fine.
sys d:
should do it in your case.
I had done that, and have done it again. It responds "transferred".
First, "Bad or missing Command Interpreter" is an "old friend". It
has been part of my FreeDOS experience, but not lately, because I
have not tried to install FreeDOS lately. Somehow I always got past
that.
The full error line is:
"Bad or missing Command Interpreter: C"\Freedos\BIN\COMMAND.COM
C'\fREEdos\BIN /E"1024 /P=C"\FDAUTO.BAT"
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
