[Ham-Computers] RE: bios flash question

Fri, 6 Sep 2002 00:45:44 -0700

Hi all,

I wanted to follow up on this thread I started...the one about the bios that
wouldn't flash.  After trying all the ideas presented here, I contacted the
US "manufacturer" (or rep) tech support, who have been amazing...the tech
support line was answered on the first ring by a responsive, knowlegeable
fellow, who tried several ideas, most of which involved issuance of the
newest and "most powerful/flexible" awdflash.exe program...no luck...a point
by point check of bios versions, board revs, bios flash enable switches, etc
still no good.  The US rep company has just contacted me asking for my
address so they can send me a new, preflashed chipset.

Now that is outstanding support of new gear, let alone 1998-vintage stuff.
I'll probably never know exactly what the base cause of all this was, but I
think that the support folks at NexComputer, Inc in Fremont California
deserve a compliment.

will advise of ultimate outcome, and thank you all who tried to help.

regards

John Collins
____________________________-
----- Original Message -----
From: "Hsu, Aaron" <[email protected]>
To: <[email protected]>
Cc: "'refmon'" <[email protected]>
Sent: Wednesday, September 04, 2002 03:18 PM
Subject: [Ham-Computers] RE: bios flash question

> Some Slot 1 systemboards will not work properly with any type of P-III
until
> *after* the BIOS is upgraded with a version that supports the P-III.
Random
> "strange" operation or downright failure to POST are common situations.
>
> I would suggest that you try using a P-II processor during the BIOS
upgrade.
> Also, make sure that any "BIOS Protection" options in the CMOS settings
are
> disabled (these prevent tampering with the BIOS, intentional or not).
Last,
> make sure that any CPU or system cache is disabled - also known to cause
> BIOS upgrade errors.
>
> And remember, unless the board supports the voltage requirements of the
> "coppermine" or "tualatin" P-III CPU's (500E, 550E, 600E, 650E, 700E, 733+
> MHz), you should use these CPU's - stick with the original P-III's (or a
> lowly P-II).
>
> 73 and good luck,
>
>   - Aaron Hsu, NN6O (ex-KD6DAE)
>     {nn6o}@arrl.net
>     {athsu}@unistudios.com
>     No-QRO Int'l #1,000,006
>     . -..- - .-. .-   ".... . .- ...- -.--"
>
>
>
> -----Original Message-----
> From: refmon [mailto:[email protected]]
> Sent: Wednesday, September 04, 2002 2:46 PM
> To: [email protected]
> Subject: [Ham-Computers] bios flash question
>
>
> Hi,
>
> My recent Win 98 shutdown fix is holding up rather well, thanks to all
that
> helped.
>
> I've run into an odd situation during an attempt at bios flash...I'm
> wondering if anyone else has seen or dealt with this, or may know where I
> should go:
>
> I routinely flash bios on many PC's and am familiar with procedures,
general
> risks, etc.  Case here involves Peak 6220 single board PC with the 440BX
> chipset dated circa 1998...support PII only..it takes a PIII but registers
> it as a PII.  I am using filename 6220R20B.bin, a specific bios update
> download which updates the bios with PIII support.  Instructions call for
> the usual usage of the awardflash utility...so far no problem.
>
> Here's what happens:  invoke awdflash, enter new bios file.bin name, yes
to
> backup, name backup...a backup file is made.  Yes to "are you sure you
want
> to program?" gets a checksum and an immediate "files are not the same
size"
> error and I'm dumped out of the program to the DOS prompt.  In
> experimenting, I tried the process using the file I had created as a
backup
> (this should be exactly what is already in flash), and I get the same
> message.
>
> Does anyone have the magic answer?  Is this cockpit error or oddity
perhaps
> of the specific board?
>
> thanks in advance for any info at all
>
> John Collins
> _____________________________
> _______________________________________________
> Ham-Computers mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/ham-computers
>
>