On 4/24/2012 5:09 AM, Francois Labreque wrote:

>
>
>> Oddly, I tried both an older DOS disk, and to run a disk diagnostic disk
>> that I think belongs to the drive itself. The first one showed:
>>
>> Unable to find command processor, for example, C:\Command.com, press
>> enter to try again, or reboot the machine.
>>
>> A>
>>
>> The diagnostic disk did the same thing, only with C> on it. Why this
>> would happen, unless it was somehow trying to look at the HDD for it, is
>> beyond me. Very odd....
>
> your autoexec.bat sets the COMSPEC variable to point to a copy of
> command.com on the C: drive. This is usefull for software that unload
> command.com from memory to get an additional 40K of usable ram, they
> need to know where to get it back when they're done.
>
> If you have access to an editor, remove the "SET COMSPEC=" line from the
> autoexec.bat and reboot. If not, rename autoexec.bat
>
> This should allow you to run fdisk /mbr from the floppy.
>
Hmm. Except, both disks this happens with are "intended" to run stand 
alone, not against a known OS. Or, they shouldn't anyway. Will have to 
check that, but I can't imagine it doing that. :p

Post a reply to this message