ATI AIW 8500 capture problems and Macrovision question

[Crow4ever]

I had some Macrovision problems with the captures on my ATI All-In-Wonder 8500DV card, so I was told to install the Plutonium XP 8.1 (6166) drivers, which I did. I followed the (ATI) uninstall directions carefully, and (I think) successfully installed the Plutonium drivers.

Now when I go to capture in VirtualDub, I get nothing. There's no capture window. Didn't the Plutonium install capture drivers? Or do I need to install additional WDM capture drivers such as the ATI WDM Capture Driver 6.14.10.6201v1?

Also, I was told that using any ATI WDM drivers will just re-enable the Macrovision again. Is this true?

So, what else do I need to install (if anything), or how do I get my capture to work again? And will it disable the Macrovision, or do I need to look for another alternative to get by my Macrovision problem?

[dvd_maniac]

http://www.doom9.org/Soft21/SupportUtils/DisableATIMacrovisionDetection.zip

From doom9's own download page. ATI just sticks a file in there driver set to "WATCH" for macrovision. this file simply disables it.
Then Virtualdub should work fine again.
But I think you need to install the ATI drivers again, not really sure.

[Crow4ever]

I tried the DisableATIMacrovisionDetection patch for the ATI drivers, but it didn't seem to work.

[dvd_maniac]

I had the AIW 8500 128mb version and it worked fine. I now have the 9700 pro aiw and haven't had a need to try it yet but I will give it a try. By the way, what version(s) of ATI software(s) are you trying it with?

[Crow4ever]

I believe the software is either version 7.0 or 7.7 - I forget exactly which as I have uninstalled it for the moment. I know there were problems with the patch not working for the 8.x versions of the software, but that doesn't apply to me, I don't think.

Is there a possibility that something else was triggering the Macrovision? Or (since I wiped out ALL of the ATI stuff from my /windows/system32 folder, and the registry) should I maybe just try installing the software again and patching it and see if that works?

Other than that, I'm stumped.