F
FoggyBottom
I have an intermittent problem on one (for sure) or three (maybe)
machines (XP Pro, 'Classic' desktop, no themes or effects) that causes
an occasional and unpredictable unexpected termination of the
"Explorer" process that provides the desktop. It seems to happen when
the machine is busy and startup of another program is requested,
usuallly by clicking a desktop icon. The visible symptoms are that
the desktop is removed down to the wallpaper, all the icons in the
tray disappear, and the task bar disappears. Immediately afterward
the desktop icons reappear in their normal locations, the taskbar
reappears, and a few of the tray icons return. Any executing
processes seem to continue unaffected.
I've been experimenting with what looks like a fix. Priority of the
initial explorer process is set by the system at 'normal'. I've tried
changing it to 'high' on these problematic systems and the problem has
disappeared.
Here's my question: How can I cause the system-spawned Explorer
process to start at boot time at 'high' priority? Yes, I can change
it at will after the fact, but people who don't know how to do this
are using these machines and may occasionally reboot without my
knowledge. I've browsed through the registry looking for a likely
setting, but found nothing. Any help greatly appreciated.
machines (XP Pro, 'Classic' desktop, no themes or effects) that causes
an occasional and unpredictable unexpected termination of the
"Explorer" process that provides the desktop. It seems to happen when
the machine is busy and startup of another program is requested,
usuallly by clicking a desktop icon. The visible symptoms are that
the desktop is removed down to the wallpaper, all the icons in the
tray disappear, and the task bar disappears. Immediately afterward
the desktop icons reappear in their normal locations, the taskbar
reappears, and a few of the tray icons return. Any executing
processes seem to continue unaffected.
I've been experimenting with what looks like a fix. Priority of the
initial explorer process is set by the system at 'normal'. I've tried
changing it to 'high' on these problematic systems and the problem has
disappeared.
Here's my question: How can I cause the system-spawned Explorer
process to start at boot time at 'high' priority? Yes, I can change
it at will after the fact, but people who don't know how to do this
are using these machines and may occasionally reboot without my
knowledge. I've browsed through the registry looking for a likely
setting, but found nothing. Any help greatly appreciated.