Bad Bios Flash or?

  • Thread starter Thread starter Ottar Tverberg
  • Start date Start date
O

Ottar Tverberg

I tried the asus liveupdate on a A7V600-x and got checksum error...

I didn't read enough in the manual to do a proper recovery and had to shut
down for the night...

Now I'we read the instruction and prepared for a manual flash from disk..
But, the thing will not boot... I get long-short continous beeps and no
indication on screen..
Something is wrong but what?

Tried clearing cmos a fiew times, but to no help..

regards
ottar t
 
"Ottar Tverberg" said:
I tried the asus liveupdate on a A7V600-x and got checksum error...

I didn't read enough in the manual to do a proper recovery and had to shut
down for the night...

Now I'we read the instruction and prepared for a manual flash from disk..
But, the thing will not boot... I get long-short continous beeps and no
indication on screen..
Something is wrong but what?

Tried clearing cmos a fiew times, but to no help..

regards
ottar t
Click to expand...

This is the largest collection of beep codes I know of.
http://www.bioscentral.com/beepcodes/awardbeep.htm

Section 2.1.3 in the user manual indicates the board
has "Crashfree BIOS 2". Your motherboard CD contains
a BIOS file at the root level of the CD, and depending
on what version of the BIOS that happens to be, you could
try to recover the motherboard with that. If you had
a Sempron for example, you may want to do a BIOS recovery
with a later version of the BIOS than the one on the
motherboard CD. (The paper label on the BIOS chip
may indicate the release number of the factory BIOS.
Compare it to the table on this page, for your board.
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx )

Crashfree supports operation from a floppy disk or from
a CD. According to the manual, CrashFree will look for
the exact file "A7V600-X.rom" on either of those disks.
If you download an Asus BIOS to flash, you would
rename the file to match the above file name.

Boot block recovery is another form of BIOS recovery,
and in that case, a floppy containing a MSDOS boot
system, an autoexec.bat with a one-liner BIOS flash
command, a BIOS flashing program, and the BIOS file,
could be used to reflash the BIOS. But, in a sense,
CrashFree is the same thing, as you are relying on
the CrashFree code in the Boot Block of the BIOS
chip, to orchestrate the recovery. I would think if
CrashFree doesn't work, or the BIOS cannot get past
the error condition it is finding, then attempting
recovery via a Boot Block procedure won't work either.
For the Boot Block procedure to work, you would need
to be seeing the BIOS making attempts to read the
floppy drive - if it won't touch the floppy drive,
then another recovery procedure will be required.

What typically has happened to most users, is the
BIOS flashing program erases the Boot Block and
the Main BIOS code, and then the new code fails to
be flashed into the chip. With the Boot Block
erased, there is no longer any CrashFree code
available to run. (CrashFree would only really
live up to its name if there were two BIOS flash
chips. Some Gigabyte motherboards have that
feature.)

Now, since you are getting beep codes, that means
there is _some_ amount of BIOS code present. What
I cannot tell you, is where that BIOS code is
getting stuck. If somehow, you flashed the wrong
motherboard BIOS into the board, there is no way
to predict what the symptoms might be. Try
inserting a floppy into the floppy drive, with
a .ROM file on it for Crashfree to use, and see
if the BIOS will read the floppy. Wait several
minutes, as you don't want to interrupt the
flash operation, if it is happening.

If you visit the badflash.com website, they offer
a service, where they will ship you a BIOS chip with
a BIOS code programmed into it. In a couple of
days, you could have a BIOS chip in your hand. You
unplug the computer, take note of the BIOS chip
orientation (has an arrow on the plastic top), pull
the old BIOS chip out with the "U" shaped tool, then
push the new chip into place with your thumb. You have
to be careful not to bend the pins in the BIOS chip
socket while doing this, which is why the "U" shaped
removal tool is a good thing to use. The arrow mark
on the top of the new chip has to match the alignment
of the old chip, as otherwise the chip will get
burned.

In some countries Asus also offers the BIOS chip
replacement for $25, but it may take Asus longer
to ship the chip to you, than an Internet-based BIOS
chip replacement firm like badflash.com .

When doing the "clear CMOS" procedure, I hope you
have been unplugging the computer...

Good luck,
Paul
 
På Wed said:
This is the largest collection of beep codes I know of.
http://www.bioscentral.com/beepcodes/awardbeep.htm

Section 2.1.3 in the user manual indicates the board
has "Crashfree BIOS 2". Your motherboard CD contains
a BIOS file at the root level of the CD, and depending
on what version of the BIOS that happens to be, you could
try to recover the motherboard with that. If you had
a Sempron for example, you may want to do a BIOS recovery
with a later version of the BIOS than the one on the
motherboard CD. (The paper label on the BIOS chip
may indicate the release number of the factory BIOS.
Compare it to the table on this page, for your board.
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx )

Crashfree supports operation from a floppy disk or from
a CD. According to the manual, CrashFree will look for
the exact file "A7V600-X.rom" on either of those disks.
If you download an Asus BIOS to flash, you would
rename the file to match the above file name.

Boot block recovery is another form of BIOS recovery,
and in that case, a floppy containing a MSDOS boot
system, an autoexec.bat with a one-liner BIOS flash
command, a BIOS flashing program, and the BIOS file,
could be used to reflash the BIOS. But, in a sense,
CrashFree is the same thing, as you are relying on
the CrashFree code in the Boot Block of the BIOS
chip, to orchestrate the recovery. I would think if
CrashFree doesn't work, or the BIOS cannot get past
the error condition it is finding, then attempting
recovery via a Boot Block procedure won't work either.
For the Boot Block procedure to work, you would need
to be seeing the BIOS making attempts to read the
floppy drive - if it won't touch the floppy drive,
then another recovery procedure will be required.

What typically has happened to most users, is the
BIOS flashing program erases the Boot Block and
the Main BIOS code, and then the new code fails to
be flashed into the chip. With the Boot Block
erased, there is no longer any CrashFree code
available to run. (CrashFree would only really
live up to its name if there were two BIOS flash
chips. Some Gigabyte motherboards have that
feature.)

Now, since you are getting beep codes, that means
there is _some_ amount of BIOS code present. What
I cannot tell you, is where that BIOS code is
getting stuck. If somehow, you flashed the wrong
motherboard BIOS into the board, there is no way
to predict what the symptoms might be. Try
inserting a floppy into the floppy drive, with
a .ROM file on it for Crashfree to use, and see
if the BIOS will read the floppy. Wait several
minutes, as you don't want to interrupt the
flash operation, if it is happening.

If you visit the badflash.com website, they offer
a service, where they will ship you a BIOS chip with
a BIOS code programmed into it. In a couple of
days, you could have a BIOS chip in your hand. You
unplug the computer, take note of the BIOS chip
orientation (has an arrow on the plastic top), pull
the old BIOS chip out with the "U" shaped tool, then
push the new chip into place with your thumb. You have
to be careful not to bend the pins in the BIOS chip
socket while doing this, which is why the "U" shaped
removal tool is a good thing to use. The arrow mark
on the top of the new chip has to match the alignment
of the old chip, as otherwise the chip will get
burned.

In some countries Asus also offers the BIOS chip
replacement for $25, but it may take Asus longer
to ship the chip to you, than an Internet-based BIOS
chip replacement firm like badflash.com .

When doing the "clear CMOS" procedure, I hope you
have been unplugging the computer...

Good luck,
Paul
Click to expand...


I unplugged evrything when trying to clear cmos...

When I download new bios they are named x.awd, not x.rom.... should i
rename the file anyhow?

I occasionally get the mb to boot from floppy, so maybe the recovery will
work provised the file in correct format is awailable on the floppy.

thanks for the info

regards

ottar t
 
I unplugged evrything when trying to clear cmos...

When I download new bios they are named x.awd, not x.rom.... should i
rename the file anyhow?

I occasionally get the mb to boot from floppy, so maybe the recovery will
work provised the file in correct format is awailable on the floppy.

thanks for the info

regards

ottar t
Click to expand...

The reason for renaming a7v6x008.awd to A7V600-X.rom
is so the CrashFree code can find it. CrashFree doesn't
have a user interface, and looks for a fixed file name.

Other Asus BIOS flashing options will offer the ability
to name the input file, in which case renaming the file
is not necessary. Since your floppy is working, maybe
you could try booting MSDOS via the floppy. Place a
copy of Aflash and a file like a7v6x008.awd on your
MSDOS boot floppy. See section 2.1.2 "Using Aflash to
update the BIOS" in the manual.

You can get the latest version of Aflash (221) here.
http://au.asus.com/support/download/item.aspx?ModelName=Tools&Type=All&SLanguage=en-us

Pressing <alt><F2> is another option, and that will
cause EZflash to be executed from the BIOS chip (assuming
that part of the chip is not corrupted).

When you decompress the ZIP file you downloaded from the
Asus site, verify that the file size is 262144 bytes.
That is an exact multiple of 2 and is 256KB, the size of the
flash chip.

One reason for using Aflash, is if the flash chip contents
are so corrupted, that EZflash cannot be trusted. In any
case, since the floppy is working, you should be able
to use one of the options to place an earlier BIOS on the
board.

HTH,
Paul
 
Tried clearing cmos a fiew times, but to no help..

Remove the battery for about 5 minutes.
 
På Thu said:
The reason for renaming a7v6x008.awd to A7V600-X.rom
is so the CrashFree code can find it. CrashFree doesn't
have a user interface, and looks for a fixed file name.

Other Asus BIOS flashing options will offer the ability
to name the input file, in which case renaming the file
is not necessary. Since your floppy is working, maybe
you could try booting MSDOS via the floppy. Place a
copy of Aflash and a file like a7v6x008.awd on your
MSDOS boot floppy. See section 2.1.2 "Using Aflash to
update the BIOS" in the manual.

You can get the latest version of Aflash (221) here.
http://au.asus.com/support/download/item.aspx?ModelName=Tools&Type=All&SLanguage=en-us

Pressing <alt><F2> is another option, and that will
cause EZflash to be executed from the BIOS chip (assuming
that part of the chip is not corrupted).

When you decompress the ZIP file you downloaded from the
Asus site, verify that the file size is 262144 bytes.
That is an exact multiple of 2 and is 256KB, the size of the
flash chip.

One reason for using Aflash, is if the flash chip contents
are so corrupted, that EZflash cannot be trusted. In any
case, since the floppy is working, you should be able
to use one of the options to place an earlier BIOS on the
board.

HTH,
Paul
Click to expand...

on the cd that followed the mb there are tree files

A7V6SE1001.011
a7v6x002.awd
a7v61006.awd

now the ez flash is supposed to find one of these files from the cd.. so
which one is it?
I downloaded the newer bios a7v6x008.awd and renamed it to a7v6x008.rom,
but should I rename it to A7V600-X.rom instead?

I now get loong and short beeps continous.. again... Yesterday I managed
to get some more contact with the mb by playing with the reset button...

Will try once more to get in contact with the board, but need to use the
crashfree bios function as the mb does not respond to keyboard commands..

regards
ottar t
 
"Ottar Tverberg" said:
on the cd that followed the mb there are tree files

A7V6SE1001.011
a7v6x002.awd
a7v61006.awd

now the ez flash is supposed to find one of these files from the cd.. so
which one is it?
I downloaded the newer bios a7v6x008.awd and renamed it to a7v6x008.rom,
but should I rename it to A7V600-X.rom instead?

I now get loong and short beeps continous.. again... Yesterday I managed
to get some more contact with the mb by playing with the reset button...

Will try once more to get in contact with the board, but need to use the
crashfree bios function as the mb does not respond to keyboard commands..

regards
ottar t
Click to expand...

Asus motherboard CDs usually support more than one motherboard.
My P4C800-E CD for example, has other motherboard BIOS on it
( p4c800.rom , P4c800b.rom , P4C800E.rom , P4c800ed.rom , P4p800se.rom ,
P4p8x.rom , P4p8xse.rom ). None of those files has a version
number like the files you found above. The file name is just the
motherboard name.

Your three BIOS files above are likely for A7V600 SE, A7V600-X,
and A7V600 motherboards.

I tried looking in the BIOS file, but don't see anything in the
EZflash code, in terms of a file name. I would rename what
ever BIOS file you plan to use, to A7V600-X.rom as explained in
the manual. That is the best I can suggest.

A long and short beep code could be a memory error.

Paul
 
På Fri said:
Asus motherboard CDs usually support more than one motherboard.
My P4C800-E CD for example, has other motherboard BIOS on it
( p4c800.rom , P4c800b.rom , P4C800E.rom , P4c800ed.rom , P4p800se.rom ,
P4p8x.rom , P4p8xse.rom ). None of those files has a version
number like the files you found above. The file name is just the
motherboard name.

Your three BIOS files above are likely for A7V600 SE, A7V600-X,
and A7V600 motherboards.

I tried looking in the BIOS file, but don't see anything in the
EZflash code, in terms of a file name. I would rename what
ever BIOS file you plan to use, to A7V600-X.rom as explained in
the manual. That is the best I can suggest.

A long and short beep code could be a memory error.

Paul
Click to expand...

Will try to reseat the memory sticks, but should I remove all memory
sticks (2x512mb)and ide/ s-ata cables so that just the display card and
floppy are connected?
think I have read something like this in the past..

The thing about renaming the bios is not mentioned at all in the manual,
so I could not get these things to work unless you helped me..

regards
ottar t
 
"Ottar Tverberg" said:
Will try to reseat the memory sticks, but should I remove all memory
sticks (2x512mb)and ide/ s-ata cables so that just the display card and
floppy are connected?
think I have read something like this in the past..

The thing about renaming the bios is not mentioned at all in the manual,
so I could not get these things to work unless you helped me..

regards
ottar t
Click to expand...

Perhaps we should go back over the sequence of events.
I'm not sure I understand what your problem is.

Was your A7V600-X working properly before using Asus Update ?
What was your hardware configuration ?
A7V600-X
Processor type - sempron ? athlonxp ? what core clock speed ?
Memory - 2 x 512MB in slot 1 and slot 3 ?
Floppy disk drive ?
Hard drive and CDROM drive on IDE cable ?
Power supply brand and wattage rating ?
Was the "checksum error" reported by Asus Update ?
Does the current BIOS show "bad BIOS checksum" when the computer
starts ?

Does the BIOS now start correctly some times, but not
all the time ? You say that pressing the RESET button
several times gives some different symptoms. Describe the
symptoms in each case - the beep code when it fails, and
what text is on the screen when it succeeds to start.

Does text appear on the screen when the computer starts ?

Are any error messages being delivered ?

You are receiving a repetitive "one long" "one short" error
code - does this happen all the time, even when the BIOS
is able to print on the screen ?

The reason I am asking all these questions, is to determine
whether your computer is working well enough to attempt
flashing the BIOS chip or not. It could be that the
symptoms you are seeing, will require those symptoms to
be fixed first.

It could be that there is nothing wrong with the BIOS at all
right now - but you are going to have to describe precisely
what is happening. If you have RAM errors, I doubt any
BIOS flash upgrade is going to work.

If you are having a problem with the RAM, insert one DIMM in
slot 3. That is the slot furthest from the processor. If that
stick still gives the "one long" "one short" beep error, unplug
the computer and replace that DIMM with your second DIMM.
The purpose of this test, is to see if one of the DIMMs is
defective. Testing a single DIMM at a time, is the least
stressful hardware condition.

*****
The following is a summary of the BIOS flashing methods:

1) CrashFree BIOS 2
This BIOS flashing method is restricted to one set of
symptoms. If you see "Bad BIOS Checksum" when the computer
first starts, and the computer is not overclocked, then
that means the Boot Block is intact, but the BIOS code has
found that the checksum of the main BIOS code is incorrect.
Inserting the motherboard CD will allow the motherboard to
reflash the BIOS.

Before doing something like this, you will want to research
the requirements for your motherboard and processor type.
Visit http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
Type "A7V600-X" in the search box. The Sempron uses version
1006 of the BIOS or later. Other processors can use any BIOS.
If the motherboard CD has a version of BIOS previous to 1006
and you own a Sempron, then inserting the motherboard CD would
be a bad thing. If you flash an older BIOS into the board,
then the board will no longer POST, and you will need to visit
badflash.com to recover.

If you take a floppy, download a BIOS from the Asus download
page, then rename the unzipped file to "A7V600-X.rom", and
insert that floppy when you see the error message
"Bad BIOS Checksum", then that would allow a BIOS flash of
a version of the BIOS later than 1006. That is how you would
handle things if you are using a Sempron. For other AthlonXP
processors, the motherboard CD BIOS is good enough to recover
with.

Always verify the file size of the .rom or .awd you are using
on the floppy disk. It should be 262144 bytes, if the BIOS
flash chip is 256KB. Checking the size is a safeguard against
using the wrong file.

2) EZ Flash
If the BIOS is functioning correctly, and you wish to upgrade
the BIOS, you can press <alt> <f2> when the BIOS screen
first appears. The BIOS chip contains a copy of a BIOS
flash program called EZ Flash.

EZ Flash will prompt you for the filename. It expects to
find the BIOS file on a floppy diskette. You type the name
of the file at the prompt "Please enter filename for new
BIOS". If the file on the floppy is named a7v6x008.awd , then
that is what you type into the screen. Answer the other prompts
with "Y" for Yes. When EZ flash displays the version number of
the BIOS it is about to flash, verify that the number is the
one you expect. If you downloaded 1006, the screen should show
that 1006 number. If the information is incorrect, then do not
proceed any further.

3) Aflash
There is a BIOS flashing program that can be run from MSDOS.
To use it, copy the aflash executable onto an MSDOS boot disk.
Copy the new BIOS file a7v6x008.awd to the floppy as well.
Boot the floppy. You should see an MSDOS prompt. Type
"aflash" at the prompt, to execute the flash program on the
floppy disk. Press "2" to update the BIOS, after verifying
the information on the screen. Type in the full path name
of the BIOS file "A:\a7v6x008.awd". The file could even be
stored on the hard drive, I think. When the BIOS prompts you,
press "Y" to do the update, again verifying that the proposed
BIOS version is the correct one.

4) Asus Update
This method works from Windows. Boot into Windows, install
Asus Update, execute the installed program, and follow the
prompts. It is generally best if the BIOS file you are about
to flash, is stored locally on the disk drive, just before
the flashing operation begins. That prevents a networking
problem from interrupting the flash operation.

Option (1) is used when the BIOS is corrupt. Option 2-4 are
used when the computer is operating normally. The most dangerous
flashing method is Asus Update, as there are more things that can
go wrong, than in a simpler environment like MSDOS. EZ Flash would
be a good method, as long as there are no warning messages on the
Asus download page stating not to use that update method. Always
check the Asus download page for any warnings about methods 2-4
as being inappropriate for a certain version of BIOS.
******* end of summary *******

Paul
 
På Sat said:
Perhaps we should go back over the sequence of events.
I'm not sure I understand what your problem is.

Was your A7V600-X working properly before using Asus Update ?
YES

What was your hardware configuration ?
A7V600-X
Processor type
Click to expand...
athlonxp Thorton 2000MHz 133FSB
memory - 2 x 512MB in slot 1 and slot 2 PC3200
Floppy disk drive
Hard drive on serial-ATA
DVD/ CDROM drives on IDE cable
Enermax EG365-VE 365Watt
Was the "checksum error" reported by Asus Update ?
Click to expand...

Yes, and had i been aware of what this lead to I would have put the cd or
a floppy in the slots before restart
Does the current BIOS show "bad BIOS checksum" when the computer
starts ?
Click to expand...
It did so when I last got a POST from it, but I did not get it to fetch
new bios from floppy, probably because I didn't rename it to .rom as this
is not stated anywhere in the manual..
Does the BIOS now start correctly some times, but not
all the time ? You say that pressing the RESET button
several times gives some different symptoms. Describe the
symptoms in each case - the beep code when it fails, and
what text is on the screen when it succeeds to start.
Click to expand...

I havent been able to get the mb to post since a fiew days ago, but when I
got it to post it said somthing like

xxx boot block version or revision 1 ..
Bios Checksum error
Detecting floppy
some times it also detected cd-drives
Does text appear on the screen when the computer starts ?
Click to expand...
Not anymore it does
Are any error messages being delivered ?
Click to expand...
Not anymore
You are receiving a repetitive "one long" "one short" error
code - does this happen all the time, even when the BIOS
is able to print on the screen ?
Click to expand...
Now I dont get any responce from the MB except for the loong and short
beeps which runs continously.
Nothing is showing up on the screen
The reason I am asking all these questions, is to determine
whether your computer is working well enough to attempt
flashing the BIOS chip or not. It could be that the
symptoms you are seeing, will require those symptoms to
be fixed first.

It could be that there is nothing wrong with the BIOS at all
right now - but you are going to have to describe precisely
what is happening. If you have RAM errors, I doubt any
BIOS flash upgrade is going to work.

If you are having a problem with the RAM, insert one DIMM in
slot 3. That is the slot furthest from the processor. If that
stick still gives the "one long" "one short" beep error, unplug
the computer and replace that DIMM with your second DIMM.
The purpose of this test, is to see if one of the DIMMs is
defective. Testing a single DIMM at a time, is the least
stressful hardware condition.
Click to expand...

I get the same loong beep and short with either dimm installed or with no
installed..
Dont think its related to memory, and i dont think the athlon is toasted
either, has been workin flawlessly in my older mb + the week i had this mb
working before the fatal windows flash..



unfortunatly i used the asus update methode...

I was running XP PRo SP2 fully updated befor the crash with the pc-cillin
2002 updated as antivirus..


From the lack of responce from the card now, i guess a new flashed bios is
the only option to get things working again.. (or a new mb)

thank you for your help
Had the description for renaming the bios files befor putting it on the
floppy I would have recovered using the CrashFree BIOS 2 option... or had
i even just put in the driver cd it should have worked..

Your help seem to come to late for me, sorry

regards
ottar t
 
From the lack of responce from the card now, i guess a new flashed bios is
the only option to get things working again.. (or a new mb)

thank you for your help
Had the description for renaming the bios files befor putting it on the
floppy I would have recovered using the CrashFree BIOS 2 option... or had
i even just put in the driver cd it should have worked..

Your help seem to come to late for me, sorry

regards
ottar t
Click to expand...

Yes, when the BIOS said "Bios Checksum error", that was the
opportunity to feed it a floppy with A7V600-X.rom . As I
understand it, from reading the experiences of other people,
it seems if you don't give it the file it wants, it erases
the BIOS anyway, which means "CrashFree" only gives you one
shot. It suggests the CrashFree code is not well written.

Badflash.com should be able to help you out. They could get
you a new chip in a couple of days, while if you managed to
find the right person at Asus, it could take much longer and
cost just as much. The EEPROM programmer method is also a
possibility, as modern flash chips are getting more standardized
interfaces, meaning there are fewer variations to worry about
(LPC low pin count , FWH firmware hub, and so on). The problem is,
there are not too many EEPROM programmers available at
computer stores - I doubt I could find one in a computer
store where I live. (My former employer has many of them.)
Depending on how comprehensive the device coverage is on a
programmer, it could cost $100 or it could cost $7000.

The "hot flash" method, where you plug the erased chip into
a running motherboard, is another repair method. But with
PLCC chips, I consider it to be pretty risky. I can see how,
with care, you could do a dual inline plastic package (by
bending the leads so the device fits the socket with ease),
but with PLCC you really need some kind of adapter, to make
it easier to connect the chip. The ioss.com.tw "BIOS Savior"
is one such device, and Eksit has some of those.

http://www.eksitdata.com/ (Left hand menu, click "BIOS Savior")

The BIOS Savior model required is determined by the flash chip type.
http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionSheet.html

Paul
 
På Tue said:
Yes, when the BIOS said "Bios Checksum error", that was the
opportunity to feed it a floppy with A7V600-X.rom . As I
understand it, from reading the experiences of other people,
it seems if you don't give it the file it wants, it erases
the BIOS anyway, which means "CrashFree" only gives you one
shot. It suggests the CrashFree code is not well written.
Click to expand...

The strange thing is that there is no such file on the cd and no
description in the manual about the need to make such a backup file
awailable on floppy before proceeding with the flash trough Probe.

After this happend to me I'we read that flashing with this program is like
Russian rulett with 5 of 6 shots in the barrel...

I'm not impressed with Asus at all from my experience..
Badflash.com should be able to help you out. They could get
you a new chip in a couple of days, while if you managed to
find the right person at Asus, it could take much longer and
cost just as much. The EEPROM programmer method is also a
possibility, as modern flash chips are getting more standardized
interfaces, meaning there are fewer variations to worry about
(LPC low pin count , FWH firmware hub, and so on). The problem is,
there are not too many EEPROM programmers available at
computer stores - I doubt I could find one in a computer
store where I live. (My former employer has many of them.)
Depending on how comprehensive the device coverage is on a
programmer, it could cost $100 or it could cost $7000.

The "hot flash" method, where you plug the erased chip into
a running motherboard, is another repair method. But with
PLCC chips, I consider it to be pretty risky. I can see how,
with care, you could do a dual inline plastic package (by
bending the leads so the device fits the socket with ease),
but with PLCC you really need some kind of adapter, to make
it easier to connect the chip. The ioss.com.tw "BIOS Savior"
is one such device, and Eksit has some of those.

http://www.eksitdata.com/ (Left hand menu, click "BIOS Savior")

The BIOS Savior model required is determined by the flash chip type.
http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionSheet.html

Paul
Click to expand...

Went to ebay and ordered a new flashed bios from Biosprofi, waiting for it
now..
Even asked the webshop I bought the mb from for help. They quickly sent me
a new chip, but I guess forgot to check type and program,,, Got the new
bios yesterday, but alltough the beep is gone the mb wont POST..

Changing chip back and forth are easy, but just leaves me with beep and no
POST and no beep and no POST..
The light in my cd burner lights up now and then though, but thats
probably cause the sound cable are connected to the MB.. No light in
floppy...

regards
Ottar T
 
Il Tue, 10 May 2005 01:28:47 -0400, (e-mail address removed) (Paul) ha
scritto:
Yes, when the BIOS said "Bios Checksum error", that was the
opportunity to feed it a floppy with A7V600-X.rom . As I
understand it, from reading the experiences of other people,
it seems if you don't give it the file it wants, it erases
the BIOS anyway, which means "CrashFree" only gives you one
shot. It suggests the CrashFree code is not well written.

Badflash.com should be able to help you out. They could get
you a new chip in a couple of days, while if you managed to
find the right person at Asus, it could take much longer and
cost just as much. The EEPROM programmer method is also a
possibility, as modern flash chips are getting more standardized
interfaces, meaning there are fewer variations to worry about
(LPC low pin count , FWH firmware hub, and so on). The problem is,
there are not too many EEPROM programmers available at
computer stores - I doubt I could find one in a computer
store where I live. (My former employer has many of them.)
Depending on how comprehensive the device coverage is on a
programmer, it could cost $100 or it could cost $7000.

The "hot flash" method, where you plug the erased chip into
a running motherboard, is another repair method. But with
PLCC chips, I consider it to be pretty risky. I can see how,
with care, you could do a dual inline plastic package (by
bending the leads so the device fits the socket with ease),
but with PLCC you really need some kind of adapter, to make
it easier to connect the chip. The ioss.com.tw "BIOS Savior"
is one such device, and Eksit has some of those.

http://www.eksitdata.com/ (Left hand menu, click "BIOS Savior")

The BIOS Savior model required is determined by the flash chip type.
http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionSheet.html

Paul
Click to expand...

Hi,

you can find a good bios replacement service at the following adress

www.recoverybios.com

This site has also the RD1 Bios Savior kits

Bye
 
Halla Ottar.

Har samme mobo, og gjorde akkurat det samme som deg (for en halvtime
siden)...
Hele driten gikk til skogen...
Blir vel å kjøpe nytt da... De koster vel ikke så mye for tiden...
Sure greier, at det ikke finnes en recovery funksjon innebygget.

- Min piper ikke eller gir fra seg bilde.

- Kyrre
(e-mail address removed)
 
På 16 May 2005 09:03:50 -0400, skrev cage
Halla Ottar.

Har samme mobo, og gjorde akkurat det samme som deg (for en halvtime
siden)...
Hele driten gikk til skogen...
Blir vel å kjøpe nytt da... De koster vel ikke så mye for tiden...
Sure greier, at det ikke finnes en recovery funksjon innebygget.

- Min piper ikke eller gir fra seg bilde.

- Kyrre
(e-mail address removed)
Click to expand...

Det finns recovery, men du må tydeligvis ha det klar før flashing..
Står mye om dette i den tidligere tråden...

Jeg kjøpte ny chip ferdig flashet via ebay.de. den kostet 14 euro ferdig
tilsendt pr post fra
http://www.biosprofi.de/
Ny chip ferdig programert kom i løpet av et par dager.

Jeg betalte via PayPal..

Kontaktet komplett.no som til nå har sendt meg to chiper, en tom (ingen
POST) og en merket phoenix... Sendte de riktignok gratis, men det hjelper
jo ikke så lenge de ikke funker. Kanskje du er heldigere..

lykke til

mvh
ottar
 
Back
Top