To: andy kelly who wrote (1476 ) 5/24/1998 11:10:00 AM From: Spots Read Replies (2) | Respond to of 32871
Andy In Win 3.1 there are three components of memory important to windows known as graphical, user, and main (or if not main something similar -- it's been years since I used 3.11 regularly). You can see a metered display by running sysmeter.exe, which should be in your windows directory. It will put up a little bar graph of your current allocations. Of these three, graphical and user are fixed size (128k if I remember correctly), and main represents the virtual memory available on your machine. Virtual memory is real memory plus the swap file. Most Win 3.11 problems are caused by a shortage of graphical memory, because that is a scarce, fixed resource. However, in you case it sounds like a main memory problem. As Brad said earlier (I think it was Brad), earlier versions of both Netscape and IE had notorious memory leaks, which is a way of saying they allocate memory then forget about it, so rather than reusing it they allocate more. Sooner or later, they allocate all the real memory available, so windows begins SWAPPING the real memory into the virtual memory swap file. At this point, many memory accesses are turned into a disk access, your hard disk goes crazy, and everything returns to a crawl. This is called THRASHING. Sound familiar? Unfortunately, Win 3.11 is very stupid about memory allocation. If a program allocates memory and fails to deallocate it, Win 3.11 usually CANNOT deallocate the memory when the program terminates. When that happens, your only choice is to restart windows (you don't actually have to reboot, but you do have to exit windows to DOS then restart windows). You can tell if this is going on by watching the sysmeter display. If the third bar on the graph gets shorter and shorter, you are gradually using up main memory. If this is your problem you can postpone it but not fix it by adding more real memory (adding more virtual memory by increasing the swap file won't help because thrashing begins when you actively allocate more memory than you have real memory available). The best advice posted here is first, and quickest, upgrade to the latest browser version. Second, upgrade to Win 95. Win 95 CAN deallocate memory when a program leaves it allocated on termination. Usually. Anyhow, it's a heck of a lot better than Win 3.11 (which couldn't do it at all). When you upgrade to Win 95 (or Win 98) you probably want to add more real memory anyhow, but that's another issue. Good luck, Spots