• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

AIW 8500DV cannot initialize TV after a reboot

Shagger

Golden Member
Any ideas would be great - I am running an ATI 8500DV. I have the TV set up to record certain shows during the day. When I open the TV appplication it sometimes gives me the error "Unable to initialize TV" and informs me that DMA is not enabled on the drive(s) I am trying to record on. If I clear the error window, the program will record flawlessly. I have triple checked the DMA settings and they are ON for the two drives I record on. I run a A7N8X-DX with a Barton 2500+ OC'ed to 3200+. I boot off the primary SATA channel with a WD 160JB and a SATA adapter and have two WD 160GB drives storing my shows. I am running the latest catalyst drivers and the latest Si3112 drivers as well. I had a HD crash so I rebuilt this from the ground up, so it is not polluted yet with much garbage drivers.

Any body got an idea? TIA.
 
The ATI DMA detection routine basically sucks, and doesn't seem to recognize anything but MS IDE drivers. This in turn affects the ATI scheduler when it runs it prior to recording a show showing the error message (which should not even pop up after the user checks the "don't show this warning again" checkbox). I don't know why it has to run those checks before recording.
 
That is exactly my issue - I have checked that box to not show the error over and over again but no luck. do you think the issue is due to the fact that I updated the driver for the PCI / IDE bus to the latest one from NVIDIA?
 
If they were MS IDE drivers before, installing the nvidia IDE drivers would do it (trigger the error message, which of course is in error itself) So using MS IDE drivers might just do the trick.
 
Originally posted by: rbV5
If they were MS IDE drivers before, installing the nvidia IDE drivers would do it (trigger the error message, which of course is in error itself) So using MS IDE drivers might just do the trick.
Dude, you rock - I rolled back the NVIDIA drivers to the older MCP drivers and we are in bidness! Thanks a lot!

 
Good deal, I'm glad it worked for you.

If ATI would simply fix the IDE detection<--remove), this wouldn't be an issue. I can't believe it's even necissary. Mention that DMA must be enabled for proper capture performance in the MMC release notes and be done with it.
 
Back
Top