Windows 7 = no HDCP???

[VirtualLarry]

Not that I have a blu-ray machine in this box anyways, but I've noticed that my ATI 3450 card with HDMI out, no longer shows HDCP in the display info that the television displays upon a mode swtich. When I boot the machine, and it is showing the BIOS, it does show HDCP, as it should. But then when Windows 7 boots, and the Windows display driver takes over, it does a mode-switch and it no longer displays HDCP.

This is with both the out-of-box Windows 7 ATI driver, and the beta driver posted to ATI's web site for ATI cards and Windows 7.

Also, I'm running 64-bit here, not sure if that makes any difference.

Video card is an Asus 3450 PCI-E 256MB card with VGA, DVI, and HDMI outputs. Using the HDMI output currently, hooked up to a 1080P Sceptre 32" LCD TV.

 

[Scotteq]

I would retitle the thread to read: "ATI = No HDCP on Windows 7???"

It's available on Vista, Microsoft didn't remove it. Therefore it's a driver issue.

 

[bsobel]

Originally posted by: Scotteq
I would retitle the thread to read: "ATI = No HDCP on Windows 7???"
It's available on Vista, Microsoft didn't remove it. Therefore it's a driver issue.

Larry is known for misleading thread titles and discussions. This is a driver issue, ask ATI when they will address it.

 

[Crusty]

Originally posted by: bsobel

Originally posted by: Scotteq
I would retitle the thread to read: "ATI = No HDCP on Windows 7???"
It's available on Vista, Microsoft didn't remove it. Therefore it's a driver issue.

Larry is known for misleading thread titles and discussions. This is a driver issue, ask ATI when they will address it.

You are forgetting the most important part... any issue that arises from using an OS is always the fault of the OS maker.. never the driver maker or software vendor! 😉

 

[VirtualLarry]

Originally posted by: Crusty
You are forgetting the most important part... any issue that arises from using an OS is always the fault of the OS maker.. never the driver maker or software vendor! 😉

Considering that the issues are with the driver that is provided out of the box with the OS - then it IS the OS vendor's problem. Since that's where the driver came from.

Therefore it's hardly misleading.

 

[TheStu]

Originally posted by: VirtualLarry

Originally posted by: Crusty
You are forgetting the most important part... any issue that arises from using an OS is always the fault of the OS maker.. never the driver maker or software vendor! 😉

Considering that the issues are with the driver that is provided out of the box with the OS - then it IS the OS vendor's problem. Since that's where the driver came from.

Therefore it's hardly misleading.

Are you sure the driver came from microsoft? I mean, sure that is who gave it to you, but are you saying that because I downloaded the FEAR demo from FilePlanet that FilePlanet made the demo?

Microsoft has been working on 7 for a while, its not exactly secret. So at some point, I would imagine that they gave the beta to ATi and nVidia and said "Hey guys, you know what would be great? If you didn't suck like you did last time, and actually gave us some drivers that you know... worked!"

To which ATi and nVidia replied "Whatever dude, we don't need you we can sell our wares to Apple and whoever makes Linux, they are treasure troves of games just waiting to be tapped... oh wait, no they aren't, we do need you after all."

Now, if this was the latest OS X beta, then yes, I would believe that the drivers came from Apple. But Microsoft realizes that there are about eleventy (11ty) billion graphics cards out there, and those are just the ones that say ATi on them. Not to mention mobile, and integrated solutions and the all-in-wonders (do they still make those) and you are left with Microsoft spending all of their time making included drivers for all those cards and no time making their (Microsoft's) software

 

[ChronoReverse]

The drivers actually come from ATI and are conveniently hosted by MS.

In any case, the older WDDM 1.0 drivers should still work so try downloading the current Catalysts and install that.

 

[Crusty]

Originally posted by: VirtualLarry

Originally posted by: Crusty
You are forgetting the most important part... any issue that arises from using an OS is always the fault of the OS maker.. never the driver maker or software vendor! 😉

Considering that the issues are with the driver that is provided out of the box with the OS - then it IS the OS vendor's problem. Since that's where the driver came from.

Therefore it's hardly misleading.

Sure because Microsoft knows how to write a driver for an ATI designed part. That makes a lot of sense. Did it ever occur to you that maybe at some point MS went to AMD and asked them to build a generic driver they can include in their OS?

 

[TheStu]

Originally posted by: Crusty

Originally posted by: VirtualLarry

Originally posted by: Crusty
You are forgetting the most important part... any issue that arises from using an OS is always the fault of the OS maker.. never the driver maker or software vendor! 😉

Considering that the issues are with the driver that is provided out of the box with the OS - then it IS the OS vendor's problem. Since that's where the driver came from.

Therefore it's hardly misleading.

Sure because Microsoft knows how to write a driver for an ATI designed part. That makes a lot of sense. Did it ever occur to you that maybe at some point MS went to AMD and asked them to build a generic driver they can include in their OS?

Yea, I got that argument covered 🙂