Here we go again...

Got sick of the sound-sync issues with newer drivers and crappy
performance of MMC 9.1x versions... reverted to drivers
5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
is "Unable to start TV." Ran the uninstaller, reinstalled it all
clean... same thing.

Other apps that use the "ATI Rage Video Theater Capture" device work
fine, but not MMC. WTF???

Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
should make a difference - everything seems to be able to use the
capture functions except the MMC itself.

"Matt Ion" <soundy106@gmail.com> wrote in message
news:busUi.146788$Da.92375@pd7urf1no...
> Got sick of the sound-sync issues with newer drivers and crappy
> performance of MMC 9.1x versions... reverted to drivers
> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
> is "Unable to start TV." Ran the uninstaller, reinstalled it all
> clean... same thing.
>
> Other apps that use the "ATI Rage Video Theater Capture" device work
> fine, but not MMC. WTF???
>
> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
> should make a difference - everything seems to be able to use the
> capture functions except the MMC itself.

When going back to an older version you have to do the whole nine yards.
Which means manual cleaning per ati.com/install. Even not cleaning out the
temp folder can cause problems.

For me the long way around has ended up being the fastest since 9.0.6 even
going forward.

T Shadow wrote:
> "Matt Ion" <soundy106@gmail.com> wrote in message
> news:busUi.146788$Da.92375@pd7urf1no...
>> Got sick of the sound-sync issues with newer drivers and crappy
>> performance of MMC 9.1x versions... reverted to drivers
>> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
>> is "Unable to start TV." Ran the uninstaller, reinstalled it all
>> clean... same thing.
>>
>> Other apps that use the "ATI Rage Video Theater Capture" device work
>> fine, but not MMC. WTF???
>>
>> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
>> should make a difference - everything seems to be able to use the
>> capture functions except the MMC itself.
>
> When going back to an older version you have to do the whole nine yards.
> Which means manual cleaning per ati.com/install. Even not cleaning out the
> temp folder can cause problems.
>
> For me the long way around has ended up being the fastest since 9.0.6 even
> going forward.

Did all that... tracked down and nuked all references to ATI in the
registry, cleared the TEMP files, everything. Still no luck - MMC
"can't start the TV" but all other apps can start and access the tuner
just fine.

*grumble grumble* any other suggestions? MMC 9.08 will be fine, but I
guess I need to find the right combination of drivers to go with it.

>>> Got sick of the sound-sync issues with newer drivers and crappy
>>> performance of MMC 9.1x versions... reverted to drivers
>>> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
>>> is "Unable to start TV." Ran the uninstaller, reinstalled it all
>>> clean... same thing.
>>>
>>> Other apps that use the "ATI Rage Video Theater Capture" device work
>>> fine, but not MMC. WTF???
>>>
>>> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
>>> should make a difference - everything seems to be able to use the
>>> capture functions except the MMC itself.
>>
>> When going back to an older version you have to do the whole nine yards.
>> Which means manual cleaning per ati.com/install. Even not cleaning out the
>> temp folder can cause problems.
>>
>> For me the long way around has ended up being the fastest since 9.0.6 even
>> going forward.
>
>Did all that... tracked down and nuked all references to ATI in the
>registry, cleared the TEMP files, everything. Still no luck - MMC
>"can't start the TV" but all other apps can start and access the tuner
>just fine.
>
>*grumble grumble* any other suggestions? MMC 9.08 will be fine, but I
>guess I need to find the right combination of drivers to go with it.

When you said, Ran the uninstaller, reinstalled it all clean... same
thing.", did you mean you just un-installed MMC or you un-installed
_all_ ATI s/w? You have to un-install all ATI s/w, not just MMC. And
then you have to re-install the drivers, DAO/MDAC and MMC in order.

"Chuck U. Farley" <chuckufarley@dyslexia.com> wrote in message
news:2u5rj350klqtdbhs3k0uhfenrd6tr6nogn@4ax.com...
>
> >>> Got sick of the sound-sync issues with newer drivers and crappy
> >>> performance of MMC 9.1x versions... reverted to drivers
> >>> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
> >>> is "Unable to start TV." Ran the uninstaller, reinstalled it all
> >>> clean... same thing.
> >>>
> >>> Other apps that use the "ATI Rage Video Theater Capture" device work
> >>> fine, but not MMC. WTF???
> >>>
> >>> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
> >>> should make a difference - everything seems to be able to use the
> >>> capture functions except the MMC itself.
> >>
> >> When going back to an older version you have to do the whole nine
yards.
> >> Which means manual cleaning per ati.com/install. Even not cleaning out
the
> >> temp folder can cause problems.
> >>
> >> For me the long way around has ended up being the fastest since 9.0.6
even
> >> going forward.
> >
> >Did all that... tracked down and nuked all references to ATI in the
> >registry, cleared the TEMP files, everything. Still no luck - MMC
> >"can't start the TV" but all other apps can start and access the tuner
> >just fine.
> >
> >*grumble grumble* any other suggestions? MMC 9.08 will be fine, but I
> >guess I need to find the right combination of drivers to go with it.
>
> When you said, Ran the uninstaller, reinstalled it all clean... same
> thing.", did you mean you just un-installed MMC or you un-installed
> _all_ ATI s/w? You have to un-install all ATI s/w, not just MMC. And
> then you have to re-install the drivers, DAO/MDAC and MMC in order.
>
>


Agreed. The manual cleaning method would cover display drivers.

Reinstall the WDM drivers first before the display drivers. The manual clean
has always worked for me. If this isn't working uninstall the other apps
that access the multimedia part of the AIW and do at least a repair install
on MMC.

Was going to suggest running the test program in the configuration app but
it's crashing in my system even though AFAIK my system is working perfectly

Never had a problem with it but .NET installation might be able to cause
problems.

Could be you got a bad download. Recently got a bad d/l for another device
that was 5 bytes short of the 1.3GB it should have been. Wasted a couple
hours on that besides the d/l times.

Chuck U. Farley wrote:
>>>> Got sick of the sound-sync issues with newer drivers and crappy
>>>> performance of MMC 9.1x versions... reverted to drivers
>>>> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
>>>> is "Unable to start TV." Ran the uninstaller, reinstalled it all
>>>> clean... same thing.
>>>>
>>>> Other apps that use the "ATI Rage Video Theater Capture" device work
>>>> fine, but not MMC. WTF???
>>>>
>>>> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
>>>> should make a difference - everything seems to be able to use the
>>>> capture functions except the MMC itself.
>>> When going back to an older version you have to do the whole nine yards.
>>> Which means manual cleaning per ati.com/install. Even not cleaning out the
>>> temp folder can cause problems.
>>>
>>> For me the long way around has ended up being the fastest since 9.0.6 even
>>> going forward.
>> Did all that... tracked down and nuked all references to ATI in the
>> registry, cleared the TEMP files, everything. Still no luck - MMC
>> "can't start the TV" but all other apps can start and access the tuner
>> just fine.
>>
>> *grumble grumble* any other suggestions? MMC 9.08 will be fine, but I
>> guess I need to find the right combination of drivers to go with it.
>
> When you said, Ran the uninstaller, reinstalled it all clean... same
> thing.", did you mean you just un-installed MMC or you un-installed
> _all_ ATI s/w? You have to un-install all ATI s/w, not just MMC. And
> then you have to re-install the drivers, DAO/MDAC and MMC in order.

Yes, I ran the ATI uninstaller... c:\Program Files\ATI
Technologies\UninstallAll\AtiCimUn.exe

Did that the first time. Do that every time.

Oddly enough, every time someone here complains about this ridiculous
process, someone else pipes up that it's really not necessary. I wish
people would make up their minds.

T Shadow wrote:
> "Chuck U. Farley" <chuckufarley@dyslexia.com> wrote in message
> news:2u5rj350klqtdbhs3k0uhfenrd6tr6nogn@4ax.com...
>>>>> Got sick of the sound-sync issues with newer drivers and crappy
>>>>> performance of MMC 9.1x versions... reverted to drivers
>>>>> 5-12_xp-2k_dd_ccc_wdm_enu_28472.exe and v9.08 MMC... and now all I get
>>>>> is "Unable to start TV." Ran the uninstaller, reinstalled it all
>>>>> clean... same thing.
>>>>>
>>>>> Other apps that use the "ATI Rage Video Theater Capture" device work
>>>>> fine, but not MMC. WTF???
>>>>>
>>>>> Asus A8V Deluxe mobo, Radeon 9800Pro AIW, XPPro/SP2. Like any of that
>>>>> should make a difference - everything seems to be able to use the
>>>>> capture functions except the MMC itself.
>>>> When going back to an older version you have to do the whole nine
> yards.
>>>> Which means manual cleaning per ati.com/install. Even not cleaning out
> the
>>>> temp folder can cause problems.
>>>>
>>>> For me the long way around has ended up being the fastest since 9.0.6
> even
>>>> going forward.
>>> Did all that... tracked down and nuked all references to ATI in the
>>> registry, cleared the TEMP files, everything. Still no luck - MMC
>>> "can't start the TV" but all other apps can start and access the tuner
>>> just fine.
>>>
>>> *grumble grumble* any other suggestions? MMC 9.08 will be fine, but I
>>> guess I need to find the right combination of drivers to go with it.
>> When you said, Ran the uninstaller, reinstalled it all clean... same
>> thing.", did you mean you just un-installed MMC or you un-installed
>> _all_ ATI s/w? You have to un-install all ATI s/w, not just MMC. And
>> then you have to re-install the drivers, DAO/MDAC and MMC in order.
>>
>>
>
>
> Agreed. The manual cleaning method would cover display drivers.
>
> Reinstall the WDM drivers first before the display drivers. The manual clean
> has always worked for me. If this isn't working uninstall the other apps
> that access the multimedia part of the AIW and do at least a repair install
> on MMC.
>
> Was going to suggest running the test program in the configuration app but
> it's crashing in my system even though AFAIK my system is working perfectly
>
> Never had a problem with it but .NET installation might be able to cause
> problems.
>
> Could be you got a bad download. Recently got a bad d/l for another device
> that was 5 bytes short of the 1.3GB it should have been. Wasted a couple
> hours on that besides the d/l times.

I don't get any errors installing. The WDM drivers themselves work fine
- I can capture video with AMCAP, Vegas, Windows Movie Maker, ChrisTV,
BeyondTV (or could, before it expired), NeroVision... I can even set ATI
Rage Theater Video as my video device in MSN Messenger. EVERYTHING else
works with the card... except MMC! All other parts of MMC work fine,
the TV portion just seems unable to start the capture drivers.

>Oddly enough, every time someone here complains about this ridiculous
>process, someone else pipes up that it's really not necessary. I wish
>people would make up their minds.

As with all things in life, it works for some and not for others.

Even though it won't help you now, I'd suggest investing $50 to $100
USD and getting a second hd and disk imaging s/w. Do an image of your
root drive before doing _any_ install/upgrade and then if it doesn't
work out, just restore the image and you're back where youy started.
This process has yanked my *** out of more fires than I can remember.

>Never had a problem with it but .NET installation might be able to cause
>problems.

To much memory/resource overhead for me to even mess with .NET. CCC
just isn't worth it to me.

>Could be you got a bad download. Recently got a bad d/l for another device
>that was 5 bytes short of the 1.3GB it should have been. Wasted a couple
>hours on that besides the d/l times.

****, that had to be frustrating.

Glad to see you jstill poke you head in here, between you and J Clark,
it's almost like this is a real ng again. <g>

Chuck U. Farley wrote:
>> Oddly enough, every time someone here complains about this ridiculous
>> process, someone else pipes up that it's really not necessary. I wish
>> people would make up their minds.
>
> As with all things in life, it works for some and not for others.
>
> Even though it won't help you now, I'd suggest investing $50 to $100
> USD and getting a second hd and disk imaging s/w. Do an image of your
> root drive before doing _any_ install/upgrade and then if it doesn't
> work out, just restore the image and you're back where youy started.
> This process has yanked my *** out of more fires than I can remember.

Already got 1.4TB of total space across four internal drives... with a
320GB system drive, imaging can take hours, and to really be effective
you need to keep at least two previous versions around. Not really an
efficient way to work, or an efficient use of space.