Video Capture Driver not fully installing

H

Himanshu

I have driver software for a USB video capture device. I installed
the software and connected the Device on XP PRO, and everything worked
fine. I tried installing on XPE, but the driver only partially
installed (exclamation mark next to device in device manager). I have
All DirectX components + USB components installed. Finally, I compared
the files installed (in driver details) for the drivers in each
platform and noticed that on XPE the file: vidcap.ax did not get
included. I created a custom component from the driver software's inf
file (which included vidcap.ax), but it still did not install this
file, when I connected the device.

I had some warnings or errors when I made the component, but don't
know what to make of them:


Info:processing file : C:\WINDOWS\inf\WSUSBVID.INF
Info:C:\WINDOWS\inf\WSUSBVID.INF: type PNP device INF
Info:Creating: Westover USB Video
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:C:\WINDOWS\inf\ks.inf: [DelFiles] needs to be processed by the
user.
+++ CRITICAL ERROR +++:An error occurred when trying to add a registry
resource HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaCategories\{19689BF6-C384-48FD-AD51-90E58C79F70B}\Name.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[Filter.AddReg]: contains RunOnce AddReg item.
+++ CRITICAL ERROR +++:An error occurred when trying to add a registry
resource HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NUVision\VID_0dad&PID_0000\Settings\.
Warning:[P0000.Install.NT]: cannot handle key "SubClass".
Warning:[P0000.Install.NT]: cannot handle key "DeviceType".
Warning:[P0000.Install.NT]: cannot handle key "DeviceSubType".
Warning:[P0000.Install.NT]: cannot handle key "Capabilities".
Warning:[P0000.Install.NT]: cannot handle key "DeviceData".
Warning:[P0000.Install.NT]: cannot handle key "ICMProfiles".
Info:Completed processing file [Import succeeded] :
C:\WINDOWS\inf\WSUSBVID.INF
Info:processing file : C:\importdir\WSUSBVID.INF
Info:INF Importer is creating look up tables. This will take a few
minutes. Please wait...
Info:More than one component has the same Concordance ID [NEC PCI TO
USB OPEN HOST CONTROLLER:pCI\VEN_1033&DEV_0035&REV_41].
Info:More than one component has the same Concordance ID [STSL
COMPOSITE USB DEVICE:USB\VID_05FA&PID_3303].
Info:More than one component has the same Concordance ID [GENERIC USB
HUB:USB\CLASS_09&SUBCLASS_01].
Info:More than one component has the same Concordance ID [GEODE -
NATIVE MODE AUDIO DRIVER (WINDOWS XP/2000):pCI\VEN_1078&DEV_0103].
Info:More than one component has the same Concordance ID [SIS 7001 PCI
TO USB OPEN HOST CONTROLLER:pCI\VEN_1039&DEV_7001&CC_0C0310].
Info:Creating: Westover USB Video
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:[DeviceRegistration]: contains RunOnce AddReg item.
Warning:C:\importdir\ks.inf: [DelFiles] needs to be processed by the
user.
+++ CRITICAL ERROR +++:An error occurred when trying to add a registry
resource HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaCategories\{19689BF6-C384-48FD-AD51-90E58C79F70B}\Name.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[BdaDevice.RunOnce.AddReg.NT]: contains RunOnce AddReg item.
Warning:[Filter.AddReg]: contains RunOnce AddReg item.
Warning:[Filter.AddReg]: contains RunOnce AddReg item.
+++ CRITICAL ERROR +++:An error occurred when trying to add a registry
resource HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NUVision\VID_0dad&PID_0000\Settings\.
Warning:[P0000.Install.NT]: cannot handle key "SubClass".
Warning:[P0000.Install.NT]: cannot handle key "DeviceType".
Warning:[P0000.Install.NT]: cannot handle key "DeviceSubType".
Warning:[P0000.Install.NT]: cannot handle key "Capabilities".
Warning:[P0000.Install.NT]: cannot handle key "DeviceData".
Warning:[P0000.Install.NT]: cannot handle key "ICMProfiles".
Info:Completed processing file [Import succeeded] :
C:\importdir\WSUSBVID.INF



Any ideas would be greatly appreciated.
Thanks,
Himanshu
 
A

Andy Allred [MS]

That file vidcap.ax is owned by "USB Video Device". This should have
been detected by TAP when you ran it against XP-Pro when this device
was attached to it. I'd recommend rebuilding your config by importing
TAP's resulting PMQ generated by the build of XP-Pro with *all* devices
having been plugged into it so it can identify the hardware components
and the software enumerated components.
 
K

KM

vidcap.ax is indeed part of the "USB Video Device" component. But the component seems to be a part of SP2 only.

Himanshu,
Here is primitives you will need to make sure to get in your image:

Component: Primitive: Msh263 [Version 5.1.2600.2096, R2085]
Component: Video For Windows Core [Version 5.1.2600.2096, R2085]
Component: DirectShow Video For Windows / WDM [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.sys [Version 5.1.2600.2096, R2085]
Component: Kernel Streaming User Mode Support [Version 5.1.2600.2096, R2085]
Component: Analog TV [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.inf [Version 5.1.2600.2096, R2085]


There are some more files you will need (like usbvideo.inf, etc.)
When you import the inf make sure it finds all the dependent INF files.
Read, for example, this tip page: http://msdn.microsoft.com/embedded/community/community/tips/xp/compo/default.aspx
 
A

Andy Allred [MS]

yeah, good call. i can't seem to find it in any repository before SP2
either and i don't see it in the full build of XP Pro Gold or SP1.
 
H

Himanshu

Hello, I have all the components listed below included, except that
the version for all my components are R1507. Forgive me for being new
at this, but where is the upgrade to this version. I have been at the
windows embedded site to download the lates QFE's:

http://www.microsoft.com/downloads/...&freetext=&DisplayLang=en&DisplayEnglishAlso=
Here is primitives you will need to make sure to get in your image:

Component: Primitive: Msh263 [Version 5.1.2600.2096, R2085]
Component: Video For Windows Core [Version 5.1.2600.2096, R2085]
Component: DirectShow Video For Windows / WDM [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.sys [Version 5.1.2600.2096, R2085]
Component: Kernel Streaming User Mode Support [Version 5.1.2600.2096, R2085]
Component: Analog TV [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.inf [Version 5.1.2600.2096, R2085]

I've found the inf file for the "USB Video Device" and I built a
custom component from the SP2 usbvideo.inf. Unfortunately, this did
not fix my problem either. In the end vidcap.ax was still not
installed as part of the driver.
 
K

KM

Himanshu,

I don't think that is an upgrade to this component in SP1. I guess you have only wait for SP2.
Or you can try getting this component out of beta SP2 db to include to your SP1 configuration (don't know if it is legal, though, so
please consult with your legal folks).
There is a bunch of settings in the component and its child components that may be hard to list.

--
Regards,
KM, BSquare Corp.

Hello, I have all the components listed below included, except that
the version for all my components are R1507. Forgive me for being new
at this, but where is the upgrade to this version. I have been at the
windows embedded site to download the lates QFE's:

http://www.microsoft.com/downloads/...&freetext=&DisplayLang=en&DisplayEnglishAlso=
Here is primitives you will need to make sure to get in your image:

Component: Primitive: Msh263 [Version 5.1.2600.2096, R2085]
Component: Video For Windows Core [Version 5.1.2600.2096, R2085]
Component: DirectShow Video For Windows / WDM [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.sys [Version 5.1.2600.2096, R2085]
Component: Kernel Streaming User Mode Support [Version 5.1.2600.2096, R2085]
Component: Analog TV [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.inf [Version 5.1.2600.2096, R2085]

I've found the inf file for the "USB Video Device" and I built a
custom component from the SP2 usbvideo.inf. Unfortunately, this did
not fix my problem either. In the end vidcap.ax was still not
installed as part of the driver.
 
H

Himanshu

To follow up on the thought that usb video device component was
needed, I installed the video capture driver software on a machine
that was running with SP1 only (expecting that it wouldn't work), and
it still works (except that it doesn't include vidcap.ax in the
driver's file list, but the device operates normally). There must be
some component I'm missing, but running TAP on the SP1 machine, it
looks like I've got all the needed components.

I appreciate all the help you all have been providing.
Thanks,
Himanshu

KM said:
Himanshu,

I don't think that is an upgrade to this component in SP1. I guess you have only wait for SP2.
Or you can try getting this component out of beta SP2 db to include to your SP1 configuration (don't know if it is legal, though, so
please consult with your legal folks).
There is a bunch of settings in the component and its child components that may be hard to list.

--
Regards,
KM, BSquare Corp.

Hello, I have all the components listed below included, except that
the version for all my components are R1507. Forgive me for being new
at this, but where is the upgrade to this version. I have been at the
windows embedded site to download the lates QFE's:

http://www.microsoft.com/downloads/...&freetext=&DisplayLang=en&DisplayEnglishAlso=
Here is primitives you will need to make sure to get in your image:

Component: Primitive: Msh263 [Version 5.1.2600.2096, R2085]
Component: Video For Windows Core [Version 5.1.2600.2096, R2085]
Component: DirectShow Video For Windows / WDM [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.sys [Version 5.1.2600.2096, R2085]
Component: Kernel Streaming User Mode Support [Version 5.1.2600.2096, R2085]
Component: Analog TV [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.inf [Version 5.1.2600.2096, R2085]

I've found the inf file for the "USB Video Device" and I built a
custom component from the SP2 usbvideo.inf. Unfortunately, this did
not fix my problem either. In the end vidcap.ax was still not
installed as part of the driver.
That file vidcap.ax is owned by "USB Video Device". This should have
been detected by TAP when you ran it against XP-Pro when this device
was attached to it. I'd recommend rebuilding your config by importing
TAP's resulting PMQ generated by the build of XP-Pro with *all* devices
having been plugged into it so it can identify the hardware components
and the software enumerated components.
 
K

KM

Himanshu,

You have two ways to figure this out:
1) Use Dependency Walker/Regmon/Filemon tools to find out missing components
2) Check out the USB Video stack implemented in SP2. Grab all reg.settings and file from the SP2 related components in to your
SP1 configuration (risky but still doable).

--
Regards,
KM, BSquare Corp.

To follow up on the thought that usb video device component was
needed, I installed the video capture driver software on a machine
that was running with SP1 only (expecting that it wouldn't work), and
it still works (except that it doesn't include vidcap.ax in the
driver's file list, but the device operates normally). There must be
some component I'm missing, but running TAP on the SP1 machine, it
looks like I've got all the needed components.

I appreciate all the help you all have been providing.
Thanks,
Himanshu

KM said:
Himanshu,

I don't think that is an upgrade to this component in SP1. I guess you have only wait for SP2.
Or you can try getting this component out of beta SP2 db to include to your SP1 configuration (don't know if it is legal, though, so
please consult with your legal folks).
There is a bunch of settings in the component and its child components that may be hard to list.

--
Regards,
KM, BSquare Corp.

Hello, I have all the components listed below included, except that
the version for all my components are R1507. Forgive me for being new
at this, but where is the upgrade to this version. I have been at the
windows embedded site to download the lates QFE's:
http://www.microsoft.com/downloads/...&freetext=&DisplayLang=en&DisplayEnglishAlso=
Here is primitives you will need to make sure to get in your image:

Component: Primitive: Msh263 [Version 5.1.2600.2096, R2085]
Component: Video For Windows Core [Version 5.1.2600.2096, R2085]
Component: DirectShow Video For Windows / WDM [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.sys [Version 5.1.2600.2096, R2085]
Component: Kernel Streaming User Mode Support [Version 5.1.2600.2096, R2085]
Component: Analog TV [Version 5.1.2600.2096, R2085]
Component: Primitive: Ks.inf [Version 5.1.2600.2096, R2085]

I've found the inf file for the "USB Video Device" and I built a
custom component from the SP2 usbvideo.inf. Unfortunately, this did
not fix my problem either. In the end vidcap.ax was still not
installed as part of the driver.

That file vidcap.ax is owned by "USB Video Device". This should have
been detected by TAP when you ran it against XP-Pro when this device
was attached to it. I'd recommend rebuilding your config by importing
TAP's resulting PMQ generated by the build of XP-Pro with *all* devices
having been plugged into it so it can identify the hardware components
and the software enumerated components.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top