Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!ucbcad!nike!rutgers!caip!clyde!cbatt!ihnp4!gargoyle!sphinx!cjdb
From: cjdb@sphinx.UChicago.UUCP (Charles Blair)
Newsgroups: net.micro.pc
Subject: Strange PC/AT
Message-ID: <718@sphinx.UChicago.UUCP>
Date: Fri, 17-Oct-86 22:55:11 EDT
Article-I.D.: sphinx.718
Posted: Fri Oct 17 22:55:11 1986
Date-Received: Sat, 18-Oct-86 15:44:39 EDT
Distribution: na
Organization: University of Chicago Library Computer Systems
Lines: 32
Keywords: Boot failure



I have a vintage IBM PC/AT configured as follows: 1-20 Mb Seagate hard
disk, 1-1.2 Mb diskette drive, 1-360 K diskette drive. I regularly boot
from the A drive, since I use the 1.2 Meg floppy for file backups, and
I don't like taking it out to boot the machine. It has an autoexec as
follows: 

c:
autoexec

My C:autoexec.bat does the real configuring of the system. The problem
is this.

I never have a problem cold-booting the machine. However, whenever I
warm boot (because I've written some bad code, or have downloaded some
bad code from the net!), I get the following message with the floppy in
the A drive: bad or missing c:\sys\vdisk.sys <next line> bad or missing
command interpreter.

Now I happen to have a copy of c:command.com on a: (in the root), and
my vdisk.sys can't be bad, because on cold boot I have no problem with
it. If I remove the floppy from the A drive and try Ctrl-Alt-Del again,
I get the message "Boot Failure," after the machine has tried to boot
from c:. I don't really understand this behaviour. Does anyone have any
ideas?

Thanks.

-- 
Charles Blair   			    ..!ihnp4!gargoyle!sphinx!cjdb
The University of Chicago		    lib.cb%chip@UChicago.Bitnet