VOGONS


First post, by 386_junkie

User metadata
Rank Oldbie
Rank
Oldbie

The Systempro Project

1) Beginnings (The modified System): - 386_Junkie’s duo core 386; The modified Systempro!
2) Build (The Systempro): - The Systempro Project; The Build
3) Bios: - <----------You are here
4) Bugs: -
5) Benching (386 class): - The Systempro Project; Benchmarking (386 class)
6) Benching (386 class) round 2: -
7) Benching (4/586 class): -

______________________________________________________________

The Bios

After the amount of accumulative hours I’ve spent constructing from scratch the System Configuration (Compaq’s bios), and afterwards entering to make changes for any hardware change from system boards and memory, to graphics… I figured this could do with a thread of its own anyway. This and giving a worthy heads up to anyone who is planning on undertaking such a Compaq adventure or even those who are genuinely interested in the Systempro, or even Compaq bios of this era.

26f583508375453.jpg

I’ll start by saying this technically is not a bios as such, it is actually NVRAM, a similar to (1287) Dallas RTC clock chip that has limited battery life which few here have modified, retrofitting a coin cell to revive their beloved and most cherished.

890e07508375455.jpg c76e5e508375450.jpg

Well on the Systempro there is instead a (1397) Dallas, which is where the System Configuration is created (from scratch when the RTC is blank) loaded in by three floppy discs, or is where any change to the hardware is made, also requiring the three floppies. Some other cfg’s and tools I’ve been using: -

d83884508375458.jpg

I’ve learned the hard way and through time that the system likes to be loaded with hardware added in a certain order. Not adding hardware in a specified order results in system hang up’s, configuration error messages, and locking (write protect!) of the NVRAM, and a lot of frustrating time! The order in the addition of hardware is as follows: -

1 System bus hardware (CPU & Memory boards)
2 EISA bus boards
3 Fixed Disk controllers

If you need to make a change at any one level you need to remove the below levels first, make the change, and then replace the levels… very time consuming it can be, though can be streamlined a little once you figure the routine.

So the System Configuration, once you’re in looks like this: -

f9ad88508376445.jpg 9aba8d508376452.jpg

There is really only one area to hardware, which is of course; - “Configure Hardware”. In here you can make changes the system, but for the benefit of the viewing public I’ll go right into “view or edit details”.

b70849508376460.jpgde90a6509530429.jpg 564192509530438.jpg 0bcf63509530452.jpg 1d14e5509530459.jpg 271110509530465.jpg

It can be seen from the photos that this System Configuration is relatively primitive compared to some of the higher end 386 motherboards that have advanced chipset options, and user configurable timing. Instead this is just a humble 1989 software loaded from floppy into NVRAM, configuring system hardware… nothing more, nothing less. It does not even detect the system FSB change… the software being fixed to see the 386 (33MHz only) processor boards, but not the change I made to the system bus, changing out the oscillator to make the system run at a steady 40MHz.

With the system setup and configured, it’s time to test and bench.

90acfe509480068.jpg

Last edited by 386_junkie on 2016-10-15, 05:59. Edited 1 time in total.

Compaq Systempro; EISA Dual 386 ¦ Compaq Junkiepro; EISA Dual 386 ¦ ALR Powerpro; EISA Dual 386

EISA Graphic Cards ¦ EISA Graphic Card Benchmarks

Reply 1 of 1, by hyoenmadan

User metadata
Rank Member
Rank
Member
386_junkie wrote:

I’ll start by saying this technically is not a bios as such, it is actually NVRAM, a similar to (1287) Dallas RTC clock chip that has limited battery life which few here have modified, retrofitting a coin cell to revive their beloved and most cherished.

Is more accurate to say that SystemPro Firmware doesn't have a System Setup Utility built in the ROM image. This was a common practice, not only for Compaq, but also other vendors like IBM, because this allowed to bundle bigger, nicer, and sometimes even graphical System Setup utilities in a set of floppies, with big detailed online help files, extra diagnostic tools, all it customized in all the languages supported by the vendor, without the need to bundle bigger and expensive EPROM/Masked ROM chips to fit all it, and the possibility to update the System Setup data files without the need to UV-flash the EPROMs, or buy a new set of pre-flashed chips in each program update, something which was essential in the EISA times to support every new released adapter and its respective EISA ID/Card Configuration.

Ofc, when clones killed big vendors market, better and nice configuration tools was moot point against cheap hardware prices, while it was an extra R&D cost to create and update them. Also the rise of EEPROM memory made easier to update system firmware/bios image, and the death of EISA in favor of PCI killed the need of floppies with the card configuration files. So Compaq/IBM/etc finally concluded was more convenient for then develop smaller Setup Utilities which could fit with in the ROM image (no detailed help, no diverse language customizations, no detailed diagnostics). This finally made obsolete the concept of the "System Configuration" disks forever.