S
Steve Nielsen
I've had this problem repeatedly on one particular XP Pro PC (Dell
Optiplex GX260). Unfortunately the only information I can get about it
is in the Event Viewer Application log:
"The shell stopped unexpectedly and Explorer.exe was restarted."
No where can I find an information about what actually causes the shell
to stop and there are no coresponing entries in System or Security logs.
Also browsing the network is always extremely slow on this one and I get
frequent "not responding" conditions when opening Word and Excel files
from network shares. We use both MS Networking and Novell using both IPX
and IP, the problems are the same no matter which type share I access.
The PC is a clean install of XP, all hardware tests good. It has the
latest Novell client, the machine is up to date (minus SP2 and
unnecessary/inapplicable non-critical Windows updates), virus and
spyware free. I've applied all the network tweaks Novell reccommends
(network provider order, no unneeded protocols, etc.) to no avail.
Any ideas on how to trouble shoot this is appreciated, in particular how
can I determine exactly WHAT causes the shell to stop?
Thanks,
Steve
Optiplex GX260). Unfortunately the only information I can get about it
is in the Event Viewer Application log:
"The shell stopped unexpectedly and Explorer.exe was restarted."
No where can I find an information about what actually causes the shell
to stop and there are no coresponing entries in System or Security logs.
Also browsing the network is always extremely slow on this one and I get
frequent "not responding" conditions when opening Word and Excel files
from network shares. We use both MS Networking and Novell using both IPX
and IP, the problems are the same no matter which type share I access.
The PC is a clean install of XP, all hardware tests good. It has the
latest Novell client, the machine is up to date (minus SP2 and
unnecessary/inapplicable non-critical Windows updates), virus and
spyware free. I've applied all the network tweaks Novell reccommends
(network provider order, no unneeded protocols, etc.) to no avail.
Any ideas on how to trouble shoot this is appreciated, in particular how
can I determine exactly WHAT causes the shell to stop?
Thanks,
Steve