Reply 120 of 394, by PC Hoarder Patrol
- Rank
- l33t
As cyclone3d has already updated one of his systems from the shipping Zenith BIOS, 1.00.10 WLB08, to the latest one from the archived Zenith support page, 1.00.14 WL014, with no apparent issues, I can't foresee any problems. The only wrinkle was that the PLATFORM.BIN file which PHlash uses during the update wasn't configured to allow any way to backup the old BIOS and it'd be nice to have that backup - I'm sure some other flashing util will be able to do it when he gets a chance to test his other system.
As I posted previously, ideally BIOS & SCU are at the same revision level but between minor updates this isn't always a must. We won't really know till owners start to add & configure EISA or PCI cards with the various BIOS revisions we have available!
Yes, the BIOS is a soldered Intel flash chip.
A normal update involves booting to DOS (floppy) then inserting the BIOS update floppy & running the PHlash util and then a power cycle on completion. If the update fails then you boot from the BIOS update floppy and recovery starts automatically - there's no recovery jumper; just a BIOS write protect jumper (J6A).
Remember that the 512KB BIOS will contain not just the standard system stuff but the OB video bios and compressed elements of the SCU & selected EISA config files. If the required EISA config files aren't provided thru the BIOS then they're loaded from disc as normal. Any elements of the 'live' EISA configuration are most likely stored in the BIOS and the NVRAM on the Dallas chip, so when / if you choose to battery mod the RTC chip is a personal one.