IE 6.0 and NT 4.0 (sp6a)

[Guest]

One of our departments had to upgrade to IE6.0 because a website that they
use made this a requirement. Over half of the members of this dept have Win
NT4.0sp6a installed and when we upgraded them all the NT machines have
problems with IE. The issue really doesn't appear until the user tries to
log off or shut down. If they used IE during the logon session a end task
box will pop up when they log off (or shut down). The file for this end task
is iexplore.exe. You can try to end task but it doesn't work for a several
minutes. You can also leave it alone and it will eventually log off (shut
down). Has anyone come across this problem? We can't afford to upgrade the
office, some of the users got their PC's upgraded but the rest aren't
scheduled until at least next year. I've looked around and I haven't found
anything that might lead me to a solutions. I'd be extremely grateful for
any suggestions.

 

[Robert Aldwinckle]

(Cross-post to NT newsgroup added)

One of our departments had to upgrade to IE6.0 because a website that they
use made this a requirement. Over half of the members of this dept have Win
NT4.0sp6a installed and when we upgraded them all the NT machines have
problems with IE. The issue really doesn't appear until the user tries to
log off or shut down. If they used IE during the logon session a end task
box will pop up when they log off (or shut down). The file for this end task
is iexplore.exe. You can try to end task but it doesn't work for a several
minutes. You can also leave it alone and it will eventually log off (shut
down). Has anyone come across this problem? We can't afford to upgrade the
office, some of the users got their PC's upgraded but the rest aren't
scheduled until at least next year. I've looked around and I haven't found
anything that might lead me to a solutions. I'd be extremely grateful for
any suggestions.

Sounds like they are trying to shut down the OS without first closing
their apps? Also, depending on the connection type (e.g. dial-up)
there could be a prompt which would normally occur when the app
is closed. Such a conflict could result in the kind of symptom you
are describing. Also there is a registry zap which is normally used
for such things as making sure a final write of large files gets done
before the task is aborted by shutdown. Perhaps your site has used
such a mod to give an extra long wait for such cases. AFAIK you
can't differentiate between apps with that setting. Unfortunately
I can't remember offhand what the name of the setting is; so I'm
cross-posting to an NT newsgroup hoping that somebody there
knows what I'm talking about. (Hello, Dave? ...<g> )


HTH

Robert Aldwinckle
---