Reply to thread

Message

<blockquote data-quote="mikesusangray" data-source="post: 77581" data-attributes="member: 17718">Solved!Problem fixed - though not the easy way.Since I had already gone to that much trouble, I went ahead and did yet another clean re-install of XP. Not exactly fun, but this time MP worked - and I found the problem as well:I had saved my olf ffdshow settings to a .reg file, which I double clicked to restore. Apparently, is was caused by something about either (1) the settings themselves, (2) the version of ffdshow they came from or (3) a change between the version I saved the settings from and the version I installed.It should be noted that no other programs had this problem.I've enclosed the .reg file for future reference (extension changed to .txt).I also had a bear of a time finding an ffdshow version that would play nice with MP - particuarly when it came to using AVSynth scripts. But I've found one, so everything is running now.Mike</blockquote>

[QUOTE="mikesusangray, post: 77581, member: 17718"] [b]Solved![/b] Problem fixed - though not the easy way. Since I had already gone to that much trouble, I went ahead and did yet another clean re-install of XP. Not exactly fun, but this time MP worked - and I found the problem as well: I had saved my olf ffdshow settings to a .reg file, which I double clicked to restore. Apparently, is was caused by something about either (1) the settings themselves, (2) the version of ffdshow they came from or (3) a change between the version I saved the settings from and the version I installed. It should be noted that no other programs had this problem. I've enclosed the .reg file for future reference (extension changed to .txt). I also had a bear of a time finding an ffdshow version that would play nice with MP - particuarly when it came to using AVSynth scripts. But I've found one, so everything is running now. Mike [/QUOTE]

Verification