BIOS Updates forum

This is my current BIOS specification:

Program: eSupport.com BIOS Agent Version 3.23
BIOS Date: 10/16/01
BIOS Type: American Megatrends
BIOS ID: 62-1016-001437-00101111-040201-SiS735-M830LR
OEM Sign-On: Release 10/16/2001 S
Chipset: SiS 735 rev 1
Superio: ITE 8705/SiS 950 rev 1 found at port 2Eh
OS: WinXP
CPU: AMD 1100 Mhz MAX: 1200 Mhz
BIOS ROM In Socket: Yes
BIOS ROM Size: 256K
Memory Installed: 512 MB
Memory Maximum: 512 MB
Memory Slot 01: 0 MB
Memory Slot 02: 512 MB
Memory Slot 03: 0 MB
Memory Slot 04: 0 MB

I've searched and searched but can't seem to find the right update.
Can someone please help me???

ftp://ftp.pcchips.com.tw/BIOS-n/M830L/

Latest: 021029S.zip

Pcchips is a little slow with updating their Bios releases
The identical ECS K7S5A (Rev 1.x/3.x) have a newer Bios 08/22003 supporting newer CPU as well as OC-Bios with more settings in Bios available
www.ecs.com.tw for ECs Bios
www.rhcf.com for K7S5A OC-Bios

Hmmm....It didn't work!
I did the following:
1) Created a ms_dos boot disc
2) Copied the file you posted and aminf336.exe to the disc.
3) Booted the machine from the floppy disc.
4) Wrote the command: 'aminf336 021029s"
This gave me the following reply:
Chipset type - SiS SiS/SB
FlashPart - Winbound 49F002U_V3
Old BIOS - Realese 10/16/2001 S
New BIOS - Release 10/29/2002 S
Old BIOS Tag is <M830LR> -- New BIOS Tag is <M830>
Error9 - The BIOS tag is incorrect

Any suggestions what to do next?

The newer BIOSes are merged. What I mean is that they have a LAN autodetect feature, so a new M830 BIOS covers the whole family of M830 boards. The warning message is quite normal.

In fact, if you check http://www.pcchips.com.tw/BIOS.html for the M830 and M830L (=M830LR) BIOS links, you'll see that they both point to the same file, in the M830 folder.

All you have to do is ignore that warning message.

Note: if this doesn't convince you, read the following items:
BIOS change announcement (11/11/2002)
Model Name Defining Rule (07/03/2002)
...at http://www.pcchips.com.tw/news/news.html

I ignored the warning message, and it worked!!!

tnx for the help