Confusing info... CAT uses .net framework 2.0?

jpinard · Feb 1, 2006, 06:44 AM

Look at this thread: [color=black] [/color][color=white]http://www.quartertothree.com/game-talk/showthread.php?t=24014[/color]

...and you'll see Jason Cross says CCC will work with "either" .net framwork 1.1 OR 2.0... but it runs better with 2.0. Is this correct?

I was under the assumption CCC ONLY used .net framework 1.1

reggis · Feb 1, 2006, 01:45 PM

With CAT 6.1, either .NET (1.1 or 2.0 or both) works. In general, .NET 2.0 is reported to be a better. I orginally installed running 1.1 only, loaded up 2.0 and uninstalled 1.1 (2.0 only) until I loaded the latest update for MCE -- requires .NET 1.1 w/SP. So, I have personally run 6.1 CCC with 1.1 only, 2.0 only and 2.0 and 1.1 frameworks.

MindlessOath · Feb 1, 2006, 01:57 PM

CCC which is the new control panel for ati drivers uses .net

ati ditched the old platform because when vista comes our way they will be ready with a compatible control panel and alot of their testing is already done now.

.net wasnt needed for winXP and in most cases its not really effective, but the whole vista thing is where its at. and no one can complain... unless their whiney crybabbys

i suggest installing .net 1.1 from windowsupdate and then searching for .net2.0 and installing that too. its not bad to have both.

CCC will choose which one to use.

ccc was compiled using 1.1
the 2.0 beta did perform better for a while, when it was installed.
2.0final is now differnt, but until microsoft makes people upgrade to it then CCC cant be complied to 2.0 (compaitiiblity issues with noobs).

so install both, have enough memory for your system and pagefile size should help too. the faster the memory (cas 2 etc) the better. faster hdd will also be good to make a better performing system.

Matth · Feb 1, 2006, 03:56 PM

6.1 CCC, rumnning (at the moment) acceptably with .net 2.0

The annoying "Broadcasteventwindow" at shutdown seems to be less common this way.
It's not just a CCC problem, this annoyance seems to have been reported in many .net based applications, with no real conclusion as to the cause or prevention.

I'd take an "almost as good" alternative on a more reliable runtime platform, over anything using .net. The background junk of CCC that runs even when NOT doing anything with it, means the .net bugs have many times more chance of showing up, than in an application run only when required.

Of course, if the .net application closing issue is ever fully diagnosed and fixed - my guess is that it is some form of synchronization issue, as it sems to be random and o0ften provoked or cleared by other changes.

The_Neon_Cowboy · Feb 1, 2006, 07:03 PM

It complied on 1.1 , it will run on 1.1 or 2.0 , if 1.1 is nt present it
can be force to run on 2.0 other wise with 1.1 and 2.0 it will use the 1.1.

Feb 1, 2006, 06:44 AM	#1
jpinard DriverHeaven Addict Join Date: Jul 2003 Posts: 278 Rep Power: 0	Confusing info... CAT uses .net framework 2.0? Look at this thread: [color=black] [/color][color=white]http://www.quartertothree.com/game-talk/showthread.php?t=24014[/color] ...and you'll see Jason Cross says CCC will work with "either" .net framwork 1.1 OR 2.0... but it runs better with 2.0. Is this correct? I was under the assumption CCC ONLY used .net framework 1.1

Feb 1, 2006, 01:45 PM	#2
reggis DriverHeaven Junior Member Join Date: Sep 2003 Location: South Dakota Posts: 21 Rep Power: 0	With CAT 6.1, either .NET (1.1 or 2.0 or both) works. In general, .NET 2.0 is reported to be a better. I orginally installed running 1.1 only, loaded up 2.0 and uninstalled 1.1 (2.0 only) until I loaded the latest update for MCE -- requires .NET 1.1 w/SP. So, I have personally run 6.1 CCC with 1.1 only, 2.0 only and 2.0 and 1.1 frameworks. __________________

Feb 1, 2006, 01:57 PM	#3
MindlessOath DriverHeaven Senior Member Join Date: Jul 2003 Posts: 1,121 Rep Power: 0	CCC which is the new control panel for ati drivers uses .net ati ditched the old platform because when vista comes our way they will be ready with a compatible control panel and alot of their testing is already done now. .net wasnt needed for winXP and in most cases its not really effective, but the whole vista thing is where its at. and no one can complain... unless their whiney crybabbys i suggest installing .net 1.1 from windowsupdate and then searching for .net2.0 and installing that too. its not bad to have both. CCC will choose which one to use. ccc was compiled using 1.1 the 2.0 beta did perform better for a while, when it was installed. 2.0final is now differnt, but until microsoft makes people upgrade to it then CCC cant be complied to 2.0 (compaitiiblity issues with noobs). so install both, have enough memory for your system and pagefile size should help too. the faster the memory (cas 2 etc) the better. faster hdd will also be good to make a better performing system. __________________ ATI Radeon X800XT PE <---- LOOK UPDATED!! AMD Athlon 2Ghz, nforce2, 512mb ddr3500 LINKS U SHOULD KNOW!!!! DriverCleaner - use every time u install new drivers! ATI driver feedback - to report driver problems Tacticalcenter - my Gaming website and forums ATI 3rd party Optimized Driver Compairison

Feb 1, 2006, 07:03 PM	#5
The_Neon_Cowboy HardwareHeaven Extreme Member Join Date: Dec 2002 Location: U.S.A. Posts: 16,009 Rep Power: 92 System Specs	It complied on 1.1 , it will run on 1.1 or 2.0 , if 1.1 is nt present it can be force to run on 2.0 other wise with 1.1 and 2.0 it will use the 1.1. __________________

Feb 1, 2006, 03:56 PM	#4
Matth Flash Banner Hater Join Date: Jun 2002 Location: UK Posts: 3,426 Rep Power: 93 System Specs	6.1 CCC, rumnning (at the moment) acceptably with .net 2.0 The annoying "Broadcasteventwindow" at shutdown seems to be less common this way. It's not just a CCC problem, this annoyance seems to have been reported in many .net based applications, with no real conclusion as to the cause or prevention. I'd take an "almost as good" alternative on a more reliable runtime platform, over anything using .net. The background junk of CCC that runs even when NOT doing anything with it, means the .net bugs have many times more chance of showing up, than in an application run only when required. Of course, if the .net application closing issue is ever fully diagnosed and fixed - my guess is that it is some form of synchronization issue, as it sems to be random and o0ften provoked or cleared by other changes.