Xref: utzoo comp.os.msdos.apps:2166 comp.windows.ms:13811
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!qualcom.qualcomm.com!qualcom.qualcomm.com!antonio
From: antonio@qualcom.qualcomm.com (Franklin Antonio)
Newsgroups: comp.os.msdos.apps,comp.windows.ms
Subject: Re: MS-DOS v5.0 Release Date 11th June
Message-ID: <1991Jun15.035442.2411@qualcomm.com>
Date: 15 Jun 91 03:54:42 GMT
References: <72798@microsoft.UUCP> <6669@gssc.UUCP> <1991Jun13.161907.25853@vuse.vanderbilt.edu>
Sender: news@qualcomm.com
Organization: Qualcomm Inc., San Diego, CA
Lines: 31
Nntp-Posting-Host: qualcom.qualcomm.com

In article <1991Jun13.161907.25853@vuse.vanderbilt.edu> jsims@vuse.vanderbilt.edu (J. Robert Sims) writes:
>It wouldn't surprise me one bit if this was the official position.  I
>called tech support because Word for Windows appeared to be grabbing
>more system resources than it should; I had two documents open, and
>couldn't print due to insufficient memory! (With _ample_ available

I have seen this very same symptom.  I have often had two documents open
(sometimes just one page memos), and been unable to switch documents
or print the second document after printing the first.  W4W interacts
with Windows to produce some kind of memory management confusion.  In one
case, i was unable to switch to a 2nd document, even tho the program
manager said i had 1800k mem and 62% of system resources available.
It's pretty obvious that W4W gets Windows confused.

>Tech support told me
>that the resources had disappeared into a black hole; the solution was
>to restart Windows, because Windows does not properly release
>resources when applications are finished.  

I think it's more complicated than that.  I've seen W4W claim there wasn't
enough memory, even when there was, in cases where NO APP HAD EVER TERMINATED
in the present windows session!

>When I asked about an
>update, I was told that "Microsoft doesn't consider this to be a bug,"
>and that I should reboot my machine often to eliminate the problem. 

It's pretty obvious that there are memory management bugs in W4W.
Microsoft has the habit of putting some pretty junior people on the
tech support phone lines.  My theory is that that's how they train
new people.