Xref: utzoo comp.sys.ibm.pc.hardware:7455 comp.sys.ibm.pc.misc:8422
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!mcnc!xanth!cs.odu.edu!epperly
From: epperly@cs.odu.edu (William "Badger" Epperly)
Newsgroups: comp.sys.ibm.pc.hardware,comp.sys.ibm.pc.misc
Subject: Re: invalid drive B
Message-ID: <1991Apr9.235059.17885@cs.odu.edu>
Date: 9 Apr 91 23:50:59 GMT
References: <1054@venice.SEDD.TRW.COM>
Sender: usenet@cs.odu.edu (Usenet News Poster)
Reply-To: epperly@cs.odu.edu (William "Badger" Epperly)
Distribution: usa
Organization: Old Dominion University, Norfolk, VA
Lines: 29
Nntp-Posting-Host: drizzle.cs.odu.edu

Hi!  This is my first time posting to this group, although I have
read it many times.
I have a small problem that I am hoping someone can help with.
my machine :
	Austin 386SX
	4 meg ram
	71 meg hd
	5 1/4 1.22
	3 1/2 1.44
	less than 1 yr. old

Problem:
	When I boot the machine, for the first time each day, I sometimes
	get the double 'beep' and a message stating that I have an 
	invalid drive b:.  I am then informed that I should run setup
	and correctly set the values for my b: drive.  The problem is
	that I do have the correct information in the set up routine
	and by tapping f2 esc the machine boots fine.  I don't even have
	to actually enter the configuration routine of setup.  What I
	find interesting is that it is an intermittent problem, i.e. it
	will happen about 5-7 mornings in a row, and then for the next
	couple of days it works fine.  I have even taken the time to 
	log my actions to see if it is something that I am running
	that is causing the problem.  Anyone have any ideas?
	Please email and I will post a summary.
	Thanks.

	William Epperly
	epperly@cs.odu.edu