Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Dave Hanson who wrote (999)	6/2/1998 10:21:00 AM
From: Spots	Read Replies (1) \| Respond to of 14778

I can only think of obvious things, but what the heck, maybe there's something. Have you looked at the process list in the task manager to determine what memory is being used? It sounds to me like either a driver or an app running as a service (since it seems pervasive). I have no such problem myself. Did this start recently or has it always been a problem? If recently, what did you do just before that? Update a driver; install an ap with a background component (e.g., PCanywhere runs as a service); install a new device, new scsi card, new sound card etc? Task manager is probably the best starting point.

To: Dave Hanson who wrote (999)	6/2/1998 5:13:00 PM
From: LTBH	Read Replies (1) \| Respond to of 14778

The info was generic, not NT specific. Guess I should also ensure a better understanding. It seems you are describing a memory release problem and perhaps a memory leak problem. In any troubleshooting scenario you have to keep variables as constant as possible, keep good notes and start as simple as possible. For memory release: bring up resource meter or appropriate NT sub, monitor GUI, mem and disk swap. Run one program per boot. Note start numbers for above, run awhile, note any increase in above items, close program and note any changes to items. The program that shows a increase in numbers after use and no decrease after close has a memory release problem. The program that shows and increase after running awhile AND a decrease after close that equals the start point has a memory leak problem. If you use Datek, their connection SW has a mem leak. Closing that connection and then reopening the site will restore. I have never been able to get IE 4.0 to run stable so don't know about it but 3.0 had a leak problem which was corrected in 3.02. Do one program at a time and you should be able to pin it down. Doubt all your SW is at fault. If this tests to be the case then would suspect something about your NT setup and suggest asking the guy familiar with SPOTty problems. Networm