Shadow Lord
Veteran Member
So a few people have been asking me about this and wanting pictures posted. I had planned on giving the system a better write up but I got distracted with the AMI Enterprise III restoration during the pandemic (and I guess the pandemic too ) so this will have to do. I am happy to answer any questions people may have.
I got my hands on a pretty complete/in box Systempro XL Dual 486-50 system thanks to Chulofiasco a while back. The system has been sitting and waiting patiently for some love.
When I got the system it came with:
1. 2 x 486-50DX Processor Boards
2. 32MB of ECC RAM
3. IDA Controller Board
4. 1 IDA HDD but not the correct cable in the case. This drive never spun up for me but that could have been me as much as the drive. Initially I thought I had the correct cable in there but I later found out it was a regular SCSI cable. The other issue I have come to realize is that many Compaq branded/purposed drives do not spin up on power on. I had, incorrectly, assumed that I did not hear the drive spin up the drive must have been bad where as this could have been an issue of the drive not getting the proper signal to spin up do to the incorrect cable. One of these days I will go back to testing it out but I am not holding my breath.
Initially, the system booted fine but by the time I got it there was no signs of life. It turned out the problem was two leaking capacitors in the PSU. Having repaired the PSU I attempted my first boot:
Lots of error message but most of them were to be expected. The processor error was a bit concerning (and rightly so). This picture does not show it but there was also a CPU cache error that went away when I upgraded the BIOS to the latest version.
The system defaults to 16MB of RAM (regardless of actual memory amount) until the ECU is run.
The battery on the RTC in this system (like the AMI Enterprise) seems to be still intact. That is, after setting options and time and unplugging the system for a few days correct time and machine config were retained. However, after sitting in a warehouse for a few years the system had lost all of its settings. Luckily many of the errors on that screen were easily addressed by running the ECU.
One thing to note about the ECU: Initially I used the latest ECU (2.58) which was still hosted on the HP WWW site. However, with that ECU on every run I would get an error indicating the clear CMOS pin was set (even when it wasn't). I initially attributed this to low voltage on the RTC battery. Thanks to Maeslin on Vogons I was able to get a replacement RTC setup using coin cell batteries.
However, the error persisted - at this point this could be due to an issue with the board (although it is unlikely given that it functions perfectly fine in every other way) or it could be that the newest ECUs, due to changes in the Proliant line and use of CD-ROMs to boot, produce that error (more likely in my opinion). An extensive testing of ECU versions from 2.26B (what came with the unit) to 2.58 seemed to confirm this. The older ECU versions did not produce this error.
In fact version 2.40 (which I have given a copy of to Mr. Slug for his extensive EISA CFG DB) is the last version not to cause the error on my Systempro XL. A few other notes on the ECUs:
1. Version 2.30 is the first version to support the larger 32MB recovery partition needed for the later Compaq utils.
2. Version 2.34A corrects a bug that caused the ECU to ask for the date every time it was run (even if it was already set correctly). I would recommend this as the oldest ECU to use on the Systempro line. I use 2.40 myself and if you don't mid getting the error you can use 2.58 - it requires one extra press of the enter key but works fine otherwise.
The CPU error was more of an issue. I stripped the system to the bare minimum and tested each CPU card separately:
One of the CPU boards consistently would give me an error. After multiple different config attempts and a number of Google searches it became apparent one the boards was bad. At first I was hoping it was just a bad CPU chip but swapping CPU chips in between the two cards did not relieve the issue.
Nothing on the CPU board was repairable by me so that only left replacement as an option. Luckily, I was able to find a replacement in the UK and I was up and running in SMP once the new board arrived.
I got my hands on a pretty complete/in box Systempro XL Dual 486-50 system thanks to Chulofiasco a while back. The system has been sitting and waiting patiently for some love.
When I got the system it came with:
1. 2 x 486-50DX Processor Boards
2. 32MB of ECC RAM
3. IDA Controller Board
4. 1 IDA HDD but not the correct cable in the case. This drive never spun up for me but that could have been me as much as the drive. Initially I thought I had the correct cable in there but I later found out it was a regular SCSI cable. The other issue I have come to realize is that many Compaq branded/purposed drives do not spin up on power on. I had, incorrectly, assumed that I did not hear the drive spin up the drive must have been bad where as this could have been an issue of the drive not getting the proper signal to spin up do to the incorrect cable. One of these days I will go back to testing it out but I am not holding my breath.
Initially, the system booted fine but by the time I got it there was no signs of life. It turned out the problem was two leaking capacitors in the PSU. Having repaired the PSU I attempted my first boot:
Lots of error message but most of them were to be expected. The processor error was a bit concerning (and rightly so). This picture does not show it but there was also a CPU cache error that went away when I upgraded the BIOS to the latest version.
The system defaults to 16MB of RAM (regardless of actual memory amount) until the ECU is run.
The battery on the RTC in this system (like the AMI Enterprise) seems to be still intact. That is, after setting options and time and unplugging the system for a few days correct time and machine config were retained. However, after sitting in a warehouse for a few years the system had lost all of its settings. Luckily many of the errors on that screen were easily addressed by running the ECU.
One thing to note about the ECU: Initially I used the latest ECU (2.58) which was still hosted on the HP WWW site. However, with that ECU on every run I would get an error indicating the clear CMOS pin was set (even when it wasn't). I initially attributed this to low voltage on the RTC battery. Thanks to Maeslin on Vogons I was able to get a replacement RTC setup using coin cell batteries.
However, the error persisted - at this point this could be due to an issue with the board (although it is unlikely given that it functions perfectly fine in every other way) or it could be that the newest ECUs, due to changes in the Proliant line and use of CD-ROMs to boot, produce that error (more likely in my opinion). An extensive testing of ECU versions from 2.26B (what came with the unit) to 2.58 seemed to confirm this. The older ECU versions did not produce this error.
In fact version 2.40 (which I have given a copy of to Mr. Slug for his extensive EISA CFG DB) is the last version not to cause the error on my Systempro XL. A few other notes on the ECUs:
1. Version 2.30 is the first version to support the larger 32MB recovery partition needed for the later Compaq utils.
2. Version 2.34A corrects a bug that caused the ECU to ask for the date every time it was run (even if it was already set correctly). I would recommend this as the oldest ECU to use on the Systempro line. I use 2.40 myself and if you don't mid getting the error you can use 2.58 - it requires one extra press of the enter key but works fine otherwise.
The CPU error was more of an issue. I stripped the system to the bare minimum and tested each CPU card separately:
One of the CPU boards consistently would give me an error. After multiple different config attempts and a number of Google searches it became apparent one the boards was bad. At first I was hoping it was just a bad CPU chip but swapping CPU chips in between the two cards did not relieve the issue.
Nothing on the CPU board was repairable by me so that only left replacement as an option. Luckily, I was able to find a replacement in the UK and I was up and running in SMP once the new board arrived.