Install scanner

  • Thread starter Thread starter Lucvdv
  • Start date Start date
L

Lucvdv

Trying to install a scanner post FBA (only have a setup CD), I get "the
class installer denied the request to install or update a driver for this
device".

Does anyone have an idea what component(s) might be necessary to make it
work?

I've got the Imaging class installer and dependencies, and anhting I could
find that's related to imaging.

I added another scanner to the target to be sure I had everything that's
necessary, but it doesn't help.
 
Lucvdv,
Is this USB scanner?

Windows Image Acquisition Core?
Regards,
Slobodan
 
Lucvdv,
Is this USB scanner?
Click to expand...

Yes, a HP PSC 1350 USB scanner/printer.

I added the PSC 950 (the highest model number I found in TD) to the target,
hoping that it would have the same requirements, but it still won't work.
That's 3 components: HP PSC 950, HP PSC 950 USB and HP PSC 950 Scanner.

The PSC 1350's setup succeeds in installing the printer and USB storage
(built-in CF reader), but the scanner part fails.
Windows Image Acquisition Core?
Click to expand...

Is present, "Windows Image Acquisition User Interface" too.
 
Lucvd,

If you have all this.

Try deleting setupapi.log and then installing drivers from CD. then send us
new setupapi.log

Also go to device manager and try removing troubled node and reinstlaling
driver from there.

Regards,
Slobodan
 
Lucvdv,

Does the scanner work on XP Pro with driver that is coming from XP Pro installation CD or WU?
Or does the scanner have its own driver?

If you are able sucessfully use the scanner on XP Pro, just verify what driver is used there and match it in your XPe image.
If it still doesn't work, SetupApi.log will likely show some info.

KM
 
Trying to install a scanner post FBA (only have a setup CD), I get "the
class installer denied the request to install or update a driver for this
device".

Does anyone have an idea what component(s) might be necessary to make it
work?

I've got the Imaging class installer and dependencies, and anhting I could
find that's related to imaging.

I added another scanner to the target to be sure I had everything that's
necessary, but it doesn't help.
Click to expand...

There's something I didn't mention here, but I don't think it's related.

When I leave everything as is after FBA and run the setup from CD, it looks
for all driver files relative to C:\Windows instead of relative to the CD
root.

For example if there's a file D:\Drivers\Scanner\xxxx.sys on the CD, setup
tries to find it at C:\Windows\Drivers\Scanner\xxxx.sys, doesn't find it,
and prompts for the correct location. I browsed to the correct location
each time it prompted, so all files were copied successfully.

This doesn't happen if I first edit the setup source paths in the registry
at HKLM\Software\Microsoft\Windows\CurrentVersion\Setup and make them point
to D:\ instead of C:\Windows.

The installation fails with the same error either way.
 
Lucvd,

If you have all this.

Try deleting setupapi.log and then installing drivers from CD. then send us
new setupapi.log
Click to expand...

The setupapi.log is over 60K large even after deleting it before starting
the installation, so I zipped and attached it instead of including it as
text in the message body. That will avoid line breaks inserted by
newsreaders as well.
Also go to device manager and try removing troubled node and reinstlaling
driver from there.
Click to expand...

Already tried that several times :(


And said:
Does the scanner work on XP Pro with driver that is coming from XP Pro installation CD or WU?
Or does the scanner have its own driver?
Click to expand...

There's no support for it in XP Pro or WU.
It comes with its own driver on CD, which works on XP Pro.



Thanks to both for the suggestions so far.

I'm currently comparing the relevant setupapi.log section of XPe to that of
XP Pro, if that turns up anything I'll let you know.
 
Lucvdv,

Look in inf file for dependencies on other inf files expecialy you shoud try
to find reason for this:

#I123 Doing full install of "USB\VID_03F0&PID_3B11&MI_00\6&2EAF109A&1&0000".
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem2.inf, using [STRINGS] instead.
#E275 Error while installing services. Error 0xe0000219: The installation
failed because a function driver was not specified for this device instance.
#E122 Device install failed. Error 0xe0000219: The installation failed
because a function driver was not specified for this device instance.
#E154 Class installer failed. Error 0xe000022b: The class installer has
denied the request to install or upgrade this device.
#I060 Set selected driver.

You might want to increase setupapi logging levels so that all informations
are logged it might help you.

Also this is strange:
Try using FAT for start:
#-336 Copying file "D:\drivers\dot4\Win2000\HPZidr12.dll" to
"C:\WINDOWS\system32\HPZidr12.dll" via temporary file
"C:\WINDOWS\system32\SETDC.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZidr12.dll" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZidr12.dll".
Error 1307: This security ID may not be assigned as the owner of this
object.
#-336 Copying file "D:\drivers\dot4\Win2000\HPZipr12.dll" to
"C:\WINDOWS\system32\HPZipr12.dll" via temporary file
"C:\WINDOWS\system32\SETDF.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZipr12.dll" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZipr12.dll".
Error 1307: This security ID may not be assigned as the owner of this
object.
#-336 Copying file "D:\drivers\dot4\Win2000\HPZipm12.exe" to
"C:\WINDOWS\system32\HPZipm12.exe" via temporary file
"C:\WINDOWS\system32\SETE2.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZipm12.exe" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZipm12.exe".
Error 1307: This security ID may not be assigned as the owner of this
object.
#-336 Copying file "D:\drivers\dot4\Win2000\HPZinw12.exe" to
"C:\WINDOWS\system32\HPZinw12.exe" via temporary file
"C:\WINDOWS\system32\SETE5.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZinw12.exe" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZinw12.exe".
Error 1307: This security ID may not be assigned as the owner of this
object.
#-336 Copying file "D:\drivers\dot4\Win2000\HPZisn12.dll" to
"C:\WINDOWS\system32\HPZisn12.dll" via temporary file
"C:\WINDOWS\system32\SETE8.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZisn12.dll" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZisn12.dll".
Error 1307: This security ID may not be assigned as the owner of this
object.
#-336 Copying file "D:\drivers\dot4\Win2000\HPZipt12.dll" to
"C:\WINDOWS\system32\HPZipt12.dll" via temporary file
"C:\WINDOWS\system32\SETEB.tmp".
#W025 A newer file "C:\WINDOWS\system32\HPZipt12.dll" was overwritten by an
older (signed) file. Version of source file: 7.0.0.0. Version of target
file: 7.0.0.0. The SP_COPY_FORCE_NEWER flag was ignored. The existing target
file was signed.
#E249 Failed to apply security to file "C:\WINDOWS\system32\HPZipt12.dll".
Error 1307: This security ID may not be assigned as the owner of this
object.

Regards,
Slobodan

PS:
If this is file created only by setup that install scanner then it is huge
and strange. You might want to install from inf itself instead of using
setup program.
 
PS:
If this is file created only by setup that install scanner then it is huge
and strange. You might want to install from inf itself instead of using
setup program.
Click to expand...

The resulting log file on XP Pro is less than half the size of this one.
Apparently it retries to install the driver several times before giving up.

The size is so large also because it installs several things at once: USB
Multifunction device, USB printer, USB storage, USB scanner, and its own
version of USB Printing support (apparently different from the version
included in XP Pro/XPe, but still with "Microsoft" as author, while the
other INF's have HP there).


Installing from INF isn't really the direction I want to go, because
different scanners and printers may be used in the future. What I want to
obtain is that I can install any printer or scanner from its own setup CD
after deployment, without having to update the device.
Space is not an issue (running from harddisk), so I added just about all of
XP Pro to minimize the risk of problems there, but even with a >900 MB
target it still won't work :(

There must be some lower level component that I forgot, I just can't
imagine what.
 
Lucvdv,

You should use "Divide and Conquer" approach, by this I mean that you really
should make all your drivers install trough inf files and when you manage to
do that if your setup.exe still does not work then you should concentrate on
that.
Since driver installation is one thing and what setup does and expect is
completely different.

You might not even have a problem with scanner but with something else that
you do not see because of this huge bloat produced by setup.

Regards,
Slobodan
 
Lucvdv,

You should use "Divide and Conquer" approach, by this I mean that you really
should make all your drivers install trough inf files and when you manage to
do that if your setup.exe still does not work then you should concentrate on
that.
Since driver installation is one thing and what setup does and expect is
completely different.

You might not even have a problem with scanner but with something else that
you do not see because of this huge bloat produced by setup.
Click to expand...


I found it...

It's a dependency on an INF file, as you suggested earlier.

The file in question, sti.inf, is part of several digital camera and
scanner components, but it's not on the driver CD and /not/ in the HP PSC
950 scanner component that I had added as "closest match" to the PSC 1350.


Thanks to you and KM for the help.
 
Back
Top