HP Photosmart C8180 wireless problems

[JJustin]

Big frustration with HP PSC 8180 installation to my XP Pro, SP2 system
through wireless router (Linksys), with printer uninstalling itself (disabled
in device manager), loss of inbox drivers, and printer disappearing
completely from Control panel (after reboot). Also huge problem now with
svchost.exe process associated with HPSLPSVC.dll gobbling up 50% of my CPU
constantly.

Attempted partial fixes include updating drivers using the XP universal
driver set instead of the HP drivers from the install CD --- this allows
printer to remain available, but now printing is ridiculously slow, with as
much as 5-10 minute delays to print a one-page text document.

Very little on HPSLPSVC process on the Net knowledge resources. Sleep
Service?? Somehow connected to CUE ... ?? using RUN CMD --> tasklist/svc
together with Task Manager I've been able to be certain that it is this
HPSLPSVC process that is eating up my CPU. Is this normal function? What is
purpose of this process? Is it related to other HP PSC 8180 installation to
XP problems? HP support site has some related info for parallel problems
people have experienced with Vista OS, and some related issues with USB
connectivity, but no fixes for XP wireless installs.

 

[heyray2]

Big frustration with HP PSC 8180 installation to my XP Pro, SP2 system
through wireless router (Linksys), with printer uninstalling itself (disabled
in device manager), loss of inbox drivers, and printer disappearing
completely from Control panel (after reboot). Also huge problem now with
svchost.exe process associated withHPSLPSVC.dll gobbling up 50% of my CPU
constantly.

Attempted partial fixes include updating drivers using the XP universal
driver set instead of the HP drivers from the install CD --- this allows
printer to remain available, but now printing is ridiculously slow, with as
much as 5-10 minute delays to print a one-page text document.

Very little onHPSLPSVCprocess on the Net knowledge resources. Sleep
Service?? Somehow connected to CUE ... ?? using RUN CMD --> tasklist/svc
together with Task Manager I've been able to be certain that it is thisHPSLPSVCprocess that is eating up my CPU. Is this normal function? What is
purpose of this process? Is it related to other HP PSC 8180 installation to
XP problems? HP support site has some related info for parallel problems
people have experienced with Vista OS, and some related issues with USB
connectivity, but no fixes for XP wireless installs.

I am experiencing the same issue with my networked Photosmart C6280.
The "HPSLPSVC" seems to be some sort of network printer discovery
service, which scans your network periodically for compatible
printers.

There are only two "fixes" for the issue I've found so far:

1. Stop and start the "HP Network Devices Support" service, which
lowers the CPU usage for the service to almost zero, until the next
system reboot.
2. Stop the "HP Network Devices Support" service, and set it to
"Manual". This will prevent the service from starting at boot time.

From what I can tell, this service is only needed if your network
printer obtains its IP address dynamically. The service will scan the
network for printers that are not already mapped on your computer and
create a mapping.

I simply just set a static IP on my network printer and set the
service to manual after, that way the CPU usage issue is worked out
and my printer is still available. If I ever make a change to my
printer's IP address, I can simply just start the service again long
enough for the HP software to locate the printer, then stop it again.

I hope this helps!

 

[Dan.Headon]

I am experiencing the same issue with my networked Photosmart C6280.
The "HPSLPSVC" seems to be some sort of network printer discovery
service, which scans your network periodically for compatible
printers.

There are only two "fixes" for the issue I've found so far:

1. Stop and start the "HP Network Devices Support" service, which
lowers the CPU usage for the service to almost zero, until the next
system reboot.
2. Stop the "HP Network Devices Support" service, and set it to
"Manual". This will prevent the service from starting at boot time.

From what I can tell, this service is only needed if your network
printer obtains its IP address dynamically. The service will scan the
network for printers that are not already mapped on your computer and
create a mapping.

I simply just set a static IP on my network printer and set the
service to manual after, that way the CPU usage issue is worked out
and my printer is still available. If I ever make a change to my
printer's IP address, I can simply just start the service again long
enough for the HP software to locate the printer, then stop it again.

I hope this helps!

Can you please explain how to actually perform the 2 fixes you have
suggested? Sorry for being so ignorant.

Dan

 

[heyray2]

Can you please explain how to actually perform the 2 fixes you have
suggested? Sorry for being so ignorant.

Dan- Hide quoted text -

- Show quoted text -

1. Start Menu -> Run
2. Type in "services.msc"
3. Scroll down the list of services for the "HP Network Devices
Support" service, and double-click on it
4. Set "Startup Time" to "Manual"

 

[socman88922]

1. Start Menu -> Run
2. Type in "services.msc"
3. Scroll down the list of services for the "HP Network Devices
Support" service, and double-click on it
4. Set "Startup Time" to "Manual"

Thanks for the tip. I just got a HP D7460, set it up as a fixed
address on my home network and started having very strange things
happening. Static devices on my network were not accessible locally
and through the web, and my desktop's CPU was running at 50%, and I
couldn't access the web through firefox, however I could still ping.
There is definitely a problem with the HP software service "HPSLPSVC"
hogging CPU.

I turned it off: Control Panel->Admin Tools->Services->HP Network
Devices Support(right clicked then properties)->Start Up type->Changed
to "Disabled"

Hopefully HP will pull their heads out with this one.

 

[Richard Nenahlo]

Big frustration with HP PSC 8180 installation to my XP Pro, SP2 system
through wireless router (Linksys), with printer uninstalling itself (disabled
in device manager), loss of inbox drivers, and printer disappearing
completely from Control panel (after reboot).  Also huge problem now with
svchost.exe process associated with HPSLPSVC.dll gobbling up 50% of my CPU
constantly.

Attempted partial fixes include updating drivers using the XP universal
driver set instead of the HP drivers from the install CD --- this allows
printer to remain available, but now printing is ridiculously slow, with as
much as 5-10 minute delays to print a one-page text document.

Very little on HPSLPSVC process on the Net knowledge resources.  Sleep
Service?? Somehow connected to CUE ...  ??  using RUN CMD --> tasklist/svc
together with Task Manager I've been able to be certain that it is this
HPSLPSVC process that is eating up my CPU.  Is this normal function?  What is
purpose of this process?  Is it related to other HP PSC 8180 installation to
XP problems?  HP support site has some related info for parallel problems
people have experienced with Vista OS, and some related issues with USB
connectivity, but no fixes for XP wireless installs.

We had the same problems...plus a few more..on our desktop and laptop
XP Home systems. First, the svchost.exe problem was eating 50% to
100% of CPU. We could never print via wireless from the laptop. We
replaced our Buffalo router with two others but, it didn't help. The
first day, the desktop was able to print some documents but, after a
day or so, we started getting 'HPProgramAssistant' pop-ups that seemed
to be trying to update the installed software. These never
stopped...even if I accepted the updates....and I couldn't use the
computer. Then, my screen actually started to flicker! The Best Buy
"Geek Squad" tech came twice and spent more than 6 hours trying to fix
the problem. Ultimately, he had to give up and we were left with no
other option than to uninstall the software and return the printer for
a full refund...which Best Buy accepted. The tech's opinion was that
the installed software worked but, downloaded "updates" somehow
corrupted that software. I've never been so close to taking a hammer
to a machine in my life.