Trouble flashing my X2

[Mr. Smith]

I have my usb bootable stick with win98 file stuff on a la this

I have atiflash files on the usb (ATIFlash, ATIFlash.chg and dos4gw)

Finally I have my modded X2 bios files (3870X2_0.rom and 3870X2_1.rom)

With usb set to boot a get my cmd line - c:\

I type - c:\atiflash

load of instructions for atiflash...

I type - c:\atiflash -p 0 3870X2_0.rom

Then I get error 3870X2_0.rom not found...

I'm supposed to hit enter, then type c:\atiflash -p 1 3870X2_1.rom, enter then reboot.

What am I doing wrong? I only ever flashed nvidia before

 

[Rastalovich]

U tried adding the path to the rom file(s) ?

e.g. c:\atiflash -p 0 c:\3870X2_0.rom

(have no idea about the flags)

Why u flashing ?

 

[Mr. Smith]

Hey Rast, c:\atiflash -p 0 3870X2_0.rom is the correct command it just can't see the .rom for some reason!

Riva doesn't work so you can't apply clocks at boot, you have to manually set each cards OC every boot and it is a PITA.

I'm flashing with a modified bios - higher core/ram clocks (875/975) and higher voltage on the 3d clocks (apparently doesn't work but worth a shot)...

With this bios a light OC is already set, I don't mind manually cranking for benching.

 

[Rastalovich]

Hey Rast, c:\atiflash -p 0 3870X2_0.rom is the correct command it just can't see the .rom for some reason!

If ur prompt > is c:\> it should see the file, if it`s on c:\ (ur usb pen)

If it`s in c:\, but not seeing it, u can insert the c:\ path direction infront of the 3870X2_0.rom to `make` it see it

 

[equk]

I used ATIWinflash to flash my custom BIOS onto my X1900XT just made sure no antivirus etc was running just in case and it was fine.

 

[Mr. Smith]

Winflash makes my system lag hard and nothing happens. I'll try it with my av off.

Rast, I'll give your method a shot too. Fingers crossed lol

Edit:

Winflash 2.0.0.2 doesn't work with or without av on/off. Just makes my pc spazz out.

Edit: Rast wins a cookie, and some reps

Flashed

 

[Rastalovich]

Want chocolate chips, with some of those mashed nuts.

Not if it`s chocolate in nature tho. They`re ok with nothing else added, perhaps some nuts.

 

[Mr. Smith]

Bump.

Er, help! I flashed the card and all seemed well on XP, rocked Crysis and other games with no issues. The settings I flashed weren't even my max and passed hours of atitool artifact scanning and various hours of gaming. 875/975 were the final figures and everything was fine in XP gaming.

Since moving to Vista I've been slow to install everything but last night I thought I'd have a taste of dx10 gaming. I set everything to 'very high' and dropped the res down to a pretty small size... I struggled to see any difference over the dx9 .cfg tweak :/ Then I noticed a few weird effects in the clouds... Artifacts

Then I knocked down to high settings and to a more reasonable res. Artifacts. Lots of them.

What now? Re-edit the bios back and flash back to stock and re-test? If faulty RMA and deffo get a refund this time.

Or is this some 64bit issue that I haven't forseen? I read you need to alter file X in 3dm06 to make it work in Wista 64... Again, slow to install stuff this time so haven't bothered to try.

Sigh. Might have to get a GX2. Or switch back to XP, or vista 32, or some combination of everything mentioned in this post.

 

[JN]

Can you not just underclock the card via software (so that its back to stock settings) and re-test?

 

[Mr. Smith]

Can you not just underclock the card via software (so that its back to stock settings) and re-test?

Well technically yes, if I wanted to make my life easier... Which I do!

The thought did occur to me but I lost it somewhere between rage/frustration.

So I put on Flight of the Conchords which is damn funny.

Thanks mate.

Plan - 1. atigpu tool clock down. Check dx10 crysis for artifacts. No artifacts, find new vista stable settings (why they aren't the same is beyond me), re-flash.

2. Artifacts at stock. Re-flash to old bios settings and rma for refund. Wait for gx2.

 

[Rastalovich]

Just on the point of 3dmark06. Being as 1.02 didn`t want to know, I went with: (Vista 64)

Newest 1.10 version

Feburary Hotfix

Run as Admin

.. as per the website, worked fine.