home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!agate!doc.ic.ac.uk!uknet!brunel!ccusbdm
- From: Brian.Milner@brunel.ac.uk (Brian D Milner)
- Newsgroups: comp.os.ms-windows.setup
- Subject: Help! Bizarre System Error!
- Message-ID: <Bzr9oL.Iz@brunel.ac.uk>
- Date: 24 Dec 92 08:45:57 GMT
- Organization: Brunel University, West London, UK
- Lines: 30
-
-
- This is for the second time of asking. The first time I used the subject
- line: System Error Blues, so maybe it was too cryptic and no-one read it.
- This time I'll call it "Help! Bizarre System Error."
-
- The Details - Standard Windows installation runs OK, until PC is
- attached to the network. Then the message comes up:
-
- System Error
- Cannot Read From Drive J.
-
- That is to say, boot PC, launch windows: Windows runs OK.
- But boot PC, *attach to network*, launch windows: System error.
-
- I'm using a standard PC-NFS v4.0a attachment that had worked with
- many other PCs just fine. Windows doesn't need to access drive J. when
- launching, so why does it complain? MS Helpline say reinstall windows, but
- I've done that and the results are identical.
-
- It used to say "Cannot Read From Drive H." until I changed
- "Set temp=h:\" to "set temp=c:\" in the autoexec.bat. I've tried changing
- the lastdrive=j line in config.sys to lastdrive=z, with no result.
-
- Any clues, anyone? Any miracle answers? Puullleessee?
-
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- |Brian Milner, The Computer Centre, Brunel University , West London, UK |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- |brian.milner@brunel.ac.uk | Failed films #27 - The Sound of Mucus |
- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-