FromTheRafters wrote:
> "~BD~"<~BD~@nomail.afraid.org> wrote in message
> news:BNSdnTuM_ZLf313RnZ2dnUVZ8omdnZ2d@bt.com...
>> FromTheRafters wrote:
>>> "~BD~"<~BD~@nomail.afraid.org> wrote in message
>>> news:7OKdnVAJtM3Rs13RnZ2dnUVZ8qmdnZ2d@bt.com...
>>
>> [....]
>>
>>>> You have now confused me, Dustin!
>>>>
>>>> Have you actually *removed* and replaced a BIOS chip around 100
>>>> times
>>>> as you stated - or simply flashed the chip to replace the data?
>>>
>>> I believe he meant exactly what he said.
>>>
>>> Some BIOS chips had to be removed and put in a jig (the eeprom burner
>>> Dustin mentioned) to reprogram them. Even some that were flashable by
>>> local software needed to be done this way because the computer with
>>> the
>>> corrupted BIOS code wouldn't boot and offer up a software platform to
>>> run the reflashing routine. The BIOS recovery jumper scenario was
>>> developed to get around this unfortunate situation - it holds enough
>>> non-flashable (permanent) BIOS routines to present the software
>>> environment needed to re-flash the chip 'in place' with the new BIOS
>>> image stored on a floppy.
>>>
>>> [...]
>>
>> Ah! Thanks for that info. FTR.
>>
>> When I flashed the BIOS that one time, I used a floppy disk/drive.
>> Many desktops/laptops nowadays don't have a floppy drive. How is BIOS
>> flashing carried out on such machines? TIA
>
> Dual BIOS?
>
> I don't know, because I no longer keep up with such things, but ISTR
> hearing of modern BIOSes having a rudimentary yet full functioning BIOS
> program in a non-flashable area of the same chip that has the EEPROM.
> Sorta like the "BIOS jumper" routine, except that it is a full BIOS
> program not just barely enough to reflash from a floppy. You set the
> jumper, reboot the machine, use this environment to get a BIOS upgrade
> image from the vendor, and reflash your EEPROM - then de-energize - set
> the jumper back - reboot.
>
>

Significant changes, eh?!!!

It seems as if you *are* keeping up with such things after all!