BIOS Savior for A8N-SLI

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Sat, 25 Jun 2005 17:41:16 -0400, "FG" <personne@videotron.cam>
wrote:

>On both types.

Great!! Please fill us in on your use of awdflash.exe on the these
two boards. Any problems completing the flash using it? Did you have
to employ a workaround?
>
>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
>2qerb19oprgpqhp3j0apo5mnnj0tle1b0a@4ax.com...
>> On Sat, 25 Jun 2005 09:30:16 -0400, "FG" <personne@videotron.cam>
>> wrote:
>>
>>>The reference was to A8N-SLI Deluxe's manual -
>>>but that page number also applies to A7N8X-E Deluxe.
>>
>> So I take it you have it installed in an A7N8X-E?
>>>
>>>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
>>>u7vpb19e9kfsp0l0vf201dtegsbl6pmgc5@4ax.com...
>>>> On Fri, 24 Jun 2005 19:40:49 -0400, "FG" <personne@videotron.cam>
>>>> wrote:
>>>>
>>>>>True. But a floppy is easy to make.
>>>>>Page 4 - 2 of your motherboard manual.
>>>>>
>>>>>By the way, I have a Bios savior. It is much
>>>>>safer in that even if there is a ^pwer failure during the
>>>>>flashing process.
>>>>
>>>> What motherboard do you have it installed in?
>>>>
>>>>>
>>>>>"J&SB" <jandsb@cox.net> a écrit dans le message de news:
>>>>>nd0ve.51082$iU.24185@lakeread05...
>>>>>> Thanks for the detailed run-down. I'm going to get one of these for
>>>>>> my
>>>>>> A8N-SLI Deluxe. I think the price is a bargain for the peace of mind
>>>>>> that
>>>>>> you get. What other boot device would support this procedure? I'm
>>>>>> one
>>>>>> of
>>>>>> those guys with a relatively new rig, and they just don't put floppies
>>>>>> in
>>>>>> them any more.
>>>>>> Thanks,
>>>>>> Jim
>>>>>>
>>>>>> "milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>> news😱numb1ljq0iud8uh25r4tg8ege4eiljmfj@4ax.com...
>>>>>>> On Thu, 23 Jun 2005 20:09:00 -0400, "J&SB" <jandsb@cox.net> wrote:
>>>>>>>
>>>>>>>>Say Ron,
>>>>>>>>Now that you've identified the right BIOS Savior, would you mind
>>>>>>>>going
>>>>>>>>through your installation and flashing procedure step-by-step for us
>>>>>>>>who
>>>>>>>>walk with trepidation when it comes to this sort of thing? Thanks in
>>>>>>>>advance. I'd really like to get one of these and rest easier.
>>>>>>>>Jim
>>>>>>>
>>>>>>> Sure.
>>>>>>> 1 -- Before I installed my motherboard, I used the neat little
>>>>>>> BIOS-chip extractor supplied by IOSS to remove the PLCC BIOS chip.
>>>>>>> Just like CPUs, these things go in only one way, and it's easy to
>>>>>>> tell
>>>>>>> because one corner of the chip and socket are not square. The
>>>>>>> instructions illustrate how to keep things in alignment.
>>>>>>> 2 -- plug the BIOS Savior into the motherboard socket vacated by the
>>>>>>> original BIOS.
>>>>>>> 3 -- keeping the alignment in mind plug the original BIOS chip into
>>>>>>> the identical socket on the top of the BIOS Savior. At this point,
>>>>>>> the original chip is plugged into the Savior, and the Savior is
>>>>>>> plugged into the mobo. There is NEVER an ELECTRICAL CONNECTION
>>>>>>> between the EPROM in the BIOS Savior and the original BIOS chip
>>>>>>> mounted in the BIOS Savior.
>>>>>>> 4 -- with the BIOS Savior switch set on ORG (for "original"), boot
>>>>>>> the
>>>>>>> machine with a bootable floppy containing awdflash.exe in the drive.
>>>>>>> 5 -- run awdflash.exe and elect to save the original BIOS to the
>>>>>>> floppy, giving it any name you wish.
>>>>>>> 6 -- flip the BIOS Savior switch to "RD1."
>>>>>>> 7 -- run awdflash again, this time telling it that you want to
>>>>>>> reprogram the BIOS. Type in the name you gave the SAVED original
>>>>>>> BIOS, and let it write that BIN file to the BIOS Savior's chip.
>>>>>>>
>>>>>>> In my case, AWDFLASH gave a checksum error when trying to flash the
>>>>>>> BIOS Savior. I had saved the original BIOS as ORIGINAL.BIN, so I set
>>>>>>> the Savior to ORG, hit ALT-F2 during POST, and used Asus EZFlash
>>>>>>> instead of awdflash.exe. After EZFlash was running, I set the BIOS
>>>>>>> Savior to "RD1," and proceeded with the flash. EZFlash had no
>>>>>>> trouble
>>>>>>> flashing the BIOS Savior. Now I have the same version of the BIOS in
>>>>>>> both the Savior and the original chip. The data stored in CMOS is
>>>>>>> therefore appropriate for both, and I can POST with the switch set in
>>>>>>> either position.
>>>>>>>
>>>>>>> After you get this far, you can leave the switch on either setting:
>>>>>>> A -- you can leave it set on RD1. This leaves your pristine original
>>>>>>> BIOS sitting there unused, while you run day-to-day from the BIOS
>>>>>>> Savior's chip, keeping the original in reserve. You might even want
>>>>>>> to remove it and put it somewhere else for safekeeping.
>>>>>>> B -- you can set the switch back to ORG, running day-to-day from your
>>>>>>> original BIOS, and using the BIOS Savior as a backup. If you get a
>>>>>>> badflash, simply clear the CMOS, flip the BIOS Savior switch, and
>>>>>>> boot
>>>>>>> from the known good backup.
>>>>>>> C -- a development engineer could have different versions of the BIOS
>>>>>>> in the Savior and the original chip and switch back an forth from one
>>>>>>> boot to the next. I suspect that you'd have to clear CMOS to do
>>>>>>> that.
>>>>>>> Not sure.
>>>>>>> D -- you can use the BIOS Savior as a flashing device, something like
>>>>>>> they do at badflash.com. If a friend had a messed-up BIOS, you could
>>>>>>> extract the chip from his computer and then plug it into the BIOS
>>>>>>> Savior. You'd then simply boot to a floppy, flip the switch, and
>>>>>>> reflash his bad BIOS.
>>>>>>>
>>>>>>> This really takes the fear and worry out of flash a BIOS. If it goes
>>>>>>> bad, just flip a switch, and you're back in business.
>>>>>>>
>>>>>>>>"milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>>>>news😛i5kb1tqrldgttk7bdkvrf416fm4sanuqq@4ax.com...
>>>>>>>>> On Tue, 14 Jun 2005 02:58:26 -0400, "FG" <personne@videotron.cam>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>>My advice : contact them by e-mail, stating the type and number of
>>>>>>>>>>your BIOS. They usually answer rapidly. My guess is that as long
>>>>>>>>>>as the BIOS is the same size it will work.
>>>>>>>>>>
>>>>>>>>>>As long as you disconnect your computer and proceed with care,
>>>>>>>>>>your board will not be damaged.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I'm still going to buy the only BIOS Savior that IOSS makes and
>>>>>>>>>>> see
>>>>>>>>>>> if
>>>>>>>>>>> it works. If it doesn't, then it should be a fairly simple
>>>>>>>>>>> matter
>>>>>>>>>>> to
>>>>>>>>>>> remove it and plug the original BIOS back into its original slot.
>>>>>>>>>>> I've never done this before, though, so I'm wondering how great a
>>>>>>>>>>> likelihood there is of damaging the mobo or BIOS chip using the
>>>>>>>>>>> chip-extracting device supplied with the BIOS Savior. Anybody
>>>>>>>>>>> know?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Ron
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> FG,
>>>>>>>>> You were correct. The size of the RD1-PMC4 is the same size as the
>>>>>>>>> A8N-SLI BIOS, I did not damage anything, and it DOES WORK!
>>>>>>>>>
>>>>>>>>> The use of the included BIOS-chip extractor was not well
>>>>>>>>> documented,
>>>>>>>>> but once I figured it out, it popped the original BIOS out almost
>>>>>>>>> effortlessly. Installation was a breeze -- thirty seconds flat.
>>>>>>>>>
>>>>>>>>> I am thrilled to finally have a computer with a working BIOS Savior
>>>>>>>>> installed. I can flash new BIOS versions at will without having to
>>>>>>>>> fear that I'll screw anything up.
>>>>>>>>>
>>>>>>>>> VERY, very importantly, I could not program the BIOS Savior with
>>>>>>>>> AWDFLASH.EXE, the newest version available for download at Asus,
>>>>>>>>> ver.
>>>>>>>>> 8.24, I believe. It gave a checksum error and refused to proceed.
>>>>>>>>> HOWEVER, I then tried the built-in Asus EZFlash (ALT-F2 during
>>>>>>>>> POST),
>>>>>>>>> and it copied the original BIOS file, 1004, to the BIOS Savior
>>>>>>>>> just
>>>>>>>>> as though it was writing to the regular BIOS chip. I could then
>>>>>>>>> leave
>>>>>>>>> the BIOS Savior set to RD1 and reboot. It's perfectly transparent.
>>>>>>>>> I
>>>>>>>>> cannot recommend the BIOS Savior highly enough. I'll report this
>>>>>>>>> success to IOSS, but it seems like they're no longer updating their
>>>>>>>>> compatibility pages. I deduce that they don't care if they sell
>>>>>>>>> this
>>>>>>>>> product any longer or else their marketing department should all be
>>>>>>>>> fired en masse.
>>>>>>>>>
>>>>>>>>> Anyway, spread the gospel. BIOS Savior RD1-PMC4 is compatible with
>>>>>>>>> the A8N-SLI series.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Ron
>>>>>>>>
>>>>>>>
>>>>>>> Ron
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> Ron
>>>
>>
>> Ron
>

Ron
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Read your manual and detailed instructions below.

"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
p8ksb19rg30tbn3pknui7c9hn8thjht3u7@4ax.com...
> On Sat, 25 Jun 2005 17:41:16 -0400, "FG" <personne@videotron.cam>
> wrote:
>
>>On both types.
>
> Great!! Please fill us in on your use of awdflash.exe on the these
> two boards. Any problems completing the flash using it? Did you have
> to employ a workaround?
>>
>>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
>>2qerb19oprgpqhp3j0apo5mnnj0tle1b0a@4ax.com...
>>> On Sat, 25 Jun 2005 09:30:16 -0400, "FG" <personne@videotron.cam>
>>> wrote:
>>>
>>>>The reference was to A8N-SLI Deluxe's manual -
>>>>but that page number also applies to A7N8X-E Deluxe.
>>>
>>> So I take it you have it installed in an A7N8X-E?
>>>>
>>>>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de
>>>>news:
>>>>u7vpb19e9kfsp0l0vf201dtegsbl6pmgc5@4ax.com...
>>>>> On Fri, 24 Jun 2005 19:40:49 -0400, "FG" <personne@videotron.cam>
>>>>> wrote:
>>>>>
>>>>>>True. But a floppy is easy to make.
>>>>>>Page 4 - 2 of your motherboard manual.
>>>>>>
>>>>>>By the way, I have a Bios savior. It is much
>>>>>>safer in that even if there is a ^pwer failure during the
>>>>>>flashing process.
>>>>>
>>>>> What motherboard do you have it installed in?
>>>>>
>>>>>>
>>>>>>"J&SB" <jandsb@cox.net> a écrit dans le message de news:
>>>>>>nd0ve.51082$iU.24185@lakeread05...
>>>>>>> Thanks for the detailed run-down. I'm going to get one of these for
>>>>>>> my
>>>>>>> A8N-SLI Deluxe. I think the price is a bargain for the peace of
>>>>>>> mind
>>>>>>> that
>>>>>>> you get. What other boot device would support this procedure? I'm
>>>>>>> one
>>>>>>> of
>>>>>>> those guys with a relatively new rig, and they just don't put
>>>>>>> floppies
>>>>>>> in
>>>>>>> them any more.
>>>>>>> Thanks,
>>>>>>> Jim
>>>>>>>
>>>>>>> "milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>>> news😱numb1ljq0iud8uh25r4tg8ege4eiljmfj@4ax.com...
>>>>>>>> On Thu, 23 Jun 2005 20:09:00 -0400, "J&SB" <jandsb@cox.net> wrote:
>>>>>>>>
>>>>>>>>>Say Ron,
>>>>>>>>>Now that you've identified the right BIOS Savior, would you mind
>>>>>>>>>going
>>>>>>>>>through your installation and flashing procedure step-by-step for
>>>>>>>>>us
>>>>>>>>>who
>>>>>>>>>walk with trepidation when it comes to this sort of thing? Thanks
>>>>>>>>>in
>>>>>>>>>advance. I'd really like to get one of these and rest easier.
>>>>>>>>>Jim
>>>>>>>>
>>>>>>>> Sure.
>>>>>>>> 1 -- Before I installed my motherboard, I used the neat little
>>>>>>>> BIOS-chip extractor supplied by IOSS to remove the PLCC BIOS chip.
>>>>>>>> Just like CPUs, these things go in only one way, and it's easy to
>>>>>>>> tell
>>>>>>>> because one corner of the chip and socket are not square. The
>>>>>>>> instructions illustrate how to keep things in alignment.
>>>>>>>> 2 -- plug the BIOS Savior into the motherboard socket vacated by
>>>>>>>> the
>>>>>>>> original BIOS.
>>>>>>>> 3 -- keeping the alignment in mind plug the original BIOS chip into
>>>>>>>> the identical socket on the top of the BIOS Savior. At this point,
>>>>>>>> the original chip is plugged into the Savior, and the Savior is
>>>>>>>> plugged into the mobo. There is NEVER an ELECTRICAL CONNECTION
>>>>>>>> between the EPROM in the BIOS Savior and the original BIOS chip
>>>>>>>> mounted in the BIOS Savior.
>>>>>>>> 4 -- with the BIOS Savior switch set on ORG (for "original"), boot
>>>>>>>> the
>>>>>>>> machine with a bootable floppy containing awdflash.exe in the
>>>>>>>> drive.
>>>>>>>> 5 -- run awdflash.exe and elect to save the original BIOS to the
>>>>>>>> floppy, giving it any name you wish.
>>>>>>>> 6 -- flip the BIOS Savior switch to "RD1."
>>>>>>>> 7 -- run awdflash again, this time telling it that you want to
>>>>>>>> reprogram the BIOS. Type in the name you gave the SAVED original
>>>>>>>> BIOS, and let it write that BIN file to the BIOS Savior's chip.
>>>>>>>>
>>>>>>>> In my case, AWDFLASH gave a checksum error when trying to flash the
>>>>>>>> BIOS Savior. I had saved the original BIOS as ORIGINAL.BIN, so I
>>>>>>>> set
>>>>>>>> the Savior to ORG, hit ALT-F2 during POST, and used Asus EZFlash
>>>>>>>> instead of awdflash.exe. After EZFlash was running, I set the BIOS
>>>>>>>> Savior to "RD1," and proceeded with the flash. EZFlash had no
>>>>>>>> trouble
>>>>>>>> flashing the BIOS Savior. Now I have the same version of the BIOS
>>>>>>>> in
>>>>>>>> both the Savior and the original chip. The data stored in CMOS is
>>>>>>>> therefore appropriate for both, and I can POST with the switch set
>>>>>>>> in
>>>>>>>> either position.
>>>>>>>>
>>>>>>>> After you get this far, you can leave the switch on either setting:
>>>>>>>> A -- you can leave it set on RD1. This leaves your pristine
>>>>>>>> original
>>>>>>>> BIOS sitting there unused, while you run day-to-day from the BIOS
>>>>>>>> Savior's chip, keeping the original in reserve. You might even
>>>>>>>> want
>>>>>>>> to remove it and put it somewhere else for safekeeping.
>>>>>>>> B -- you can set the switch back to ORG, running day-to-day from
>>>>>>>> your
>>>>>>>> original BIOS, and using the BIOS Savior as a backup. If you get a
>>>>>>>> badflash, simply clear the CMOS, flip the BIOS Savior switch, and
>>>>>>>> boot
>>>>>>>> from the known good backup.
>>>>>>>> C -- a development engineer could have different versions of the
>>>>>>>> BIOS
>>>>>>>> in the Savior and the original chip and switch back an forth from
>>>>>>>> one
>>>>>>>> boot to the next. I suspect that you'd have to clear CMOS to do
>>>>>>>> that.
>>>>>>>> Not sure.
>>>>>>>> D -- you can use the BIOS Savior as a flashing device, something
>>>>>>>> like
>>>>>>>> they do at badflash.com. If a friend had a messed-up BIOS, you
>>>>>>>> could
>>>>>>>> extract the chip from his computer and then plug it into the BIOS
>>>>>>>> Savior. You'd then simply boot to a floppy, flip the switch, and
>>>>>>>> reflash his bad BIOS.
>>>>>>>>
>>>>>>>> This really takes the fear and worry out of flash a BIOS. If it
>>>>>>>> goes
>>>>>>>> bad, just flip a switch, and you're back in business.
>>>>>>>>
>>>>>>>>>"milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>>>>>news😛i5kb1tqrldgttk7bdkvrf416fm4sanuqq@4ax.com...
>>>>>>>>>> On Tue, 14 Jun 2005 02:58:26 -0400, "FG" <personne@videotron.cam>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>>My advice : contact them by e-mail, stating the type and number
>>>>>>>>>>>of
>>>>>>>>>>>your BIOS. They usually answer rapidly. My guess is that as
>>>>>>>>>>>long
>>>>>>>>>>>as the BIOS is the same size it will work.
>>>>>>>>>>>
>>>>>>>>>>>As long as you disconnect your computer and proceed with care,
>>>>>>>>>>>your board will not be damaged.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I'm still going to buy the only BIOS Savior that IOSS makes and
>>>>>>>>>>>> see
>>>>>>>>>>>> if
>>>>>>>>>>>> it works. If it doesn't, then it should be a fairly simple
>>>>>>>>>>>> matter
>>>>>>>>>>>> to
>>>>>>>>>>>> remove it and plug the original BIOS back into its original
>>>>>>>>>>>> slot.
>>>>>>>>>>>> I've never done this before, though, so I'm wondering how great
>>>>>>>>>>>> a
>>>>>>>>>>>> likelihood there is of damaging the mobo or BIOS chip using the
>>>>>>>>>>>> chip-extracting device supplied with the BIOS Savior. Anybody
>>>>>>>>>>>> know?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Ron
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> FG,
>>>>>>>>>> You were correct. The size of the RD1-PMC4 is the same size as
>>>>>>>>>> the
>>>>>>>>>> A8N-SLI BIOS, I did not damage anything, and it DOES WORK!
>>>>>>>>>>
>>>>>>>>>> The use of the included BIOS-chip extractor was not well
>>>>>>>>>> documented,
>>>>>>>>>> but once I figured it out, it popped the original BIOS out almost
>>>>>>>>>> effortlessly. Installation was a breeze -- thirty seconds flat.
>>>>>>>>>>
>>>>>>>>>> I am thrilled to finally have a computer with a working BIOS
>>>>>>>>>> Savior
>>>>>>>>>> installed. I can flash new BIOS versions at will without having
>>>>>>>>>> to
>>>>>>>>>> fear that I'll screw anything up.
>>>>>>>>>>
>>>>>>>>>> VERY, very importantly, I could not program the BIOS Savior with
>>>>>>>>>> AWDFLASH.EXE, the newest version available for download at Asus,
>>>>>>>>>> ver.
>>>>>>>>>> 8.24, I believe. It gave a checksum error and refused to
>>>>>>>>>> proceed.
>>>>>>>>>> HOWEVER, I then tried the built-in Asus EZFlash (ALT-F2 during
>>>>>>>>>> POST),
>>>>>>>>>> and it copied the original BIOS file, 1004, to the BIOS Savior
>>>>>>>>>> just
>>>>>>>>>> as though it was writing to the regular BIOS chip. I could then
>>>>>>>>>> leave
>>>>>>>>>> the BIOS Savior set to RD1 and reboot. It's perfectly
>>>>>>>>>> transparent.
>>>>>>>>>> I
>>>>>>>>>> cannot recommend the BIOS Savior highly enough. I'll report this
>>>>>>>>>> success to IOSS, but it seems like they're no longer updating
>>>>>>>>>> their
>>>>>>>>>> compatibility pages. I deduce that they don't care if they sell
>>>>>>>>>> this
>>>>>>>>>> product any longer or else their marketing department should all
>>>>>>>>>> be
>>>>>>>>>> fired en masse.
>>>>>>>>>>
>>>>>>>>>> Anyway, spread the gospel. BIOS Savior RD1-PMC4 is compatible
>>>>>>>>>> with
>>>>>>>>>> the A8N-SLI series.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Ron
>>>>>>>>>
>>>>>>>>
>>>>>>>> Ron
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> Ron
>>>>
>>>
>>> Ron
>>
>
> Ron
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Paul wrote:
> In any case, it looks like the user has no control any more with this
> program. Either this means Asus is not updating the boot block, or
> they are paying lip service to the concept of CrashFree (i.e. it is
> updated every time).
>
> Paul

If you use the EZ-Flash utility built into the BIOS to flash, you can
see that some of the flash blocks are shown as "No Update". Presumably
this is the boot block area..

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Sun, 26 Jun 2005 13:05:10 -0400, "FG" <personne@videotron.cam>
wrote:

>Read your manual and detailed instructions below.

There's nothing in any manual about this, and the only "detailed
instructions below" are the ones I wrote myself. I'm asking if you
had any trouble using AWDFLASH to program your BIOS Savior. I did,
and I'm wanting to know if my experience was the exception or the
rule.
>
>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
>p8ksb19rg30tbn3pknui7c9hn8thjht3u7@4ax.com...
>> On Sat, 25 Jun 2005 17:41:16 -0400, "FG" <personne@videotron.cam>
>> wrote:
>>
>>>On both types.
>>
>> Great!! Please fill us in on your use of awdflash.exe on the these
>> two boards. Any problems completing the flash using it? Did you have
>> to employ a workaround?
>>>
>>>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de news:
>>>2qerb19oprgpqhp3j0apo5mnnj0tle1b0a@4ax.com...
>>>> On Sat, 25 Jun 2005 09:30:16 -0400, "FG" <personne@videotron.cam>
>>>> wrote:
>>>>
>>>>>The reference was to A8N-SLI Deluxe's manual -
>>>>>but that page number also applies to A7N8X-E Deluxe.
>>>>
>>>> So I take it you have it installed in an A7N8X-E?
>>>>>
>>>>>"milleron" <millerdot90@SPAMlessosu.edu> a écrit dans le message de
>>>>>news:
>>>>>u7vpb19e9kfsp0l0vf201dtegsbl6pmgc5@4ax.com...
>>>>>> On Fri, 24 Jun 2005 19:40:49 -0400, "FG" <personne@videotron.cam>
>>>>>> wrote:
>>>>>>
>>>>>>>True. But a floppy is easy to make.
>>>>>>>Page 4 - 2 of your motherboard manual.
>>>>>>>
>>>>>>>By the way, I have a Bios savior. It is much
>>>>>>>safer in that even if there is a ^pwer failure during the
>>>>>>>flashing process.
>>>>>>
>>>>>> What motherboard do you have it installed in?
>>>>>>
>>>>>>>
>>>>>>>"J&SB" <jandsb@cox.net> a écrit dans le message de news:
>>>>>>>nd0ve.51082$iU.24185@lakeread05...
>>>>>>>> Thanks for the detailed run-down. I'm going to get one of these for
>>>>>>>> my
>>>>>>>> A8N-SLI Deluxe. I think the price is a bargain for the peace of
>>>>>>>> mind
>>>>>>>> that
>>>>>>>> you get. What other boot device would support this procedure? I'm
>>>>>>>> one
>>>>>>>> of
>>>>>>>> those guys with a relatively new rig, and they just don't put
>>>>>>>> floppies
>>>>>>>> in
>>>>>>>> them any more.
>>>>>>>> Thanks,
>>>>>>>> Jim
>>>>>>>>
>>>>>>>> "milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>>>> news😱numb1ljq0iud8uh25r4tg8ege4eiljmfj@4ax.com...
>>>>>>>>> On Thu, 23 Jun 2005 20:09:00 -0400, "J&SB" <jandsb@cox.net> wrote:
>>>>>>>>>
>>>>>>>>>>Say Ron,
>>>>>>>>>>Now that you've identified the right BIOS Savior, would you mind
>>>>>>>>>>going
>>>>>>>>>>through your installation and flashing procedure step-by-step for
>>>>>>>>>>us
>>>>>>>>>>who
>>>>>>>>>>walk with trepidation when it comes to this sort of thing? Thanks
>>>>>>>>>>in
>>>>>>>>>>advance. I'd really like to get one of these and rest easier.
>>>>>>>>>>Jim
>>>>>>>>>
>>>>>>>>> Sure.
>>>>>>>>> 1 -- Before I installed my motherboard, I used the neat little
>>>>>>>>> BIOS-chip extractor supplied by IOSS to remove the PLCC BIOS chip.
>>>>>>>>> Just like CPUs, these things go in only one way, and it's easy to
>>>>>>>>> tell
>>>>>>>>> because one corner of the chip and socket are not square. The
>>>>>>>>> instructions illustrate how to keep things in alignment.
>>>>>>>>> 2 -- plug the BIOS Savior into the motherboard socket vacated by
>>>>>>>>> the
>>>>>>>>> original BIOS.
>>>>>>>>> 3 -- keeping the alignment in mind plug the original BIOS chip into
>>>>>>>>> the identical socket on the top of the BIOS Savior. At this point,
>>>>>>>>> the original chip is plugged into the Savior, and the Savior is
>>>>>>>>> plugged into the mobo. There is NEVER an ELECTRICAL CONNECTION
>>>>>>>>> between the EPROM in the BIOS Savior and the original BIOS chip
>>>>>>>>> mounted in the BIOS Savior.
>>>>>>>>> 4 -- with the BIOS Savior switch set on ORG (for "original"), boot
>>>>>>>>> the
>>>>>>>>> machine with a bootable floppy containing awdflash.exe in the
>>>>>>>>> drive.
>>>>>>>>> 5 -- run awdflash.exe and elect to save the original BIOS to the
>>>>>>>>> floppy, giving it any name you wish.
>>>>>>>>> 6 -- flip the BIOS Savior switch to "RD1."
>>>>>>>>> 7 -- run awdflash again, this time telling it that you want to
>>>>>>>>> reprogram the BIOS. Type in the name you gave the SAVED original
>>>>>>>>> BIOS, and let it write that BIN file to the BIOS Savior's chip.
>>>>>>>>>
>>>>>>>>> In my case, AWDFLASH gave a checksum error when trying to flash the
>>>>>>>>> BIOS Savior. I had saved the original BIOS as ORIGINAL.BIN, so I
>>>>>>>>> set
>>>>>>>>> the Savior to ORG, hit ALT-F2 during POST, and used Asus EZFlash
>>>>>>>>> instead of awdflash.exe. After EZFlash was running, I set the BIOS
>>>>>>>>> Savior to "RD1," and proceeded with the flash. EZFlash had no
>>>>>>>>> trouble
>>>>>>>>> flashing the BIOS Savior. Now I have the same version of the BIOS
>>>>>>>>> in
>>>>>>>>> both the Savior and the original chip. The data stored in CMOS is
>>>>>>>>> therefore appropriate for both, and I can POST with the switch set
>>>>>>>>> in
>>>>>>>>> either position.
>>>>>>>>>
>>>>>>>>> After you get this far, you can leave the switch on either setting:
>>>>>>>>> A -- you can leave it set on RD1. This leaves your pristine
>>>>>>>>> original
>>>>>>>>> BIOS sitting there unused, while you run day-to-day from the BIOS
>>>>>>>>> Savior's chip, keeping the original in reserve. You might even
>>>>>>>>> want
>>>>>>>>> to remove it and put it somewhere else for safekeeping.
>>>>>>>>> B -- you can set the switch back to ORG, running day-to-day from
>>>>>>>>> your
>>>>>>>>> original BIOS, and using the BIOS Savior as a backup. If you get a
>>>>>>>>> badflash, simply clear the CMOS, flip the BIOS Savior switch, and
>>>>>>>>> boot
>>>>>>>>> from the known good backup.
>>>>>>>>> C -- a development engineer could have different versions of the
>>>>>>>>> BIOS
>>>>>>>>> in the Savior and the original chip and switch back an forth from
>>>>>>>>> one
>>>>>>>>> boot to the next. I suspect that you'd have to clear CMOS to do
>>>>>>>>> that.
>>>>>>>>> Not sure.
>>>>>>>>> D -- you can use the BIOS Savior as a flashing device, something
>>>>>>>>> like
>>>>>>>>> they do at badflash.com. If a friend had a messed-up BIOS, you
>>>>>>>>> could
>>>>>>>>> extract the chip from his computer and then plug it into the BIOS
>>>>>>>>> Savior. You'd then simply boot to a floppy, flip the switch, and
>>>>>>>>> reflash his bad BIOS.
>>>>>>>>>
>>>>>>>>> This really takes the fear and worry out of flash a BIOS. If it
>>>>>>>>> goes
>>>>>>>>> bad, just flip a switch, and you're back in business.
>>>>>>>>>
>>>>>>>>>>"milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>>>>>>>>>>news😛i5kb1tqrldgttk7bdkvrf416fm4sanuqq@4ax.com...
>>>>>>>>>>> On Tue, 14 Jun 2005 02:58:26 -0400, "FG" <personne@videotron.cam>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>My advice : contact them by e-mail, stating the type and number
>>>>>>>>>>>>of
>>>>>>>>>>>>your BIOS. They usually answer rapidly. My guess is that as
>>>>>>>>>>>>long
>>>>>>>>>>>>as the BIOS is the same size it will work.
>>>>>>>>>>>>
>>>>>>>>>>>>As long as you disconnect your computer and proceed with care,
>>>>>>>>>>>>your board will not be damaged.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm still going to buy the only BIOS Savior that IOSS makes and
>>>>>>>>>>>>> see
>>>>>>>>>>>>> if
>>>>>>>>>>>>> it works. If it doesn't, then it should be a fairly simple
>>>>>>>>>>>>> matter
>>>>>>>>>>>>> to
>>>>>>>>>>>>> remove it and plug the original BIOS back into its original
>>>>>>>>>>>>> slot.
>>>>>>>>>>>>> I've never done this before, though, so I'm wondering how great
>>>>>>>>>>>>> a
>>>>>>>>>>>>> likelihood there is of damaging the mobo or BIOS chip using the
>>>>>>>>>>>>> chip-extracting device supplied with the BIOS Savior. Anybody
>>>>>>>>>>>>> know?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ron
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> FG,
>>>>>>>>>>> You were correct. The size of the RD1-PMC4 is the same size as
>>>>>>>>>>> the
>>>>>>>>>>> A8N-SLI BIOS, I did not damage anything, and it DOES WORK!
>>>>>>>>>>>
>>>>>>>>>>> The use of the included BIOS-chip extractor was not well
>>>>>>>>>>> documented,
>>>>>>>>>>> but once I figured it out, it popped the original BIOS out almost
>>>>>>>>>>> effortlessly. Installation was a breeze -- thirty seconds flat.
>>>>>>>>>>>
>>>>>>>>>>> I am thrilled to finally have a computer with a working BIOS
>>>>>>>>>>> Savior
>>>>>>>>>>> installed. I can flash new BIOS versions at will without having
>>>>>>>>>>> to
>>>>>>>>>>> fear that I'll screw anything up.
>>>>>>>>>>>
>>>>>>>>>>> VERY, very importantly, I could not program the BIOS Savior with
>>>>>>>>>>> AWDFLASH.EXE, the newest version available for download at Asus,
>>>>>>>>>>> ver.
>>>>>>>>>>> 8.24, I believe. It gave a checksum error and refused to
>>>>>>>>>>> proceed.
>>>>>>>>>>> HOWEVER, I then tried the built-in Asus EZFlash (ALT-F2 during
>>>>>>>>>>> POST),
>>>>>>>>>>> and it copied the original BIOS file, 1004, to the BIOS Savior
>>>>>>>>>>> just
>>>>>>>>>>> as though it was writing to the regular BIOS chip. I could then
>>>>>>>>>>> leave
>>>>>>>>>>> the BIOS Savior set to RD1 and reboot. It's perfectly
>>>>>>>>>>> transparent.
>>>>>>>>>>> I
>>>>>>>>>>> cannot recommend the BIOS Savior highly enough. I'll report this
>>>>>>>>>>> success to IOSS, but it seems like they're no longer updating
>>>>>>>>>>> their
>>>>>>>>>>> compatibility pages. I deduce that they don't care if they sell
>>>>>>>>>>> this
>>>>>>>>>>> product any longer or else their marketing department should all
>>>>>>>>>>> be
>>>>>>>>>>> fired en masse.
>>>>>>>>>>>
>>>>>>>>>>> Anyway, spread the gospel. BIOS Savior RD1-PMC4 is compatible
>>>>>>>>>>> with
>>>>>>>>>>> the A8N-SLI series.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Ron
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Ron
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Ron
>>>>>
>>>>
>>>> Ron
>>>
>>
>> Ron
>

Ron
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

In article <g62vb19re6773t54ne849mgi7ulmqgeaps@4ax.com>,
miller.90@spamlessosu.edu wrote:

> On Sun, 26 Jun 2005 13:05:10 -0400, "FG" <personne@videotron.cam>
> wrote:
>
> >Read your manual and detailed instructions below.
>
> There's nothing in any manual about this, and the only "detailed
> instructions below" are the ones I wrote myself. I'm asking if you
> had any trouble using AWDFLASH to program your BIOS Savior. I did,
> and I'm wanting to know if my experience was the exception or the
> rule.
>
> Ron

I wonder if AWDFLASH has special case code working in it, so you
get different responses depending on the motherboard ? Did you
try /wb to force writing the boot block of the BIOS Savior chip ?
Would it be complaining about the checksum of the boot block
on the new chip, or the checksum of the main code area ?

Now, I just did an experiment, of no particular value. You mention
how EZFLASH was able to flash the chip, and yet AWDFLASH could not.
Using a hex edit, I took a look through an A8N-SLI Deluxe BIOS file.
(I happened to have one from a previous experiment.) Files within
an Award BIOS are delimited by the string "-lh5-". I take two
characters before -lh5-, on the suspicion they could be a checksum,
then copy all the code until the next -lh5- string. (I used to do
this without a hex editor, using "splitawd", but the new BIOS files
befuddle that program.)

In the following example, the file name is declared soon after the
the -lh5-

%K-lh5-`VØ&@ awdflash.exe

If I decompress that LHA file (chunk of code delimited by -lh5-
header), the resulting file left in the folder is "awdflash.exe"
(no surprise), and it has exactly the same size and checksum,
as the AWDFLASH that comes with the BIOS file I downloaded (my
downloaded ZIP file had a BIOS file, a text file, and AWDFLASH
in it). In other words, in this case AWDFLASH and EZFLASH are
one in the same animal, and the execution environment must be
causing different behaviors (such as tolerating checksum errors
or the like).

A version string inside the program reads "AwardBIOS Flash Utility
for ASUS V1.11", so that is not the same program as 8.24b. It
is 44886 bytes in length.

So, I think AWDFLASH has capabilities that remain to be tapped...

It seems the A8N-SLI_deluxe_1009sd02.zip containing its own copy
of AWDFLASH is no longer available. The flash.txt file included
in the ZIP file says (and this tells you it was cooked up at
Asus Germany):

"ACHTUNG:

Dieses BIOS darf NUR mit den folgenden Flashtoolversionen
upgedated werden (oder h–here Versionen) !

Keine ”lteren Versionen verwenden !

Warning:

This BIOS can only be flashed with the following flashtool
versions (or higher versions) ! Do NOT use older versions !

- ASUS LiveUpdate v6.05.01
- ASUS AWDFLASH v1.11

Flashtools -> ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/BIOS_FLASH_UTILS"

and if you go here, this is the same version of awdflash included
in the 1009sd02 download, as well as being the same file as
you get when extracting it from inside a BIOS file. This is
version 1.11 ...

ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/BIOS_FLASH_UTILS/DOS/AWDFLASH/awdflash.exe

Since you have the BIOS Savior, try experimenting with that
version of awdflash (1.11), and see how it behaves.

Paul
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Tue, 28 Jun 2005 04:17:01 -0400, nospam@needed.com (Paul) wrote:

>In article <g62vb19re6773t54ne849mgi7ulmqgeaps@4ax.com>,
>miller.90@spamlessosu.edu wrote:
>
>> On Sun, 26 Jun 2005 13:05:10 -0400, "FG" <personne@videotron.cam>
>> wrote:
>>
>> >Read your manual and detailed instructions below.
>>
>> There's nothing in any manual about this, and the only "detailed
>> instructions below" are the ones I wrote myself. I'm asking if you
>> had any trouble using AWDFLASH to program your BIOS Savior. I did,
>> and I'm wanting to know if my experience was the exception or the
>> rule.
>>
>> Ron
>
>I wonder if AWDFLASH has special case code working in it, so you
>get different responses depending on the motherboard ? Did you
>try /wb to force writing the boot block of the BIOS Savior chip ?
>Would it be complaining about the checksum of the boot block
>on the new chip, or the checksum of the main code area ?
>
>Now, I just did an experiment, of no particular value. You mention
>how EZFLASH was able to flash the chip, and yet AWDFLASH could not.
>Using a hex edit, I took a look through an A8N-SLI Deluxe BIOS file.
>(I happened to have one from a previous experiment.) Files within
>an Award BIOS are delimited by the string "-lh5-". I take two
>characters before -lh5-, on the suspicion they could be a checksum,
>then copy all the code until the next -lh5- string. (I used to do
>this without a hex editor, using "splitawd", but the new BIOS files
>befuddle that program.)
>
>In the following example, the file name is declared soon after the
>the -lh5-
>
>%K-lh5-`VØ&@ awdflash.exe
>
>If I decompress that LHA file (chunk of code delimited by -lh5-
>header), the resulting file left in the folder is "awdflash.exe"
>(no surprise), and it has exactly the same size and checksum,
>as the AWDFLASH that comes with the BIOS file I downloaded (my
>downloaded ZIP file had a BIOS file, a text file, and AWDFLASH
>in it). In other words, in this case AWDFLASH and EZFLASH are
>one in the same animal, and the execution environment must be
>causing different behaviors (such as tolerating checksum errors
>or the like).
>
>A version string inside the program reads "AwardBIOS Flash Utility
>for ASUS V1.11", so that is not the same program as 8.24b. It
>is 44886 bytes in length.
>
>So, I think AWDFLASH has capabilities that remain to be tapped...
>
>It seems the A8N-SLI_deluxe_1009sd02.zip containing its own copy
>of AWDFLASH is no longer available. The flash.txt file included
>in the ZIP file says (and this tells you it was cooked up at
>Asus Germany):
>
> "ACHTUNG:
>
> Dieses BIOS darf NUR mit den folgenden Flashtoolversionen
> upgedated werden (oder h–here Versionen) !
>
> Keine ”lteren Versionen verwenden !
>
> Warning:
>
> This BIOS can only be flashed with the following flashtool
> versions (or higher versions) ! Do NOT use older versions !
>
> - ASUS LiveUpdate v6.05.01
> - ASUS AWDFLASH v1.11
>
> Flashtools -> ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/BIOS_FLASH_UTILS"
>
>and if you go here, this is the same version of awdflash included
>in the 1009sd02 download, as well as being the same file as
>you get when extracting it from inside a BIOS file. This is
>version 1.11 ...
>
>ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/BIOS_FLASH_UTILS/DOS/AWDFLASH/awdflash.exe
>
>Since you have the BIOS Savior, try experimenting with that
>version of awdflash (1.11), and see how it behaves.
>
> Paul


Wow, what a huge effort!
I downloaded the 1.11 AWDFLASH, and I'll try flashing the BIOS Savior
with it.
More later.

Ron
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

I just ran across a new low-price leader for the RD1-PCM4 at Paragon
Computer Accessories:
http://www.paragonca.com/rd1.html

On Wed, 8 Jun 2005 05:43:54 -0400, "J&SB" <jandsb@cox.net> wrote:

>There are complete kits here:
>http://www.frozencpu.com/scan/se=Electronics/se=IOSS%20BIOS%20Savior/mp=menu_search.html
>for about $25 but again, it's difficult to know which, if any, is compatible
>with the A8N-SLI or A8N-SLI Deluxe.
>
>
>"milleron" <millerdot90@SPAMlessosu.edu> wrote in message
>news:sfbca11g42pstvpjklkorjdc69au7ip1cl@4ax.com...
>>
>> Asus' Crash-Free BIOS notwithstanding, the most elegant protection
>> against BIOS-flashing disasters is the BIOS Savior by IOSS in Taiwan.
>> Unfortunately, they don't seem to have updated their Web site and
>> compatibility list for about four years. Nevertheless, the BIOS
>> Savior is still for sale. Mwave has a 4MB version,
>> http://www.mwave.com/mwave/viewspec.hmx?scriteria=BA09803
>> but there's no compatibility table there, either.
>> Is it possible that this version would work with the 4MB BIOS on the
>> A8N-SLI?
>>
>>
>> Ron
>

Ron