>Hi:
>
> The strangest thing is happening. Yesterday I started getting out of memory messages while connected. Tracking down the problem I discovered the following:
>
> I open good old System Monitor and "Allocated Memory" shows less than 1 meg.
> I launch DialUp-Networking and instantly "Allocated Memory" shows 60 megs!!!!!!!
>
> I have my swap file configured to 50 megs min and max to cut down on the grow/shrink process.
>
> The machine has 64MB RAM.
>
>Somebody please shed some light on this before I reinstall WIN95, I'm almost done with a 8 month project and can't afford that now.
>
If this is Win95 or Win95a (the retail version, not the OEM version that
contains FAT32), there are known bugs in the original DUN and the update
that shipped in Service Pack 1 that resulted in severe memory bleeds,
especially with multiple invocations of DUN and WinSock. Installing the
latest kernal and DUN patches (available from Microsoft's web site or off
the TechNet CDs) will correct the problem (I'd recommend getting
KRNLUPD.EXE, VTCPUP20.EXE and VIPUP11.EXE from
http://support.microsoft.com/support/downloads/LNP195.asp?PR=CHS&FR=0&M=S&
and installing them in exactly that order; I'd also grab WIN95Y2K.EXE while
I was there, and a more recent Dial Up Networking (I use the one that
installs with IE4.0, Dial-Up Networking v1.2, which includes all the
patches from the ISDN Accelerator Pack and some additional goodies like
MultiLink and scripting extensions if your ISP supports them.)

If you are running OSR2 or OSR2.1, then you already have the Kernal patch,
and should probably reinstall drivers and update your WinSock to version 2.0
if it's an early copy of OSR2.

Ed