SI
SI
discoversearch

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 )
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Spots who wrote (1007)6/2/1998 8:33:00 PM
From: Dave Hanson  Read Replies (1) of 14778
 
Really helpful answer, Spots. Once again, you and Networm make my life easier. :) I had forgotten that virtual memory was displayed in a seperate column, and not included by default. And I'd neglected to figure out what the "commit charge" meant at all.

(Task manager sure is a nice little tool, by the way. I love the ability to monitor and even kill rouge programs or processes.)

Now it does look like the memory amounts are adding up.

Were I running a system with more than 64 megs cachable RAM (TX chipset), I would have upgraded by now. But I understand that NT loads from the top of the memory down, and hence I'd take a substantial performance hit if I entered the non-cachable range of memory. So I'm seeing if I can "scrimp" by with 64 megs without it affecting performance much. I think that if I can get the observed leaks fixed, I'll be in good shape.

Thanks again,

Dave
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News