install process can't find a driver DLL

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm trying to manually install a video driver. there is a yellow "!" in front
of the device in Device manager. When clicking "update driver", and choosing
the directory where the INF is and so on, eventually an error message pops up
saying that a certain DLL cannot be found. Well, this DLL _is_ there on the
image.

I tried to switch this DLL to a DLL of a lower version number just by
overwriting the new with the old, and voila! the "!" disappeared. Now, when
including this older DLL version and building a new image, the same old error
occurs.

what is wrong? why can't the install wizard see the DLL?? is there som
linking issue here?

Thank you
 
Here is the setupapi.log:

[SetupAPI Log]
OS Version = 5.1.2600
Platform ID = 2 (NT)
Service Pack = 0.0
Suite = 0x0040
Product Type = 1
Architecture = x86
[2006/04/20 03:41:05 1368.63]
#-198 Command line processed: C:\WINDOWS\system32\mmc.exe
"C:\WINDOWS\System32\devmgmt.msc"
#-166 Device install function: DIF_REMOVE.
#I289 Removing device
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#I048 Device removed.
[2006/04/20 03:43:44 296.3 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1165&dev_0080&subsys_965610b5&rev_00,pci\ven_1165&dev_0080&subsys_965610b5,pci\ven_1165&dev_0080&cc_040000,pci\ven_1165&dev_0080&cc_0400
#-018 Searching for compatible ID(s):
pci\ven_1165&dev_0080&rev_00,pci\ven_1165&dev_0080,pci\ven_1165&cc_040000,pci\ven_1165&cc_0400,pci\ven_1165,pci\cc_040000,pci\cc_0400
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "PCI\VEN_1165&DEV_0080&SUBSYS_965610b5" in
C:\WINDOWS\inf\foresight_2k.inf; Device: "AccuStream 170"; Driver:
"AccuStream 170"; Provider: "Foresight Imaging"; Mfg: "Foresight Imaging";
Section name: "hd4nt".
#I023 Actual install section: [hd4nt]. Rank: 0x00000001. Effective driver
date: 03/18/2000.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [hd4nt] in
"c:\windows\inf\foresight_2k.inf".
#I320 Class GUID of device remains: {4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [hd4nt.Interfaces] from
"c:\windows\inf\foresight_2k.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0" finished
successfully.
 
Ok, i grepped around on the net and looked at an older version of the inf
(couldn't find a newer one for your model), but it appears this thing
depends on the kernel streaming stack and wdm stuff that other multimedia
devices require.

Did you add all of this to the runtime? Here's a tip to ensure you probably
have that stuff. Install any wdm audio device to your configuration in
target designer and see if it brings in any new components. If it does, then
this is likely the cause of your failure.

Besides that, have you tried installing this device from the desktop on
XP-Pro? If you did, did you run TAP.exe on that pro box after ensuring the
device was fully functional, this will ensure you bring in any additional
class installers, or filters or software enumerated devices when you import
that resulting PMQ into your config. And as an additional experiment, try
building that config by not disabling any of the components resulting from
the PMQ import.

Good luck.

--
Andy
--
Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.


Mr. K. said:
Here is the setupapi.log:

[SetupAPI Log]
OS Version = 5.1.2600
Platform ID = 2 (NT)
Service Pack = 0.0
Suite = 0x0040
Product Type = 1
Architecture = x86
[2006/04/20 03:41:05 1368.63]
#-198 Command line processed: C:\WINDOWS\system32\mmc.exe
"C:\WINDOWS\System32\devmgmt.msc"
#-166 Device install function: DIF_REMOVE.
#I289 Removing device
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#I048 Device removed.
[2006/04/20 03:43:44 296.3 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_1165&dev_0080&subsys_965610b5&rev_00,pci\ven_1165&dev_0080&subsys_965610b5,pci\ven_1165&dev_0080&cc_040000,pci\ven_1165&dev_0080&cc_0400
#-018 Searching for compatible ID(s):
pci\ven_1165&dev_0080&rev_00,pci\ven_1165&dev_0080,pci\ven_1165&cc_040000,pci\ven_1165&cc_0400,pci\ven_1165,pci\cc_040000,pci\cc_0400
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "PCI\VEN_1165&DEV_0080&SUBSYS_965610b5" in
C:\WINDOWS\inf\foresight_2k.inf; Device: "AccuStream 170"; Driver:
"AccuStream 170"; Provider: "Foresight Imaging"; Mfg: "Foresight Imaging";
Section name: "hd4nt".
#I023 Actual install section: [hd4nt]. Rank: 0x00000001. Effective driver
date: 03/18/2000.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [hd4nt] in
"c:\windows\inf\foresight_2k.inf".
#I320 Class GUID of device remains:
{4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [hd4nt.Interfaces] from
"c:\windows\inf\foresight_2k.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0".
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of
"PCI\VEN_1165&DEV_0080&SUBSYS_965610B5&REV_00\4&1A671D0C&0&78F0" finished
successfully.


-------

Andy Allred said:
Please check setupapi.log for more information. Also, try turning on
verbose
logging of setupapi from our blog on this subject:
http://blogs.msdn.com/embedded/archive/2006/03/14/550941.aspx

Good luck.
--
Andy
--
Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
Click to expand...
 
Back
Top