can not "add an imaging device"

[Todd]

Hi All,

XP Pro SP3

I am trying to repair a customer with an HP Office Jet 5510
multifunction printer/scanner.

The printer and fax seem to be install okay. But scanner
does not show up.

When I go into "Scanners and Cameras" and click on "Add Device",
I get ignored. No pop up.

When I run "setup.exe" from the downloaded (343MB) drivers from
HP, I get ignored.

In device manager, when I scan for new devices, I get a pop up
that tells me "the required section was not found in the inf".
The inf is c:\windows\inf\oem6.inf. I tried renaming it with no
symptom change. I tried removing the "HP PSC and Office jet" driver
from Add Remove programs. Still no symptom change.

I am thinking I am going to have to search through the registry
and scrub out all things office jet.

How would you guys approach this problem?

Many thanks,
-T

 

[Todd]

From: "Todd" <[email protected]>

| Hi All,
|
| XP Pro SP3
|
| I am trying to repair a customer with an HP Office Jet 5510
| multifunction printer/scanner.
|
| The printer and fax seem to be install okay. But scanner
| does not show up.
|
| When I go into "Scanners and Cameras" and click on "Add Device",
| I get ignored. No pop up.
|
| When I run "setup.exe" from the downloaded (343MB) drivers from
| HP, I get ignored.
|
| In device manager, when I scan for new devices, I get a pop up
| that tells me "the required section was not found in the inf".
| The inf is c:\windows\inf\oem6.inf. I tried renaming it with no
| symptom change. I tried removing the "HP PSC and Office jet" driver
| from Add Remove programs. Still no symptom change.
|
| I am thinking I am going to have to search through the registry
| and scrub out all things office jet.
|
| How would you guys approach this problem?
|
| Many thanks,
| -T

The major problem with HP all-in-one devicres is their very intrusive
and overly complicated software.

The only soultion is to completely unistall their bloatware and
reinstall it. Preferably with the latest version available on the HP
website and not from their CD.

http://h10025.www1.hp.com/ewfrf/wc/...=en&cc=us&dlc=en&sw_lang=&product=311255#N191

I did get it from HP's web site

When I run "setup.exe" from the downloaded (343MB) drivers
from HP, ...

The setup.exe from the download just dies.

Do you know of universal HP drivers cleaner that will brute force
an uninstall?

Many thanks,
-T

 

[David H. Lipman]

I did get it from HP's web site

When I run "setup.exe" from the downloaded (343MB) drivers
from HP, ...

The setup.exe from the download just dies.

Do you know of universal HP drivers cleaner that will brute force
an uninstall?

Many thanks,

I wish there was one. There isn't.

Have you closed/killed EVERY program that is running before trying to Uninstall the HP
all-in-one software ?

Have you tried Revo Uninstaller ?

 

[Paul]

I did get it from HP's web site

When I run "setup.exe" from the downloaded (343MB) drivers
from HP, ...

The setup.exe from the download just dies.

Do you know of universal HP drivers cleaner that will brute force
an uninstall?

Many thanks,
-T

Does the installer have a log file ?

I looked in autorun.inf of your 343MB package and I see references to .NET 1.1 .
Do you have that installed ? On my SP3 OEM disc, it appears
to be on the disc (so it should already be there).

To verify dotnet, you can use the verifier tool. It has a
menu of the various versions.

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

The reason I'm thinking of the verifier, is your report is it "just
dies". Maybe if .NET is missing, a missing mscoree.dll report is
being hidden from you by the installer (it ate the error message).

WinXP has a WIA service in Services, and that is Windows Image
Acquisition. That might have some impact on whether scanning works,
depending on the software path. My WIA service is running right
now and is set to Automatic, and I have no image acquisition devices
connected (neither webcam nor scanner).

Another thing that sometimes causes problems, is Windows Installer,
and depending on how ancient a version you've got, that needs updating.
But again, if that were the issue, I'd expect an error message.

http://www.microsoft.com/download/en/details.aspx?id=8483

The "silence" is the strange part here. Maybe an AV program could stop
it, for example. That might be a silent failure, but then the AV should
have logged something (to celebrate how clever it was).

Paul

 

[Todd]

Does the installer have a log file ?

I looked in autorun.inf of your 343MB package and I see references to
.NET 1.1 .
Do you have that installed ? On my SP3 OEM disc, it appears
to be on the disc (so it should already be there).

To verify dotnet, you can use the verifier tool. It has a
menu of the various versions.

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

The reason I'm thinking of the verifier, is your report is it "just
dies". Maybe if .NET is missing, a missing mscoree.dll report is
being hidden from you by the installer (it ate the error message).

WinXP has a WIA service in Services, and that is Windows Image
Acquisition. That might have some impact on whether scanning works,
depending on the software path. My WIA service is running right
now and is set to Automatic, and I have no image acquisition devices
connected (neither webcam nor scanner).

Another thing that sometimes causes problems, is Windows Installer,
and depending on how ancient a version you've got, that needs updating.
But again, if that were the issue, I'd expect an error message.

http://www.microsoft.com/download/en/details.aspx?id=8483

The "silence" is the strange part here. Maybe an AV program could stop
it, for example. That might be a silent failure, but then the AV should
have logged something (to celebrate how clever it was).

Paul

I think it is time for me to run my dot net scrubber and
reinstall what ever missing version gets complained about
by the various programs. Dot net 1.1 is a pain in the
neck. It gets corrupted all the time.

And install the latest installer.

Also, look around for some error logs.

Thank you for the tips!

-T

 

[Todd]

I wish there was one. There isn't.

Have you closed/killed EVERY program that is running before trying to Uninstall the HP
all-in-one software ?
Yes


Have you tried Revo Uninstaller ?

No. I actually carry it with me, but had forgotten I had it.

Thank you!

-T

 

[Char Jackson]

I think it is time for me to run my dot net scrubber and
reinstall what ever missing version gets complained about
by the various programs. Dot net 1.1 is a pain in the
neck. It gets corrupted all the time.

I work on maybe a dozen systems a week and have yet to do my first
dotnet repair. I have no idea why you're seeing it be corrupted all
the time. Are you seeing that with the same set of users over and
over?

 

[Todd]

I work on maybe a dozen systems a week and have yet to do my first
dotnet repair. I have no idea why you're seeing it be corrupted all
the time. Are you seeing that with the same set of users over and
over?

Are we speaking again? I black listed you over on the W7 list.
Seems you do not care for Microsoft being abbreviated M$ and
I do not care for the thought police.

Anyway...

The older the system, the more likely dot net will be corrupted.
Windows does not have a self healing file system, so the older
the more likely things can get corrupted. 1.1 especially jams
with M$ Updates. Once I fix it, it stays fixed.

I also attempt to recover all the user's stuff, so things
like dot net and IE tend to get messed up in the process
and have to be repaired. Better than loosing all the customer's
settings. I wipe and reinstall only in in the most severe cases.

Also, I only see computers when something has gone wrong.

 

[Char Jackson]

Are we speaking again? I black listed you over on the W7 list.
Seems you do not care for Microsoft being abbreviated M$ and
I do not care for the thought police.

Anyway...

Well, at least your attitude is consistent across groups. Consistently
bad, but I digress.

The older the system, the more likely dot net will be corrupted.
Windows does not have a self healing file system, so the older
the more likely things can get corrupted. 1.1 especially jams
with M$ Updates. Once I fix it, it stays fixed.

My comment was directed more toward the reason why you need to fix it
in the first place. You reveal in the following paragraph that the
reason you need to fix it is because it was you who broke it while you
were attempting to recover user files. There might be something about
your file recovery procedure that could be improved.

I also attempt to recover all the user's stuff, so things
like dot net and IE tend to get messed up in the process
and have to be repaired. Better than loosing all the customer's
settings. I wipe and reinstall only in in the most severe cases.

Also, I only see computers when something has gone wrong.

Same here. People don't call unless something has gone wrong.

 

[Todd]

You reveal in the following paragraph that the
reason you need to fix it is because it was you who broke it while you
were attempting to recover user files.

Yes, a little of both. I have nothing to do with the M$ updates
throwing a fit. And, I have nothing to do with file systems
getting corrupted. But, do have a lot to do with in place
reinstalls confusing versions and needing things to be repaired
after the reinstall. IE and dot net being the two biggies.