VMR9 issues,Config crashes since M.S. updates last week

[sub]

I installed the patch as you suggested, I thought it was just to provide you with more detailed logs - after I installed it I was able to get thru Config completely, I have version 1.0.16 installed

Argh! That patch is intended to be used on the current release (1.1.5), and will most likely lead to problems on 1.0.16. You should install 1.0.16. It fixes a lot of problems with this older release.

QUESTION: I know Overlay Manager produces a lower quality video, but is that only when viewing, or does it also affect the recording? I mainly use this as a PVR to record movies/tv shows and don't use it too much for just viewing - I am just VERY happy that I have at least gotten it to work this far, I have attached the logs for your viewing and comments - once again, many thanks !

The video renderer is only used for playback. It has no effect on the recording you make.

[sub]

2007-12-21 18:39:08.937 VERBOSE DirectShowPlayerVMR9Custom()...VMR9 not supported

I'm sure this error that is stopping PVRX2 from running is something to do with the video card drivers you're currently running.

Do you have the ATI Catalyst drivers installed? What version?

[sixsix]

I have the latest 7.12 display drivers, Catalyst Control Center, and Theater 550 Pro wdm drivers released yesterday - odd that the patch got vers 1.0.16 working for me? I really am afraid (very afraid!) to do anything to this as it is the first time in a week and a half that it has worked - but you are the expert, and if you say it will lead to problems then I will update to 1.1.5 - I will wait until I hear back from you regarding this post. Thanks sub for all your help ...

[sub]

I wouldnt use a 1.1.5 patch on 1.0.16. This patch is likely to have broken stuff even if it seems ok.

[tieke]

Just to say that I too started having config crashes etc last week, which I attributed to microsoft updates - I run nod32 and the crashes were similar to the recording service problems I had prior to installing the dotnet remoting hotfix. I suspect this hotfix can no longer be applied/doesn't work? To avoid wasting further time, I reverted to an earlier image and changed to kapersky av, which seems to have done the trick.
cheers,
tieke