wiki.millerjs.org

User Tools

Site Tools

agilent_infiniium_54830

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
agilent_infiniium_54830 [2025/07/25 14:52] – [Motherboard Swap & New OS Install] adminagilent_infiniium_54830 [2025/07/30 01:26] (current) – [Photos] admin
Line 147: Line 147:
 The 54830 uses a 20 pin ATX power connector - this will work fine with many MicroATX boards that have a 24 pin socket, but keep in mind that the cable harness is very short. Compare the locations of the ATX power connectors on the original VP22 board, the NCR board I chose, and another MicroATX G41 board with three PCI slots.  The 54830 uses a 20 pin ATX power connector - this will work fine with many MicroATX boards that have a 24 pin socket, but keep in mind that the cable harness is very short. Compare the locations of the ATX power connectors on the original VP22 board, the NCR board I chose, and another MicroATX G41 board with three PCI slots. 
  
-[{{:0:infiniium_54830:motherboards:vp22_board.jpg?300|Motorola VP22}}] +{{:0:infiniium_54830:motherboards:vp22_board.jpg?300|Motorola VP22 }} 
-[{{:0:infiniium_54830:motherboards:ncr_board.png?300|NCR 302DNR6D00941}}] +{{:0:infiniium_54830:motherboards:ncr_board.png?300|NCR 302DNR6D00941 }} 
-[{{:0:infiniium_54830:motherboards:gigabyte_board.jpg?300|Gigabyte GA-G41M-ES2H}}]+{{:0:infiniium_54830:motherboards:gigabyte_board.jpg?300|Gigabyte GA-G41M-ES2H}}
  
  
 === CPU Power === === CPU Power ===
-Most boards are going to require a separate CPU power connector, which the power supply in the 54830 does not offer, as the original socket 370 Pentium III didn't need that much power. It is possible to splice a CPU power connector into the available 12v rail, but this supply is only rated for about 30 watts. I (and some others) opted to mount a 12v meanwell power supply in the chassis to provide the CPU power directly. +Most boards are going to require a separate CPU power connector, which the power supply in the 54830 does not offer, as the original socket 370 Pentium III didn't need that much power. It is possible to splice a CPU power connector into the available 12v rail, but this supply is only rated for about 30 watts. I (and some others) opted to mount a 12v meanwell power supply in the chassis to provide the CPU power directly. There is suitable space between the motherboard and fans. 
  
 === Drive Power === === Drive Power ===
 There are two 5v power cables available for the CD-ROM and LS-120/HDD boards. These boards are not used in my case, so I chose to use one of them to provide 5v for a SATA SSD. The SATA optical drive I used for installing Windows 7 I powered externally, but one could use the other 5v connector that is available. There are two 5v power cables available for the CD-ROM and LS-120/HDD boards. These boards are not used in my case, so I chose to use one of them to provide 5v for a SATA SSD. The SATA optical drive I used for installing Windows 7 I powered externally, but one could use the other 5v connector that is available.
  
 +==== IO Shield ==== 
 +The 54830 has a rectangular impression on it, exactly where a standard IO shield would fit, but they chose to not punch it all the way out, and instead only punch out the port holes. I have not found a single motherboard newer than socket 370 with the same port arrangement - so cutting out the IO shield is pretty much a requirement. My solution was to remove the motherboard tray entirely from the unit, then drill out the four rivets holding the rear plate to the tray. Once that's done, I drilled holes into the IO shield impression on the rear plate, then used a dremel to cut it out and finish the edges. 
  
 ++++ ++++
Line 164: 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't work, other than the fact that it's very tedious. The process may be able to be done in virtualization software, but I haven't tried it yet. 
 +
 +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/hacking around in a Windows XP install - my preference is to start with a fresh install and then apply the necessary drivers and patches. 
 +
 +=== 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, etc. If you choose to continue to use the CT65550 GPU with the internal screen with the new board, be aware that the internal LCD/VGA out are limited to 640x480, and by default windows 7 will now go below 800x600. You may want to do the majority of the install and configuration before installing this card, using a separate monitor on the onboard graphics, to keep things easy. 
 +
 +=== 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.
 +
 +{{ :0:infiniium_54830:mesa.reg |mesa.reg}}
 +
 +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.
 +
 +<code>psexec -i -s C:\Windows\regedit.exe</code>
 +
 +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),Infiniium Display, four Infiniium Memory Controllers (which will all use the same driver), at the CT65550. 
 +
 +^ Device                               ^ PCI ID     ^ Driver      ^
 +| Infiniium Main Interface             | n/a        | mesa.sys    |
 +| Infiniium Acquisition Board (5483x)  | 15BC:0501  | adobe.sys   |
 +| Infiniium Display                    | 103C:1020  | tstone.sys  |
 +| Infiniium Memory Controller          | 15BC:0500  | zeum.sys    |
 +| CT65550                              | 102C:00E0  | idk         |
  
 ++++ ++++
 +
 +===== Photos =====
 +
 +{{gallery>:0:infiniium_54830:mod}}
agilent_infiniium_54830.1753455177.txt.gz · Last modified: by admin
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki