Amcap in XPE

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

Guest

Hello,

We are testing a video grabber chip under XPE. The drivers work fine under
XPPro with Amcap, but when I try it under XPE it freezes when I shall preview
the video.

I have imported the driver to the chip and resolved all dependencies...

What do I need from DirectX to run Amcap?
Do I need more that DirectX components?

Any ideas?

Thanks
/Göran
 
Goran,

This may not be a fix for you but rather a tip to gather more data about the
problem:
- verify if the video driver got installed and working properly on your
XPe image (Device Manager/devcon/SetupApi.log)
- if the MB happened to support AGP, make sure a GART driver was included
(agp440.sys for Intel chipsets), and got installed properly (SetupApi.log)
- make sure "TAPI Audio, Video and RTP Filters" component included along
with DirectX stack (all DirectShow)
- if nothing from above works for you, you can try XPProEmulation image on
your device (www.xpefiles.com) to see whether it is a missing dependency
issue

KM
 
Hello,

- I seems that the driver got installed properly. I can't see errors
regarding to the driver in SetupApi.log.
- We have support for AGP, but it is set to use PCI in BIOS.
- I may be blind, but I can't find the "TAPI Audio, Video and RTP Filters"
component. Where is it located??
- I will continue trying with the XPPro emulation component...

Thanks
/Göran
 
Goran,
- I seems that the driver got installed properly. I can't see errors
regarding to the driver in SetupApi.log.
- We have support for AGP, but it is set to use PCI in BIOS.
Click to expand...

Not all BIOS settings are read in XP. It may not hurt to add GART driver.
- I may be blind, but I can't find the "TAPI Audio, Video and RTP Filters"
component. Where is it located??
Click to expand...

It is there under "Software : System : Networking & Communications :
Infrastructure" category. Component's Visibility = 200 so you may need to
lower you TD min.Visibility option.

Interesting to note. I just noticed that Micrsoft has set EOL (End of Life)
for the component in Revision R1509 (v 5.1.2600.2180). This "life ended"
version of the component doesn't depend on anything, doesn't bring in any
reg.entries, any files, etc. While older versions (R620/R1507) have all of
it.
I don't know the reason why the component was "cleaned up" and "EOL'ed" but
it doesn't sound good.

If you are really interested in knowing how this component can help you,
revert database back to SP1 and include it in your image to see the
component's resources.
 
Back
Top