Re: AW: Anybody tried ATI CCC 11.6 already? HDTV working fine?
But, that shouldn't make a difference, if it is a AV-Receiver or a TV, that is connected to the HDMI port. Is sound working for you, when you hibernate the computer with the TV disconnected(unplugged cable), then connect the TV while computer is off and then resume hibernate. Is the TV then shown as connected HDMI audio device in the device manager?
AW: Anybody tried ATI CCC 11.6 already? HDTV working fine?
yesterday I tried the 11.6 and removed it after few tests again.
problem for me is the overscan issue: after resume from standby the overscan settings are not restored and I get black borders on my LOEWE 32" FullHD screen. That I have black borders is quite stupid, because it should be able to do a 1:1 pixel mapping.
this is so annyoing, I cannot understand how they (AMD) manage to produce driver updates and sometimes the bug is in, then not, then it... *arghhh*
Yeah I have that stupid overscan bug as well. Even right after installing and rebooting, it was set to 10% and I had to manually re-set it to 0% to get rid of the blackness around the image.
(HDMI -> HDMI connection)
The overscan setting always was kind of dodgy. I also do not understand how they can screw it up so bad. And it's over a year now and they still have not re-enabled the possibility to change the GPU scaling options while running the native resolution of the display.
O Frabjous Joy!
That seems to have done the trick.
Thank you so much for your help and advice, CyberSimian. I hadn't thought of deleting the various folders, but I'll bear that in mind for any future disasters. Now I can record King & Conqueror on Sunday!
Cheers
Ralph
O Frabjous Joy!
That seems to have done the trick.
Thank you so much for your help and advice, CyberSimian. I hadn't thought of...
I've been running MediaPortal on my PC for several years, but the most recent update "MediaPortal 1.38 Release " does...
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working nicely. The reason it failed is because DotNetFrameworkChecker.cs looks in Registry HKLM SOFTWARE\\Microsoft\\NET Framework Setup\\NDP for v4/v4.0 AND v3.5. W10 has V4.0 but not 3.5. MP installer...
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working...
Just tried a new Client-only install on a clean Win10 Pro box. Installer doesnt realise .NET 4 Framework already 'installed' (part...