Long delay when opening a new window or folder branch

[Xenophile]

WinXP Pro w/SP3. I have searched through the threads and a few problems
resemble this but are not quite the same. What happens often, though not
every time, when I work through a directory tree or when I launch another
program, is that once the window is launched (which happens iquickly n a
normal way). the system effectively seizes up so I can't click on anything or
enter any text. Even the clock stops. I can move the cursor but clicking it
does nothing. By seeing how far the clock jumps ahead when the delay is over
I see that the delay is almost always 30 seconds. The only notable changes
in my system between when it was normal and now are: Installed SP3 and
Installed and ran a registry cleaner (RegCure).
[I posted a few weeks ago but get 2 suggestions and none of them worked]

 

[Leonard Grey]

Does your registry cleaner have an "undo" feature?

If it does - lucky you - "undo" back to before this problem started,
then uninstall your registry cleaner and do not use registry cleaners in
the future.

If it does not have an "undo" you may be up the creek, unless there is
some way of finding out what it did to your computer.

Open Task Manager (CTRL+ALT+DEL) and display the Processes tab. Set the
processes to display in decreasing order of CPU usage. When the problem
appears, make a note of what process is occupying the majority of the
CPU resources. That might be your culprit.

 

[Bill in Co.]

Now wait just a cottin pickin minute here, Leonard. Aren't you forgetting
to consult our resident "expert" Twayne first, before making such a
proclamation?
ROFL! (sorry, I just couldn't resist)

Does your registry cleaner have an "undo" feature?

If it does - lucky you - "undo" back to before this problem started,
then uninstall your registry cleaner and do not use registry cleaners in
the future.

If it does not have an "undo" you may be up the creek, unless there is
some way of finding out what it did to your computer.

Open Task Manager (CTRL+ALT+DEL) and display the Processes tab. Set the
processes to display in decreasing order of CPU usage. When the problem
appears, make a note of what process is occupying the majority of the
CPU resources. That might be your culprit.
---
Leonard Grey
Errare humanum est

WinXP Pro w/SP3. I have searched through the threads and a few problems
resemble this but are not quite the same. What happens often, though not
every time, when I work through a directory tree or when I launch another
program, is that once the window is launched (which happens iquickly n a
normal way). the system effectively seizes up so I can't click on
anything or
enter any text. Even the clock stops. I can move the cursor but
clicking it
does nothing. By seeing how far the clock jumps ahead when the delay is
over
I see that the delay is almost always 30 seconds. The only notable
changes
in my system between when it was normal and now are: Installed SP3 and
Installed and ran a registry cleaner (RegCure).
[I posted a few weeks ago but get 2 suggestions and none of them worked]

 

[Xenophile]

I can't go back to an earlier registry because I have made some changes and I
would like them to stay. As for the programs that seem to be running when I
see the hesitation, th eonly one that is consistently on top in the CPU
useage is jqs.exe, but it seems to be on top nomatter what is running and
even when there is no desitation (although when I am having the 30 second
hesitation I can't even open the Task manager so I rely here on the few times
when it was already running).

Does your registry cleaner have an "undo" feature?

If it does - lucky you - "undo" back to before this problem started,
then uninstall your registry cleaner and do not use registry cleaners in
the future.

If it does not have an "undo" you may be up the creek, unless there is
some way of finding out what it did to your computer.

Open Task Manager (CTRL+ALT+DEL) and display the Processes tab. Set the
processes to display in decreasing order of CPU usage. When the problem
appears, make a note of what process is occupying the majority of the
CPU resources. That might be your culprit.
---
Leonard Grey
Errare humanum est

WinXP Pro w/SP3. I have searched through the threads and a few problems
resemble this but are not quite the same. What happens often, though not
every time, when I work through a directory tree or when I launch another
program, is that once the window is launched (which happens iquickly n a
normal way). the system effectively seizes up so I can't click on anything or
enter any text. Even the clock stops. I can move the cursor but clicking it
does nothing. By seeing how far the clock jumps ahead when the delay is over
I see that the delay is almost always 30 seconds. The only notable changes
in my system between when it was normal and now are: Installed SP3 and
Installed and ran a registry cleaner (RegCure).
[I posted a few weeks ago but get 2 suggestions and none of them worked]

 

[Leonard Grey]

Jqs.exe is Java Quick Starter. This is a feature - I use the term
loosely - that preloads a portion of Java into memory to allow your Java
applications to start faster.

Disable Java Quick Starter and see if that solves your problem. To do
this, go to Control Panel > Java > Advanced tab > Miscellaneous > remove
the check mark from Java Quick Starter.
---
Leonard Grey
Errare humanum est

I can't go back to an earlier registry because I have made some changes and I
would like them to stay. As for the programs that seem to be running when I
see the hesitation, th eonly one that is consistently on top in the CPU
useage is jqs.exe, but it seems to be on top nomatter what is running and
even when there is no desitation (although when I am having the 30 second
hesitation I can't even open the Task manager so I rely here on the few times
when it was already running).

Does your registry cleaner have an "undo" feature?

If it does - lucky you - "undo" back to before this problem started,
then uninstall your registry cleaner and do not use registry cleaners in
the future.

If it does not have an "undo" you may be up the creek, unless there is
some way of finding out what it did to your computer.

Open Task Manager (CTRL+ALT+DEL) and display the Processes tab. Set the
processes to display in decreasing order of CPU usage. When the problem
appears, make a note of what process is occupying the majority of the
CPU resources. That might be your culprit.
---
Leonard Grey
Errare humanum est

WinXP Pro w/SP3. I have searched through the threads and a few problems
resemble this but are not quite the same. What happens often, though not
every time, when I work through a directory tree or when I launch another
program, is that once the window is launched (which happens iquickly n a
normal way). the system effectively seizes up so I can't click on anything or
enter any text. Even the clock stops. I can move the cursor but clicking it
does nothing. By seeing how far the clock jumps ahead when the delay is over
I see that the delay is almost always 30 seconds. The only notable changes
in my system between when it was normal and now are: Installed SP3 and
Installed and ran a registry cleaner (RegCure).
[I posted a few weeks ago but get 2 suggestions and none of them worked]

 

[Xenophile]

I turned off jqs.exe and did not notice any difference so far (it certainly
did not slow down any processes). But I noticed that a process called
hpqPhotoCrm.exe hangs around near the top of my CPU column (in Task Manager).
I can't find a process by that name anywhere in My Programs and I see there
is some concern about it on the web. There are actually 3 hpq* processes
visible just below System Idle Process. HP software was responsible for an
earlier problem I had -- it added an invalid entry to my registry which a
registry cleaning program removed and that in turn caused some of the HP
Image software to fail until I put that entry back (following HP's
instructions -- amazing that they could unblushingly tell me to add the
invalid Registry entry back to it's software in order for it to run).

I'm not sure how to keep hpq* from launching without causing harm to the
current flakey state of the system. Any ideas?

Jqs.exe is Java Quick Starter. This is a feature - I use the term
loosely - that preloads a portion of Java into memory to allow your Java
applications to start faster.

Disable Java Quick Starter and see if that solves your problem. To do
this, go to Control Panel > Java > Advanced tab > Miscellaneous > remove
the check mark from Java Quick Starter.
---
Leonard Grey
Errare humanum est

I can't go back to an earlier registry because I have made some changes and I
would like them to stay. As for the programs that seem to be running when I
see the hesitation, th eonly one that is consistently on top in the CPU
useage is jqs.exe, but it seems to be on top nomatter what is running and
even when there is no desitation (although when I am having the 30 second
hesitation I can't even open the Task manager so I rely here on the few times
when it was already running).

Does your registry cleaner have an "undo" feature?

If it does - lucky you - "undo" back to before this problem started,
then uninstall your registry cleaner and do not use registry cleaners in
the future.

If it does not have an "undo" you may be up the creek, unless there is
some way of finding out what it did to your computer.

Open Task Manager (CTRL+ALT+DEL) and display the Processes tab. Set the
processes to display in decreasing order of CPU usage. When the problem
appears, make a note of what process is occupying the majority of the
CPU resources. That might be your culprit.
---
Leonard Grey
Errare humanum est

Xenophile wrote:
WinXP Pro w/SP3. I have searched through the threads and a few problems
resemble this but are not quite the same. What happens often, though not
every time, when I work through a directory tree or when I launch another
program, is that once the window is launched (which happens iquickly n a
normal way). the system effectively seizes up so I can't click on anything or
enter any text. Even the clock stops. I can move the cursor but clicking it
does nothing. By seeing how far the clock jumps ahead when the delay is over
I see that the delay is almost always 30 seconds. The only notable changes
in my system between when it was normal and now are: Installed SP3 and
Installed and ran a registry cleaner (RegCure).
[I posted a few weeks ago but get 2 suggestions and none of them worked]