mwizard@eecs.cs.pdx.edu (Craig Nelson) (03/03/91)
OK, programmers, I need help, and I need it fast. Win 3.0 just crashed on me about 20 minutes ago. I have a 40 page report due in about 36 hours and it's written in Word for windows. I don't turn in that report and I'm screwed. I don't graduate Symptoms: Like to tell you but there aren't many. I type "win" like always, the blue windows intro screen pops up, the hard disk spins for a few seconds, then I get thrown into textmode, it spins for anther couple of seconds and I am greeted with the same C:\WINDOWS> prompt I started with. no hour glass, no Programm Manager, nothing. Need help and need it quick. PS> Don't tell me to reinstall windows, my system disk is being replaced already due to i'ts crash. MS is sending me a new one. Craig (mwizard@eecs.ee.pdx.edu) Mail me and I might call you , no matter where you are. I'm desperate.
cadsi@ccad.uiowa.edu (CADSI) (03/04/91)
From article <1846@pdxgate.UUCP>, by mwizard@eecs.cs.pdx.edu (Craig Nelson): > > > OK, programmers, I need help, and I need it fast. Win 3.0 just > crashed on me about 20 minutes ago. I have a 40 page report due in about > 36 hours and it's written in Word for windows. I don't turn in that report > and I'm screwed. I don't graduate > My few suggestions: 1) if you are trying 386 enhanced mode, cut the size of your disk cache for a time. If its smartdrive, take it out. see if windows will boot then. 2) If you use QEMM, use himem instead for a test. QEMM is a little (ok, real) quirky. 3) If you are trying Standard mode, try the same things. I've seen Windows do just those things when not enough extended memory is available. 4) Last but not least, you 'could' start renaming some of .grp files to see if they are creating problems. Windows is easily confused when confronted with icky .grp files. 5) try reinstalling your video drivers. 6) try real mode (after removing himem.sys and disk caches and all other tsr's).