Agilent 8163B lightwave multimeter with missing CF card

[ddrl46]

A while ago I acquired an Agilent 8163B lightwave multimeter which gave a fatal error when powering up.
It turned out that this fatal error was caused by someone having removed the compact flash card from which the instrument is supposed to boot...

Some time later I was able to get my hands on the bigger brother of this unit, the Agilent 8164B, in order to clone the contents of the compact flash card and transplant it into my unit.

After placing this freshly cloned compact flash card into my unit and flashing the correct firmware for the 8163B to the unit via ATTools (listed on the 8163B page from Keysight) the instrument appeared to boot up correctly, however the instrument reports that it is unable to find its model number and serial number and reports these as "<NO CAL DATA>!".
In this state the instrument refuses to detect any modules which get inserted into the unit.

What is strange is that when I connect to the unit via the ATTools utility which is used to update the firmware in the unit the model number of the unit is correctly identified.

The compact flash card which was missing from my instrument contains two files, a BOOTROM.SYS file and a firmware image. The firmware image I was able to easily replace with the correct one for the 8163B, I'm however not sure if the BOOTROM.SYS file is the same between the 8164B and 8163B. This could be causing my problems.

I'm wondering if someone would be able to create an image, or at least copy the BOOTROM.SYS file, from their 8163B compact flash card?
This card is accessible via the module bay and is readable on a normal PC.

Attached below are some pictures of what is displayed on my unit.

[seebeck]

Hi ddrl46,

Attached are the BOOTROM.SYS file and SYSTEM.image for your reference.
FW Version: V3.85
You can find additional information in Keysight website, link as: https://www.keysight.com/us/en/product/8163B/lightwave-multimeter.html

With best regards.
Seebeck.

[ddrl46]

Hello seebeck,

Thank you very much for the files  , after some more troubleshooting it turned out that the previous owner of this instrument has been messing with the EEPROM near the GPIB connector (AT24C64) on the mainboard.
After copying the contents of the EEPROM from a working 8164B to my 8163B it was able to boot up correctly and identify modules as well.

Only thing is that now the instrument identifies itself as a 8164B, but that is not a huge issue. I tried to edit this by modifying the EEPROM data, but it seems there is some checksum in there.