Problems with Catalyst 5.6

  • Thread starter Thread starter Andrew R. Gillett
  • Start date Start date
A

Andrew R. Gillett

Just installed Catalyst 5.6, having previously been using Catalyst 4.7.

Now I get very sluggish screen updates in Windows. When Windows first
starts, the screen goes blank several times, each time it redraws the
background which takes about two seconds. There is also slowdown
whenever I open a menu with transparency effects (e.g. the start menu or
any drop-down menu)

The Catalyst Control Center fails to start, I get this:

cli.exe - Application Error
The application failed to initialize properly (0xc0000135). Click on OK
to terminate the application.


System is Athlon 64 3500+ with Radeon X800 Pro (256Mb)
 
In said:
Just installed Catalyst 5.6, having previously been using Catalyst 4.7.

Now I get very sluggish screen updates in Windows. When Windows first
starts, the screen goes blank several times, each time it redraws the
background which takes about two seconds. There is also slowdown
whenever I open a menu with transparency effects (e.g. the start menu or
any drop-down menu)

The Catalyst Control Center fails to start, I get this:

cli.exe - Application Error
The application failed to initialize properly (0xc0000135). Click on OK
to terminate the application.
Click to expand...

After a reboot, the slowdown isn't happening any more, but cli.exe still
crashes.
 
Andrew said:
After a reboot, the slowdown isn't happening any more, but cli.exe still
crashes.
Click to expand...

I would be insulting your intelligence if I asked whether you installed
the required .NET framework to support the CCC??


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0523-8, 11/06/2005
Tested on: 12/06/2005 01:21:23
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
 
Sometime on, or about Sun, 12 Jun 2005 01:08:54 +0100, Andrew R. Gillett
wrote:
Just installed Catalyst 5.6, having previously been using Catalyst 4.7.

Now I get very sluggish screen updates in Windows. When Windows first
starts, the screen goes blank several times, each time it redraws the
background which takes about two seconds. There is also slowdown
whenever I open a menu with transparency effects (e.g. the start menu or
any drop-down menu)

The Catalyst Control Center fails to start, I get this:

cli.exe - Application Error
The application failed to initialize properly (0xc0000135). Click on OK
to terminate the application.

System is Athlon 64 3500+ with Radeon X800 Pro (256Mb)
Click to expand...

Did you totally uninstall the old drivers before installing the new ones?
I've had problems in the past when I hadn't done that.

The ATI Uninstall Utility that's in the Add or Remove Programs does a
pretty decent job of doing this. Reboot after uninstalling and cancel any
Windows prompting for new video drivers. Then install the Catalyst 5.6
drivers.

Sam
 
Now I get very sluggish screen updates in Windows. When Windows first
Whenever I've updated to new or different Catalysts, XP always seems to do
this sluggish screen rewrite after the first boot on install. It always goes
back to normal on the second reboot. It seems to be a common "feature". The
only time it stayed that way was the first time I installed an ATI card
switching over from Nvidia a couple of years back. The reason was my failure
to remove all traces of the Nvidia drivers and dll's. Once I did this, it
acted normally. I also thought there was something wrong because there was
no video card BIOS "splash" on bootup, but upon googling I found that ATI
cards just don't do it.
 
Sometime on, or about Sun, 12 Jun 2005 01:08:54 +0100, Andrew R. Gillett
wrote:


Did you totally uninstall the old drivers before installing the new ones?
I've had problems in the past when I hadn't done that.

The ATI Uninstall Utility that's in the Add or Remove Programs does a
pretty decent job of doing this. Reboot after uninstalling and cancel any
Windows prompting for new video drivers. Then install the Catalyst 5.6
drivers.

Sam
Click to expand...


Yes, speaking as one who's always taken care about removing old ATI
stuff before changing drivers, the ATI Software Uninstall Utility
seems to to an excellent job, Sam. I use it the same way as you do -
to remove remains after uninstalling, rather than as an uninstall
method itself, as some people seem to do.

I'd also recommend deleting the ATI unpacking folder (usually C:\ATI)
after using the Uninstall Utility.

Patrick

<[email protected]> - take five to email me...
 
patrickp said:
Yes, speaking as one who's always taken care about removing old ATI
stuff before changing drivers, the ATI Software Uninstall Utility
seems to to an excellent job, Sam. I use it the same way as you do -
to remove remains after uninstalling, rather than as an uninstall
method itself, as some people seem to do.

I'd also recommend deleting the ATI unpacking folder (usually C:\ATI)
after using the Uninstall Utility.

Patrick

<[email protected]> - take five to email me...
Click to expand...

I always burn the ati install directory to a cd. Even though I will never
use the terrible 5.6 catylish crashers again.

I notice that without that net thingy. Cli.exe will produce 3 error
messages, unable to load blah, blah, still I was able to get a shut down
without a hang...put the net thingy back, same good ole shut down hang, for
a few seconds, ending program...dosnet....

When back to 5.3...just a few seconds, from my ghost cd...

my 2 cents
 
I always burn the ati install directory to a cd. Even though I will never
use the terrible 5.6 catylish crashers again.

I notice that without that net thingy. Cli.exe will produce 3 error
messages, unable to load blah, blah, still I was able to get a shut down
without a hang...put the net thingy back, same good ole shut down hang, for
a few seconds, ending program...dosnet....

When back to 5.3...just a few seconds, from my ghost cd...

my 2 cents
Click to expand...
Well, it's been a long time since I had any error messages or hangs on
installing new (or old) ATI software, and I usually try new stuff even
if I decide not to keep it. AIR there was a problem with several of
the 3.x's that I used to have to solve with a manual install and, of
course, it's often a problem trying to get the TV/Video In apps to
work with OEM cards. 5.6 and MMC 9.08 went in without a squeak.
However, I have no intention of going anywhere near the Control Center
and .net...

Patrick

<[email protected]> - take five to email me...
 
Yes, speaking as one who's always taken care about removing old ATI
stuff before changing drivers, the ATI Software Uninstall Utility
seems to to an excellent job, Sam. I use it the same way as you do -
to remove remains after uninstalling, rather than as an uninstall
method itself, as some people seem to do.

I'd also recommend deleting the ATI unpacking folder (usually C:\ATI)
after using the Uninstall Utility.

Patrick

<[email protected]> - take five to email me...
Click to expand...

I never let ATI install into the root directory... always change it to
c:\program files\ATI instead. And, yes I do wipe that out when it's no
longer needed. It writes the new drivers into a sub-folder of a different
name anyhow, so there's no danger of them mixing.

A long time ago, I used to just install the new drivers right over the old
ones. Once I started noticing slow re-drawing of the screen and other
oddities, I started doing a total uninstall first. It takes longer, since
you have to reboot after doing the uninstall. But the end results are worth
it.

Sam
 
I would be insulting your intelligence if I asked whether you installed
the required .NET framework to support the CCC??
Click to expand...

That was the problem. However, I don't consider it to be a matter of
intelligence, just poor software design. I don't recall the installer
telling me I needed to install the .NET framework. And even if it had,
when I ran it it should have been able to tell me "You need to install
the .NET framework" rather than quitting with an unhelpful error
message.

I've now uninstalled it, since it was doing a number of annoying things
such as trying to access the internet, and failing to shut down
properly.
 
Back
Top