Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!ogicse!ucsd!qualcom.qualcomm.com!qualcom.qualcomm.com!antonio
From: antonio@qualcom.qualcomm.com (Franklin Antonio)
Newsgroups: comp.windows.ms
Subject: Re: WfW cool but wicked buggy... (long)
Message-ID: <1991Jun26.072248.8281@qualcomm.com>
Date: 26 Jun 91 07:22:48 GMT
References: <37000002@inmet>
Sender: news@qualcomm.com
Organization: Qualcomm Inc., San Diego, CA
Lines: 20
Nntp-Posting-Host: qualcom.qualcomm.com

In article <37000002@inmet> newbie@inmet.inmet.com writes:
>Just to add my eight bits to the WfW noise, I have three annoying problems
>...
>1. Low on memory. My system has 4MB with a 4MB swapfile (nearly 5MB free
>with nothing running). With only WfW and ATM running, there is about 4MB
>free, around 62 percent of system resources available. Editing a small
>(less than 20k) document with outlines, tables, index, etc. While editing a 
>table, I tried to define a style. WfW kept telling me I was low on memory.

Yep!  I have 8MB ram, with default swap file.  I often run into the W4W
low on memory problem.  Usually when i try to print, or open another 
file, or sometimes just bring a different document to the front!
This has happened at times when i've had as little as 2 documents of
one page each open, and no other apps running.  I don't know how to cause
this to happen on command, unfortunately.  W4W has memory management bugs.
No two ways about it.

>The only way I could get it to stop was to quit and restart!

Same here.