🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: bit.listserv.labmgr
Article #854

Can a DOS PC boot without COMMAND.COM? -Reply

#854
From: Brandon Winbush
Date: Fri, 02 Feb 1996 00:00
47 lines
2754 bytes
----------------------------Original message----------------------------
I am not a DOS God, but I have witnessed similar things.  A correct
version of the command.com is required on the computer,  The newer
versions of DOS are smart enough to check in the OS directory if it can
not find it in the directory specified by shell=.

Command.com is needed.  I do not like the new feeature, when it locates
command.com.  There are also a couple of ther system files that the
computer needs.  There physicla location in the computer's FAT table
are very important.  If DOS does not find them there, your computer is
toast.

>>> Sylvia Schwartz <sylvias@saturn.caps.maine.edu> 01/11/96
10:18pm >>>
----------------------------Original message----------------------------
This is not a problem, just a mystery that has been bothering me.

Recently on powering on one of our lab computers, I saw a message
"Bad or missing command interpreter". It's a familiar message in public
computer labs: COMMAND.COM had been erased or corrupted. I was
walking away to grab a back-up disk when I realized that the computer
was continuing to boot up normally. But how???

I checked to make sure that COMMAND.COM was really missing, and
typed
DIR/AH to make sure it hadn't been given the "hidden" attribute. There
was a copy of COMMAND.COM in the DOS directory, but CONFIG.SYS
had a shell command specifying that COMMAND.COM was to be found
in the root directory.

When I restored COMMAND.COM to the root directory by copying it from
\DOS, the computer booted without the error message, but I was able to
reproduce the situation for the benefit of a skeptical colleague by
deleting it again.

The computer is a Gateway 486DX-33 running DOS 6.0. It has a
network connection and Windows, but is set to boot in stand-alone
mode to the C: prompt.

Can anyone tell me how this PC was able to recover from what (in my
previous experience) ought to be a fatal error? Thanks.


Sylvia Schwartz                     sylvias@saturn.caps.maine.edu
Director, Academic Computer Center
Westbrook College
Portland, Maine
Technical Details
Message-ID: <s110bebe.014@wpgate.shs.ilstu.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fc881,852139b8beb15522,start
X-Google-Attributes: gidfc881,public
From: Brandon Winbush <BKWINBU@wpgate.shs.ilstu.edu>
Subject: Can a DOS PC boot without COMMAND.COM? -Reply
Date: 1996/02/02
Message-ID: <s110bebe.014@wpgate.shs.ilstu.edu>
X-Deja-AN: 137970769
sender: Computer Lab Managers <LABMGR@UKCC.UKY.EDU>
comments: ********************************************************
approved-by: List Moderator <LSTOWN@UKCC.UKY.EDU>
newsgroups: bit.listserv.labmgr
resent-subject: Can a DOS PC boot without COMMAND.COM? -Reply
x-mailer: MailBook 95.01.000