ok,
try double checking your
startups for anything that
points to hp.
it is likely that there is a
startup for it and its being
loaded into memory,
so it may be the reason
why it is showing up as
a process in mem via
the task manager.
another utility you can
use is "process explorer".
with it you will get additional
details about the running processes.
in this particular matter, you
should be able to find the
parent folder for that process
and delete it.
afterwards you can clean
out the registry of those keys
that were orphaned when their
parent folder was deleted.
incidentally, unless you are
running a laptop with proprietary
software that requires to be
started up at boot time,
you really should only have
a few startups and not a dozen
or so.
in particular you would want
an anti virus program starting
up with the system.
all else/other programs can
be started up manually.
gl, keep us aprised.
--
db·´¯`·...¸>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- Microsoft Partner
- @hotmail.com
~~~~~~~~~~"share the nirvana" - dbZen
>
>
"bbxrider" wrote in message news:OUoZJM33KHA.1452@TK2MSFTNGP06.phx.gbl...
> turns out the document viewer is a program listed in the task manager and with the task manager
> you can go directly to the process which turns out to be a hp thing, hpqtra08.exe, so I think
> there should be solution to that, will post when I find it
> good thing, cause there's about 15 start up programs and it would be kinda tedious trying to
> eliminate by trial and error
>
> "db" wrote in message news:43E8F5D7-BE43-4EC2-A558-547392C744C6@microsoft.com...
>> what you might try
>> is a clean boot.
>>
>> click on start>run>msconfig
>>
>> then under the start up
>> tab uncheck/disable any
>> line items that are enabled.
>>
>> you might want to jot down
>> which ones they are.
>>
>> then click apply/save
>> and reboot.
>>
>> if the pop up no longer
>> appears then it was likely
>> the result of a startup.
>>
>> the next step would be
>> to see which one it is.
>>
>> let us know.
>>
>> --
>>
>> db·´¯`·...¸>
>> DatabaseBen, Retired Professional
>> - Systems Analyst
>> - Database Developer
>> - Accountancy
>> - Veteran of the Armed Forces
>> - Microsoft Partner
>> - @hotmail.com
>> ~~~~~~~~~~"share the nirvana" - dbZen
>>
>>>
>>>
>>
>> "bbxrider" wrote in message news:eeg#7wy3KHA.1016@TK2MSFTNGP02.phx.gbl...
>>> thanks, it did not come up in safe mode, but still comes up when booting full mode.
>>> there seems to be some posts about it being an hp image zone problem, I don't
>>> have hp image zone, but do have an hp printer those solutions talk about uninstalling
>>> image zone which of course I don't have
>>>
>>> "db" wrote in message news:O7q$Qdy3KHA.5084@TK2MSFTNGP02.phx.gbl...
>>>> the repair install would
>>>> have replaced any missing
>>>> or corrupted "system" files
>>>> on the hard disk with genuine
>>>> ones from the cd.
>>>>
>>>> so the issue you are having
>>>> must be related to a third party
>>>> program.
>>>>
>>>> what you might want to try
>>>> is to boot into safe mode
>>>> and simply observe if that
>>>> message pops up or not.
>>>>
>>>> however, I am guessing that
>>>> it won't in which case the first
>>>> step to rid yourself of that
>>>> nagging pop up is to initiate
>>>> a clean boot.
>>>>
>>>> --
>>>>
>>>> db·´¯`·...¸>
>>>> DatabaseBen, Retired Professional
>>>> - Systems Analyst
>>>> - Database Developer
>>>> - Accountancy
>>>> - Veteran of the Armed Forces
>>>> - Microsoft Partner
>>>> - @hotmail.com
>>>> ~~~~~~~~~~"share the nirvana" - dbZen
>>>>
>>>>>
>>>>>
>>>>
>>>> "bbxrider" wrote in message news:uULalWy3KHA.4752@TK2MSFTNGP02.phx.gbl...
>>>>> I recently did a install/repair to my xp pro. It worked ok except for I keep getting
>>>>> "insert the 'document viewer' disk" use source 1,
>>>>> there is nothing in the event log about any install errors, I installed the windows install
>>>>> cleanup but to use that you have to know which app to clean up and I can't find/figure
>>>>> out which app win thinks is a problem. The app in question must be held somewhere?
>>>>> otherwise how would the installer get fired?
>>>>> any ideas where this elusive information is?
>>>>> thanks
>>>>> bob
>>>>>
>>>>>
>>>
>>>
>
>
