MMM
Results 1 to 25 of 1953

Thread: Asus A8N32-SLI initial impression....WOW!

Hybrid View

  1. #1
    Xtreme Member
    Join Date
    Oct 2005
    Location
    Newcastle, UK
    Posts
    113
    My A8N32-SLI seems to hate being flashed to the latest BIOS

    I flashed it last night using a bootable USB stick with the AFUDOS method. Unfortunately it doesn't want to read the A8N321009.ROM file name so I renamed it to A8N32SLI.ROM which fixed it and it flashed fine. Then I get the infamous Bad Bios checksum error that has happened to me before on the same mobo using the ALT + F2 method which I fixed it by flashing to the previous latest BIOS.

    This time it didn't want to flash at all and refuses to display anything no matter how many times I reset the CMOS . This motherboard seems to have its own mind and spits out the 1009 BIOS .

    I've applied for an RMA which hopefully I can get a new one since the motherboard I got had its packaging damaged and the Northbridge Asus cover had a dent and lots of scratches . Hopefully a new motherboard will solve my X1800 XT which overclocks poorly

  2. #2
    Registered User
    Join Date
    Nov 2005
    Posts
    56
    Quote Originally Posted by Cybertronic
    I flashed it last night using a bootable USB stick with the AFUDOS method. Unfortunately it doesn't want to read the A8N321009.ROM file name so I renamed it to A8N32SLI.ROM which fixed it and it flashed fine. Then I get the infamous Bad Bios checksum error that has happened to me before on the same mobo using the ALT + F2 method which I fixed it by flashing to the previous latest BIOS.
    That checksum error, I believe, is caused simply by the name change...file that one under "strange but true." ASUS has to get its act together and make sure the BIOS file has a DOS-friendly 8.3 format before it generates its internal checksum. Guess why A8N32903.ROM doesn't have the same problem? let's see...could it be it was released with an 8.3 name?

    At any rate, if the bad checksum doesn't scare you off, going into the BIOS, loading the defaults and rebooting fixes it...fixed mine anyways.

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •