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: thecow who wrote (30510)	11/17/2002 6:13:16 AM
From: thecow	Read Replies (1) \| Respond to of 110653

To the thread: I have been remiss in my hosting duties of late and I'd like to try to correct the oversite. We have had several new participants with questions and suggestions for solving problems lately and I have not greeted them properly. We have a very democratic thread here so please don't be offended if a question posted to me goes unanswered. I often post nothing if I don't have any ideas and rely on the participants of the thread to chime in. No one on the thread has ever voiced displeasure when someone else answers a question directed to them...as it should be. We're all in this to help one another. The volume of posts has picked up recently and I thank all for it. tc :-)

To: thecow who wrote (30510)	11/17/2002 2:26:38 PM
From: mr.mark	Read Replies (1) \| Respond to of 110653

hi tc re, The Troubleshooting Flowchart... maybe excellent, maybe not. it would be neat if several people here put it through its paces, or at least remembered it and turned to it when troubleshooting. might help the group to know this. imo, these flowcharts are limited in scope and in specificity, but the good ones are useful tools, nonetheless. i'm having a situation where some process is churning my hd during boot up, way past the log on point when it used to stop making noise. i'm trying a number of things to identify what may be the cause of this excessive writing to disk, and i turned to the flowchart. it didn't cover the prob i am experiencing. the executable i am looking at right now is LSASS.EXE, which appears to be a rather important system file, acting mainly as an authenticator, to verify user logins. reason my attention has turned to LSASS.EXE is that its mem usage during bootup is 4332k, then when everything settles down (all the churning stops), the mem usage for that process has dropped to 932k. of the approximately three dozen processes running (viewable in task manager), none show a decrease in mem usage during this time span like LSASS.EXE. so i'm focused right there for now. any thoughts from you on this would be welcome, of course. :) mark