You can do a clean install of Windows 7 SP1 on a new motherboard.
( FYI I have a 54831b - I modified my case cutting out the IO shield )
I ended up extracting all of the HKLM infiniium registry keys and classes from the HKLM part of the registry including parts relating to agilient services. This was done first on a fully updated Windows XP system with V571 of the Infiniium software and latest IO libries.
I got the original INF files from the recovery partition and edited them so they would look in the current directory for drivers.
Look for: 1 = %DiskId1%,,,""
Change it to: 1 = ,,,"
FYI I got the sys and dll drivers from the updated XP windows sub folders. I placed these in a single folder a copied them to the Windows 7 SP1 new install motherboard using a Intel B75 based chipset
adobe.inf ( Acquisition board )
adobe.sys
agBridge.inf
agBridge.sys
agt357.inf
agt82341.sys
agt82350.sys ( GPIB)
agt82357.sys
agtgpibclass.dll
agtgpibclass_pci.dll
agtgpib.inf
mesa.inf ( this is the main interface )
Mesa.sys
tstone.inf
tstone.sys
zeum.inf ( memory interface )
zeum.sys
Using Microsoft Sysinternal Utilities I open a command prompt running as System. I launched regedit and imported the registry data exported from the XP machine. There are regisry parts that do not get created if we just install drivers - for eample the Infiniium Main interface is not created by installing a driver so the import of the XP infiniium registry keys fixes this. Services related keys make sure services are started, etc
Once 7 SP1 was installed on the new motherboard I had to do all of the updates before the scope application would fully work - ie 186 plus updates ( I had tried it before all updates were installed ) FYI - you have to give the system time to boot up.
I Installed the V571 and 17.1 version of the IO Libraries
I then manually installed each driver picking the option to browse specifically for the driver and picking have disk.
Main interface, Acquisition Board, and 4 copies for the memory controller. I did them in sequence of the driver properties Device Instance number ending in 103010f0 for the first one, the first digit changes 1,3,5,7 for each board. It will warn about the lack of driver signing.
I ended up using a P8B75-M but also worked with a P5DL-M.
I never considered using the CHIP and Tecnoligy board pair - never tried them.
Using the P8B75-M board required me to extend the length of the cable to the acquisition board - the P5DL-M board does not need this change
Durring the experiments to get this to work I tried ever incresing ammounts of the saved registry from the XP machine.
At some point when I get more time and recover from this I will try to repeat this on a clean install and fully document it. It took me a few weekends and late nights. I used the Sysinternals Process monitor to track registry and file access for clues. I would not have been able to do this without all of the work done previously by forum members in this thread - thanks!