Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!strath-cs!str-va!cids05
From: cids05@vaxa.strath.ac.uk (@Dr Stephen K Tagg@)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.0 hangs after exit
Message-ID: <1991Jun5.112335.11800@vaxa.strath.ac.uk>
Date: 5 Jun 91 11:23:34 GMT
References: <1991Jun4.001659.609@nntp.hut.fi> <1991Jun4.181923.2809@ux1.cso.uiuc.edu>
Organization: Strathclyde University VAX Cluster
Lines: 26

In article <1991Jun4.181923.2809@ux1.cso.uiuc.edu>, phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN) writes:
> Tapani.Otala@hut.fi (Tapani Otala) writes:
> 
>>Any ideas why Windows 3.0 would consistently hang after exit?
>>After selecting Close in Program Manager, it clears the screen, returns
>>to text mode, and hangs.
>>(there seems to be some problems with this
>>one as it is... could be some incompatibility problem with the 1M memory
>>on the VGA card)
> 
> If you still get the hang with minimal startup and closedown of Windows,
> then perhaps the driver for your VGA is suspect.
I suggest memory management is probably at fault.
On my system I have some nasty memory (a once-a-day SIMM parity error - just
about bearable but I wish I could harden it up to make an engineer able to find
it!) which leads to UAE and similars. Typically I close everything down
successfully but when I get back to dos I get either
1) ERROR memory parity error - only half a line at the top of the screen
or
2) Compaints from QEMM386 5.11 about exception codes - usually then totally
unable to re-boot.

Quite stable within Windows (except for having spotted it with Enhanced mode
UAE) but totally no go when back to DOS.

Best of luck with the detection work....