Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!usc!randvax!cave
From: cave@randvax.UUCP (Jonathan Cave)
Newsgroups: comp.windows.ms
Subject: Re: <None>
Message-ID: <2907@randvax.UUCP>
Date: 28 Feb 91 17:44:35 GMT
References: <2606.27c462bf@incstar.uucp>
Reply-To: cave@randvax.UUCP (Jonathan Cave)
Organization: RAND Corp., Santa Monica, Ca.
Lines: 18

In article <2606.27c462bf@incstar.uucp> noyce@incstar.uucp writes:
>Just a general question - It appears that if you work in Win 3.0 for
>a long time, doing multiple document open/close, either in Excel 2.1d
>or Word 4 Windows, that eventually, memory gets so fragmented, that
>Win 3.0 appears to 'run out' of memory.  At this point,  I have found
>that the only way to re-coupe this memory, is to exit Win 3.0 to the
>C:> prompt, then re-enter Windows.

I have a large Excel model that runs SAS jobs on ethernetted Unix boxes.
When the rcp's and rsh's required to upload the scripts to the Unix box
and run the SAS job are executed after a long session, I sometimes get
bounced with an "Insufficient Memory to start application" error.
However, if I simply rerun that macro, it works just fine. Given the
sophistication (low) of some of the ultimate users, this is more than
a minor annoyance.  Esay fixes, like running a memory compacter, create
more problems than they solve (e.g. UAEs).  For now, I have an on.error
workaround, but I still wish I could have my memory back when I need it.
Of course, the memory checkers always show plenty available:-)