R
Rick Langston
This behavior just started happening today, and it is very strange.
Certain programs, either invoked via an MS-DOS command line, or via a
desktop icon, will start running as
per an entry in Task Manager, but will not get any CPU slice and will not
show up in the taskbar nor will
any window for the execution appear.
After seeing this odd behavior, and knowing that I had a bunch of Windows
updates that needed to be applied,
I ran all the updates. Unfortunately the behavior persisted after I
rebooted. (I should note that it took a long
time, something like 10 minutes, for my personal settings to be loaded after
rebooting).
As an example of the problem... I have the front-end software called Dazzle
installed. It's used to run
the Endicia software for printing pre-paid postage labels. There is an icon
on my desktop for Dazzle.
If I doubleclick it, then look in Task Manager, I can see that DAZZLE.EXE is
running. But the user interface
never shows up. DAZZLE.EXE got some initial memory and page faults, but it's
getting no CPU time.
No other process is hogging the CPU. Interestingly, I can occasionally get
DAZZLE to come up if
I go to the proper directory for it in an MSDOS shell and invoke DAZZLE that
way. But that isn't
always successful either.
I can watch for a while in Task Manager. DAZZLE may get a tiny bit of CPU
once, and the beginnings
of a window will come up, and via the Applications tab of Task Manager I see
that DAZZLE.EXE is
"not responding".
It's appearing to me that certain executables have their priority set so low
that they can't execute.
As mentioned before, this behavior only started happening today. I don't
recall doing anything that would
have made this behavior start, nor downloading anything suspicious either.
Do this characteristics sound at all familiar?
Certain programs, either invoked via an MS-DOS command line, or via a
desktop icon, will start running as
per an entry in Task Manager, but will not get any CPU slice and will not
show up in the taskbar nor will
any window for the execution appear.
After seeing this odd behavior, and knowing that I had a bunch of Windows
updates that needed to be applied,
I ran all the updates. Unfortunately the behavior persisted after I
rebooted. (I should note that it took a long
time, something like 10 minutes, for my personal settings to be loaded after
rebooting).
As an example of the problem... I have the front-end software called Dazzle
installed. It's used to run
the Endicia software for printing pre-paid postage labels. There is an icon
on my desktop for Dazzle.
If I doubleclick it, then look in Task Manager, I can see that DAZZLE.EXE is
running. But the user interface
never shows up. DAZZLE.EXE got some initial memory and page faults, but it's
getting no CPU time.
No other process is hogging the CPU. Interestingly, I can occasionally get
DAZZLE to come up if
I go to the proper directory for it in an MSDOS shell and invoke DAZZLE that
way. But that isn't
always successful either.
I can watch for a while in Task Manager. DAZZLE may get a tiny bit of CPU
once, and the beginnings
of a window will come up, and via the Applications tab of Task Manager I see
that DAZZLE.EXE is
"not responding".
It's appearing to me that certain executables have their priority set so low
that they can't execute.
As mentioned before, this behavior only started happening today. I don't
recall doing anything that would
have made this behavior start, nor downloading anything suspicious either.
Do this characteristics sound at all familiar?