Prev: Mobility X1600 drivers
Next: Radeon 9650 windows compatible?
From: First of One on 8 Sep 2006 17:40
"Chuckg" <glasgowc1(a)gmail.com> wrote in message
news:1157688210.682397.30100(a)m79g2000cwm.googlegroups.com...
> The gamma settings between fullscreen 3D and desktop are different.

Does the flicker remain when you set both the desktop and fullscreen 3D
gamma value to the defaults (i.e. 1.0)?

> Re: D3D, I have DirectX 9.0c installed, it came with the original XP
> SP2 install.

Microsoft updates DirectX every two months or so, without rolling the
version number. The latest one was released in August 2006. However, I don't
think this is the cause of your screen flicker.

--
"War is the continuation of politics by other means.
It can therefore be said that politics is war without
bloodshed while war is politics with bloodshed."



From: Chuckg on 8 Sep 2006 19:23
First of One wrote:

> "Chuckg" <glasgowc1(a)gmail.com> wrote in message
> news:1157688210.682397.30100(a)m79g2000cwm.googlegroups.com...
> > The gamma settings between fullscreen 3D and desktop are different.
>
> Does the flicker remain when you set both the desktop and fullscreen 3D
> gamma value to the defaults (i.e. 1.0)?

Yes. The flicker remains when I set *everything* back to the defaults
in Catalyst Control Center, aamof.

Oddly enough, it appears that my old gamma settings are still being
applied, as the 3-D games I started to test this theory (KOTOR, KOTOR
II) were still as bright.

Maybe that's what's messing it up -- somehow, in all the ATI Catalyst
Control Center installing and uninstalling, the original profiles have
gotten nailed in there, and the current profiles conflict. I wouldn't
have the faintest idea how to confirm this guess, or resolve it if it's
true.

I do know that using ATI Uninstall utility to strip everything out and
reinstalling the ATI driver set from scratch hasn't worked so far, tho.

I really hope your bag of tricks ain't empty yet. *g*

> > Re: D3D, I have DirectX 9.0c installed, it came with the original XP
> > SP2 install.
>
> Microsoft updates DirectX every two months or so, without rolling the
> version number. The latest one was released in August 2006. However, I don't
> think this is the cause of your screen flicker.

It's not. I DL'ed the latest DirectX redist from Microsoft (Aug 2006)
and put it in -- no change.

--
Chuckg

From: Chuckg on 8 Sep 2006 19:40
Some more data for anyone.

I cleared out my Events log, then deliberately triggered the failure
again, twice.

Here's a dump of my ACE Event Log:

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000004:
2006-09-08 18:35:45:218 Exception: Object reference not set to an
instance of an object.
Exception Called by: ATI.ACE.CLI.Component.Icomponent.Icomponent::Run
processID:00488
threadID:(CLIIcomponent ) domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000003:
2006-09-08 18:35:45:218 ATI ACE Runtime not found!
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000002:
2006-09-08 18:35:45:218 Can't connect to Runtime
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:45
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000001:
2006-09-08 18:35:45:203 Exception <Runtime(a)2308>: No connection
could be made because the target machine actively refused it
Exception Called by:
ATI.ACE.LOG.Foundation.Service.Service::ConnectToObjectImpl
processID:00488 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(LOG.Foundation.Service, Version=1.2.2405.30446,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000003:
2006-09-08 18:35:42:718 Exception: Object reference not set to an
instance of an object.
Exception Called by: ATI.ACE.CLI.Component.Icomponent.Icomponent::Run
processID:01952
threadID:(CLIIcomponent ) domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
************************************************************************************************************************

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000002:
2006-09-08 18:35:42:687 ATI ACE Runtime not found!
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:01952 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:35:42
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000001:
2006-09-08 18:35:42:656 Can't connect to Runtime
Error Called by:
ATI.ACE.CLI.Component.Icomponent.Icomponent::ConnectToRuntime
processID:01952 threadID:(CLIIcomponent )
domainName:(cli.exe )
assemblyName:(CLI.Component.Icomponent, Version=1.2.2405.30454,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000013:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3 Method:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000012:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3 Method:
ATI.ACE.CLI.Aspect.OverDrive3.Graphics.Dashboard.DB_OverDrive3
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM ACEEventLogSource Information None 0 N/A GLASGOWC1 0000000011:
2006-09-08 18:33:23:296 Target:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2 Method:
ATI.ACE.CLI.Aspect.DeviceDFP2.Graphics.Dashboard.DB_DeviceDFP2
Error Called by:
ATI.ACE.CLI.Component.Dashboard.DashboardForm::DashboardForm_Closing
processID:03424 threadID:(CLIDashboard )
domainName:(cli.exe )
assemblyName:(CLI.Component.Dashboard, Version=1.2.2405.30455,
Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------

9/8/2006 6:33:23
PM AC
From: Danny G. on 9 Sep 2006 08:34

"Chuckg" <glasgowc1(a)gmail.com> wrote in message news:1157757791.809511.226150(a)h48g2000cwc.googlegroups.com...
> First of One wrote:
>
>> "Chuckg" <glasgowc1(a)gmail.com> wrote in message
>> news:1157688210.682397.30100(a)m79g2000cwm.googlegroups.com...
>> > The gamma settings between fullscreen 3D and desktop are different.
>>
>> Does the flicker remain when you set both the desktop and fullscreen 3D
>> gamma value to the defaults (i.e. 1.0)?
>
> Yes. The flicker remains when I set *everything* back to the defaults
> in Catalyst Control Center, aamof.
>
> Oddly enough, it appears that my old gamma settings are still being
> applied, as the 3-D games I started to test this theory (KOTOR, KOTOR
> II) were still as bright.
>
> Maybe that's what's messing it up -- somehow, in all the ATI Catalyst
> Control Center installing and uninstalling, the original profiles have
> gotten nailed in there, and the current profiles conflict. I wouldn't
> have the faintest idea how to confirm this guess, or resolve it if it's
> true.
>
> I do know that using ATI Uninstall utility to strip everything out and
> reinstalling the ATI driver set from scratch hasn't worked so far, tho.
>
> I really hope your bag of tricks ain't empty yet. *g*
>
>> > Re: D3D, I have DirectX 9.0c installed, it came with the original XP
>> > SP2 install.
>>
>> Microsoft updates DirectX every two months or so, without rolling the
>> version number. The latest one was released in August 2006. However, I don't
>> think this is the cause of your screen flicker.
>
> It's not. I DL'ed the latest DirectX redist from Microsoft (Aug 2006)
> and put it in -- no change.
>
> --
> Chuckg


This might be way off in left field but the I've noticed less flicker issues when
"Display Detection Option" in CCC is set to "use manual detection."


Dan


From: Chuckg on 9 Sep 2006 10:10
Danny G. wrote:

> This might be way off in left field but the I've noticed less flicker issues when
> "Display Detection Option" in CCC is set to "use manual detection."

Thanks for trying, but it didn't work.

--
Chuckg

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Mobility X1600 drivers
Next: Radeon 9650 windows compatible?