D
Darkfalz
ftp://ftp.asus.com.tw/pub/ASUS/mb/sock478/p4p800/P4P81015.zip
No idea what's new.
No idea what's new.
D
Darkfalz
Darkfalz said:
1.. Do not use old version Afudos.exe to flash BIOS. Must use new
Afudos.exe which is included in zip file to flash BIOS.
2.. Using ASUSLiveUpdate to flash BIOS,you need to upgrade ASUSLiveupdate
to v 5.22.02 or later before flash BIOS.
3.. Please do not use Ezflash for updating this BIOS unless the loaded
BIOS is of version 1014.
4.. Support new CPUs. Please refer to our website at:
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
5.. Fix boot devices failed to be disabled when more than one device are
in the same group.
6.. Revise USB module.
S
Sharky
Wow, only i have replaced my P4P800DX with P4C800DX.
With the same 1014 bios-bug.
Where is the 1015 for the P4C800 ??
With the same 1014 bios-bug.
Where is the 1015 for the P4C800 ??
R
Roy Coorne
Darkfalz honoured us with the following info:
Which new CPUs? Prescott ("*E") is satisfied with BIOS 1014.
Revised USB module - HTH.
Roy
Which new CPUs? Prescott ("*E") is satisfied with BIOS 1014.
Revised USB module - HTH.
Roy
M
Maximus
Darkfalz said:
Asus seems following the confusing process for products and services.
Why is it so complex, or making it complex, with using Afudos.exe; EZflash;
and
ASUS_LiveUpdate on different versions of BIOS of the SAME motherboard(s) ??
If LiveUpdate is safe enough, or one more version, EZFlash, just to be safe
to
update by either of the two would make users feel safe. Or is this confusing
way
a good and reliable way for users to fry their boards and have to buy
another ?
Unbelievable !!
D
Darkfalz
Why is it so complex, or making it complex, with using Afudos.exe;
EZflash;
Live Update is for Windows dummies who dont' know what a command prompt or
"DOS mode" is. Unfortunately, there are lots of people like this.
AFUDOS is for competent people and probably the preferred (and old
fashioned) way of updating.
EZFlash is more of a disaster recovery than a flashing method, but since
flashing BIOSes is what it does, no harm in letting it do just that.
I don't see what you're so upset about.
EZflash;
Live Update is for Windows dummies who dont' know what a command prompt or
"DOS mode" is. Unfortunately, there are lots of people like this.
AFUDOS is for competent people and probably the preferred (and old
fashioned) way of updating.
EZFlash is more of a disaster recovery than a flashing method, but since
flashing BIOSes is what it does, no harm in letting it do just that.
I don't see what you're so upset about.
T
Todd Clayton
Darkfalz said:
Well, much to my own chagrin, I've found myself using Live Update more
and more. I don't have a floppy drive in this PC to make bootable. Plus
I've also been avoiding burning a CD for a 512k file to use EZFlash.
I don't trust it as far as I could throw it, but so far so good.
--
+---------------------------------+--------------------------------+
| Todd Clayton aka DJ Todd | Real Synthetic Audio |
| http://www.synthetic.org | Electro-Industrial-Synthpop |
| irc.habber.net #rmipeople | radio for the net-generation. |
| (e-mail address removed) | Unlicensed, Unregulated, and |
| ICQ: 56785153 | Unconventional. |
+---------------------------------+--------------------------------+
<exii> You know you suck when Christ Analogue outsells you.
M
Maximus
Darkfalz said:
I agree totally with the function assumed for each "method"; but if you read
the original post - re-post here - you can see the phrase: DO NOT in front
of Afudos, etc.; with asteriks for added emphasis:
1.. Do *NOT* use *old version* Afudos.exe to flash BIOS. MUST use *NEW*
Afudos.exe which is included in zip file to flash BIOS.
2.. Using ASUSLiveUpdate to flash BIOS, you need to upgrade ASUSLiveupdate
to * v 5.22.02 or later * before flash BIOS.
3.. Please do NOT use Ezflash for updating *this* BIOS *unless* the
loaded
BIOS is of version 1014.
4.. Support new CPUs. Please refer to our website at:
http://www.asus.com.tw/support/cpusupport/cpusupport.aspx
5.. Fix boot devices failed to be disabled when more than one device are
in the same group.
6.. Revise USB module
If many people out there are "dummies", it is reasonable to assume too that
they
may not read or check the flash utilities to use before flashing. But, risks
probably
become higher if not only the BIOS but also the flash-utility are new
versions each
time they are released. Not sure if this is a waste of time or not, for
revising/renovating
flash-utility.
My response may seem hastily irritated; but that is only appearance.
Sorry for any misunderstanding.
F
fisho
Just tried to find it, looks like it has been removed.
P
Paul
"Maximus" said:
It does seem strange, in this day and age, to have these utilities
thwarted on a per-BIOS-release basis. Some of this has to do with
reflashing the "boot block", and sometimes Asus makes you download
a "special file", in which all that is happening, is an extra argument
is being fed to the flasher utility, to have it update the boot block.
This is bloody stupid, when you consider that the CrashFree feature
_relies_ on the Boot Block not being flashed, as if the Boot Block
gets corrupted, then CrashFree isn't going to work. The whole
premise of a Boot Block, is the services it provides are very
simple (enough code so a new BIOS can be flashed), and the Boot Block
code should be thoroughly tested before the motherboard is released.
The rest of the BIOS can be written after the motherboard is
released (like the code to read the SPD on the DIMMs or set the
manual memory timings)
And, seeing as customers can return the motherboard via RMA, it
only increases warranty expense, to have a crappy BIOS flashing
method. As Asus likes to count every penny, when it comes to putting
components on the motherboard, you think they would rethink how the
flasher utilities are supposed to work.
If they wanted to, Asus could put a header on each BIOS file, and
the header could contain opcodes or special instructions, to feed
to the flasher utilities. Then, the flasher utilities would always
work, and the BIOS file would be fiddled to suit the situation.
Having to encode the flashing algorithm as a series of instructions
in a README file, is crazy.
Paul
D
Darkfalz
Oh dear.... that's not a good sign. I'm having no problems so far though.
D
Darkfalz
Darkfalz said: