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 : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Patricia Meaney who wrote (19333)	5/1/2001 3:46:01 PM
From: CatLady	Read Replies (1) \| Respond to of 110652

What else are you running besides DigiChat, Etrade and IE? Adding memory might help, but Win98 just doesn't manage memory resources as well as Win2000.

To: Patricia Meaney who wrote (19333)	5/1/2001 3:50:12 PM
From: Ed Forrest	Respond to of 110652

Patrica This may get you started in learning about resources. 216.230.195.137 Ed

To: Patricia Meaney who wrote (19333)	5/1/2001 3:53:13 PM
From: thecow	Read Replies (1) \| Respond to of 110652

Patricia I doubt if you have a ram shortage problem. Here's a post by PMS addressing ram and 98. Message 15722940 From frequenting the Medved thread that gottfried mentioned earlier today I would think the problem is the streamer and chat running at the same time, not your machine's ram.

To: Patricia Meaney who wrote (19333)	5/1/2001 4:00:49 PM
From: Ed Forrest	Read Replies (1) \| Respond to of 110652

Patrica Here is what noted writer and computer guru Fred Langa has to say about resources and ram. 1) Resource Leaks, Part III In Part One of this series ( winmag.com ), we discussed the how and why of "resource leaks;" what they are, the problems they can cause, and how you can determine if your system is suffering from them: To refresh your memory, resource leaks typically involve two special, fixed-size, internal scratchpad areas of Windows memory; their size is unchangeable, and not related at all to how much RAM your system has. In poorly coded apps, some of this limited, special memory may be used by an app but not released when the app closes---or crashes. Over time, more and more of these limited resources may be marked as "in use" even when they're really not. Eventually, there's not enough space available to continue, and you get an "out of memory" error message (even if you have tons of RAM), or a crash.