agilent_infiniium_54830
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| agilent_infiniium_54830 [2025/07/25 15:10] – [Motherboard Swap & New OS Install] admin | agilent_infiniium_54830 [2025/07/30 01:26] (current) – [Photos] admin | ||
|---|---|---|---|
| Line 165: | Line 165: | ||
| ++++ New OS Install | | ++++ New OS Install | | ||
| + | ==== OS Install ==== | ||
| + | I opted to go with Windows 7, but other users have had success with as new as Windows 10. 7 seemed like a good balance of modern features while still being light enough to run very quickly. You will need to use a 32bit variant of whatever OS you choose, as the drivers will not work on 64bit systems. | ||
| + | Again, shoutout to EEVBlog users Howardlog and magore, they did all the legwork here, I just wanted to aggregate it into a single place. | ||
| + | |||
| + | === Upgrading? === | ||
| + | Some users on the EEVBlog forums have reported success in upgrading the base Windows XP install. I have not yet tried this myself, but I have no reason to think it wouldn' | ||
| + | |||
| + | I tried booting a system-restored drive (that I was using on the VP22 board without issue) on the newer NCR G41 board, but it resulted in a BSOD very early into the installation process. It's very possible that this could be easily resolved, but I'm not really interested in patching/ | ||
| + | |||
| + | === Installation Considerations === | ||
| + | For the most part, you can treat this as a normal windows install. Apply updates as usual. You'll probably want to disable power saving features such as PCI device sleep, system standby, hibernation, | ||
| + | |||
| + | === CT65550 Requirement === | ||
| + | An important note about the CT65550 driver is that it does not like to work with other valid display outputs. I disabled the iGPU in the motherboard BIOS, it's possible that disabling it in windows will work as well, but I didn't test that. Failing to disable it will result in a 0x0000007E stop error BSOD in the windows boot process. | ||
| + | |||
| + | === Registry Merge === | ||
| + | The driver for the Infiniium Main Interface is not applied to a physical piece of a hardware like a PCI card, it has to be created through the windows registry. EEVBlog user has extracted the correct registry keys from the Windows XP restore image, and made them available in a single registry patch file. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | This patch must be applied to a running system (you can't merge it into an offline hive, as far as I can tell) and it must be done as the SYSTEM user. The easiest way to do this is to use psexec.exe from the Microsoft Sysinternal Utilities to launch regedit as the system user, then import the .reg file. I found that version 2.41 of psexec (current as of this writing) did not work, but 2.11 from 2016 worked just fine. | ||
| + | |||
| + | < | ||
| + | |||
| + | Once this has been merged, reboot the system and open device manager when it comes up. You should see Infiniium Main Interface listed with no driver installed. Point it to mesa.inf (make sure mesa.sys is in the same directory) and it should install successfully. | ||
| + | |||
| + | === Hardware Drivers === | ||
| + | You will install drivers for seven more pieces of hardware. Infiniium Acquisition Board (5483x), | ||
| + | |||
| + | ^ Device | ||
| + | | Infiniium Main Interface | ||
| + | | Infiniium Acquisition Board (5483x) | ||
| + | | Infiniium Display | ||
| + | | Infiniium Memory Controller | ||
| + | | CT65550 | ||
| ++++ | ++++ | ||
| + | |||
| + | ===== Photos ===== | ||
| + | |||
| + | {{gallery>: | ||
agilent_infiniium_54830.1753456206.txt.gz · Last modified: by admin