New AMD Dual Core CPU Driver

You didnt try hard enough then...

worksforme.jpg
 
My pc is running great, but COD2 seems to be chugging now. I think it was the AMD patch. I was running 1600x1200 everything max, and it ran fine. Check sig for specs.
 
I downloaded the update for my Venice 3500+ and:

Super Pi Time Dropped for 1m from 39.2, to 38.7 - not sure if that was coincedence though. . .
 
TicTac said:
I downloaded the update for my Venice 3500+ and:

Super Pi Time Dropped for 1m from 39.2, to 38.7 - not sure if that was coincedence though. . .


:confused: im confused :confused:
 
I was under the impression that all the driver did was enable CNQ. Anywho, im doing my own testing right now with superpi 1m.

EDIT* maybe I wont, its for SP2 only and I refuse to get that POS. I forced the old one to install but I cant unpack this one.
 
ooooppss, sorry - didnt realise this was a dual core thread - the new drivers have been released for all the Athlons so I assumed this was its thread.

I am pretty sure the improved time is due to just a fresh reboot or somthing - all though that is my quickest 1m time.
 
burningrave101 said:
What do you mean it doesn't work with Opterons? Try again lol.

Just a stupid mistake on my part...forgot to re-boot after uninstalling the old driver...It refused to install 'til I re-booted...silly me... :p
 
for some reason it wont install for me, I get stuck at the " searching for drivers installation screen and it never goes anywhere" anybody get this?
 
Atleast the original poster will admit their mistakes. Look at the thread title, people.
 
Jakalwarrior said:
EDIT* maybe I wont, its for SP2 only and I refuse to get that POS. I forced the old one to install but I cant unpack this one.

that "pos" is actually microsoft's best update to XP yet, and I'm no f4nboy...
 
aldy402 said:
for some reason it wont install for me, I get stuck at the " searching for drivers installation screen and it never goes anywhere" anybody get this?


off topic - I see that your sig states ou have an "opterOWN 165" - wasn't the opterOWN a 144 and not a 165? Please excuse my ignorance...
 
I switched from 2 7800gtx 256meggers to 1 7900gtx and had problems with alt-tabbing out of CS:S ..screen would flicker from desktop to game rapidly until I alt-tabbed back in ..

I updated to latest greatest AMD drivers and that fixed that little annoyance ..

..next day valve updates their source games of which one bug noted was the particular problem I was having of which updating cpu driver already fixed for me

as far as improvements ..dono . My 3dmark06 score went up by a couple hundred but I updated to latest 90 series beta drivers (64-bit) before updating cpu drivers in an attempt to fix the alt-tab flicker problem ..

 
themulf said:
My pc is running great, but COD2 seems to be chugging now. I think it was the AMD patch. I was running 1600x1200 everything max, and it ran fine. Check sig for specs.

Ever since CoD2's 1.2 patch I've had horrible mouse lag in CoD2, activision support can't help me.. and none of the Dual-core fixes help me.

Edit: This one seems to fix the CoD2 mouse lag for me.
 
fuelvolts said:
off topic - I see that your sig states ou have an "opterOWN 165" - wasn't the opterOWN a 144 and not a 165? Please excuse my ignorance...

Not really. The phras was coined from the first batch of Opterons that had the downclocked FX-57 cores. This was the CANBE0530 stepping. They came in 144 and 146 I know for sure. 148 and 150 probably havd CABNE's also. It was these chips that were hitting 3Ghz on air cooling and low volts. However, being that even newer Opterons seems to clock rather well, its really just a general term, its not assigned to a specific model of CPU. If he wants to call it an OpterOWN... no harm in that. It is a damn good OC. :p
 
Viper87227 said:
Not really. The phras was coined from the first batch of Opterons that had the downclocked FX-57 cores. This was the CANBE0530 stepping. They came in 144 and 146 I know for sure. 148 and 150 probably havd CABNE's also. It was these chips that were hitting 3Ghz on air cooling and low volts. However, being that even newer Opterons seems to clock rather well, its really just a general term, its not assigned to a specific model of CPU. If he wants to call it an OpterOWN... no harm in that. It is a damn good OC. :p

OIC - continue on with normal thread!
 
Argh can you help me i downloaded the file. double clicked it and it said i need to uninstall previous version. so i did that rebooted now when i try installing the new drivers it comes up with "The file C:\boot.ini could not be opened" :s how do i install it?

Thanks
 
Is your boot.ini write protected?

Anyway, the fact that you're getting that message seems to tell me that it is still adding the /usepmtimer to the boot.ini. Thanks :).
 
How would i know if its write protected. I dont even have it obviuosly :s
When i boot my pc it says invalid boot.ini booting from C:\WINDOWS
 
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0 )partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partiti on(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /bootlogo /usepmtimer

Just copy that into a .txt file and call it boot.ini and put it in your c:\windows or c:\ wherever it is looking for it.
 
I have XP home not pro so instead of the txt file being professional can i just change it to home or is it more complicated than that?

Thanks
 
Ok tried that, then tried Home Edition and even tried a backup file that i found of the boot which also didnt work :s

I think i need to change my hdd because its a D when it should be C. How do i do this? i tried right clicking my computer ... manage ... etc but it says i cant change it.
I dont want to have to do reinstall windows again :(

Thanks
 
Well, that's why the driver won't install...it's looking for the boot.ini on the wrong drive (C vs. D). I'm not sure what to tell you on that one. How'd you get that to happen anyway?
 
kirbyrj said:
Well, that's why the driver won't install...it's looking for the boot.ini on the wrong drive (C vs. D). I'm not sure what to tell you on that one. How'd you get that to happen anyway?


It just sorta... happens. I have the same problem. Installed windows, and for some reason the windows drive ended up the E: Drive.
 
Back
Top