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: dpl who wrote (18187)	3/30/2001 8:14:19 AM
From: Nemer	Read Replies (1) \| Respond to of 110631

Hey David ... I'm on a roll ... got a STRONG streak of one going .... with solving pezz's difficulty so I'll give you the answer which popped into my head before I head out to the lumber yard to get some sticks .... "your time line" ===> 1st time -- Windows was "hung" in a loop within itself and/or performing some arduous task of housecleaning/keeping which caused it to be waaaaaaaay slow ..and even could have been in a "Morpheous" (sp)loop from which it couldn't recover .... you got impatient and aborted the load.... 2nd time -- Winddows started in safe mode because that is what it is supposed to do 3rd time -- everything functioned and it ran "hot, straight, and normal" ... The way things have been going in the marketplace, I've contemplated calling you for a job ... got anything available that pays ......say ... errrrr..... maybeeeeee 10% of what you make ?????? you getting any rain? you're welcome to some of mine cause I have a large amount of too much wet ......gggg good to see you and I can't believe this is the first time for Win98 to goof up on you .... hehehehe Nemer

To: dpl who wrote (18187)	3/30/2001 9:19:23 AM
From: tanstfl	Read Replies (1) \| Respond to of 110631

Hi David, In addition to the cause proposed, you are describing the classic symptoms of registry corruption. Windows boots, gets blocked by corruption in the registry; gets rebooted into safe mode and restores a good backup registry; and then boots up normally. Tracking down the cause is the trick. A stray gamma ray or an unusual conflict between device drivers and it goes away until the next weird Windows glitch; probably not for a while. If it recurs consistently, then first try and remember if you're installing a new driver or even software package just before it happens. When the registry is installed from a backup the old driver will be there and you may not even realize it. Often, though, it is a hardware glitch. Bad memory should be the second suspect. However, since memory problems are often intermittent, it can be quite frustrating to track them down. But, the first thing to do is reseat all the hardware, including any socketed chips. Alternate cycles of heating and cooling often create a bad connection that will be hard to isolate because once the system heats up, the contacts expand and become "good" again. Good luck, Steve Edit: It also can be the result of going into the CMOS and changing the BIOS settings beyond the hardware specs. A way to check that is to alternate between default settings, optimum settings, and safe settings. Sometimes doing this will fix a real problem by reducing the stress on a failing component. The price you pay is degraded system performance. Again, only try this if you are consistently having this problem.