solved it myself, Re: system nearly absolutely frozen
- From: "bloozman" <bloozman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 25 Sep 2005 12:21:02 -0700
Just in case anyone else can profit from this situation, I will give the
post-script. I ran dell diagnostics utility on my machine to see if there
was a more serious hardware problem. That turned up nothing, so I went back
to my 2nd fundamental operating principle when dealing with microsoft
software/operating systems. I should have done it sooner, but my Dell
machine is five years old and has had a lot of use, so I believed it was a
worthwhile test.
Microsoft OS Operating Principles
1) When in doubt reboot
2) When still in doubt reinstall :)
This will get you through probably 90% of your problems, in my experience.
Upon painfully clicking through my semi-frozen windows, I managed after 20
minutes to get the Windows 2000 CD reinstall executable to finally fire off a
working thread.
After another 20 minutes I was home free. Now I am just finishing up
reinstalling SP4. The rest of this stuff was a wild goose chase. -- Bloozman
"Dave Patrick" wrote:
> When you view the logged events in Event Viewer (double-click them in the
> right-hand pane) in the upper right corner, third button down is a copy to
> clipboard, then you can paste in the body of a reply message.
>
> Please do so for each of the different System Log events (that are a Type:
> 'Error' or 'Warning') since last boot so we can see all of the event detail.
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "bloozman" wrote:
> |I deduced what you meant by setting files to Overwrite as needed in the
> Event
> | Viewer under the Action tab which finally came up. I followed your
> | instructions for the temporary reboot to the letter. The Event Viewer
> System
> | Log is now showing some Warnings, Errors and Information. Most of it
> looks
> | harmless. The failure of the "boot-start drivers failed to load: SMPLSCSI
> "
> | might mean something. I am listing them all below:
> |
> | System Log Warnings, Errors and Information:
> |
> | Error: Source: Service Control Manager: The Remote Access Connection
> Manager
> | service depends on the Telephony service which failed to start because of
> the
> | following error: No attempts to start the service have been made since the
> | last boot.
> |
> | Warning: Source Srv: The C: disk it at or near capacity. You may need to
> | delete some files.
> |
> | Error: Source DCOM: The server {1BE1F766-5536-11D1-B726-00C04FB926AF} did
> | not register with DCOM wihin the required timeout
> |
> | Error: Source Service Control Manager: The following boot-start drivers
> | failed to load: SMPLSCSI
> |
> | Error: The System Nofification service depends on the COM+ Event System
> | service which failed to start because of the following error: No attempts
> to
> | start the service have been made since the last boot.
> |
> | Information: The Event service was started
> |
> | Information: Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 4
> | Uniprocessor Free
> |
> | Error: the hpdj service depends on the Print Spooler service which failed
> to
> | start because of the following error: No attempts to start the service
> have
> | been made since the last boot.
> |
> |
> | "bloozman" wrote:
> |
> | > I am sorry Mr. PatricK, I don't know which file properties you are
> referring
> | > to, to set to "Overwrite as needed? Where? Do you mean all of the
> system
> | > files? Nothing in Event Viewer allowed such a change, right-clicking or
> | > otherwise. Of course, there were no error files in there to alter the
> | > properties of.
> | >
> | > I am attempting the rest of the temporary fix. I was able to set the
> | > "Startup Type:" to "Disabled". Oddly, the machine upon my return seemed
> a bit
> | > more responsive at first -- at least prior to the current reboot in
> process.
> | > Now it seems back to the slow motion mode.
> | >
> | > I also checked the link you left for the more permanent fix. There was
> no
> | > downloadable executable hotfix attached. the main point of the page
> | > indicated to call Microsoft via phone. Are you really asking me to call
> | > Microsoft and ask for someon to send me the hotfix? It has been my
> | > experience that no one at Microsoft ever returns a phone call from a
> | > consumer. Experts like you in the forum are our only hope.
> | >
> | > There were a few links to "articles" for additional information which
> led to
> | > more links to "articles" for additional information essentially
> regarding new
> | > file naming schema for Windows Software Update Packages.
> | >
> | > Is there a link directly to a downloadable hotfix executable, a patch or
> | > service pack update of some kind that would fix the corrupt Event Viewer
> Logs?
> | >
> | > I very much appreciate your assistance.
>
>
>
.
- References:
- Re: system nearly absolutely frozen
- From: Dave Patrick
- Re: system nearly absolutely frozen
- From: Dave Patrick
- Re: system nearly absolutely frozen: more insight from Event Viewer
- From: bloozman
- Re: system nearly absolutely frozen: more insight from Event Viewer
- From: Dave Patrick
- Re: system nearly absolutely frozen
- Prev by Date: Re: Chkdsk screen hangs
- Next by Date: Re: Control Panel Problem
- Previous by thread: Re: system nearly absolutely frozen: more insight from Event Viewer
- Next by thread: Re: run tightVNC after booting?
- Index(es):
Relevant Pages
|
