List of DFI NF4 Ultra/SLI Bios

[NiCKE^]

http://home.no/trac3r/dfi_lanparty_n...ultra_bios.htm made this today might be to help for someone.

[pershoot]

i will update cdrom image tonight with 441's and the older 2 misc bioses which are missing from it.

[Smokin_Joe]

http://home.no/trac3r/dfi_lanparty_n...ultra_bios.htm made this today might be to help for someone.

Which is better, the 325 or 331-3 for bh-5? Anyone have any results. I got the 331-3 working great but in that list 325 says optimised for bh-5.

[NiCKE^]

I don't know Smokin_Joe because my Winchester have been dead for about a month now

[Onepagebook]

why is this thread not sticky?

[vlad]

why is this thread not sticky?

I Agree!!!!!!!!!!

[NiCKE^]

Should be sticky and why isn't OPB on his chat clients so I can ask him some questions

[conrad.maranan]

I'll sticky this thread in the Best of AMD section tonight. I'd like for a few more people to see my post so that they'll know where to look for it.

[Onepagebook]

I'll sticky this thread in the Best of AMD section tonight. I'd like for a few more people to see my post so that they'll know where to look for it.

Thank you buddy

[Fumle]

Today i went to shop where i boguht my DFI SLi-DR for getting an replacement, but he wanted to test it, he also used an pair of OCZ VX PC3200 and it worked fine with Dual Channel, he did an bios update with some kind of BIOS, DRAM setting etc etc

I went home plugged it in to my system, but my own OCZ VX PC3200 kit cant run Dual Channel, i believe that my VX memory is an very early kit

The VX memory works just fine with Dual Channel in an MSI K8N Neo2

I think this this could be an BUG with all the "BUGGED" DFI S939 Boards, or not ??

[Quanticles]

3/4 of the posts on here were just about becoming sticky, too bad we cant go back and delete all of those =P

[Quanticles]

The link to the 331-3 bios seems to be broken. Can someone email me the file? Plz PM

[vlad]

The link to the 331-3 bios seems to be broken. Can someone email me the file? Plz PM

Try here. Rebels Haven BIOS Page

[Quanticles]

u da man =)

[vlad]

I aim to please.

[pershoot]

refreshed cdrom image with 119, 316, 441-1 to 3.

[FireDragon]

Thnxs for the sticky...

Dragon

[rocka]

anyone experienced the 4.14 and newer versions? and any improvements on 3.31-3 esp. from vlad who aims to please ?

[vlad]

anyone experienced the 4.14 and newer versions? and any improvements on 3.31-3 esp. from vlad who aims to please ?

Nope. Sorry but right now Im down I flashed from 3.13-3 to 4.14-1 & something
went wrong Luckly I had two spair chip's so Ill be up in a day or two.

[pershoot]

hey you guys like the idea of these added to the cdrom image:

NTFS support
a possible mini linux running prime95
network support (tcp/ip & SMB)
ramdrive/workarea support
cdrom support

??

i need to clean up the batch and reword the instructions also...

[Super Nade]

Guys,

I see many BIOS'es for TCCD, what do you recommend for my 512 x 2 PDP XBLK ?
I can't even hit 275 Mhz with the 3-25 BIOS. Can you guys please recommend something else?

[Frodin]

Hi, I've got a problem, not sure if it's specific to the bootable BIOS cd rom, but i tried using it to flash my BIOS (since I could not get the Diamond Flash Image floppy to work, tried 3 different floppy disks that all read/wrote fine on another computer). I chose "load optimized defaults" and selected boot from cd rom in the BIOS prior to booting from the bootable cd rom. I saved and restarted the system, got into the flash menu and went for "flash 310" to flash to the 310 BIOS. It started writing the new BIOS, and got about 1/5 of the way, but suddenly there was an error message saying "your BIOS ROM is write protected" and the flashing process stopped.
I had no way of exiting the flash- program other than doing a reset, and now this message appears every time i try to start the computer:
"BIOS ROM checksum error
Detecting floppy drive A media.
INSERT SYSTEM DISK AND PRESS ENTER"
So I guess the BIOS ROM is screwed. I tried resetting the CMOS, but it didn't make any difference. I followed the flash procedures to the point (loading optimized defaults, selecting boot from cd rom, saving and restarting) as per this link on DFI-street and the first post in this thread. I hope any of you got a clever idea as to what went wrong with my flash. I will make a similar thread on the DFI-street forum.
Sincerely, Frodin

[NiCKE^]

Tried to follow my AWDFLASH guide?

[pershoot]

Hi, I've got a problem, not sure if it's specific to the bootable BIOS cd rom, but i tried using it to flash my BIOS (since I could not get the Diamond Flash Image floppy to work, tried 3 different floppy disks that all read/wrote fine on another computer). I chose "load optimized defaults" and selected boot from cd rom in the BIOS prior to booting from the bootable cd rom. I saved and restarted the system, got into the flash menu and went for "flash 310" to flash to the 310 BIOS. It started writing the new BIOS, and got about 1/5 of the way, but suddenly there was an error message saying "your BIOS ROM is write protected" and the flashing process stopped.
I had no way of exiting the flash- program other than doing a reset, and now this message appears every time i try to start the computer:
"BIOS ROM checksum error
Detecting floppy drive A media.
INSERT SYSTEM DISK AND PRESS ENTER"
So I guess the BIOS ROM is screwed. I tried resetting the CMOS, but it didn't make any difference. I followed the flash procedures to the point (loading optimized defaults, selecting boot from cd rom, saving and restarting) as per this link on DFI-street and the first post in this thread. I hope any of you got a clever idea as to what went wrong with my flash. I will make a similar thread on the DFI-street forum.
Sincerely, Frodin

very wierd. thats a first. u can rescue with a floppy. make a bootable dos floppy and place awdflash.exe and bios file on there. then create an autoexec.bat file and in there put:

@echo off
awdflash.exe BIOSFILE.BIN /py /sn

replace BIOSFILE.BIN with filename

when it finishes clear cmos for a good amount of time.

[Frodin]

very wierd. thats a first. u can rescue with a floppy. make a bootable dos floppy and place awdflash.exe and bios file on there. then create an autoexec.bat file and in there put:

@echo off
awdflash.exe BIOSFILE.BIN /py /sn

replace BIOSFILE.BIN with filename

when it finishes clear cmos for a good amount of time.

Thanks for the quick reply!
How do i create an autoexec.bat file? In the DOS- prompt when I boot from the floppy? (presuming it actually works... I remember fooling around in the autoexec.bat file in the win95 days, but never created one. )
I will be flashing the 310 BIOS, so I guess it will go like this:
@echo off
awdflash.EXE NF4LD310.BIN /py /sn
And then I put the autoexec.bat on the floppy with awdflash.exe and the NF4LD310.BIN file, and it will "autorun"? Sorry for the noob questions, I was hoping the bootable BIOS cd rom was actually going to spare me these dos command prompt parameters/ switches/ whatever they're called...

And there's no "BIOS write- protect" jumper on the board is there? Never heard of it before, and it's not listed in the manual (yes, I've checked the *.pdf from the DFI website too)