[Ham-Computers] Final story RE: bios flash question

Sun, 15 Sep 2002 00:27:49 -0700

Hi all,

I have been blessed with a working answer to my bios-won't-flash issues!!
Actually, the problem was solved in record breaking time and in a most
professional manner by Technical Support at Nexcom Computers, the US rep for
the Peak 6220 Single Board Computer.  To rehash:  a routine bios upgrade
flash to install PIII support on my PII-only Peak 6220, kept generating a
"file sizes don't match" error from the awdflash program...no one, least of
all me, believed the file sizes really didn't match...well, the message is
true!  I had ruled out the truth of the message because my backed-up
original bios matched the new bios size exactly...little did I know that the
awdflash program was padding my factory original bios in the flash backup
process...that's why when I tried to reflash original with the backed up
original file, the sizes didn't match.

Here's the problem:  early Peak 6220's (and they mentioned this is true of
many early PII boards intended for later PIII upgrade) has a 128K PII
bios...not a 256K bios like we're all used to...so the upgrade flash was not
possible.  However, Nexcom promptly flashed me a new 256K PIII compatible
chip and FedEx'd it to me at no charge!!  Change the chip, flip a couple of
factory-only switches, stuff in a 750MHz PIII and the machine fired right
up-set a few bios configs and the PIII is up and stable as a rock.

In case there are any others out there with this potential problem, here's
the procedure:

You'll need a 256K bios chip with 6220R20B.bin bios or newer from support or
other reliable source.

Set dip switch #3 to 3-on/4-off   (sets bios memory chip sizing to
256K...opposite settings indicate a 128K bios chip)

Set dip switch S4 to 4-on  (enables flash/upgrade of bios in the
future...opposite setting disables bios upgrading as a safety precaution).

This issue is not addressed in the docs that are currently available via
download.

I did end up with a version 8-something of awdflash, if anyone is
interested.

Thanks to you all for your efforts on this issue.

regards

John Collins
_______________________________
----- Original Message -----
From: "refmon" <[email protected]>
To: <[email protected]>
Sent: Friday, September 06, 2002 12:45 AM
Subject: Re: [Ham-Computers] RE: bios flash question

> 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
> >
> >
>
>