From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0057_01C57900.C3DC4200
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   USER32.DLL is not screwing up.  If there is a memory leak than you =
are likely running out of virtual memory.  A handle leak can also cause =
problems.  You can't create new processes because there is insufficient =
resources to do so.  You get an error mentioning USER32.DLL because = there
is either insufficient resources to load it or for it to = initialize.

   The fix is to increase your page file size, add a new page file, or =
add more RAM.  Well that and to fix the memory and/or handle leak.

Rich

   wrote in message =
news:e09be0.d8b459{at}harborwebs.com...
  Hi...

  I recently posted that I'm having a problem with "initialization of
  USER32.DLL failed" on my NT4 Workstation/SP6.

  I have reason to believe that its Vsoup thats causing the problem. =
Vsoup is a
  multi-threaded Win32 command-line program that leeches Usenet groups =
off the
  net. I think this program "leaks" memory or isn't closing up its =
threads that
  its using.

  I changed the registry setting
  HKEY_LOCAL_MACHINE/System/ControlSet/Control/Windows to add the 512k =
limit on
  the SessionControl variable (as explained on Microsoft's KB site), but =
this
  only makes the problem worse because the "leaking memory" hits the =
512k mark
  and thus crashes my system with that stupid User32.dll error message.

  Is there any way to prevent this problem from happening in the first =
place? I
  really don't want to replace Vsoup because I wrote a =
custom-application in
  order for it to work with the BBS software, but now I'm tempted to =
have to
  start over with some other Usenet program...

  Unless theres a way to fix the user32.dll file from screwing up?

  Any ideas or suggestions or help would be appreciated...

  *Nick*
  Andre Consulting

  --- Renegade v05-19.4 DOS
------=_NextPart_000_0057_01C57900.C3DC4200
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
USER32.DLL is not screwing =
up. =20
If there is a memory leak than you are likely running out of virtual=20
memory.  A handle leak can also cause problems.  You
can't = create new=20
processes because there is insufficient resources to do so.  You = get an=20
error mentioning USER32.DLL because there is either insufficient = resources to=20
load it or for it to initialize.
 
   The fix
is to increase =
your page file=20
size, add a new page file, or add more RAM.  Well that and to fix = the=20
memory and/or handle leak.
Rich
 

  <Nick.Andre{at}harborwebs.com&g=">mailto:Nick.Andre{at}harborwebs.com">Nick.Andre{at}harborwebs.com&g=
t;=20
  wrote in message news:e09be0.d8b459{at}harborwebs.=
com...Hi...I=20
  recently posted that I'm having a problem with "initialization=20
  ofUSER32.DLL failed" on my NT4
Workstation/SP6.I have =
reason to=20
  believe that its Vsoup thats causing the problem. Vsoup is =
amulti-threaded=20
  Win32 command-line program that leeches Usenet groups off thenet. =
I think=20
  this program "leaks" memory or isn't closing up its threads =
thatits=20
  using.I changed the registry=20
  settingHKEY_LOCAL_MACHINE/System/ControlSet/Control/Windows to add =
the=20
  512k limit onthe SessionControl variable (as explained on =
Microsoft's KB=20
  site), but thisonly makes the problem worse because the "leaking =
memory"=20
  hits the 512k markand thus crashes my system with that stupid =
User32.dll=20
  error message.Is there any way to prevent this problem from =
happening=20
  in the first place? Ireally don't want to replace Vsoup because I =
wrote a=20
  custom-application inorder for it to work with the BBS software, =
but now=20
  I'm tempted to have tostart over with some other Usenet=20
  program...Unless theres a way to fix the user32.dll file from =
screwing=20
  up?Any ideas or suggestions or help would be=20
  appreciated...*Nick*Andre
Consulting--- Renegade =
v05-19.4=20
(1:229/426)

------=_NextPart_000_0057_01C57900.C3DC4200--

--- BBBS/NT v4.01 Flag-5