home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.apps
- Path: sparky!uunet!rei2!fox
- From: fox@rei.com (Fuzzy Fox)
- Subject: Re: System Error: Cannot Read Drive C
- Message-ID: <1992Dec22.203832.8529@rei.com>
- Date: Tue, 22 Dec 1992 20:38:32 GMT
- References: <105333@bu.edu>
- Organization: Recognition Equipment, Inc.
- Lines: 29
-
- jdr@acs.bu.edu (Jay Rosenbaum) writes:
-
- >I've been running Windows 3.1 for a long time, generally with no problems.
- >I use Stacker, 4DOS/NDOS, all flawlessly...until now.
-
- >Suddenly, the other day, when I tried to pop up a DOS program from
- >within windows, I get the dreaded white box, and it says:
-
- > System Error
- > Cannot Read Drive C:
- > CANCEL RETRY
-
- I get the same problem, except my read error shows up on drive D: (the
- stacked drive) and will not go away until I shut down the whole system.
- Actually, if I CANCEL a few times, the error box will go away, but the
- DOS box will start generating Abort/Retry/Fail messages, of which only
- Abort seems to do anything, but eventually I will just have to shut down
- the system. I run CHKDSK/F and SCHECK/F and no problems are reported on
- any of the disks and volumes.
-
- This only seems to happen when I try to multi-task DOS boxes from within
- Windows. I thought Stacker supported this sort of activity. Actually,
- it usually does, but apparently not always.
-
- --
- #ifdef TRUE | Fuzzy Fox (a.k.a. David DeSimone) fuzzy@netcom.com
- #define TRUE 0 |
- #define FALSE 1 | "You have been recruited by the Star League to defend
- #endif | the Frontier against Xur and the Kodan Armada."
-