M2N-E BIOS Update (maybe?)

I tried to update the BIOS on an ASUS M2N-E motherboard (from 0802 >
1202). ASUS Update did not show 1202 as an option when trying to
update from the internet. I then downloaded the file and tried to
transfer it to a floppy- got error msg "Cannot read from source file
or disk" (Vista64). Tried to copy to floppy on another computer using
XP- no luck. Finally, installed new BIOS via ASUS Update "update from
file" option. BIOS showed installed at 100 %, but verification froze
at 86 % (retry or cancel option). Retry, same result. Cancel, restart-
boot screen shows BIOS version 1202 and computer boots normally. BIOS
settings did not reset to default, all previously selected options
intact. So, do I have 1202 installed or is the 0802 version still
there?

I was updating the BIOS due to a problem with transfer speeds when
reading/saving files on my "D" drive (160GB Maxtor Diamond 10 IDE)
that I use for storage ("C" drive, 2 SATA Raptors in RAID 0 work
fine). Backing up Quicken, or doing simple task such as re-tagging an
MP3 file would take up to 40 seconds to save. Expanding a file tree
would take 15-20 seconds after selecting. There are no updated chipset
drivers for Vista 64 (they were included in Vista install), so I tried
updating the BIOS. It seems the update fixed the problem, but the fact
that the install process did not complete through verification is
bothersome.

Any suggestions or similiar experiences?

Thanks,

Fitz

Fitz wrote:
> I tried to update the BIOS on an ASUS M2N-E motherboard (from 0802 >
> 1202). ASUS Update did not show 1202 as an option when trying to
> update from the internet. I then downloaded the file and tried to
> transfer it to a floppy- got error msg "Cannot read from source file
> or disk" (Vista64). Tried to copy to floppy on another computer using
> XP- no luck. Finally, installed new BIOS via ASUS Update "update from
> file" option. BIOS showed installed at 100 %, but verification froze
> at 86 % (retry or cancel option). Retry, same result. Cancel, restart-
> boot screen shows BIOS version 1202 and computer boots normally. BIOS
> settings did not reset to default, all previously selected options
> intact. So, do I have 1202 installed or is the 0802 version still
> there?
>
> I was updating the BIOS due to a problem with transfer speeds when
> reading/saving files on my "D" drive (160GB Maxtor Diamond 10 IDE)
> that I use for storage ("C" drive, 2 SATA Raptors in RAID 0 work
> fine). Backing up Quicken, or doing simple task such as re-tagging an
> MP3 file would take up to 40 seconds to save. Expanding a file tree
> would take 15-20 seconds after selecting. There are no updated chipset
> drivers for Vista 64 (they were included in Vista install), so I tried
> updating the BIOS. It seems the update fixed the problem, but the fact
> that the install process did not complete through verification is
> bothersome.
>
> Any suggestions or similiar experiences?
>
> Thanks,
>
> Fitz

To verify what is loaded, use a BIOS tool that allows archiving
the current BIOS contents. Then, using a hex editor, look for
a version string or strings, and compare to the files you have
on hand.

Presumably some text string on the BIOS screen at startup, should
reflect the version as well, but they don't always get that stuff
right.

Another thing to note - you cannot compare an archived BIOS, byte
for byte, with the file you downloaded. As soon as the BIOS starts
up the first time, it modifies part of the flash chip contents.
It means, that instantly, the BIOS contents no longer match the
originally applied file. Major portions will match, but the DMI/ESCD
section will get overwritten with current hardware info.

That is why you want to use a hex editor, and search for version
strings in the two files. That way, you get to ignore the changes
the BIOS made, on the first bootup.

Paul

> or disk" (Vista64). Tried to copy to floppy on another computer using
> XP- no luck. Finally, installed new BIOS via ASUS Update "update from
> file" option. BIOS showed installed at 100 %, but verification froze
> at 86 % (retry or cancel option). Retry, same result. Cancel, restart-
> boot screen shows BIOS version 1202 and computer boots normally. BIOS

Download this windows 98 image:

http://www.allbootdisks.com/download...o_Ramdrive.exe

Use 7-zip to extract it into WIN98NORAM.IMA.

Download HP USB Key Utility:

http://h18023.www1.hp.com/support/fi...oad/24828.html

Use HP USB Key Utility to set a USB drive to floppy mode using the
WIN98NORAM.IMA above. Delete some files to make room for AWDFLASH.EXE
and 1202.BIN.

Reboot your PC, enter BOOT menu, boot the usb drive. Use AWDFLASH.EXE to
flash BIOS.

--
@~@ Might, Courage, Vision, SINCERITY.
/ v \ Simplicity is Beauty! May the Force and Farce be with you!
/( _ )\ (Xubuntu 7.04) Linux 2.6.23.8
^ ^ 11:10:01 up 20:26 2 users load average: 3.17 2.11 1.44
? ? (CSSA):
http://www.swd.gov.hk/tc/index/site_...ub_addressesa/

>
> To verify what is loaded, use a BIOS tool that allows archiving
> the current BIOS contents. Then, using a hex editor, look for
> a version string or strings, and compare to the files you have
> on hand.
>
Tried to install 3 different freeware BIOS tools that would allow me to
view BIOS details, none would install on Vista 64 ("cannot load driver-
installation failed"). I'll keep looking.

Thanks,

Fitz

Solution- used a different floppy, which accepted the file transfer and
re-flashed the BIOS using EZ Flash 2. Completed the full process through
verification. I don't know why the other floppy was bad- it had only
been around for 8 years or so!

Thanks for the help

Fitz
--
Your body is a temple boy,
You ought to treat it well
But you trash the place and rent it out
Like it's some cheap motel - The Badlees

Somewhere on teh interweb Fitz typed:
> Solution- used a different floppy, which accepted the file transfer
> and re-flashed the BIOS using EZ Flash 2. Completed the full process
> through verification. I don't know why the other floppy was bad- it
> had only been around for 8 years or so!
>
> Thanks for the help
>
> Fitz

Crazy! I'm not the paranoid type but even I only use new, OOTB floppies for
BIOS flashes. They're what, 50c each? Compare that to the damage and expense
of repairing/replacing that a bad BIOS flash can do and.....

Ehhh.
--
TTFN,

Shaun.

>
> Crazy! I'm not the paranoid type but even I only use new, OOTB floppies for
> BIOS flashes. They're what, 50c each? Compare that to the damage and expense
> of repairing/replacing that a bad BIOS flash can do and.....
>
> Ehhh.

It was "new" in that it has been in a hard case with dust cover and only
used once- it had a bios flash file on it! I reformatted it prior to
trying to use it and it formatted fine. With all the options ASUS has
for updating the BIOS, I hadn't planned on having to use a floppy to
begin with- the only reason I installed ASUS Update was to flash the
BIOS from a Windows environment...I had also tried EZ Flash 2 with a
flash drive, but it didn't recognize the drive. But, yeah, may be time
to invest in a box of new floppies for just this kind of thing.

Thanks,
Fitz

--
Your body is a temple boy,
You ought to treat it well
But you trash the place and rent it out
Like it's some cheap motel - The Badlees

Somewhere on teh interweb Fitz typed:
>> Crazy! I'm not the paranoid type but even I only use new, OOTB
>> floppies for BIOS flashes. They're what, 50c each? Compare that to
>> the damage and expense of repairing/replacing that a bad BIOS flash
>> can do and..... Ehhh.
>
> It was "new" in that it has been in a hard case with dust cover and
> only used once- it had a bios flash file on it! I reformatted it
> prior to trying to use it and it formatted fine.

Floppies consist of a magnetic media bound to a plastic disk with an
organic-based glue. The glue is prone to fungal deterioration. Basically,
any disk older than 18 months is a risk. (Even if it's been kept in a
relatively dry place). Once you start to use a disk that has deteriorated
rapidly gets worse.

I buy a new box of floppies every year at the longest and only use them
once, only for BIOS flashing.

However, my P5K-E WiFi-AP has a 2MB BIOS, it can't be flashed using a
floppy, even though the manual gives instructions on how to do it.

> With all the options
> ASUS has for updating the BIOS, I hadn't planned on having to use a
> floppy to begin with- the only reason I installed ASUS Update was to
> flash the BIOS from a Windows environment...

It's a good job that you used the "update from file" option. A very large
percentage of "update from internet" attempts fail.

> I had also tried EZ Flash
> 2 with a flash drive, but it didn't recognize the drive.

My P5K also won't recognize a USB drive when trying to update the BIOS. The
only option I had was to use ASUS Update and "update from file" too.
However, that makes me nervous, updating in an environment as unstable as
Windows. Asus make no mention of it but I've been wondering if it would be
possible to update in a DOS environment from a bootable CD.

> But, yeah,
> may be time to invest in a box of new floppies for just this kind of
> thing.

Good move. Replace them frequently too. My board has "ASUS CrashFree BIOS 3"
utility. Apparently, if the BIOS file is corrupted you boot with the driver
CD in the drive and it flashes with a new .rom file. However, it's unclear
going by the manual if the source for the file is the CD itself or a floppy.
Apparently there is an on-screen message during the process that says
"Checking for floppy..." Fat lot of good that would do me if that's the
case.

Cheers,
--
Shaun.