TV/VidCap not working on ATI All-In-Wonder 128 Pro w. Windows XP

Title says it all. Here's the config:
- Compaq Deskpro EN
- Dual graphics: ATI All-In-Wonder 128 Pro (16Mb PCI) as primary, 3DFX
Voodoo 3 AGP as secondary (ATI is on single IRQ)
- Windows XP SP1A w. drivers from ATI (latest)
- MMC 7.2
- WMP9 and WME9

Any attempt to talk to the WDM (ATI Rage Theater WDM) causes the "talking"
app to crash. WME says "device is not connected". Anyone have a clue?

Thanks,
Robert

 

The application accessing the WDM driver.

Robert

 

might help to know what it was...

You don;t have both videocards active at the same time do you?

 

Of course I have both active, it *is* a dual display setup as described

however, one is primary and one is secondary, if that's what you're looking
for.


Robert

 

You don;t have both videocards active at the same time do you?

can u set up the agp as secondary and working?

cause i know that to do any of the a/v stuff with the ati it needs to be
primary

 

It is currently set up as primary, but I have tested it as secondary as well
without result.

 

The problem is *with the capture drivers*, remember? All drivers function
properly save the capture drivers. Device manager gives no indication of a
problem, but whenever some application attempts to use them it crashes,
regardless of composite or S-Video selection. This occurs both with the card
as primary and as secondary.

 

Some programs may not work with the latest drivers which no longer
included vfw support. what about MMC, does that work?

 

nope. Nor does Netmeeting, Movie Maker, Intervideo WinDVR, or any other
application that uses the Rage Theater WDM interface.

 

nope. Nor does Netmeeting, Movie Maker, Intervideo WinDVR, or any other

mmc should work but netmeeting will not work with the latest driver.
you could try the 6292 drivers.

 

This may seem simplistic, but have you removed the non-ATi card,
removed the drivers and install everything so that you KNOW THAT
portion works, then start on the second adapter?

 

Workaround: I've created a second hardware profile that disables the Voodoo

There you go.