ATI driver question...  

dsperber said:

This seems to have finally turned off the event logging for me.

Thanks, will have a good work through that.

Regards....Mike Connor

Cr00zng said:

We can agree to disagree about the nature of the reasons...


I guess that's how MPAA and others prefer to "control" computers; as little information as possible...

Indeed, it's much the same as hiding recording devices on sound cards etc.

They are banking on the vast majority of people not being able to use them. This of course makes things very much more difficult for legitimate users, and doesn't stop the pirates anyway.

The entertainment industry as a whole has tried to ignore and suppress these things, and they have been buried under an avalanche as a result. They are still attempting to fight rearguard actions all over the place. Terrified as they are of losing yet more revenue.

They would have been better advised to find ways and means of distributing their material sensibly on the web.

Just how it is...........

You know what will happen if anybody ever discovers the secret of eternal youth? ( Or even a reasonable facsimile thereof ). The insurance companies will fight them to the death! :)

Regards....Mike Connor

Cr00zng said:

Well, a little grunt doesn't hurt every once in awhile and please don't get me started on the insurance companies

The issue with the log had been resolved when this thread was started; I was hoping that someone has some insight into the inner working of the HDCP with ATI/MS drivers. It seems that this forum may not be the appropriate one to look into this.

On the bright side....

There's this registry key as well, related to AMD/ATI:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag]

That's probably where some of the events that generate these logs is controlled. The sort of funny entry is:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\amdkmdag\MosquitoNoiseRemoval_NA]

It's currently set to "0"; do you think if I set it to "1", then I won't hear the mosquitoes this summer?

You won't here them coming but it won't stop them from biting.

Jim

dsperber said:

Turns out modifying only the "CurrentControlSet" registry entry was NOT sufficient to stop this stuff.

Searching on the AMD Forum, it seems you really do need to modify ALL of those ControlSet versions of ATIerecord (not minding if you don't have all of them, like ControlSet003).

Furthermore, there are additional entries for ATIerecord that need to be set to 0, so you need to do a "find" and "find next" repeatedly, and set each one you find to 0.

=========================================

For Windows 7 Click Start then type regedit
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Atierecord]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atierecord]


Right click on eRecordEnable and modify the value to 0 for all of these, don't worry if you don't have the same amount of keys.

After looking more there's more ATIeRecord entries than these, so you might want to use the search function, Edit at the top of regedit, then Find - type in atierecord (dont forget the e in the middle of ati and record). Then hit F3 to "Find Next" and keep doing that until you find every atierecord key and set it the value to 0.

===================================

This seems to have finally turned off the event logging for me.

I changed just the Current Control Set but had to restart for the log to stop.

Jim