Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!caen!uflorida!eng.ufl.edu!joker.mil.ufl.edu!cp
From: cp@joker.mil.ufl.edu (Costas Papas)
Newsgroups: comp.windows.ms.programmer
Subject: Problem with low resources!!!
Message-ID: <1990Dec7.063627.4820@eng.ufl.edu>
Date: 7 Dec 90 06:36:27 GMT
Sender: news@eng.ufl.edu
Organization: Machine Intelligence Lab, University of Florida
Lines: 21
Originator: cp@joker.mil.ufl.edu

Programming with Windows 3.0 presents many challenges.  We have recently 
come across some

- In our application, after opening around 15 modeless dialog boxes
	(with styles set to ~CS_SAVEBITS) and around 100 small windows 
	(about 15x80 pixels in size, also with ~CS_SAVEBITS), Windows
	starts to not repaint all the screen!  I switch to the Program
	Manager and it shows 650K free memory left (GlobalCompact confirms
	this), but only around 14% of free system resources.
	What does this mean?  Are we creating too many windows?

- A rumor I heard was that I could run Windows 3.0 on my 
	HP Vectra QS/20 with just 2M of memory.  Is this the case?
	Running "win/e" only brings up the system in Standard mode.
	Do I need some particular memory drivers to do this?
		
		
Thanks,
Keith

Please respond to cp@beach.cis.ufl.edu