|
| Notices |
Welcome to the DriverHeaven.net forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
 |
Apr 2, 2007, 05:51 PM
|
#1
|
|
DriverHeaven Newbie
Join Date: Apr 2007
Posts: 1
|
ATI MMC 9.16 TV problem
Ok, so Ive been using my AiW 2006 edition capture card for a long time and so far its had no problems. However, I recently upgraded to the MMC 9.16 edition along with the new set of display drivers exc. However, when I go to start up the TV application, it just fails to initalize every time. Before this, I was having some troubles capturing with v 9.02 (I think). The video preview was jerky and delayed, not to mention the audio was so crappy, you couldnt hear anything. When it started to capture, the video went pretty much back to normal, and the audio just dissapeared. I thought maybe updating the MMC and drivers would help, but now it just doesnt work. It tells me to check my display drivers in the Device Manager. I do that, and everythings working fine. Ive tried reinstalling everything except my O/s. My thoughts on whats wrong:
-My O/s partition is 4 Gigs. It only has 500MB left. My mistake, it was my first time and I forgot about programs that must go on the C drive. Maybe the lack of disk space is skrewing with the video buffer? But I have MMC installed on my 200 Gig HDD...
-.NET Framework issues. I heard somewhere that CCC and .NET 2.0 don't really go together. But shouldnt this not interfere with MMC?
-My capture card finally bit the dust. Is the thing just broken? Its sorta old, and I was thinking about upgrading soon anyway.
-My computer hates me. Thats always a viable excuse in todays world.
Anyway, if someone has had this problem before and has found a really nice solution, please speak up. I dont want to have to re-format my entire system just to get my TV to work again...
|
|
|
Apr 3, 2007, 05:12 PM
|
#2
|
|
DriverHeaven Junior Member
Join Date: Oct 2005
Location: Germany
Posts: 27
|
Try consulting system-error reports, possibly it points you to the source of the problem, e.g. 'ati***.ax/xx' etc. failure. Look around the forum for
a. CLEAN re-install of ATI-drivers. It is REALLY VERY important to do that meticulously 'by the book.'
b. IF you have re-installed very thoroughly, the next problem might be some ATI-driver-component called 'atioglxx.dll', that is present in the WDM-drivers of Catalyst 6.5, but changed in the recent ones. Try looking for that file in the .cab-file of the 6.5 WDMs and put it into 'system32'-directory in 'Windows'-folder of your windows-installation - again, for more information on this point, look around the forum.
Good luck - and perhabs just stay away from ATI MMC 9.16 altogether. It really is not worth the trouble... Alternatives: BeyondTV, ChrisTV, Intervideo WinDVR 3, MediaPortal (Highly recommended!!!OpenSource, very good forum-support, extremely feature-rich, professional design and setup, and great quality output - if the system 'carries' the load. System requirements: with hardware-encoding support of the card, MediaPortal requires about 1.8 GHz CPU-power, if the card 'only' does software-encoding, you would need more power, like 2.4 GHz or higher. http://www.team-mediaportal.com/)
So long!
|
|
|
Apr 8, 2007, 01:40 PM
|
#3
|
|
Noise? What noise?
Join Date: May 2005
Location: Canada
Posts: 6,787
|
I'd uninstall everything and go back to CD drivers and software if you want reliable video/PVR
|
|
|
Apr 12, 2007, 11:05 PM
|
#4
|
|
DriverHeaven Newbie
Join Date: May 2006
Posts: 3
|
Have you tried removing DAO along with the display and MMC drivers. I ran into this problem with my AIWX800XT, and thats what fixed it.
|
|
|
Apr 18, 2007, 03:16 PM
|
#5
|
|
Noise? What noise?
Join Date: May 2005
Location: Canada
Posts: 6,787
|
How so?
I also haven't seen an updated DAO/MDAC in quite some time...
|
|
|
Apr 18, 2007, 07:04 PM
|
#6
|
|
DriverHeaven Newbie
Join Date: May 2006
Posts: 3
|
I don,t know if it was an updated version or not, but when i tried to update from MMC 9.15 to MMC 9.16 the TV wouldn't initialize. I spent three days trying uninstalling ATi software, and reinstalling. Finally I tried unistalling DAO along with the rest, and it worked. I really have no idea why it worked. I just thought it might be worth a try.
|
|
|
May 1, 2007, 10:41 PM
|
#7
|
|
Noise? What noise?
Join Date: May 2005
Location: Canada
Posts: 6,787
|
Odd and interesting to be sure.
I haven't found that DAO crap to do anything but interfere with OTHER applications on my system 
|
|
|
May 2, 2007, 02:46 PM
|
#8
|
|
DriverHeaven Newbie
Join Date: Apr 2007
Posts: 3
|
Hi all, not sure where to start. ATI ALL IN WONDER 9600!!! for XP OS, I have lost the tv capabilaty  . In my computor under hardware, in the device manager, under sound, video and game controllers. I found ATI WDM Rage Theater Audio, ATI WDM Rage Theater and ATI WDM TV AUdio Crossbar. Under the properties tab for all 3 of these, it says this device cannot start. (code 10). I can't say 100% sure that it started when about a year ago I installed service pack 2. I will say it has been that long since my ATI TV worked. I have read a lot of comments and heard and tried a lot of suggestions from here and the ATI site among others. None have worked. The only thing I would like to know and it has been asked in many forums, is why ATI has not addressed this problem and if so giving a solution. Has anyone with xp found a solution to fix this problem. Please let me and all othere who are still sane. Thanks, Bobbyhelpme
|
|
|
May 15, 2007, 02:38 PM
|
#9
|
|
Noise? What noise?
Join Date: May 2005
Location: Canada
Posts: 6,787
|
Just for future reference bobby you need only post your problem once and in one relevant thread.
There is no solid answer as to why ATI/AMD has not fixed the issue or why they are seemingly unwilling to do so. I could speculate or guess but I really don't actually know, what with not being clairvoyant yet 
|
|
|
|
|
|