Some data that might help figure this problem out:
This can only be done on XP (or Windows 2000--not Win 98).
Bring up the Windows Task Manager. This can be done with a
right click in the "Task Bar" (which by default is the bar
at the bottom of the screen all the time, but users can
change that). In the menu that pops up from the right click
is a "Task Manager" entry--click it.
One of the tabs in the Task Manager is "Processes". Choose it.
In the "View" Menu is a "Select columns" entry. Choose it.
In the window that comes up, make sure that all these are turned on:
Memory Usage
USER objects
Virtual Memory Size
Handle Count
GDI Objects
When the machine gets stressed (but before you have killed any of the
offending processes) note the values for the various WriteLog processes:
Bandma32.exe
WriteL32.exe
WlogNetDde.exe
I suspect that on at least one of those processes that at usage of
at least one of those system resources is growing without limit.
How it came to be that starting happening now for code written
years ago is a mystery at this time.
Wayne, W5XD
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|