last change:
6.4.2002

Counter2
since 16.9.2000

A7V Troubleshooting
Why the heck is there a tank ?!?

Main Page
"HowTo" Guides
Troubleshooting Guides
BIOS related information
CPU related information
Overclocking

Articles
Downloads
Forum
Contact
Links

RD1 BIOS Savior

Addendum: the testing procedure

The testing Procedure was as follows:

Action
Notes
1. Boot from Original BIOS Chip with RD1 inserted This tells us if the RD1 interferes with booting
2. Backup old BIOS to Floppy  
3. Flashing old BIOS to RD1  
4. Booting from RD1 with old BIOS This tells us if the old BIOS version works with RD1
5. Booting from Original BIOS Chip again  
6. Flashing newest avaiable BIOS to original BIOS Chip This tells us if the newest BIOS works with the Mainboard
7. Booting from Original BIOS Chip again  
8. Flashing newest avaiable BIOS to RD1 This tells us if the newest BIOS works with RD1
9. Booting from RD1 with new BIOS  
10. Booting from Original BIOS Chip again If all Steps up to here were OK, then RD1 works

In case the boot from RD1 failed:
It is recommended to flash again if the first flash to the RD1 failed.
11. Do a second flash of the original BIOS to the RD1  
12. Booting from RD1 with new BIOS after second flashing If it works now, RD is considered working

Now on to the Test Candidates:

Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
Shuttle
HOT-663
V12
SST 29EE020
6630s019
6630S032
not listed
AWDFLASH 6.31 Evaluation!, AWDFLASH 7.66

When flashing the old BIOS into RD1, the BIOS complained after PCI listing displaying "flash unknown", so this means the old BIOS doesn't know the flash chip used in the RD1. This problem is only cosmetic, the Mainboard booted OK. After flashing the newest available BIOS, the error message dissapeared.

The RD1 is suited for this mainboard.


Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
Giga Byte
GA-6BXC
1.9
SST 29EE020
2.5
F3
yes
Flash 8.53, AWDFLASH 7.66

All test steps were OK, the RD1 is suited for this mainboard.


Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
Soltek
75KAV
F5
SST 39SF02
Q7
Q9.1
not listed
AWDFLASH 8.0

All test steps were OK, the RD1 is suited for this mainboard.


Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
ASUS
A7V133
1.05
Mosel V29C51002T
1006 Beta 0001-I
1008
yes, reported to ioss by two users
AFLASH 2.02

The only problem was that after flashing the new BIOS version to the original bios chip the CMOS had to be cleared in order to get the mainboard to boot. This seems not to be RD1 related, but the genaral ASUS problem with new BIOSes.

The RD1 is suited for this mainboard.


Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
Shuttle
AK31
V13A
Winbond 29C020
AK31S027
Ak31s40a
not listed
AWDFLASH 8.14C

All test steps were OK, the RD1 is suited for this mainboard.


Manufacturer
Model
Mainboard
revision
BIOS
Chip type
Old
BIOS version
new
BIOS version
Supported
according
to IOSS website
Flash Utility
ASUS
P2B
1.10.
Winbond W29C020
1008
1012
yes, reported to ioss by eight users
Aflash 202, Aflash 1.27

After flashing the old BIOS to the RD1, booting from it hung with POST code 63h ("Boot Attempt; Set Low Stack; Boot via INT 19h"). Flashing the new BIOS to the RD1 twice did not change anything, the P2B did not boot from RD1, only from the original bios chip.

Micke from Eksitdata gave me the tip to try a older flash tool. And lo and behold - with Aflash 1.27 I did succeed.

After using Aflash 1.27 all test steps were OK, so the RD1 is suited for this mainboard.

<< Previous Page

Page1: The Problem
Page2: What you get / how it works
Page3: Testing / Conclusion
Page4: Addendum: Testing Procedure

 

(c)2001 Disclaimer - Mail to webmaster (preferrably post in the forum)