• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Annoying ATI prob

Man of Honour
Man of Honour
Joined
18 Oct 2002
Posts
12,264
Location
Cotswolds
I upgraded from XP Home to XP Pro, and since then I can't start the Catalyst Control Center. I have googled the problem and it seems common, I have tried every solution I can find, but still I have the same problem.

The only reason I want to go into CCC is so I can have my desktop span both monitors, so games see both screens as one 'surface'. I can't do this by just extending the desktop in windows display settings.

Is there any way to set this up without using CCC?
 
CCC problems usually = .net framework problems. Try reinstalling .net 1.1.

An alternative to CCC would be to try ATI Tray Tools? Can't remember what monitor options it has though.
 
If you've done a fresh install, .net 1.1 isn't include with the install. So you'll need it. Personally though I noticed slow down, so just after a fresh install didn't install .net, then omega drivers. a lot quicker now. Dunno if you can do the same with Omega though (dual screen)
 
Fanatic said:
CCC problems usually = .net framework problems. Try reinstalling .net 1.1.

An alternative to CCC would be to try ATI Tray Tools? Can't remember what monitor options it has though.

Tried reinstalling .net 1.1, and 2.0, no joy. I also ran driver cleaner, and the ATI removal tool. I reinstalled the driver and still I get the same problem. When I go into Task Manager, CLI.exe dissapears when I try to start CCC. Restarting the runtime doesn't work either, CLI.exe starts, then dissapears again.

I have installed Tray Tools, but there is no option for a single display spanned across 2 monitors.
 
DreXeL said:
Tried reinstalling .net 1.1, and 2.0, no joy. I also ran driver cleaner, and the ATI removal tool. I reinstalled the driver and still I get the same problem. When I go into Task Manager, CLI.exe dissapears when I try to start CCC. Restarting the runtime doesn't work either, CLI.exe starts, then dissapears again.

I have installed Tray Tools, but there is no option for a single display spanned across 2 monitors.

Thats the main reason i use CCC aswell so i can stratch accross the two monitors! Its a shame that tray tools doesnt do this.

You've pretty much done everything that i can offer to the discussion.

I would have said Net. Framework also.
 
Dont suppose your virus scanner is NOD32 is it?

This caused a few problems for me. In the end it was easy enough to fix.
 
fozzy said:
Dont suppose your virus scanner is NOD32 is it?

This caused a few problems for me. In the end it was easy enough to fix.

Nope, Blueyonder PC Guard. Shutting that down doesn't help.
 
You can set dual monitors with tray tools. Right click the tray tools in your task bar, then select display > extended desktop. You can set the resolution & refresh rates for the monitors via your windows properties, display, advanced.
CCC refused to even open for me, so tray tools was the only way to get dual monitors working.
 
No, that's not the same thing. That gives two seperate displays of 1280x1024 (or whatever selected) with the second monitor just displaying an extra 'space' for the desktop. Games won't span both monitors doing it that way.

The span option in the CCC combines both displays into one single display of 2560x1024. Windows and other apps just see one big 2560x1024 display area, rather than two seperate monitors, therefore games span both monitors as if it were one monitor.
 
May i suggest a complete install of Windows again followed by .NET, followed by CCC.

I know it seems drastic, but when i've had this issue it was down to .NET issues too.

A nice clean out may do the trick.

M
 
noxidjkram@hotm said:
May i suggest a complete install of Windows again followed by .NET, followed by CCC.

I know it seems drastic, but when i've had this issue it was down to .NET issues too.

A nice clean out may do the trick.

M

Well yeah that was what I was going to do as a last resort, I was hoping to avoid it though :(
 
Back
Top Bottom