Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!uunet!bellcore!att!att!mcdchg!tellab5!vpnet!louisg
From: louisg@vpnet.chi.il.us (Louis Giliberto)
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Re: Flakey disk drive
Message-ID: <1991Jan30.211503.7013@vpnet.chi.il.us>
Date: 30 Jan 91 21:15:03 GMT
References: <942@bozo.megatek.uucp>
Distribution: usa
Organization: Vpnet Public Access
Lines: 22

If you're having the same problem I had, it has to do with how the program
you're using makes DOS calls.  

My problem was that often when installing commercial software, I would have to  put in the next disk.  When I did this, the install program wouldn't be able
to recognize the fact that I put the correct disk in.  (In fact, this 
happened with the ToolBox promo included with Windows 3).  Well, I couldn't
figure it out, and then one day it happened from the DOS prompt.  I had
switched disks in the A: drive, and DOS kept asking me to insert the disk
I had just taken out.  Bingo.  These programs do something funky that you can't
do with PC-DOS 4.0 (I dunno about MS-DOS).  What I think happens is that they
don't close open files correctly.

It never happened to me with the hard drive, so I would copy the files into
a temp dir on the HD, and install it from that temp dir to the dir I wanted
them in.  I also had to keep my data files on the HD.

I don't know if this is BIOS or DOS, but I noticed that no one who has
lower than DOS 4.0 has this problem.  If you have an older version of DOS,
try that.  It doesn't sound like a hardware problem, but I don't know what
you mean by "can't wake it up."

Louis