I have a suggestion about When I choose "Shut Down" from the Start Menu, my computer hangs at the "Please Wait" screen:

Both my PCs (one WIN95 the other WIN98) now fail to shutdown and hang at the "Please wait" screen. I have resorted to selecting "Restart in MS-DOS" from the shutdown menu. This closes Windoews and displays the DOS prompt. The computer can then be switched off and will happily load Windows when it restarts. A big annoyance is that it doesn't remember the shutdown menu selection for next time. In fact my PCs default to the "log-on as a different user". See http://www4.tpgi.com.au/users/aoaug/ms_dig.html for more comments about Windows.

[Reply or follow-up to this message]

Hi, this error often occurs because of the following reasons: 1. Advanced Power Management (APM) (-> try to shutdown it it's disabled) 2. Missing soundfiles which should be played when shutting down 3. An cram-full temp-directory 4. Local network-connections which are still open. You can try: net use * /delete. This command stops all network-connections 5. Often some programms which are running in the background (firewall, etc.) don't terminate correctly. 6. If it isn't one of these you should take a look at your bootlog.txt! For every terminated driver there must be terminate/endTerminate entry. That means you've got an corrupt driver. Good luck, Marcus.

[Reply or follow-up to this message]

Re my computer not shutting down, Windows Troubleshooter indicates that the problem is in the Bootlog.txt file. namely, the last line Terminate=Win32 is missing. They say that the problem is with a 32-bit program blocking a thread. But they don't tell me how to solve it. Is there a simple answer to my problem? And, forgive my ignorance, but what is a thread?


On Tuesday, May 7, 2002 at 3:42 pm, Marcus wrote:
>Hi,
>this error often occurs because of the following reasons:
>1. Advanced Power Management (APM) (-> try to shutdown it it's disabled)
>2. Missing soundfiles which should be played when shutting down
>3. An cram-full temp-directory
>4. Local network-connections which are still open.
>You can try: net use * /delete. This command stops all network-connections
>5. Often some programms which are running in the background (firewall, etc.) don't
>terminate correctly.
>6. If it isn't one of these you should take a look at your bootlog.txt! For every
>terminated driver there must be terminate/endTerminate entry. That means you've got
>an corrupt driver.
>
>Good luck, Marcus.

[Reply or follow-up to this message]

Hallo, a thread is one of the tasks which are running parallel on Windows. Sometimes this can be only a part of a programm. If such a part doesn't finish, Windows might not be able to terminate the whole programm. But I don't know which win32-application causes your problems. Win32 is just the type, the compiler-model... Maybe you can find some more Infos.

[Reply or follow-up to this message]

John Did you ever get a fix for this as my win98 has stared the same problem? Colin

[Reply or follow-up to this message]

Hi Colin, Computer programs are certainly temperamental, with the emphasis on mental. I downloaded the Microsoft patch a couple of times after switching off my virus control software, and it helped for a while. I also eliminated the Windows shutdown "sound", but wasn't game enough to try adjusting the registry. So, for the moment I'm learning to live with it. The computer may shut down, without having to switch it off, about 3 out of 10 times. So I'm still searching for the ultimate solution. John


On Monday, November 4, 2002 at 1:00 pm, Colin wrote:
>
>John
>
>Did you ever get a fix for this as my win98 has stared the same problem?
>
>Colin

[Reply or follow-up to this message]

One of the things I've found is that AOL can cause this problem because a part of its code becomes corrupt. Specifically, a program CFNDIS that is meant to close the comms CFOS manager of AOL - up to at least version 7.0 - may not terminate and that leaves the message 32 bit program not terminated in the bootlog. I haven't yet found a way round this as AOL don't seem to know whether they use CFOS now or not!! I'll keep you posted. Colin

[Reply or follow-up to this message]

I have the same problem and I solved it by disabling my 32-bit driver. go to control panel, system, performance, file system, troubleshooting, and then put a check on disable all 32-bit drivers.


On Saturday, November 9, 2002 at 2:19 am, Colin wrote:
>One of the things I've found is that AOL can cause this problem because a part of
>its code becomes corrupt. Specifically, a program CFNDIS that is meant to close
>the comms CFOS manager of AOL - up to at least version 7.0 - may not terminate and
>that leaves the message 32 bit program not terminated in the bootlog.
>
>I haven't yet found a way round this as AOL don't seem to know whether they use CFOS
>now or not!! I'll keep you posted.
>
>Colin
>
>

[Reply or follow-up to this message]

please respond, thank you. my Wife and I have h/p windows x/p -----------------------------------------------------------


On Tuesday, May 7, 2002 at 3:28 pm, Michael Paine wrote:
>I have a suggestion about When
>I choose "Shut Down" from the Start Menu, my computer hangs at the "Please Wait"
>screen:

>Both my PCs (one WIN95 the other WIN98) now fail to shutdown and hang at the "Please
>wait" screen. I have resorted to
>selecting "Restart in MS-DOS" from the shutdown menu. This closes Windoews and displays
>the DOS prompt. The computer can then be switched off and will happily load Windows
>when it restarts.
>A big annoyance is that it doesn't remember the shutdown menu selection for next
>time. In fact my PCs default to the "log-on as a different user".
>See
>http://www4.tpgi.com.au/users/aoaug/ms_dig.html
>for more comments about Windows.
>
>

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum