Sits and Waits 2

[RAK]

shutting down windows 95 and sits at the screen &quot;please wait while windows shuts down&quot; then when you reboot it runs through scandisk.&nbsp;&nbsp;Is there a way to correct this problem?<br><br>I have tried to get to the safe mode but machine never shuts down and reboots to the option.

 

[theripper]

RAK- (the sitting and waiting prepares you for Win98)&nbsp;&nbsp;<br><br>There can be many variables to make your system do this.&nbsp;&nbsp;Sometimes it's the network card and/or client not releasing resources, other times it's a particular software (like antivirus) that makes this happen.&nbsp;&nbsp;And, sometimes it's a combination of everything.<br><br>Troubleshooting this is an art.&nbsp;&nbsp;And there are many types of artists out there, with many different approaches to this issue.&nbsp;&nbsp;One of the most common is to close as many programs as possible, before shutting down.&nbsp;&nbsp;Ctrl+Alt+Delete to see everything that's loaded.&nbsp;&nbsp;Start shutting them down.<br><br>Another good technique [[I picked up in this forum]] is to log off the network, then shutdown.&nbsp;&nbsp;This works quite well with many novell clients.<br><br>Another type of art is &quot;reverse engineering bootology&quot; or, when was the last time you were successful at shutting down, and what has changed since?&nbsp;&nbsp;Software?&nbsp;&nbsp;Printers? Etc....&nbsp;&nbsp;Many times it's the last item you changed/installed.&nbsp;&nbsp;Uninstalling can be a big help in these cases.<br><br>Hope this gives you a good place to start.

 

[jmartin]

What version of W95 do you have? If this is Release `C` (2.5 , with IE4 bundled) this is problem. I have the same scenary with this release & I resolved applying a patch called `SP IE402` , I imagine this patch is somewhere at Microsoft site, I found this in TechNet CD`s. If you have W95 OSR2.0 (or B) the cause is another.<br>Try!

 

[tomw]

I agree with theripper...there are lots of approaches, and this can happen in W98 too, so it;s not just a W95 problem.<br><br>When It happens to me, it's usually from a program that did not release resources, although I frequently find &quot;connections to my computer&quot; (I run lots of shared folders for co-workers) that were not &quot;released&quot; although the remote user saw no indication they were still &quot;connected&quot;.<br><br>Like theripper said...it is a process to find the culprit, but be prepared to find more than one culprit.&nbsp;&nbsp;The more activity you have on your machine, the more varied the software you run, and the amount of network activity could all be part of the problem on any given day. <p>Tom Whitehead<br><a href=mailto:twhitehead@commeq.com>twhitehead@commeq.com</a><br><a href= > </a><br>

 

[Alt255]

I agree with the previous posts... with an extention: often, the service processes fail to shut down on request. My experience holds that if you put the children to bed, the mother will soon follow.<br><br>The service processes are invulnerable to CTRL+ALT+DEL. But they aren't invulnerable to the power switch. <p> <br><a href=mailto: > </a><br><a href=

http://www.vorpalcom.com>A

plain black box</a><br>

 

[Alt255]

PS. One of my jobs was to create an app that would live after Windows shutdown. Not that RAK has the same problem but he may want to check the Run and RunServiceProcess entries in his registry. Some apps refuse to give up without a fight. They make it hard for Windows to quit. <p> <br><a href=mailto: > </a><br><a href=

http://www.vorpalcom.com>A

plain black box</a><br>