When I had an ATI Radeon 9800XT Pro in use, I didn't use it...
I stuck by the "traditional/older" model of their wares, & blew-off using the .NET coded "Catalyst Control Center" larger download driver & tools edition...
Why?
Because .NET is FINE imo, for developing business applications (due to its high level of abstraction & "macro'd" commands (many commands done in 1 single commandline in code) so development is faster & also more secure (this is a BIG plus in .NET code) & stable (memory cleanup built-in, like Java "garbage collection"))... but, I personally think that is about all I would want coded in it, because of those factors.
(ASP.NET for instance, is one area where this "rule" of mine does not hold true - it outperforms "normal" ASP pages, & is much like ISAPI (IIS extensions via DLL) for speed, but far better "anti-memory leakage" control built into its code (which was a problem in ISAPI, for all of its speed, you needed to reboot your servers sometimes if it was leaky/faulty code)).
Now, today's CPU's tend to make up for its "interpreted code" speed (slower), but I still would want "powertoys/tweaking tools" coded in faster languages personally... you don't need to build smallish apps in 'safe' languages (albeit far slower too), because debugging them or "delinting them" (tracking memory allocations & deallocating each properly) should NOT be that "big of a hassle" imo @ least.
(That control panel for instance? I'd wager, even if done in C++?? Is WAY under 1,000 lines of code, by a LONG shot! That is manageable, easily, for checking your code for proper memory allocation-deallocation imo @ least, no need to write in managed code/clr imo...)
.NET apps have their place, imo @ least, mainly in line-of-business work, where accuracy &/or security of the code running outweighs the importance of sheer speed (again, ASP.NET is the 1 area that "overturns" this rule)...
After all, it's money & lives + personal info. often riding on it.
The code for this type of app? IMO, @ least, does not fit that 'mold/category'... you don't NEED classes (& thus, objects, & EVERYTHING in .NET is an object, even strings) for this type of app, because class/object use encapsulation comes with added "bulk/bloat" as well - & I don't need it for "hello world" type apps!
(Yes, this control center, no matter HOW it was coded in each version is someone's hard work so I am not out to "put it down", but it does not require the weight inherent in objects imo, for this level of work - I'd rather have sheer speed, so that I know apps read/write their settings quickly to the registry etc., as quickly as possible (disk caches lag this too though, somewhat, in write-back modes even more)).
* To each his own I suppose, but I always went to the C++ coded (assuming that was the language tool they used, MSVC++ probably) versions when I was an ATI vidcard user.
APK
P.S.=> Plus, I also think it's largely if you are a "Creature-of-Habit" as well - NVidia's latest found of "Forceware 90 series" drivers have a new control center as well... do I use it? Nope.
Sure - It's probably decent & wizards-driven & all that (attempting for better ease-of-use, much like Classic View CONTROL PANEL in the OS, vs. the newer XP models, very wizardish too iirc) but I am just WAY used to the "old-school method" of doing things in this area, w/ the older toolsets... apk