home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!biosci!agate!overload.lbl.gov!lll-winken!isg.llnl.gov!nijhuis
- From: nijhuis@isg.llnl.gov (Jan A. Nijhuis)
- Newsgroups: comp.sys.ibm.pc.hardware
- Subject: Problem with disk changes, drive B
- Message-ID: <141035@lll-winken.LLNL.GOV>
- Date: 9 Nov 92 22:28:51 GMT
- Sender: usenet@lll-winken.LLNL.GOV
- Distribution: usa
- Organization: Lawrence Laboratory Livermore, CA
- Lines: 34
- Nntp-Posting-Host: isg.llnl.gov
-
- Help!
-
- A FAQ, no doubt, but could someone please answer this and post a solution?
- I'm working on a '486 that doesn't recognize disk changes on drive B:
- Drive A is 1.2M, B is 1.44M, C is a SCSI 105M job. While trying to load
- Windows we come across disk change problems. Disk one loads fine, insert
- disk two and it looks at the disk, decides it's not the disk it wants and
- asks for disk two again. Not a problem so far. We copy all the Windows
- disks into their own subdirectories and do a Custom Install. Tell windows
- to look in the individual directories at disk change time. Cool, it works!
-
- When it gets to be time for Windows to load itself (1/3 way thru the
- installation procedure) we get a "Cannot load USER.EXE file." and the
- installation procedure self aborts.
-
- Still, loading from drive B should be possible. What causes the problem
- with the drive when it does not recognize a disk change and what is the
- solution.
-
- Next: Any guesses why installing from individual directories gives us
- the error message and self abort. the Status line looks like it has
- copies USER.EXE over just fine.
-
- Please don't tell me the disks are bad. They are not. I can read them
- just fine in my machine, Norton finds nothing wrong with them and even
- CHKDSK has no problem with them. It is a HARDWARE problem.
-
-
- --
-
- Jan A. Nijhuis,
- nijhuis@isg.llnl.gov
-
- Two wrongs do not make a right, but three will get you back on the freeway.
-