On Sat, 08 Apr 2006 19:48:01 +0100, NoNoBadDog! <(E-Mail Removed)> wrote:
>
> "Aussie" <****(E-Mail Removed)> wrote in message
> news:4437b1a6$0$20636$(E-Mail Removed)...
>>
>> "Mike" <(E-Mail Removed)> wrote in message
>> news:f8DZf.28573$(E-Mail Removed)...
>>> did you remove all traces of of the 6.2 Catalyst before going to 6.3?
>>> Since the ATI drivers aren't written very well you have to remove all
>> traces
>>> from the registry, just uninstalling them won't work. The ATI removal
>>> tool
>>> works pretty good but a third party app like Driver Cleaner works even
>>> better.
>>>
>>> "Paul M" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>> I installed Catalyst 6.3. When my computer comes out of standby, I get
>>> a
>>> BSOD.
>>>
>>> I remove Catalyst 6.3 and go back to 6.2 and the problem goes away.
>>>
>>> Anyone else experiencing a similar problem when resuming from standby
>>> with
>>> 6.3 installed?
>>>
>>>
>>
>> What a load of bull ****.I have never ever delete a driver,always
>> install
>> the new1 over the old1 'till now never had any trouble what so ever...
>>
>>
> *YOURS* is the load of bullshit! You should ALWAYS remove the old
> drivers
> first; at least the intelligent people do so...which explains why you
> never
> delete yours...
> what a dumbass.
>
> Bobby
>
>
Keep it friendly guys! ;-) My long experience gives me some insights.
I'll share them, so I can get shouted at too!
9 times out of 10 you probably can get away with installing over the top,
however it IS best practice to remove the old drivers and the control
panel first. This is established fact, from many user's hard won
experience and is ATI's own advice. It is also common sense to have a
registry/system backup to go to. I have to admit that moving 6.2 to 6.3
I'd have been likely to try over thr top first out, but when I went from
5.11 to 6.3 I decided that was too big an ask and I removed everything
first. The OPs problem with standby is not documented at ATI or elsewhere
in this newsgroup that I can determine, so it sounds like bad luck and
possibly a clean-up of the driver installation and another go at the
install might help.
On the subject of common sense and balancing the risk to your system,
sticking my neck out, there is a lot of gratuitous upgrading of drivers
done for no obvious reason and sometimes it isn't worth the potential
hassle if the release notes don't offer anything of benefit to the user's
particular system. If it ain't broke.... It doesn't pay to sit many
releases behind current, but why always rush to go 6.2 to 6.3, or 6.3 to
6.4? The benchmarks published so far for 6.4 suggest that it is
predominantly a bug-fix release, so if you don't have one of the bugs,
what is the point..... see what I mean?
To the OP - good luck with fixing your problem. At the risk of
contradicting myself, now that 6.4 is out perhaps you can go from 6.2 to
6.4 instead and do consider uninstalling the old driver, even if you don't
use a clean utility. Lastly, as I said, what is wrong with 6.2 for the
time being? Anyway, all the best.
--
Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0615-3, 14/04/2006
Tested on: 15/04/2006 12:27:06
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
Similar Threads
