Software setup/Mainboard change for Agilent 16900A/16902A/16903A logic analyzer

[ingowien]

I got a used 16903A Logic Analyzer with an ADLINK M-815G mainboard and a (very slow) PIII 1000MHz with Windows XP. The installed software version on the machine is 4.40.0001.

Theoretically this should be a powerful machine but after messing around for some days with the old single core P3/1GHz I'm not so sure any more. I used 2k and XP for ages, even with PIIIs but I don't remember it being so slow and unresponsive. However the 65550 VGA card in the 16903's backplane might be part of the problem. Probably one of the slowest VGA's ever built, even the Windows menus com appear with significant lag. However I might want to re-install it or even upgrade to a newer mainboard if that would be possible. The platform should support Win7 and Multi-Core CPUs as there has been an official update for the 16900 and the 16902 to an ADLINK M-890 board with an C2D E8400 and Win7. But I don't know the exact software version that was used for the upgrade. I assume the upgrade wasn't available for the 16903 as Agilent didn't use standard ATX backcovers and the connectors of the M-890 wouldn't fit through the 16903 mainboard tray without drill, jigsaw and file - a service Agilent probably didn't want to offer. But maybe I'm wrong in that point.

I was able to download a ISO ghost image for the M-815G mainboard (16900-14121, it's for the 16900 but it should boot) but it seems this image is only the base image without the LA application (at least GhostExp doesn't show Agilent software or setup programs). And it seems there are only two software downloads available from Agilent: SetupLA03671008.exe (which is older than what's on my machine) and SetupLA05901110.exe (which might be incompatible as mentioned in Receiving "NO VALID ID DETECTED IN FRAME!" while trying to install Agilent LPA 5.90.1100 on a 16903A?).

- Does somebody have software 4.40 or a download link? Unfortunately the Keysight FTP server seems to be empty. And I can't post in the keysight community forum, I'm getting some error that I'm not allowed to modify content.

- Do you know if 5.90.1100 is compatible with a 16903A under XP? Would this new software install any upgrades to the hardware that would not be compatible with a previous version? Or is it safe to upgrade and eventually downgrade if there are problems?

- Are there other software versions or recovery images (4.x or 5.x) available or recommended? The full installer would be preferred bit anything installable is OK as long as it's really compatible with my hardware.

- Has anybody succeeded in upgrading the mainboard to a non-Agilent (non-M890) mainboard? I'd assume that other C2D Mainboards should work as well if there is no software locking in the Agilent software. A first test with an Advantech AIMB-584 with a Ci5-4590S was not successful as I got the same NO VALID ID DETECTED IN FRAME error. But maybe that's because the 5.90 software is not compatible. At least I do find this message in the 5.90 binaries but not in the 4.40 software.

best regards and thanks for your support,
Ingo

[DaJMasta]

I can probably get back to you in a week or two - have a 16902A that I've got a socket 775 board with the intention to put in.  Mine was a similar 1GHz Coppermine Pentium 3, but with a Motorola VP22.  The form factor is standard Micro ATX, and the power connector is a standard 20 pin ATX connector.... but the power consumption of the Pentium 3 is pretty low compared to many more modern chips (only about 30W TDP), and I don't think there's a 4 pin CPU power connector (let alone a 24 pin ATX power connector or an 8 pin CPU power connector), so while I've ordered a Molex to CPU power connector adapter to take some 12V from a different rail, I wonder whether the PSU will be up to the task... that said, the power inlet connector specifies 1300W max, so it certainly could have the headroom.


In any case, you can basically install everything like a standard desktop, as far as I understand.  The installation instructions for the most recent LA software say to just uninstall the old stuff, so calibration information seems to be stored on the individual LA cards... so a stock Windows XP/7 install plus the downloadable drivers will likely be sufficient to run the instrument (though I haven't tried and don't intend to, I'll stick with XP by cloning my existing drive to an SSD and just use the newer motherboard/CPU).  I've got the most recent version running fine on my unit under XP with the original mainboard, though they are so slow the pulldown menus for the window lag in opening.  It could be that the recovery images check for hardware specifics to ensure version compatibility while the driver/software package just installs like any other program package.

At least in the 16902A, the motherboard slides out in a tray, and instead of the traditional I/O shield just has the cutouts in the back aluminum, since my replacement board has some extra and some rearranged connectors, I plan on dremeling out the space for the standard I/O shield and using that instead.  But this project is a step or two down my list, and I'm still waiting on a connector and some RAM.

[ingowien]

Thank you for your fast reply.
I had similar thoughts. I don't think power should be a real issue. Especially in the 16902 with 1200W supplies. The SSD needs less power than the HDD. There seems to be an additional 4pin power connector on the Backplane next to the CDROM IDE-Port that has 2x GND on the top and 2x12V on the bottom. As the officieal E8400 in the M890 upgrade kit has 65W, I'd assume that similar CPUs shouldn't be an issue. I haven't seen a note that there are different PSU in use for different models. I'm running a similar setup with an AIMB-584 and a Ci5-4590S in a Lecroy DDA that came with a similar Intel P3 board without P4 power connector. Pulled the extra 12V from the HDD cable, no problem at all. Runs stable and super-fast.

I've create an Acronis backup of the HDD but had to do it on a different machine as it would have required eight hours on the PIII. So If 5.90 works for you I can try to upgrade my XP intallation to that software now for a test. If it works on my machine, too I could imagine different reasons why it didn't work in my AIMB-584 test:
- Mainboard/chipset too new (though the PCI driver installed fine)
- The combination of the 16903 PCI card (or rest of the hardware), the mainboard and Win7 doesn't work.
- Problem with Win7 in general (it should work for the 16902 but I think there hasn't been an official version of the 16903 with Win7)
- Problem with the fresh setup or Win7e (I've been using a WES7 image that was lying around, maybe I should test Win7 Pro). The official upgrade kit was based on WES7 but it's always a pain to have all the required packages and drivers installed.
But basically I tried a fresh Win7 install, installed Software 5.90 and got that NO VALID ID DETECTED IN FRAME! error from the background service when it should initialize the hardware.

I'd prefer Win7 because RDP is much better, especially the function to copy files over the clipboard is really handy. But yes, if it doesn't work XP will do fine for 775 boards.

Yes, the MB is in a slide, too in the 16903A. It's just a little higher as the lower 3 slots are covered. The card cage is the same as in the 16902. The difference  is that the 16902 PCI card directly plugs into the backplane as it's so long. The 16903 PCI card is small and connects to the backplane with a ribbon cable. I think it's just a minor translation from PCI to some different bus that attaches the ACQ hardware, the super-slow VGA card for the LCD and the front panel. Just the 3M touch controller is attached to COM2 on the mainboard but almost all 775 boards I've seen have a COM2, so this shouldn't be the problem. The ribbon cable makes tests easier for the 16903 as the new mainboard hasn't to be aligned perfectly. I even had it reside outside the mainboard tray in my first test.

I have to check the ATX power connector of the M-815G board but I'd assume it is standard ATX. However yes, you always have to double check, i've seen several HP/Compaq boards with slightly different pin assignment. The most annoying issue are the ATX connectors as they didn't add a standard ATX back cover. I'm trying to find a board with similar connections with is not possible due to the strange layout of the M-815G with 3 audio plugs horizontally aligned. So I'm not sure if I'll cut out the entire ATX standard opening and insert the original backplane (which could include a lot of filing) or just create/modify the openings for the required ports.

So thanks again for your thoughts, I think I'll get a 377 board with an E8400 and do some tests. I'm not sure if it would be a good Ideal to choose one with a similar Phoenix AwardBIOS (my old board has a Phoenix - AwardBIOS - v6.00PG, Agilent Technologies, REV:AG10). On thing I'm not quite sure about is, how much faster the thing can get. Windows and software setup can be reduced significantly, but at least 3 of the 6 minutes it currently takes are hardware related. If these are still CPU limited, the start time will get better. But if that long wait is just hardware related, I will always take ages until the analyzer is usable, even with a new CPU. I know these machines were only turned on and never off but hobbyist usage is different.

best regards
Ingo

[nctnico]

Did you already install an SSD and more memory? If possible disable swap (virtual memory) on Windows. It will make the system much faster because Windows normally wants to leave as much of the memory unused and pushes everything into swap. The latter makes the system very slow.

[DaJMasta]

At least with the Motorola board in mine, I've read that 512MB is the max supported even though are 3 DIMM slots, and while the P-IIIs go up to 1.4Ghz Tualatin (at least my board is Socket 370, not a soldered down BGA), responsiveness is bad enough that it likely won't be enough running 5.x software versions.  Going to an SSD decreases load times significantly, but honestly that isn't the bad part of it on mine - boot time isn't great, but the usability beyond that that's the real issue.


Not sure if the long PCI card in mine is what you're describing, but I doubt the LA software uses much hardware acceleration, so while maybe the Aero interface does in Windows 7, I don't expect it to be a big constraint for mine.... and there's always the external monitor output which is driven by the onboard CPU graphics on later boards, so that should have as much acceleration as it could need.  I did look for a board specifically with a PCI slot on that farthest out slot, since that's the only way it would line up with the connector on the backplane that it connects to in the front of the instrument, but they appear to be standard mATX spacing, and from the device manager, I think the stuff specific to the LA are on the card and beyond, so the rest of the system basically just a standard PC.  The board I'm trying to swap into mine is an Asus P5G41T-M, also with an e8400 and 4GB of RAM.  Will move to an SATA hard drive after it's installed, since I'll likely have to add SATA drivers to the XP installation after copying.

[ingowien]

@nctnico:
Yes, I tried an SSD (took two attempts as the IDE to SATA-converter was jumpered as Slave) and the HDD UDMA cable lacks the slave sleection line. Startup time was reduced from 6m to 5m, so yes, there is an improvement but it's not that large. But SSD is definitely a must for $35. Didn't try memory upgrade until now as I'd prefer to change the entire mainboard if this is possible. I should have some old DDR-1 RAMs in spare but in general the PIII isn't worth it. In a single core every mouse click blocks everything else, that's just not state of the art since the first P4 with HT came out. If there wouldn't be a better solution I'd add 2GB of RAM and maybe a PIII-1400 with the socket 377 adapter as the board probably doesn't support the Tualatin. Probably not worth the $50 it would cost.

@DaJMasta
You're right, I just assumed the board would accept more RAM (have only 512MB). And mine only has two memory sockets. But I'd assume that 2x512MB should be supported.
There are Tualatins with an integrated socket converter, just 1mm thicker. Never tried one of these but if it would make it faster...
https://www.ebay.com/itm/Intel-Tualatin-Pentium-IIIs-1-4GHz-512K-include-On-chip-Socket-Adapter/281238323137
I didn't know that such a PCB adapter exists, at least it's in interesting construction. At least better than Intel changing the socket without 100% technical need.

I think it should be the long card as shown in https://www.eevblog.com/forum/testgear/agilent-16900a-teardown-logic-analyzer/msg647707/#msg647707. You can see that the PCI card is as long as the entire mainboard tray and directly connects to the huge multi-pin connector in the backplane. The service manual shows the same configuration for the 16900 and the 16902. Only the 16903 has the short PCi card and the flex cable. Wonder what the exact reason is. The backplane is the same size so the space for the connector would be there. Maybe the multi-frame interfacing was expensive and it was cheaper to create a smaller PCI card or the re-used an existing design. Though it has a 16903 part name.

-----

I tried if I can install 5.90.1110 into the existing XP. Doesn't work, the installer fails with some incredible "Agilent Logic and Protocol Analyzer 05.90.1110..." : "Error 2337.Could not close file: GetLastError: ." Superb error logging from MS. No file name, no error description, nothing. The installer log file is even better and contains exactly this error and nothing else, so I don't even know which MSI file caused the problem. No hint in the event log. I just love MS.
Error 2337.Could not close file:  GetLastError: .
=== Logging stopped: 12.01.2019  14:38:42 ===
Error 2337 could be related to some .Net installation error. So I'd probably end up either with a fresh XP install or trying to restore the 16900 M-815G ghost image. I think it should run without problems on the 16902.
I uninstalled and re-installed several times, always the same error. At least it's persistent.

I found an old 3.83 install version in some Windows temp folder, seems to be the complete extraction from SetupLA03830000.exe. This one installs and runs fine.

More google research revealed some almost hidden release notes:
https://www.keysight.com/upload/cmc_upload/All/Readme540.html
https://www.keysight.com/upload/cmc_upload/All/Readme530.html
https://www.keysight.com/upload/cmc_upload/All/Readme500.html
https://www.keysight.com/upload/cmc_upload/All/Readme440.html
https://www.keysight.com/upload/cmc_upload/All/Readme400.html
https://www.keysight.com/upload/cmc_upload/All/Readme383.html
https://www.keysight.com/upload/cmc_upload/All/Readme382.html
https://www.keysight.com/upload/cmc_upload/All/Readme380.html
https://www.keysight.com/upload/cmc_upload/All/Readme370.html
So Win7 support was added in 4.00.

The revision history I could find is:
05.40 (August 2012)
Version 5.40 supports Windows XP Professional Service Pack 2 and 3, Windows Vista Service Pack 1, and Windows 7 (32-bit or 64-bit  platforms) Service Pack 1.
SetupLAXXXXXXXX.exe

05.30 (March 2012)
Version 5.30 supports Windows XP Professional Service Pack 2 and 3, Windows Vista Service Pack 1, and Windows 7 (32-bit or 64-bit  platforms) Service Pack 1.
SetupLAXXXXXXXX.exe

05.20 (October 2011)

05.10 (July 2011)

05.00 (April 2011)
Version 5.00 supports Windows XP Professional Service Pack 2 and 3, Windows Vista Service Pack 1, and Windows 7 (32-bit or 64-bit platforms). 
Once you have downloaded the software:
SetupLA05000003.exe

04.40 (January 2011)
Version 4.40 supports Windows XP Professional Service Pack 2 and 3, Windows Vista Service Pack 1, and Windows 7 (on 32-bit/64-bit platforms).
SetupLA04400000.exe

04.20 (December 2010)

04.00 (October 2010)
Version 4.00 supports Windows XP Professional Service Pack 2 and 3, Windows Vista Service Pack 1, and Windows 7 (on 32-bit platforms).
SetupLA04000000.exe

03.83 (October 2009)
Version 3.83 supports Windows XP Professional Service Pack 2 and 3 and Windows Vista Service Pack 1.
SetupLA03830000.exe

Unfortunately I only have v3.83 that installs fine in XP but won't install in Win7. And v5.90 that doesn't install in XP and doesn't recognize the modules in Win7. Just the typical installation experience I have most of the time...
I'd really prefer Win7 as it's so much better when changing hardware details. XP has always been a pain, you even have to change the HAL manually from uniprocessor to multiprocessor when changing the CPU or the thin will crash. Win7 is different, once you have the AHCI drivers installed, you just plug it into a different computer and it will come up. Install the remaining drivers, ready. Thus If I could avoid XP that would really be a gain for me.

So if anybode has a setup for v4.00, 4.20, 4.40, 5.0 or whatever this would help me a lot. I'm not quite sure if v5.90 is really clean and stable or there are issues with this version. So any other release I could get would help a lot.
And it's a shame Keysight can't provide the setup files any more just because someone in the IT dept. felt that files have to be removed from the FTP server after one week.

best regards
Ingo

[ingowien]

Just a small update: I got some progress after hours of updating and testing.

Original P3 M-815G mainboard with XP (v5.90 wouldn't install here):
- I could re-install the 16900-14121 image with Ghost03, boots without problems.
- As expected no software included and it's XP SP2. Setup 05.90.1110 however requires XP SP3 (wanted to test it with a fresh image without installing previous versions first)
- Installed XP SP3 and all the other hotfixes. Created Acronis image - who knows what'll come next and it took hours until here. As USB is slower than slow I added a second HDD instead of the DVD-ROM. Never throw away your old 80GB HDDs.
- Setup 05.90.1110 runs into some .Net install error
- For some reason they only included the online installer for .Net 3.5, not the offline and that doesn't throw a proper error. Either install .Net 3.5 manually or replace the dotnetfx35_SP1_RequiresNetwork.exe installer.
- Setup 05.90.1110 installs in XP (takes ages), then the hardware is recognized and everything runs.

AIMB-584 with Ci5-4590S and Win7:
- Fresh WES7 test image, some extra packages loaded that are often missing.
- SetupLA03.xx won't install (unsupported OS).
- I was able to partially reconstruct the SetupLA04.40.0001 from the installed version on my XP setup. First install .Net 3.51 and 4.0 to be sure. Find and move the 8MB .msi file for the Logic Analyzer software in the XP Windows directory, during install it will raise errors on missing files. Search them on the HDD (somewhere in Program Files, User directories and Windows directory) and build up the content. As a surprise to me it really installed.
- v4.40.0001 installed fine in Win7 (had the mainboard outside the analyzer without PCI card attached).
- Put the AIMB next to the analyzer, move PCI card to new mainboard. Surprise: comes up, hardware is detected, everything running. Startup time reduced from 6m to less than 1:30. And that includes that I don't have an autostart for the app installed, yet.
- Surprisingly I only had the standard VGA card, I think in 256 color mode. Intel graphics not present - probably disabled by BIOS.
- Now I had the bad idea to do two things at once: install the old XP VGA driver in Win7 (not a good idea) and make the AIMB-584 enable both VGA drivers -> lots of beeps, doesn't come up any more with PCI VGA.
- BIOS defaults loaded -> still lots of beeps. Always remove PCI card, get into BIOS (no signal on both displays), do some tests -> fails again.
- Beeps vanish if palette snooping is turned on but I still can't get it to use a PCI VGA. Neither the Agilent 65550 nor some old S3s I keept in a box if I would ever have a need for them. Never expected that to happen. I don't know in which state the mainboard was in the first trial but I can't get it to use a PCI VGA as primary. And yes, it definitely came up on the internal LCD as I was wondering that the BIOS setup looks so different with the 800x600 font.
- So I switched to Intel IGFX as primary display, at least this works. Agilent Brightness Control crashes but who cares. My tiny 10" 1280x800 test display is so much better than the internal display...
- Tried an upgrade to 05.90.1110 under Win7 -> again no valid frame detected.

So the current status is:
- WinXP with 4.40 ... OK
- WinXP with 5.90 ... OK with fresh XP from Agilent ISO file + SP3 + Hotfixes, wouldn't install on the old running XP
- Win7 + 4.40 ... OK (except for VGA, touch screen not tested, yet)
- Win7 + 5.90 ... fail (no valid frame)

I think that's enough for today, the 16903 can definitely be run with a Ci5/1155 board. The AIMB will not be the target board, the onboard LVDS is meant for other projects. I think I'll get some other 1155 board as a Ci5 doesn't cost much more and offers twice the power of an E8600. With the same 65W TDP and a far more efficient chipset. And I think other mainboards might not have such issues with a PCI VGA card, Advantech boards are always a little strange in terms of compatibility and their tons of settings.

So If I may ask the community for help than this would be:
- If someone has the 65550 Win7 driver (from a running installation or as setup), this would be fine.
- An existing Win7 image for a 16900, 16902 or 16903 would be good. I could then get the VGA and touch screen drivers and check how they did other things (are they still using the mirror driver as in XP?).
- Again software setups from 4.0 to 5.8 would be appeciated. I'm not sure if my 4.40 reconstruction is really OK and it would be good to find out which versions are running and which are not. 

best regards and thanks for your support so far, especially the hint that it should run with different mainboards was very important for me,
Ingo

[ingowien]

I can provide some more details for those who are interested.
I got a cheap C2D/Mainboard/RAM combo, it's a Foxconn 45CMX-K with an E8400 an 2GB RAM. I probably wouldn't use that permanently but it should do for first tests.

FX 45CMX-K with fresh XP install:
- Unfortunately I used my last modified XP+SP3+AHCI MSDN DVD to install and this is german (overlooked the language fact). I'm not sure if this could make a difference as some paths in the Agilent software seem to be hardcoded to /program files/. Maybe I'll have to redo the test with an EN version.
- XP installs fine, I could install the Agilent graphics driver for the 65551 (just find the inf file and collect all the files referenced in it).
- The onboard VGA driver will only load if it's primary. So there's a little issue here:
  -> PCI is first in BIOS -> Boot messages and everything on LCD but external VGA not available as driver doesn't load
  -> Onboard is first in BIOS -> Boot messages on external VGA only but both work in Windows
- Ensure SP3 and all hotfixes are installed, Install VS2005=VC8 and VS2008=VC9 runtime and .Net 3.5.
- For first tests I created an adapter from the external COM1 port to an internal header. The touch driver (UPDD 3.8.34) installs, it's a serial SC4 on COM1 or COM2 but flipped, has to be calibrated.
- I only have my reconstructed 4.40 setup. But it installs. If anything fails, it's probably .Net/VC runtime.
- Hardware is detected (very fast), Analyzer software runs.
- Swap display button (long press on touch) doesn't work. It seems the system is not recognized correctly. Instead of
  To switch active display adapters, push and hold the "Touch Off" button.
  it shows
  To switch active display adapters, push the "Ext. Display" button.
  Every time you hit the touch button, it switches to the external display and stays there. It's pretty tedious to get the display back to the internal screen (settings, extend, primary...)
- V5.90 installs but has the same problem as on the other board: "no valid ID detected in frame. requires proper system BIOS".

FX 45CMX-K with modified Agilent XP image;
I didn't do more tests with a fresh install, instead tried to get the stock image to run.
- Source is the 16900-14121 iso image for the ADLINK M815G. Currently available on dropbox, search for "Keysight 16900-14121", there's a hit on keysight communities.
- Easiest way is to run it on the old board, but you can mount the registry from an external system and do the changes as well.
- Create the required entries for the CriticalDeviceDatabase, this is based on an old trick published by heise (ftp://ftp.heise.de/pub/ct/listings/0218-206.zip), maybe there are other sources as well. You only need the .reg file, the drivers are all there. For my board it was important to add 27DF and 27C0 that have been missing for some reason. Don't know why the 945 wasn't covered by the heise trick.
- Either change the new machine to single core in BIOS setup or change to a multiprocessor APIC HAL (halmacpi.dll). You might do something like 'devcon sethwid @ROOT\ACPI_HAL\0000 := +acpiapic_mp !acpiapic_up'  and 'devcon update c:\windows\inf\hal.inf acpiapic_mp' for an 'official' HAL change. Otherwise simply replace hal.dll.
- Now the OS should boot on the new board. If it there is a sudden reboot, it's still a BSOD with immediate reboot. Use F8 and disable reboot on error. If it's a 0xFB error it's probably still a non-accesible boot device. You have to check the hardware IDs of your new ATAPI/IDE controllers. Maybe changing the BIOS into IDE mode will help (though this option doesn't exist on the old 945 chipsets, they didn't have AHCI as far as I know).
- Same procedure: board drivers, SP3 + hotfixes + .Net3.5 + VS runtime
- Same behavior with graphic cards: Driver for internal VGA will only load if it's primary (using latest intel 14.32.4-2008-02-26).
- Did a test with a PCIe HD5450, same thing. Driver only loads if it's primary.
- Touch screen driver is already installed, assigned COM2 to COM1 for first tests (reboot required). Later I'll add a PCI RS232 card to avoid the cable to the external connector.
- Install Agilent software 4.40. Interesting thing: now it complains that this is a genuine Agilent system but it doesn't recognize the BIOS (obviously) and I should get the correct bios update from Agilent. Obvioulsy not possible, but this seems to be the BIOS check in the installer only, it doesn't do further checks.
- Software runs, change displays with Touch-off button works, too.
- I haven't tested software 5.90 yet, but I assume it would fail again (in my tests 5.90 only worked with the original mainboard).
- XP is not genuine any more, has to be re-activated on the new board.

So there could be two issues:
- The analyzer software isn't compatible with non-english OS versions.
- Agilent applied some modifications or registry changes that are used to detect compatibility or control functions. I've not investigated this in detail as the original image is now running. 

I still haven't checked if the new board fits into the machine, if power supply and pbtn/pled are compatible. But I assume this should work.

So the short summary would be:
- Other boards work with restrictions.
- External VGA only works if the boot screen is there (Win7 and XP), in Win7 only one screen is recognized, in XP both work. Only the generic VGA driver is available for Win7 but the performance loss is probably not that relevant for the old internal, non accelerated 65551.
- The switch screen function with long Touch-off only seems to work with the original Agilent image. Making it boot on an 945 board requires quite some work but is probably worth the effort.
- Software v4.40 worked for me with other boards, v5.90 did not (no valid ID in frame). Unfortunately still I don't have other software versions between 4.40 and 5.90 to test.
 

[ingowien]

Just a summary of my tests if anyone needs it:
Hardware:
- I didn't really trust the Foxconn mainboard and it sometimes didn't recognize the PS/2 Keyboard, so I ended with an ASUS P5G41T-M LX and a 95W C2Q Q9400. Just because that was offered on ebay for 20 EUR. Probably the 65W E8400 would have been better than the Q9400. But it came with a 50mm cooler that fits into the case, has thermal management and it doesn't get too hot as CPU load isn't that high. The board has a more decent G41 chipset and seems to be OK. The BIOS doesn't offer the option to disable extra cores but everything else seems to be OK.
- Standard ATX power supply and the 4pin ATX power from the aux power connector on the backplane work without problems.
- It's important to jumper the board to use 5V for keyboard and USB, not 5VSB (default for USB). The Agilent PSU's 5VSB doesn't provide sufficient power to drive an external 2.5" HDD otherwise. No stability issues but with 4.7V the drive wouldn't spin up.
- The PS/2 and legacy connectors on the P5G41T-M LX are approx. 2.5mm left of the original mainboard. So I decided to cut the opening for the ATX I/O shield with a fretsaw - just in case  I'd need the old cover later. Fits perfectly and I can swap to a different mainboard if required.
- I use a dual PCI to RS232 card to get the COM port for the touch panel. And a PCIe to USB3.0 card as I had one lying around.

Original XP Image from Agilent
- Boots on the new mainboard once the IDE/SATA drivers for the ICH7 27C0 and 27DF devices are added.
- Keysight kindly provided some other software versions. v4.40, v5.40 and v5.60 work with the changed mainboard. v5.70, v5.80 and v5.90 don't work (No valid ID in frame). Not an issue for me.
- VGA driver 14.38.13.5215-6.14.10.5215 from ASUS works without problems in parallel to the 65550 card. Display switching with long Touch-off works.
- The LCD brightness utilty only works in v4.40 but not later. Not an issue, the old utility and the required dlls can be copied to a dedicated directory and used from there, just add it to startup.

Clean XP setup
- Just for curiosity I tried XP SP3 EN from MSDN.
- Same issue as with previous tests, hardware is not detected and display switching with long Touch-off doesn't work.
- It turns out some registry value is required, simply install
  Windows Registry Editor Version 5.00
  [HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo]
  "Ag16900Standalone"=dword:00000001
- With that key, v4.40, v5.40 and v5.60 seem to run without issues. At least I got the same behavior as with the Agilent Image.

Win7 setup
- Same situtation, v4.40, v5.40 and v5.60 work with the new mainboard.
- With the Win7 VGA driver only one display at a time works (either internal LCD or external VGA).
- With the XP driver (either 14.38.13.5215-6.14.10.5215-XP from ASUS or 14.42.15.5420-6.14.10.5420 from Intel), both Monitors are detected and show primary/secondary desktop.  It's strange that the setup installs in Win7 though only states XP and not Win7 but it works. And better than the Win7 driver. 
- Display switching won't work, even with Ag16900Standalone in place. The sevice probably detects some incompatibility and offers video controls/OSK instead of display switching.
- Only display brightness utility from v4.40 works.
- 3M touch driver v3.8.34 installs and works fine.
- Win7 with multiple displays is annoying, especially if the external monitor is no longer attached. But there's a really cool utility named "Actual Multiple Monitors" from actualtools.
  - can show task bar and start menu on all monitors with Win7
  - adds additional functions to the desktop > right-click menu for simple configuration
  - can move new windows to the monitor having the mouse cursor
  - can create profiles for fast swithing and switch to a certain profile after system boot -> you can always fall back to the internal LCD after boot
- With this tool and the XP VGA driver the machine gets quite usable with Win7. Especially as even the standard VGA driver for the 65550 seems to be much more responsive then in XP. Of course display switching with long Touch-off would be nice but with Actual Multiple Monitors this isn't required any longer. And the highly improved Win7 RDP functions work without problems.
- Mabe even Win8 or Win10 would work but I haven't tested that.

So thanks to Keysight EMEA support I got the analyzer running with a fast mainboard and dual boot XP/Win7e. Due to the mechanical issues and the fact that unknown problems might occur I probably wouldn't do the modification on a company machine - except it's really required by the owner and problems are accepted. But for my private machine it was definitely a huge benefit.

[DaJMasta]

Great news!  I still have the best of intentions for my upgrade but it's still in the project heap.... 

[gslick]

My solution for using 16900A/16902A/16903A logic analyzers with the old and slow Windows XP motherboards is to reload Windows XP from the recovery DVD, then update to XP SP3, then install the 5.90.1110 software.

But then instead of running the 5.90.1110 software directly on the 16900A/16902A/16903A logic analyzer, also install the 5.90.1110 software on a nice fast modern PC with lots of memory and nice large monitors, and then control the analyzer remotely from the fast PC. You have to have the exact same version of the software on the analyzer and on the PC for the remote connection to work.

I need to get this setup going on my bench again and refresh my memory on exactly how it all works. I think even with a 100Mb network connection between the systems instead of a 1Gb network the performance was much better than using the software locally on the logic analyzer.

[charlyd]

Hello i join this conversation also because i got myself a 16903A with 2 16911A cards.... unit is on its way but will take some time. but i read a lot about building or changing the MB for the fastest model Win7 board. suitable in this unit...

so...

[charlyd]

is there someone who is running the 16903A with Win7 on the mobo, fast and succesfull?  if yes which mobo is installed or did you install a custom mobo?

and did you use SSD ?

[charlyd]

did someone ever try installing XP and upgrade that to win 7 ? for compatibility. I know there is nothing better then install from scratch. but sometime your are in a need for drivers and so..

[keitheevblog]

Hey everyone,

Proud new owner of a 16900A with 16950B and (5) 16910A's. Fully loaded!

I just wanted to thank everyone including ingowien for the discussions. Don't ever hesitate to post updates, especially that are chock-full of good information, out in the forums even if you think no one is listening. I can't tell you the number of times I've been rescued by a random post out there....even mine after I forgot what I did!

I just installed a SIL3114-based SATA card and SSD into my 16900A. XP was blue screening after factory disk re-imaging, throwing 0x7B STOP errors for inaccessible boot drive. Ended up repairing the XP installation with an off the shelf XP SP2 CD (with F6 floppy-drive copied drivers), and then manually installed SP3, and then installed LA Analyzer app 5.90.1110.

If I'm correct, I think the entire PCI bus has a maximum throughput available of around 1 gbps. I'm getting around 125MB/s maximum read/writes to the SSD. This might be a small improvement over the 3.5" HDD, but it should be more reliable and consistent speeds despite fragmentation or track location. Copying from the SSD to the gigabit, for SSD imaging purposes, I'm getting EXACTLY 67 megabytes per second over multiple hour average, which would be half-PCI speed. 133 MB/s total, split between the SSD and gigabit!

The bootup is somewhere around 15 seconds from power on to desktop, with another 30 seconds for all the modules to get "checked-in." I'm VERY happy with the boot-up speed. For the actual usage, I have to play around with it more.....just got it working recently.

This class of computer with USB 1.1 ports, PCI slots, 512MB RAM, and XP is so yesteryear. At least it has gig-e and can drive it relatively fast. I know that this is "sufficient" for the task, but I could definitely see me wanting to upgrade this mainboard to something newer and more modern.

I just wanted to say hello, thanks, and know that your posts are being read and are valuable!

Keith
Pittsburgh, near East Coast US

[charlyd]

hi and what about this board.. • Gigabyte G41MT-S2PT   -> Core 2 Quad cpu and 8 Gig

@Keith your max for the disk bus is 133 MB/s so SSD will never go over 133.


Does anybody have a 16900 series with an Original factory upgrade to a win7 ->  M890 MB?

[keitheevblog]

hi and what about this board.. • Gigabyte G41MT-S2PT   -> Core 2 Quad cpu and 8 Gig

@Keith your max for IDE is 133 MB/s so SSD will never go over 133.


Does anybody have a 16900 series with an Original factory upgrade to a win7 ->  M890 MB?

Hey.

Thanks for the message.

You're right, but I think for the wrong reasons!

The SSD doesn't connect via IDE. It connects via SATA, and then via PCI, which also has the same 133MB/s limitation. And if THAT doesn't slow it down, then the bus from the ICH connects to the CPU at 133MB/s. So you're right!!

There are some tangential benefits to be had from upgrading to an SSD though:

• Replaces a 13 year old drive
• Has no moving parts and so will likely be reliable long term
• Has a much faster access time/latency
• Has a higher number of concurrent IOPS
• Can be imaged at high-speed when connected to an external machine

The 16900 can't be factory upgraded to Win7 as far as I know. It doesn't have enough RAM....I think you have to go with a 16902 or a 16903.

[gslick]

The 16900 can't be factory upgraded to Win7 as far as I know. It doesn't have enough RAM....I think you have to go with a 16902 or a 16903.

The 16900A, 16902A, and 16903A are all basically the same from the CPU side of things. The motherboards were either a Radisys SC815E, a Motorola VP22, or an ADLINK M-815G, depending on the serial number. A 16902A is basically the same thing as a 16900A with a different front panel assembly with built in LCD display. You could turn one into the other by swapping the front panel assemblies. A 16903A is basically a 16902A that is limited to only 3 module slots, and only 2 accessible PCI slots instead of 3. It has a single power supply while the 16900A and 16902A have two power supplies to handle the additional module slots.

The 16901A has a different and more compact form factor, but with a larger built in LCD display. Basically the same as the 16800 series with only 2 modules slots on the side instead of in the rear. Depending on the serial number the motherboard could be an Intel D915GUX, an ADLINK M-880, or an ADLINK M-890.

The 16902B has the same general form factor as the 16902A, but with the same larger LCD display as the 16901A. Depending on the serial number the motherboard could be an ADLINK M-880 or an ADLINK M-890.

The later production 16901A and 16902B that came with the ADLINK M-890 motherboard were already running Windows 7. The earlier production 16901A and 16902B that came with an Intel D915GUX or an ADLINK M-880 motherboard could be upgraded to Windows 7 at Keysight by replacing the motherboard with an ADLINK M-890 motherboard and installing a new imaged HDD or SSD. An ADLINK M-880 motherboard system could also be upgraded to Windows 7 at Keysight by installing additional RAM on the existing ADLINK M-880 motherboard and installing a new imaged HDD or SSD.

https://literature.cdn.keysight.com/litweb/pdf/5992-0599EN.pdf
Keysight Technologies Windows 7 Upgrade Kits for 16800 Series, 16901A and 16902B Logic Analyzers Data Sheet

Summary

Windows 7 upgrade kit options are available to replace an existing Intel 915GUX motherboard or Adlink M880 motherboard with an Adlink M890 motherboard and supply a new imaged HDD or SSD. The kits cost $3495 plus installation for the 16800A and 16901A (HDD-based) and cost $5695 plus installation for the 16902B (SSD-based).

Options are available to retain an existing M880 motherboard and perform the upgrade from Windows XP to Windows 7 by supplying additional System RAM and a new, imaged HDD or SSD and cost $1495 plus installation for the 16800A and 16901A (HDD-based) and cost $1595 plus installation for 16902B (SSD-based).

Upgrades for additional external HDDs or SSDs imaged for Windows 7 are available and cost $1295 plus installation for the 16800A and 16901A (HDD-based) and cost $1895 plus installation for 16902B (SSD-based). If they are ordered separately then there is either the option to be installed at the service center or customer installed, and only if the proper upgrades have been previously purchased and installed.

Details

All 16800 Series, 16901A and 16902B logic analyzers with serial number MY51420101 or greater already have the M890 motherboard in them and are already running Windows 7 operating system.

All kits must be installed by the Keysight Technologies, Inc.Roseville, California Repair Center with the exception of additional hard drive kits that also offer an option to be customer installed. Approximate installation fees are outlined below.

All 16900A 16902A 16903A and 168xA/AD are obsolete and not upgradable to Windows 7.

System performance (CPU intensive operations and IO intensive operations) will be significantly improved by the Windows 7 upgrade kits which upgrade from the M880 motherboard to the M890 motherboard. Typical improvement is around twice the performance.

Upgrade kits which add additional memory to the existing M880 motherboard will yield performance similar to or slightly better than the original M880 motherboard running Windows XP but without the additional memory.

I have later productions versions of a 16901A and a 16902B which both came with ADLINK M-890 motherboards running Windows 7. If I remember right the 16901A has a 500GB WD hard drive, while the 16902B has a 320GB Intel SSD in an externally accessible removable drive tray. There are no recovery DVDs available for the Windows 7 systems, there is a recovery partition on the hard drive or SSD. I haven't figured out yet the best way to clone a drive to a different one of possibly different size, if I ever wanted to do that. I suppose I would need an image tool that could deal with resizing and moving partitions around as necessary.

[keitheevblog]

Thanks Glen.

Do you know which chipset, processor/speed, ram is used on the M890 motherboard?

Can you please take a high-resolution image of that motherboard, if you have it?

Thanks,
Keith

[ingowien]

There is a document "Keysight N2753A and N2754A Windows XP to Windows 7 Upgrade Kits" showing a screenshot of the XP System Properties on an M890 mainboard with an E8400 3.0GHz CPU and 3GB of RAM. That's why I used an E8400 for my tests, though there might have been different variants.

[gslick]

Thanks Glen.

Do you know which chipset, processor/speed, ram is used on the M890 motherboard?

Can you please take a high-resolution image of that motherboard, if you have it?

Thanks,
Keith

My 16901A with an M-890 motherboard has an Intel Core2 Duo E8400 @ 3.00GHz, 4GB of RAM, and a WD5000BPKX 500GB 2.5-inch 6 Gb/s disk.

The motherboard uses an Intel® 4 Series Chipsets Chipset Family, 82Q45 or 82Q43 Graphics and Memory Controller Hub (GMCH). Vendor ID 8086h, Device ID 2E10h, Revision Number 03h. I'm not sure at the moment if that if a Q45 or a Q43.

It uses an Intel® I/O Controller Hub 10 (Intel® ICH 10). That includes 2 EHCI USB 2.0 host controllers. The Gigabit Ethernet appears as an Intel 82574L, not the Gigabit Ethernet built into the ICH10.

Attached are some photos I found on the net (actually an eBay listing). I haven't opened my 16901A up yet to take a detailed look.

[gslick]

There is a document "Keysight N2753A and N2754A Windows XP to Windows 7 Upgrade Kits" showing a screenshot of the XP System Properties on an M890 mainboard with an E8400 3.0GHz CPU and 3GB of RAM. That's why I used an E8400 for my tests, though there might have been different variants.

If the system is running 32-bit Windows XP it might only be able to access 3GB of RAM even if the M-890 motherboard has 4GB of RAM.

The software image for the 16901A and 16902B with the M-890 motherboard runs 64-bit Windows Embedded Standard 7 SP1 and can access the full 4GB of RAM.

[keitheevblog]

My 16901A with an M-890 motherboard has an Intel Core2 Duo E8400 @ 3.00GHz, 4GB of RAM, and a WD5000BPKX 500GB 2.5-inch 6 Gb/s disk.

The motherboard uses an Intel® 4 Series Chipsets Chipset Family, 82Q45 or 82Q43 Graphics and Memory Controller Hub (GMCH). Vendor ID 8086h, Device ID 2E10h, Revision Number 03h. I'm not sure at the moment if that if a Q45 or a Q43.

It uses an Intel® I/O Controller Hub 10 (Intel® ICH 10). That includes 2 EHCI USB 2.0 host controllers. The Gigabit Ethernet appears as an Intel 82574L, not the Gigabit Ethernet built into the ICH10.

It sounds like you're pretty sure that's the case.

The nomenclature sure has me looking in the other direction.

We had the M815G motherboard, based on the Intel 815G chipset. Ok, all good.
We had the Intel 915GUX motherboard, again based on the Intel 915G chipset. Ok, all good.

Then we have the M880 and M890. But when you check https://en.wikipedia.org/wiki/List_of_Intel_chipsets you can't find any Intel-based chipsets with 880 or 890 in the name.....

So it makes me think about Adlink Tech based out of Taiwan. Via Technologies, also based out of Taiwan, has an 880 chipset and an 890 chipset as you can see here. https://en.wikipedia.org/wiki/List_of_VIA_chipsets

There's Biostar, also based in Taiwan, offers several motherboards that support Intel processors, but with this 880 and 890 chipsets.

Here's the 890 for instance: https://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=173#specification

This 890 takes an E8400 processor, amongst others.....

There's an 880 and various other 8xx boards.

Doesn't this strike you a bit too close of a fit to be wrong?

Thanks
Keith

[DaJMasta]

It's not that, though.  VIA chipsets are not intel Q45 chipsets, just because the number systems of some consumer grade boards match ones used by a different company for industrial motherboards.  Adlink makes hardware for industrial and commercial PoS/signage locations and similar, they don't sell to consumers like Biostar does, and you wouldn't have an intel northbridge or southbridge (Q45/43 and ICH10) with a VIA chipset, because you can't just mix and match them.


In any case, a related upgrade attempt:  I got my hands on a 16823A analyzer with a D915GUX motherboard in it and attempted to swap in a P5G41T-M for an upgrade and slight power consumption reduction, but while it would boot alright, the video controller did not take kindly to the swap - the main screen showed offset on the left 2/3rds.  Since the analyzer was reasonably fast with the P4 and windows XP on the original board, I opted to just upgrade the CPU to one of the better ones it could use and throw in more RAM, so I didn't have to muck around in screen video settings or drivers too much.  The rear output for the board worked as normal, but the internal connection from the PCIe riser card used for video wasn't quite happy with the board.  The BIOS is also customized by Agilent, with presets in the menus for the two screen sizes (12" and 15" depending on model), so I suspect there's some formatting setting for the integrated GPU to ship the picture out to the PCIe card that may be difficult to duplicate on a fully third party board.  The BIOS revision number is also totally different from intel's, intel's D915GUX number was 0482 whereas the bios identified itself as 6.0 and made no mention of a similar number format.

Long story short, upgrading the board to a consumer one will probably get you a running instrument with few issues, but getting the screen worked out properly could be tricky.

[keitheevblog]

It's not that, though.  VIA chipsets are not intel Q45 chipsets, just because the number systems of some consumer grade boards match ones used by a different company for industrial motherboards.  Adlink makes hardware for industrial and commercial PoS/signage locations and similar, they don't sell to consumers like Biostar does, and you wouldn't have an intel northbridge or southbridge (Q45/43 and ICH10) with a VIA chipset, because you can't just mix and match them.

Fair enough.

The interesting thing is that I have a family desktop machine still in regular use that uses an Intel DQ45CB motherboard with Core 2 Quad Q9550 with 8GB of ram. I stripped the CPU and RAM out of an old dell machine that was in a, eeeeessshhh, BTX motherboard. Rebuilt using new cube case, power supply, etc.

It seems many problems in the thread above were video-related issues with the touchscreen. I wonder for my 16900A whether installing 5.90.1110 on a modern-ish Windows 7(10?) machine might simply be enough? That's assuming that the Win7 drivers included work in a Win7 Pro install vs a WES7 one. I bet they do.

Outside of that, is there really any compatibility dependency on CPU/mobo/chipset/ram or any other aspect?

[ingowien]

In my tests all tested software versions (4.40, 5.40, 5.60, 5.70, 5.80, 5.90) worked with XP and the original mainboard (ADLINK M-815G).
But only 4.40, 5.40, 5.60 worked with any changed C2D mainboard (XP and Win7-x32). Versions 5.70, 5.80 and 5.90 did not work with any other mainboard than the original mainboard. Problem was that all drivers installed fine but simply the cards were not accepted (No valid ID in frame). My assumption is that some kind of hardware locking or compatibility check as added in the later versions.

I've not seen any real compatibility or stability issue in any mainboard (E8400, E6400, Q9400). No BSOD, nothing. Except that you might end up with "no valid ID in frame". And there might be limits when operating two different VGA cards in parallel where one runs the old XP driver.

[gslick]

Below is an enumeration of all of the hardware devices on the M-890 motherboard system in my 16901A, as seen by Windows.

One interesting device is the PCI\VEN_17CC&DEV_2282 "Agilent Technologies device-side USB". That is a NetChip / PLX 2282, which is a USB device controller, not a USB host controller. I wonder what that is connected to, it would have to be another USB host controller somewhere in the system.

There is a PCI\VEN_104C&DEV_AC28 Texas Instruments PCI2050 PCI-to-PCI Bridge, and behind that the PCI\VEN_15BC&DEV_0505 "Agilent Technologies 16800/16900 Series Analyzer (PCI-to-SVY)". Both of those devices might be on the PCI add-in card. I'll have to take a look at it. The PCI-to-SVY is the interface to the logic analyzer module backplane.

There is also an Agilent driver "AgtSMBusIch" for PCI\VEN_8086&DEV_3A30 "Intel(R) ICH10 Family Agilent SMBus Controller - 3A30", maybe for talking to devices on the motherboard SMBus.

Code: [Select]

+ DeviceID:
| HTREE\ROOT\0
| + DeviceID:
| | ROOT\ACPI_HAL\0000
| | HardwareIDs:
| | ->acpiapic
| | CompatibleIDs:
| | ->DETECTEDInternal\ACPI_HAL
| | ->DETECTED\ACPI_HAL
| | Device Description:
| | ->ACPI x64-based PC
| | Service:
| | ->\Driver\ACPI_HAL
| | + DeviceID:
| | | ACPI_HAL\PNP0C08\0
| | | HardwareIDs:
| | | ->ACPI_HAL\PNP0C08
| | | ->*PNP0C08
| | | Device Description:
| | | ->Microsoft ACPI-Compliant System
| | | Service:
| | | ->ACPI
| | | + DeviceID:
| | | | ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_23_-_INTEL(R)_CORE(TM)2_DUO_CPU_____E8400__@_3.00GHZ\_1
| | | | HardwareIDs:
| | | | ->ACPI\GenuineIntel_-_Intel64_Family_6_Model_23
| | | | ->*GenuineIntel_-_Intel64_Family_6_Model_23
| | | | ->ACPI\GenuineIntel_-_Intel64_Family_6
| | | | ->*GenuineIntel_-_Intel64_Family_6
| | | | ->ACPI\GenuineIntel_-_Intel64
| | | | ->*GenuineIntel_-_Intel64
| | | | CompatibleIDs:
| | | | ->ACPI\Processor
| | | | Device Description:
| | | | ->Intel Processor
| | | | Friendly Name:
| | | | ->Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
| | | | Service:
| | | | ->intelppm
| | | + DeviceID:
| | | | ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_23_-_INTEL(R)_CORE(TM)2_DUO_CPU_____E8400__@_3.00GHZ\_2
| | | | HardwareIDs:
| | | | ->ACPI\GenuineIntel_-_Intel64_Family_6_Model_23
| | | | ->*GenuineIntel_-_Intel64_Family_6_Model_23
| | | | ->ACPI\GenuineIntel_-_Intel64_Family_6
| | | | ->*GenuineIntel_-_Intel64_Family_6
| | | | ->ACPI\GenuineIntel_-_Intel64
| | | | ->*GenuineIntel_-_Intel64
| | | | CompatibleIDs:
| | | | ->ACPI\Processor
| | | | Device Description:
| | | | ->Intel Processor
| | | | Friendly Name:
| | | | ->Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
| | | | Service:
| | | | ->intelppm
| | | + DeviceID:
| | | | ACPI\PNP0A08\0
| | | | HardwareIDs:
| | | | ->ACPI\PNP0A08
| | | | ->*PNP0A08
| | | | CompatibleIDs:
| | | | ->*PNP0A03
| | | | Device Description:
| | | | ->PCI bus
| | | | Service:
| | | | ->pci
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2E10&SUBSYS_2E108086&REV_03\3&11583659&0&00
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2E10&SUBSYS_2E108086&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E10&SUBSYS_2E108086
| | | | | ->PCI\VEN_8086&DEV_2E10&CC_060000
| | | | | ->PCI\VEN_8086&DEV_2E10&CC_0600
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_2E10&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E10
| | | | | ->PCI\VEN_8086&CC_060000
| | | | | ->PCI\VEN_8086&CC_0600
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060000
| | | | | ->PCI\CC_0600
| | | | | Device Description:
| | | | | ->Intel(R) 4 Series Chipset Processor to I/O Controller - 2E10
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2E12&SUBSYS_2E128086&REV_03\3&11583659&0&10
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2E12&SUBSYS_2E128086&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E12&SUBSYS_2E128086
| | | | | ->PCI\VEN_8086&DEV_2E12&CC_030000
| | | | | ->PCI\VEN_8086&DEV_2E12&CC_0300
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_2E12&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E12
| | | | | ->PCI\VEN_8086&CC_030000
| | | | | ->PCI\VEN_8086&CC_0300
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_030000
| | | | | ->PCI\CC_0300
| | | | | Device Description:
| | | | | ->Intel(R) Q45/Q43 Express Chipset
| | | | | Service:
| | | | | ->igfx
| | | | | + DeviceID:
| | | | | | DISPLAY\MS_9001\4&2631CC80&1&UID67568640
| | | | | | HardwareIDs:
| | | | | | ->MONITOR\MS_9001
| | | | | | CompatibleIDs:
| | | | | | ->*PNP09FF
| | | | | | Device Description:
| | | | | | ->Generic PnP Monitor
| | | | | | Service:
| | | | | | ->monitor
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2E13&SUBSYS_2E128086&REV_03\3&11583659&0&11
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2E13&SUBSYS_2E128086&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E13&SUBSYS_2E128086
| | | | | ->PCI\VEN_8086&DEV_2E13&CC_038000
| | | | | ->PCI\VEN_8086&DEV_2E13&CC_0380
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_2E13&REV_03
| | | | | ->PCI\VEN_8086&DEV_2E13
| | | | | ->PCI\VEN_8086&CC_038000
| | | | | ->PCI\VEN_8086&CC_0380
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_038000
| | | | | ->PCI\CC_0380
| | | | | Device Description:
| | | | | ->Intel(R) Q45/Q43 Express Chipset
| | | | | Service:
| | | | | ->igfx
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A37&SUBSYS_3A378086&REV_00\3&11583659&0&D0
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A37&SUBSYS_3A378086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A37&SUBSYS_3A378086
| | | | | ->PCI\VEN_8086&DEV_3A37&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_3A37&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A37&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A37
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Universal Host Controller - 3A37
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&42BF6F&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A37&REV0000
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A37
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A3C&SUBSYS_3A3C8086&REV_00\3&11583659&0&D7
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3C&SUBSYS_3A3C8086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3C&SUBSYS_3A3C8086
| | | | | ->PCI\VEN_8086&DEV_3A3C&CC_0C0320
| | | | | ->PCI\VEN_8086&DEV_3A3C&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3C&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3C
| | | | | ->PCI\VEN_8086&CC_0C0320
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0320
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
| | | | | Service:
| | | | | ->usbehci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB20\4&33750BA2&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB20&VID8086&PID3A3C&REV0000
| | | | | | ->USB\ROOT_HUB20&VID8086&PID3A3C
| | | | | | ->USB\ROOT_HUB20
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A3E&SUBSYS_0700144A&REV_00\3&11583659&0&D8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3E&SUBSYS_0700144A&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3E&SUBSYS_0700144A
| | | | | ->PCI\VEN_8086&DEV_3A3E&CC_040300
| | | | | ->PCI\VEN_8086&DEV_3A3E&CC_0403
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3E&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3E
| | | | | ->PCI\VEN_8086&CC_040300
| | | | | ->PCI\VEN_8086&CC_0403
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_040300&DT_9
| | | | | ->PCI\CC_040300
| | | | | ->PCI\CC_0403&DT_9
| | | | | ->PCI\CC_0403
| | | | | Device Description:
| | | | | ->High Definition Audio Controller
| | | | | Service:
| | | | | ->HDAudBus
| | | | | + DeviceID:
| | | | | | HDAUDIO\FUNC_01&VEN_10EC&DEV_0262&SUBSYS_144A0000&REV_1002\4&3187122E&1&0101
| | | | | | HardwareIDs:
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0262&SUBSYS_144A0000&REV_1002
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0262&SUBSYS_144A0000
| | | | | | CompatibleIDs:
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_3A3E&VEN_10EC&DEV_0262&REV_1002
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC&DEV_0262&REV_1002
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0262&REV_1002
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_3A3E&VEN_10EC&DEV_0262
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC&DEV_0262
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0262
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_3A3E&VEN_10EC
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&VEN_10EC
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086&CTLR_DEV_3A3E
| | | | | | ->HDAUDIO\FUNC_01&CTLR_VEN_8086
| | | | | | ->HDAUDIO\FUNC_01&GF&VEN_10EC&DEV_0262&SUBSYS_144A0000&REV_1002
| | | | | | ->HDAUDIO\FUNC_01
| | | | | | Device Description:
| | | | | | ->Realtek High Definition Audio
| | | | | | Service:
| | | | | | ->IntcAzAudAddService
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A40&SUBSYS_3A408086&REV_00\3&11583659&0&E0
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A40&SUBSYS_3A408086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A40&SUBSYS_3A408086
| | | | | ->PCI\VEN_8086&DEV_3A40&CC_060400
| | | | | ->PCI\VEN_8086&DEV_3A40&CC_0604
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A40&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A40
| | | | | ->PCI\VEN_8086&CC_060400
| | | | | ->PCI\VEN_8086&CC_0604
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060400&DT_4
| | | | | ->PCI\CC_060400
| | | | | ->PCI\CC_0604&DT_4
| | | | | ->PCI\CC_0604
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
| | | | | Service:
| | | | | ->pci
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A48&SUBSYS_3A488086&REV_00\3&11583659&0&E4
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A48&SUBSYS_3A488086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A48&SUBSYS_3A488086
| | | | | ->PCI\VEN_8086&DEV_3A48&CC_060400
| | | | | ->PCI\VEN_8086&DEV_3A48&CC_0604
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A48&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A48
| | | | | ->PCI\VEN_8086&CC_060400
| | | | | ->PCI\VEN_8086&CC_0604
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060400&DT_4
| | | | | ->PCI\CC_060400
| | | | | ->PCI\CC_0604&DT_4
| | | | | ->PCI\CC_0604
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family PCI Express Root Port 5 - 3A48
| | | | | Service:
| | | | | ->pci
| | | | | + DeviceID:
| | | | | | PCI\VEN_8086&DEV_10D3&SUBSYS_00008086&REV_00\003064FFFF0EF72300
| | | | | | HardwareIDs:
| | | | | | ->PCI\VEN_8086&DEV_10D3&SUBSYS_00008086&REV_00
| | | | | | ->PCI\VEN_8086&DEV_10D3&SUBSYS_00008086
| | | | | | ->PCI\VEN_8086&DEV_10D3&CC_020000
| | | | | | ->PCI\VEN_8086&DEV_10D3&CC_0200
| | | | | | CompatibleIDs:
| | | | | | ->PCI\VEN_8086&DEV_10D3&REV_00
| | | | | | ->PCI\VEN_8086&DEV_10D3
| | | | | | ->PCI\VEN_8086&CC_020000
| | | | | | ->PCI\VEN_8086&CC_0200
| | | | | | ->PCI\VEN_8086
| | | | | | ->PCI\CC_020000&DT_0
| | | | | | ->PCI\CC_020000
| | | | | | ->PCI\CC_0200&DT_0
| | | | | | ->PCI\CC_0200
| | | | | | Device Description:
| | | | | | ->Intel(R) 82574L Gigabit Network Connection
| | | | | | Service:
| | | | | | ->e1qexpress
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A34&SUBSYS_3A348086&REV_00\3&11583659&0&E8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A34&SUBSYS_3A348086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A34&SUBSYS_3A348086
| | | | | ->PCI\VEN_8086&DEV_3A34&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_3A34&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A34&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A34
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Universal Host Controller - 3A34
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&1D102352&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A34&REV0000
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A34
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A35&SUBSYS_3A358086&REV_00\3&11583659&0&E9
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A35&SUBSYS_3A358086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A35&SUBSYS_3A358086
| | | | | ->PCI\VEN_8086&DEV_3A35&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_3A35&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A35&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A35
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Universal Host Controller - 3A35
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&F97D3BB&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A35&REV0000
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A35
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | + DeviceID:
| | | | | | | USB\VID_07DD&PID_0001\5&34A2064A&0&2
| | | | | | | HardwareIDs:
| | | | | | | ->USB\VID_07DD&PID_0001&REV_8023
| | | | | | | ->USB\VID_07DD&PID_0001
| | | | | | | CompatibleIDs:
| | | | | | | ->USB\Class_03&SubClass_01&Prot_02
| | | | | | | ->USB\Class_03&SubClass_01
| | | | | | | ->USB\Class_03
| | | | | | | Device Description:
| | | | | | | ->USB HID Touch Screen Controller
| | | | | | | Service:
| | | | | | | ->HidUsb
| | | | | | | + DeviceID:
| | | | | | | | HID\VID_07DD&PID_0001\6&30FFB929&1&0000
| | | | | | | | HardwareIDs:
| | | | | | | | ->HID\VID_07DD&PID_0001&REV_8023
| | | | | | | | ->HID\VID_07DD&PID_0001
| | | | | | | | ->HID_DEVICE_SYSTEM_MOUSE
| | | | | | | | ->HID_DEVICE_UP:0001_U:0002
| | | | | | | | ->HID_DEVICE
| | | | | | | | CompatibleIDs:
| | | | | | | | Device Description:
| | | | | | | | ->USB Touch Screen Controller
| | | | | | | | Service:
| | | | | | | | ->mouhid
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A36&SUBSYS_3A368086&REV_00\3&11583659&0&EA
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A36&SUBSYS_3A368086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A36&SUBSYS_3A368086
| | | | | ->PCI\VEN_8086&DEV_3A36&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_3A36&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A36&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A36
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Universal Host Controller - 3A36
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&7D61B93&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A36&REV0000
| | | | | | ->USB\ROOT_HUB&VID8086&PID3A36
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A3A&SUBSYS_3A3A8086&REV_00\3&11583659&0&EF
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3A&SUBSYS_3A3A8086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3A&SUBSYS_3A3A8086
| | | | | ->PCI\VEN_8086&DEV_3A3A&CC_0C0320
| | | | | ->PCI\VEN_8086&DEV_3A3A&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A3A&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A3A
| | | | | ->PCI\VEN_8086&CC_0C0320
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0320
| | | | | ->PCI\CC_0C03
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
| | | | | Service:
| | | | | ->usbehci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB20\4&1F9F9DFB&1
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB20&VID8086&PID3A3A&REV0000
| | | | | | ->USB\ROOT_HUB20&VID8086&PID3A3A
| | | | | | ->USB\ROOT_HUB20
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Service:
| | | | | | ->usbhub
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_244E&SUBSYS_244E8086&REV_90\3&11583659&0&F0
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_244E&SUBSYS_244E8086&REV_90
| | | | | ->PCI\VEN_8086&DEV_244E&SUBSYS_244E8086
| | | | | ->PCI\VEN_8086&DEV_244E&CC_060401
| | | | | ->PCI\VEN_8086&DEV_244E&CC_0604
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_244E&REV_90
| | | | | ->PCI\VEN_8086&DEV_244E
| | | | | ->PCI\VEN_8086&CC_060401
| | | | | ->PCI\VEN_8086&CC_0604
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060401
| | | | | ->PCI\CC_0604
| | | | | Device Description:
| | | | | ->Intel(R) 82801 PCI Bridge - 244E
| | | | | Service:
| | | | | ->pci
| | | | | + DeviceID:
| | | | | | PCI\VEN_17CC&DEV_2282&SUBSYS_00000000&REV_11\4&1D98F028&1&38F0
| | | | | | HardwareIDs:
| | | | | | ->PCI\VEN_17CC&DEV_2282&SUBSYS_00000000&REV_11
| | | | | | ->PCI\VEN_17CC&DEV_2282&SUBSYS_00000000
| | | | | | ->PCI\VEN_17CC&DEV_2282&REV_11
| | | | | | ->PCI\VEN_17CC&DEV_2282
| | | | | | ->PCI\VEN_17CC&DEV_2282&CC_0C03FE
| | | | | | ->PCI\VEN_17CC&DEV_2282&CC_0C03
| | | | | | CompatibleIDs:
| | | | | | ->PCI\VEN_17CC&CC_0C03FE
| | | | | | ->PCI\VEN_17CC&CC_0C03
| | | | | | ->PCI\VEN_17CC
| | | | | | ->PCI\CC_0C03FE
| | | | | | ->PCI\CC_0C03
| | | | | | Device Description:
| | | | | | ->Agilent Technologies device-side USB
| | | | | | Service:
| | | | | | ->Agt2280
| | | | | + DeviceID:
| | | | | | PCI\VEN_104C&DEV_AC28&SUBSYS_00000000&REV_00\4&1D98F028&1&78F0
| | | | | | HardwareIDs:
| | | | | | ->PCI\VEN_104C&DEV_AC28&SUBSYS_00000000&REV_00
| | | | | | ->PCI\VEN_104C&DEV_AC28&SUBSYS_00000000
| | | | | | ->PCI\VEN_104C&DEV_AC28&REV_00
| | | | | | ->PCI\VEN_104C&DEV_AC28
| | | | | | ->PCI\VEN_104C&DEV_AC28&CC_060400
| | | | | | ->PCI\VEN_104C&DEV_AC28&CC_0604
| | | | | | CompatibleIDs:
| | | | | | ->PCI\VEN_104C&CC_060400
| | | | | | ->PCI\VEN_104C&CC_0604
| | | | | | ->PCI\VEN_104C
| | | | | | ->PCI\CC_060400
| | | | | | ->PCI\CC_0604
| | | | | | Device Description:
| | | | | | ->PCI standard PCI-to-PCI bridge
| | | | | | Service:
| | | | | | ->pci
| | | | | | + DeviceID:
| | | | | | | PCI\VEN_15BC&DEV_0505&SUBSYS_00000000&REV_00\5&19F0F871&0&0078F0
| | | | | | | HardwareIDs:
| | | | | | | ->PCI\VEN_15BC&DEV_0505&SUBSYS_00000000&REV_00
| | | | | | | ->PCI\VEN_15BC&DEV_0505&SUBSYS_00000000
| | | | | | | ->PCI\VEN_15BC&DEV_0505&REV_00
| | | | | | | ->PCI\VEN_15BC&DEV_0505
| | | | | | | ->PCI\VEN_15BC&DEV_0505&CC_0B4000
| | | | | | | ->PCI\VEN_15BC&DEV_0505&CC_0B40
| | | | | | | CompatibleIDs:
| | | | | | | ->PCI\VEN_15BC&CC_0B4000
| | | | | | | ->PCI\VEN_15BC&CC_0B40
| | | | | | | ->PCI\VEN_15BC
| | | | | | | ->PCI\CC_0B4000
| | | | | | | ->PCI\CC_0B40
| | | | | | | Device Description:
| | | | | | | ->Agilent Technologies 16800/16900 Series Analyzer (PCI-to-SVY)
| | | | | | | Service:
| | | | | | | ->ag16900Svy
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A18&SUBSYS_3A188086&REV_00\3&11583659&0&F8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A18&SUBSYS_3A188086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A18&SUBSYS_3A188086
| | | | | ->PCI\VEN_8086&DEV_3A18&CC_060100
| | | | | ->PCI\VEN_8086&DEV_3A18&CC_0601
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A18&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A18
| | | | | ->PCI\VEN_8086&CC_060100
| | | | | ->PCI\VEN_8086&CC_0601
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060100
| | | | | ->PCI\CC_0601
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 LPC Interface Controller - 3A18
| | | | | Service:
| | | | | ->msisadrv
| | | | | + DeviceID:
| | | | | | ACPI\PNP0000\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0000
| | | | | | ->*PNP0000
| | | | | | Device Description:
| | | | | | ->Programmable interrupt controller
| | | | | + DeviceID:
| | | | | | ACPI\PNP0200\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0200
| | | | | | ->*PNP0200
| | | | | | Device Description:
| | | | | | ->Direct memory access controller
| | | | | + DeviceID:
| | | | | | ACPI\PNP0100\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0100
| | | | | | ->*PNP0100
| | | | | | Device Description:
| | | | | | ->System timer
| | | | | + DeviceID:
| | | | | | ACPI\PNP0B00\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0B00
| | | | | | ->*PNP0B00
| | | | | | Device Description:
| | | | | | ->System CMOS/real time clock
| | | | | + DeviceID:
| | | | | | ACPI\PNP0800\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0800
| | | | | | ->*PNP0800
| | | | | | Device Description:
| | | | | | ->System speaker
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C04\4&7A6EE5B&1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C04
| | | | | | ->*PNP0C04
| | | | | | Device Description:
| | | | | | ->Numeric data processor
| | | | | + DeviceID:
| | | | | | ACPI\PNP0501\1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0501
| | | | | | ->*PNP0501
| | | | | | Device Description:
| | | | | | ->Communications Port
| | | | | | Friendly Name:
| | | | | | ->Communications Port (COM1)
| | | | | | Service:
| | | | | | ->Serial
| | | | | + DeviceID:
| | | | | | ACPI\PNP0501\2
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0501
| | | | | | ->*PNP0501
| | | | | | Device Description:
| | | | | | ->Communications Port
| | | | | | Friendly Name:
| | | | | | ->Communications Port (COM2)
| | | | | | Service:
| | | | | | ->Serial
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C02\2E
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C02
| | | | | | ->*PNP0C02
| | | | | | Device Description:
| | | | | | ->Motherboard resources
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C02\10
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C02
| | | | | | ->*PNP0C02
| | | | | | Device Description:
| | | | | | ->Motherboard resources
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C02\0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C02
| | | | | | ->*PNP0C02
| | | | | | Device Description:
| | | | | | ->Motherboard resources
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A20&SUBSYS_3A208086&REV_00\3&11583659&0&FA
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A20&SUBSYS_3A208086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A20&SUBSYS_3A208086
| | | | | ->PCI\VEN_8086&DEV_3A20&CC_01018A
| | | | | ->PCI\VEN_8086&DEV_3A20&CC_0101
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A20&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A20
| | | | | ->PCI\VEN_8086&CC_01018A
| | | | | ->PCI\VEN_8086&CC_0101
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_01018A
| | | | | ->PCI\CC_0101
| | | | | Device Description:
| | | | | ->Standard Dual Channel PCI IDE Controller
| | | | | Service:
| | | | | ->pciide
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&17C62592&1&0
| | | | | | HardwareIDs:
| | | | | | ->Intel-3a20
| | | | | | ->Internal_IDE_Channel
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Device Description:
| | | | | | ->IDE Channel
| | | | | | Friendly Name:
| | | | | | ->ATA Channel 0
| | | | | | Service:
| | | | | | ->atapi
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&17C62592&1&1
| | | | | | HardwareIDs:
| | | | | | ->Intel-3a20
| | | | | | ->Internal_IDE_Channel
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Device Description:
| | | | | | ->IDE Channel
| | | | | | Friendly Name:
| | | | | | ->ATA Channel 1
| | | | | | Service:
| | | | | | ->atapi
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A30&SUBSYS_3A308086&REV_00\3&11583659&0&FB
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A30&SUBSYS_3A308086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A30&SUBSYS_3A308086
| | | | | ->PCI\VEN_8086&DEV_3A30&CC_0C0500
| | | | | ->PCI\VEN_8086&DEV_3A30&CC_0C05
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A30&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A30
| | | | | ->PCI\VEN_8086&CC_0C0500
| | | | | ->PCI\VEN_8086&CC_0C05
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0500
| | | | | ->PCI\CC_0C05
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family Agilent SMBus Controller - 3A30
| | | | | Service:
| | | | | ->AgtSMBusIch
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A26&SUBSYS_3A268086&REV_00\3&11583659&0&FD
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A26&SUBSYS_3A268086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A26&SUBSYS_3A268086
| | | | | ->PCI\VEN_8086&DEV_3A26&CC_010185
| | | | | ->PCI\VEN_8086&DEV_3A26&CC_0101
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A26&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A26
| | | | | ->PCI\VEN_8086&CC_010185
| | | | | ->PCI\VEN_8086&CC_0101
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_010185
| | | | | ->PCI\CC_0101
| | | | | Device Description:
| | | | | ->Standard Dual Channel PCI IDE Controller
| | | | | Service:
| | | | | ->pciide
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&306AF12D&1&0
| | | | | | HardwareIDs:
| | | | | | ->Intel-3a26
| | | | | | ->Internal_IDE_Channel
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Device Description:
| | | | | | ->IDE Channel
| | | | | | Friendly Name:
| | | | | | ->ATA Channel 0
| | | | | | Service:
| | | | | | ->atapi
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&306AF12D&1&1
| | | | | | HardwareIDs:
| | | | | | ->Intel-3a26
| | | | | | ->Internal_IDE_Channel
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Device Description:
| | | | | | ->IDE Channel
| | | | | | Friendly Name:
| | | | | | ->ATA Channel 1
| | | | | | Service:
| | | | | | ->atapi
| | | | | | + DeviceID:
| | | | | | | IDE\DISKWDC_WD5000BPKX-00HPJT0__________________01.01A01\5&3551BD61&0&1.0.0
| | | | | | | HardwareIDs:
| | | | | | | ->IDE\DiskWDC_WD5000BPKX-00HPJT0__________________01.01A01
| | | | | | | ->IDE\WDC_WD5000BPKX-00HPJT0__________________01.01A01
| | | | | | | ->IDE\DiskWDC_WD5000BPKX-00HPJT0__________________
| | | | | | | ->WDC_WD5000BPKX-00HPJT0__________________01.01A01
| | | | | | | ->GenDisk
| | | | | | | CompatibleIDs:
| | | | | | | ->GenDisk
| | | | | | | Device Description:
| | | | | | | ->Disk drive
| | | | | | | Friendly Name:
| | | | | | | ->WDC WD5000BPKX-00HPJT0 ATA Device
| | | | | | | Service:
| | | | | | | ->disk
| | | | | | | Drive Name C:
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_3A32&SUBSYS_3A328086&REV_00\3&11583659&0&FE
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_3A32&SUBSYS_3A328086&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A32&SUBSYS_3A328086
| | | | | ->PCI\VEN_8086&DEV_3A32&CC_118000
| | | | | ->PCI\VEN_8086&DEV_3A32&CC_1180
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_3A32&REV_00
| | | | | ->PCI\VEN_8086&DEV_3A32
| | | | | ->PCI\VEN_8086&CC_118000
| | | | | ->PCI\VEN_8086&CC_1180
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_118000
| | | | | ->PCI\CC_1180
| | | | | Device Description:
| | | | | ->Intel(R) ICH10 Family Thermal Subsystem - 3A32
| | | | + DeviceID:
| | | | | ACPI\PNP0C01\A
| | | | | HardwareIDs:
| | | | | ->ACPI\PNP0C01
| | | | | ->*PNP0C01
| | | | | Device Description:
| | | | | ->System board
| | | | + DeviceID:
| | | | | ACPI\PNP0C02\11
| | | | | HardwareIDs:
| | | | | ->ACPI\PNP0C02
| | | | | ->*PNP0C02
| | | | | Device Description:
| | | | | ->Motherboard resources
| | | + DeviceID:
| | | | ACPI\PNP0C01\1
| | | | HardwareIDs:
| | | | ->ACPI\PNP0C01
| | | | ->*PNP0C01
| | | | Device Description:
| | | | ->System board
| | | + DeviceID:
| | | | ACPI\PNP0C0C\AA
| | | | HardwareIDs:
| | | | ->ACPI\PNP0C0C
| | | | ->*PNP0C0C
| | | | Device Description:
| | | | ->ACPI Power Button
| | | + DeviceID:
| | | | ACPI\FIXEDBUTTON\2&DABA3FF&1
| | | | HardwareIDs:
| | | | ->ACPI\FixedButton
| | | | ->*FixedButton
| | | | Device Description:
| | | | ->ACPI Fixed Feature Button


[gslick]

Attached is a quick image of the M-890 motherboard as installed in my 16901A. I could try to take a higher resolution photo sometime, although it might be a while before I got around to trying to do that.

Installed in the single PCI slot is the interface to the logic analyzer module backplane.

The service manual shows a second PCI display card, which is not present here. With the M-890 motherboard the front panel LCD display connects directly to the LVDS connector on the M-890 motherboard.

The dual port USB cable connection to the M-890 motherboard goes to the two USB ports on the front panel.

The single port USB cable connection to the M-890 motherboard goes to the font panel touch screen controller.

Other than the CPU and Q45/Q43 and ICH10 chipset under the heatsinks, the interesting components on the M-890 motherboard are the following:

• ICS (IDT) ICS9LP505-2 56-pin CK505 for Intel Desktop Systems
• ITE IT8718F-S Environment Control - Low Pin Count Input / Output (EC - LPC I/O)
• Intel 82574L Gigabit Ethernet Controller
• Chrontel CH7308B-TF SDVO LVDS Transmitter (for front panel LCD display)
• Chrontel CH7318C-BF AC Coupled HDMI Level Shifter (for external DVI connector)
• Realtek ALC262 4-Channel High Definition Audio Codec
• PLX NET2282 PCI to Hi-Speed USB 2.0 Controller (no idea how this is used in this system)
• (2x) Unigen UG25U6400M8DU-ACB 2GB DDR3 1333 UDIMM 240PIN

EDIT: The Agilent / Keysight part number for the M-890 motherboard is 0960-2939. Keysight Find-A-Part says this motherboard is used in the following Logic Analyzers and 9000 Series Oscilloscopes. My guess is that the PLX NET2282 PCI to Hi-Speed USB 2.0 Controller on the M-890 motherboard is not used in the Logic Analyzer application, but is used to provide the USB device port for control from a PC in the 9000 Series Oscilloscope application.

• 16800AU
• 16801A
• 16802A
• 16803A
• 16804A
• 16806A
• 16821A
• 16822A
• 16823A
• 16851A
• 16852A
• 16853A
• 16854A
• 16900AU
• 16901A
• 16902B
• DSO9024H
• DSO9054H
• DSO9064A
• DSO9064L
• DSO9104A
• DSO9104AN
• DSO9104H
• DSO9204H
• DSO9254A
• DSO9404A
• MSO9064A
• MSO9104A
• MSO9254A
• MSO9404A

[keitheevblog]

MY XP 5.90.1110 16900A has the following entries under HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo :

• FrameModelNumber, REG_SZ "16900"
• NoDisplaySwitching, REG_SZ "false"
• Ag16900Standalone, REG_DWORD 1
• SysReady, REG_DWORD 1

agLogicSvc.exe throws "NO VALID ID DETECTED IN FRAME!" error that occurs whenever the main HKEY_LOCAL_MACHINE\AgMachineInfo key doesn't exist in the registry.

There are other versions of that error that have "REQUIRES FACTORY HARDWARE INITIALIZATION!" or "REQUIRES PROPER SYSTEM BIOS!" suffixes which is related to the checking of the "SecureId" key, which I don't seem to have anywhere. You could also get a "SYSTEM FILTER DRIVER MISSING! Re-install logic analyzer software or run [agHwInstall -install] from the logic analyzer installation directory." error in some cases.

Last but not least, a "MfgOnly" key when set throws "MANUFACTURING-ONLY SETTINGS ACTIVE!"

[keitheevblog]

Hey Glen,

Thanks

It looks a lot like this Adlink Tech M-321 here:

https://www.prosoft.ru/cms/f/441897.pdf

no?

Keith

[gslick]

It looks a lot like this Adlink Tech M-321 here:

https://www.prosoft.ru/cms/f/441897.pdf

Yep, that does look like a match, or at least a customized build of the M-321. Good find.

These are the differences I noticed between the M-321 manual and the M-890 motherboard:

• The M-890 version only populates one Intel 82574L Gigabit Ethernet Controller, not two.
• The M-890 version does not populate the CN5 LVDS Inverter connector next to the CN6 LVDS connector.
• The M-890 version populates two additional SATA connectors next to the PCI slot which are not populated on the M-321 version. On the cover photo of the manual linked above it appears that they just pasted green rectangles on the photo where those additional two SATA connectors are located.

I wonder if it is any easier to find an ADLINK M-321 motherboard than an M-890 motherboard. A quick look on the net doesn't turn up any available anywhere.

EDIT: The two additional SATA connectors next to the PCI slot on the M-890 version are not SATA, they are PCI-e. They are not used in the 16901A / 16902B application, but they are used in the 9000 Series Oscilloscope application to connect to the signal acquisition system.  See this thread for more details about that:
https://www.eevblog.com/forum/testgear/agilentkeysight-infiniium-mso9000-series-motherboard-repairupgrade/

[keitheevblog]

I couldn't seem to find any sources. However, I am starting to believe that there aren't many hardware restrictions at all.

I did notice that your M890 board includes an extra 4-pin CPU power cord. My M815G definitely doesn't use it......just the 24-pin power cable to the backplane.

I'm not sure if anyone finds this interesting, but linked is a source-ish-code for how the "NO VALID ID DETECTED IN FRAME!" registry checking logic works specifically in agLogicSvc.exe :

https://pastebin.com/EgX1JBuZ

Thanks

[ingowien]

I did notice that your M890 board includes an extra 4-pin CPU power cord. My M815G definitely doesn't use it......just the 24-pin power cable to the backplane.

In my 16903 there is an extra 4pin power connector on the backplane with 2xGND + 2x+12V. I used that for the P4 power on the C2D board. The old P3 boards didn't have the extra power connector introduced with the first P4 CPUs.

However I'm sure you recognized that the 16900A/16902A/16903A are very different from the 16901A and 16902B.
The older hardware revision uses a parallel style LCD connected to an extra 65550 VGA card either on the back plane (16903A) or on the PCI card (16900A/16902A). The latter use an LVDS panel directly connected to the mainboard. So If unless you already have one of the newer analyzers (that probably has a more modern mainboard), a matching LVDS panel or an M-890 I think it would be easier to use a common C2D mainboard. None of the mainboards I found will fit the cutouts in the 1690xA backcover. Or did anybody find a mechanically suitable mainboard?

[ingowien]

agLogicSvc.exe throws "NO VALID ID DETECTED IN FRAME!" error that occurs whenever the main HKEY_LOCAL_MACHINE\AgMachineInfo key doesn't exist in the registry.

I did a quick test with v5.90 on my 16903A with the Asus P5G41T-M LX, C2Q Q9400, Win7 Embedded Std with the registry key AgMachineInfo in place. Indeed I didn't get the "No valid ID" error but the service got stuck when initializing the hardware. I tried this two times with reverting to my running Acronis image between the tests confirming that v5.40 still works. Maybe the combination of Win7, the 16903A hardware and v5.90 doesn't work or some registry keys are still missing. I'll stick with v5.40 for now as Win7 and USB 3 support is more important for me than v5.90.

Maybe v5.40 or v5.60 it is a good starting point for other users as well. I think I installed v5.40 on my test machine as this is the last release before changing to .Net 4.0, no other special reason if I remember correctly.

[keitheevblog]

None of the mainboards I found will fit the cutouts in the 1690xA backcover. Or did anybody find a mechanically suitable mainboard?

I think that the parallel port on the back might be tough due to the fact that it's rarely used any more.

Depending on the existing layout, it may be possible to cut a standardized rectangular hole to accept a standard PC I/O shield. This way, 90% of the motherboards out there would be compatible with it. If done carefully, you could end up with a reasonable looking finished product.

I'm not in love with "taking a knife to" my analyzer, but this might work!

[ingowien]

Yes, that's what I did. The good thing is that the mainboard tray if the 16903A is not one piece but the back cover can be taken off. I used a fretsaw to preserve the original shield as good as possible but if you don't care, you can use a jigsaw as well. You have to be aware that mechanical assembly isn't that rigid any more as the original design relies on the serial/parallel port screws for additional strength. That is obviously not as rigid with the I/O shield but it works. It might be useful to add some extra screws on the bottom side for improved EMC compatibility but I didn't do that.
So yes, going for a standard ATX I/O shield is definitely the best option.

[gslick]

I did a quick test with v5.90 on my 16903A with the Asus P5G41T-M LX, C2Q Q9400, Win7 Embedded Std with the registry key AgMachineInfo in place.

What did you do about the motherboard power supply connections? The M-815G motherboard has a 20-pin ATX power supply connector, and no CPU power supply connector. The Asus P5G41T-M LX motherboard has a 24-pin ATX power supply connector and a 4-pin CPU power supply connector.

Did you just connect the 20-pin power supply plug from the 16903A power supply to 20 of the 24 pins of the Asus P5G41T-M LX motherboard power supply connector and call it good?

[ingowien]

Did you just connect the 20-pin power supply plug from the 16903A power supply to 20 of the 24 pins of the Asus P5G41T-M LX motherboard power supply connector and call it good?

Yes. The additional 4 pins are just GND, 3V3, 5V and 12V. There are already 4x 5V and 3x 3V3 in place and 12V usually isn't the issue as the CPU has its own 12V P4 power. We're powering lots of Ci3 and Ci5 mainboards from PicoPSUs that only have 20 pins and never had an issue. Internal resistance may be lower with those as there are no cables but on the other hand they are less powerful than a 400W ATX supply. It might be an issue if lots of 12V PCIe power is required but that isn't the case here.

[gslick]

Thanks. I missed your earlier reply which answered the other part of my question.

In my 16903 there is an extra 4pin power connector on the backplane with 2xGND + 2x+12V. I used that for the P4 power on the C2D board.

The 16900A backplane also has the extra 4-pin power connector.

[charlyd]

Hello i have this Gigabyte-GA-6VTXDR with 2x  1.4GHZ tualatin cpu on it.. would it be good to give that a go?  or is that also too slow?  ok better a WIN7 or better of course..
but for the compatibility?

..mmmmmmmm too big board...

[charlyd]

anybody found out what SSD controller is the best? i see many models on ebay.. but i can imagine that some are a better choise then others..

[charlyd]

did some search on mobo's what about this one?   GA-EQ45M-S2-rev-2.1  has lots of CPU support. and looks like the size of the M-890.  has some sata connectors power con on the right place.

for CPU here:   https://www.gigabyte.com/fi/Motherboard/GA-EQ45M-S2-rev-21#support-cpu
for mem here:  http://download.gigabyte.eu/FileList/Memory/motherboard_memory_ga-eq45m-s2_v2.x.pdf

i decided to buy this board because it has a compatible chipset [Intel® Q45 + ICH10DO chipset ] as the M890.
one small difference is the TFT screen F65550 connector on the M890 board. but i will try to get the F65550 driver to work.

[charlyd]

did any body find out a way to bypass or fake the message:  " NO VALID ID DETECTED IN FRAME! REQUIRES PROPER SYSTEM BIOS  "

i have got it also...would be nice to fool it. Is there a way to edit it into the bios files?  i have the bios file from my current MoBo. Hexeditor can do the job.
i can export the bios from my M815-G with a programmer to get a valid ID out if it.

but where is it written and is it possible to "hack my Bios ;-) " or fool the check...


who can help me out with a link to the older versions... can i download them somewhere.

[gslick]

did any body find out a way to bypass or fake the message:  " NO VALID ID DETECTED IN FRAME! REQUIRES PROPER SYSTEM BIOS  "

Are you currently running Windows XP or Windows 7 on the new motherboard? What version of the logic analyzer application are you trying when you get this error message?

Might be best to try to figure out what software binary is checking the motherboard signature. Maybe the binary could be patched to bypass the motherboard signature check.

[keitheevblog]

I've done some work on this exact topic.

See reply #31.

AgLogicSvc.exe is responsible for displaying that message. I disassembled that binary using the NSA's Ghidra and then decompiled it into C++.

I don't claim to have a 100% grasp on it, however, the driving factors are a series of registry keys. And how the executable was configured (what was passed into it when called)

Look at that pastebin. Ctrl-f for your message, and look at that IF block.

Search your Registry for a key called SecureID. I'd also go back and reread my other message where I call out the other keys, and make sure they are in place.

There's another possibility that despite the messenger AgLogicSvc.exe reporting it there's some underlying reason why it can't or won't work.

That binary can be patched. But the registry keys seem to be the initial driving factor,  and also the easiest to correct. I'd wait until that message is displayed and then without closing it, look for the keys mentioned.

Ingowien (sp on mobile) reports 5.60 working fine. It's versions 5.70 or after that throw that message. Unless you needed those features, you could probably just use an earlier version.

Keith

EDIT: make sure to check that AgMachineInfo and the subkey FrameModelNumber is present and has a value.  It sure looks like that message can't be displayed if those two things are true! I'm away and on mobile, but that looks right! Check the pastebin and the previous message with keys for details.

[charlyd]

@Glen, i am running Windows XP sp 3 ( fresh install ) and LA version 5.90     i f i have earlier version which i do not have ( maybe someone can advertise a goolge-drive link with all version downloadable.

@ keitheevblog  ok i will test it is you have a new exe file available.

tonight i wil look for the "secureID"  in de registry from the M815G board.

[charlyd]

@ keitheevblog   is it an idea to also look inside version 5.6  and compare to 5.9 look how they did error handling/the check inside 5.6 and edit it like that in 5.9 ? and then compile again?

:edit:   not found any secureID key in the registry.

and agHWinstall says in the bottom of the checks none

verifying harddrive image  N/A  does this matter? does the software check if the install is from the image?

after checking this settings
MY XP 5.90.1110 16900A has the following entries under HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo :

FrameModelNumber, REG_SZ "16900"
NoDisplaySwitching, REG_SZ "false"
Ag16900Standalone, REG_DWORD 1
SysReady, REG_DWORD 1

after the check has ran and not finished succesfull :  the FrameModelnumber value changes  to 169  "00" are gone  and not possible to edit..   but i can delete the entry
and add it again...

strange..

What more can i test???

another problem i have is   i cannot restore the original image on a disk and boot up on the new board.  the new drive is SATA fresh install works fine but the agilent image and sata drives..not. i disabled AHCI and setted the bios in legacy mode. still not.

so i am curious if an older version of the LA software would work so here an other call can someone share his older LA version(s) with me..?

[charlyd]

can somebody help me out with a picture of the original powerswitch connector on the M815G board site from the 16903A 
the 4 pin cable with the wiring

1. blue
2. black
3. yellow
4. orange
 
i made some pictures before i started but i think i deleted them on my phone 
a close up picture of the M815G MoBo side would be enough if you coloring is the same as mine. ( it has the metal plate over it)

It sound like a silly question but one way or an other my upgrade (refurbished) MoBo died after few days working from reverse wiring  ?

[ingowien]

All I can show is a picture of the connector that was attached to my M815G board. It's unmodified as I always create adapter cables. It matches the labeling on the M185G board (CN21).
Hope this helps.

[charlyd]

many thanks @ingowien this is very clear for me. now i gonna work out what exactly happend because from what i see i only had the both GND in the middle swapped. but that doesn t make much difference …( of course i will correct them).  from the other hand Glen also showed me some pictures from connectors and his middle wires were both black. (gnd- colors) earlier model LA.
From out of the factory it is so easy to use the same wiring colors - as produced before- if there is 100% no difference, but no they changed it for yellow instead of black. Does this mean anything, like you are not allowed to pretend they are both 100% same?  (something like one is GND and the other is "GND".)


@ingowien: did you work out the touch screen on the comport?

[Calhoon]

Hello, friends.
Help me please.
I have no experience working with this equipment.
I have Agilent 16802A with 4Mb.
I want to upgrade it to 32Mb?
The instructions say that I need a license key. Where can I find him?
Are there any other ways?

[ingowien]

Hi, the 16802A is just the chassis, you need to know which cards you're using.
If it's a 1695x or 1695x, you're probably stuck with the 4MB. The memory size is defined by eeprom content and may be checksum protected. Agilent/Keysight doesn't sell upgrades any more (I've asked them, they refuse) and I don't know of any hack. If you find one, please post here.

You can check this thread, especially reply #23 comments on 169xx cards:
https://www.eevblog.com/forum/testgear/hpagilent-1675x-logic-analyzer-card-memory-up-hack/msg1394202/#msg1394202

[gslick]

The original 16800A series logic analyzers had eight models:

16801A 34 logic analyzer channels, single slot
16802A 68 logic analyzer channels, single slot
16803A 102 logic analyzer channels, single slot
16804A 136 logic analyzer channels, dual slot
16806A 204 logic analyzer channels, dual slot
16821A 34 logic analyzer channels, 48 pattern generator channels, dual slot
16822A 68 logic analyzer channels, 48 pattern generator channels, dual slot
16823A 102 logic analyzer channels, 48 pattern generator channels, dual slot

The 34, 68, and 136 logic analyzer channel models used either one or two 16911A equivalent modules.

The 102 and 204 logic analyzer channel models used either one or two 16910A equivalent modules.

The 48 pattern generator channel models used a 16720A equivalent module.

The mainframes were equivalent to the two slot 16901A mainframe, except that the single slot 16800A models were cost reduced with lower capacity power supplies and a single module slot backplane. As far as I know a two slot 16800A mainframe is identical to a 16901A, except for mainframe ID information stored somewhere that the analyzer software can use to determine the mainframe type.

Also as far as I know the 16910A, 16911A, and 16720A equivalent modules used by the 16800A series are identical with normal 16910A, 16911A, and 16720A modules except for ID information stored somewhere that the analyzer software can use to determine the 16800 series specific module type.

I have never had a 16800A series logic analyzer myself to experiment with. As far as I know the ID information in the 16800A series mainframes and modules is used to lock the series so that logic analyzer and pattern generator modules cannot be interchanged between the 16800A series and the 16900A series. The logic analyzer software does not recognize modules swapped between the two series (again, I haven't verified that myself). That was probably just a marketing decision so that if you wanted complete flexibility in that form factor you would have to buy a 16901A mainframe at some price premium over a similarly configured 16800A series mainframe.

So anyway, back to the original question about upgrading a 68 channel 16802A with 4M sample depth, the analyzer module is equivalent to a 16911A. Those have 1M, 4M, 16M and 32M sample depth options, and 250 MHz and 500 MHz state options, and they are upgraded with a software license mechanism. When the upgrade license is installed on the module it must change something in non-volatile memory somewhere on the module. I am not aware of anyone yet who has successfully reverse engineered the 16910A / 16911A module option mechanism, so no one here can help you unless someone comes forward with new information about this.

If the 16800A series mainframes and modules weren't ID locked, one option would be to swap the analyzer module with a 32M sample depth 16752A or 16752B module. That would work on a 16900A series mainframe, but as far as I know would be prevented from working on a 16800A series mainframe. If that is incorrect, I would be happy to be corrected by someone who has tried it and found that it actually works.

[charlyd]

last weekend i finished my 16903A project it is working with the gigabyte GA-EQ45M-S2 board /3.3Ghz i installed Windows XP and i got everything working on software version 5.60.
All credits go to ingowien for doing lots of different OS research on these units.

It would be nice if someone would put some effort in try to get version 5.90 hacked and bypass the frame ID, so it would work on not agilent boards. Then we have the latest version for these unit on the market working ;-)

Win7 embedded is also something i still want to try, but i think i will end up with the current XP version on this fast Board.
here is a picture from the current mobo intalled and working like a charm.

[tim292stro]

For clarity, the theory is that 16903A runs with "any" micro-ATX motherboard with PCI up to version 5.80?

[ingowien]

I've not found restrictions, yet. But I've only tested three or four motherboards. So it would be an optimistic theory.
- I've not seen problems with more modern CPUs. C2D, Ci3-3000 Ci5-4000 worked. At least C2D was officially provided by Agilent.
- I've not seen problems with Hyper-Threading or Multi-Cores.
- I only tested 32bit W2k, XP and Win7. Not sure about x64.
- It might be required to have a PCI slot in the right position (not necessarily for the 16903 but for the 16900 and 16902).
- The CPU heatsink has to be small enough to fit under the card cage.
As I learned from the post from gslick, the BIOS locking might have been introduced for the 16800 series to restrict usage of cards there.

[tim292stro]

Interesting.

I did see in the release notes that 5.9 seems to want a 64-bit OS due to wanting >4GB of RAM, and definitely anything after 6.0 requires a 64-bit OS in the notes.

I picked up a DOA 16903A from eplace for $100, and I want to see about resurrecting it.  I suspect a PSU as it's totally dead and I found a reseller on that same site liquidating service stock for $50/each+shipping - if it doesn't work when I'm done then I'm only out the equivalent of three tanks of gas in California.  I have the ability to dump a BIOS ROM and take a peek at what's in there - while I have it apart I'll do that, bearing in mind that without proof 5.9 works on this motherboard there are no guarantees.

I'd consider doing something a bit more "modern" than the older 755 socket motherboards if CPU and chipset is not a gating factor - something like an IMB-C2060 which supports an E3 Xeon and ECC-REG memory - but still has the PCI slot for the front-end (not sure if it needs to be slot 3 or 4 which is PCI).

First step will be to see if I can get it to run with as much of the existing hardware as possible, but then I'll see about swapping out for something newer/more-performant - and then maybe see if I can do some Linux/WINE...  Also of potential interest, I found that there is a 12.3" touchscreen on the market for about $150 USD with decent resolution which can be de-packaged and tucked inside - I just need to dig into how deeply tied into the front-end the touch screen is (I don't mind abandoning existing hardware in place as long as it doesn't cripple the unit).

[ingowien]

v5.90 definitely runs on x32. The release notes say: "Version 5.90 of the Agilent Logic and Protocol Analyzer software is a 32-bit application and therefore it is supported for use with 32-bit as well as 64-bit operating systems."
So the client software definitely runs on x32 and x64 Windows. The setup contains both x32 and x64 drivers for ag16900Rio and ag16900Svy so yes, maybe it would run on x64, too. As I don't have need for more than 4GB RAM, I have not tested that. But I don't think there would be a VGA driver for the internal VGA, so definitely the requirement to change the internal VGA card and/or display. Which would be too much effort for me for no real benefit.
More than 4GB are required for M950xA but not for 1690x.
I think v6.xx only supports the 168xx and the U4xxxx analyzers but not the 16900 series. At least the current version v6.60 does.

[gslick]

v5.90 definitely runs on x32. The release notes say: "Version 5.90 of the Agilent Logic and Protocol Analyzer software is a 32-bit application and therefore it is supported for use with 32-bit as well as 64-bit operating systems."
So the client software definitely runs on x32 and x64 Windows. The setup contains both x32 and x64 drivers for ag16900Rio and ag16900Svy so yes, maybe it would run on x64, too. As I don't have need for more than 4GB RAM, I have not tested that. But I don't think there would be a VGA driver for the internal VGA, so definitely the requirement to change the internal VGA card and/or display. Which would be too much effort for me for no real benefit.

The standard OS installation for the final versions of the 16901A, 16902B, and the 16801A, 16802A, 16803A, 1680A4, 16806A, 16821A, 16822A, 16823A models with the Adlink M-890 motherboard is 64-bit Windows Embedded Standard 7, running version 5.x of the logic analyzer application, up through Version 5.90.1110. Those models with the Adlink M-890 motherboard use the built-in Q45 chipset graphics controller and LVDS interface on the motherboard to drive the LCD, and the motherboard is maxed out at 4GB of RAM.

As you have noted trying to run a 64-bit version of Windows on a 16902A or 16903A with an updated motherboard would be a challenge because as far as I know there is no 64-bit version of a display driver available anywhere for the Chips 65550 video controller used to drive the LCD in those models. On a 16900A with no built-in LCD at least the display driver issue would be removed.

[tim292stro]

In the case of replacing the motherboard, I'd also be talking about moving to a 1600x1200 LCD over HDMI - abandoning the factory LCD and touch screen hardware.

That should resolve that issue, unless the factory LCD is required for the LA functions to operate.

[ingowien]

I just discovered: Any mainboard should be OK as long as the xilinx boot files in the hardware already match the software you're installing.
The binaries are contained in your application directory, e.g. agM3*.xsvf for 3-slot machines (16903) and agM6*.xsvf for 3-slot machines (16900 and 16902). However the software might refuse to flash them.
If a correct mainboard is detected, the boot ROM update utility will re-flash the boot files if required. Otherwise it will not touch the hardware and the service will probably not be able to access the hardware. Indicated by a message concerning the system BIOS during/after software installation.
The mainboard checks are very strict, even a VP22 mainboard might not be sufficient if it is unbranded or from a different device. As far as I found, the firmware update will only be started on a VP22 if the IDs "AGILENT TECHNOLOGIES" and "16900A/902A Logic Analysis System" are contained in the BIOS. However I don't know which exact IDs are used (chassis/system/OEM manufacturer and product ID). One could reverse engineer agProgBootRom.exe, there are some Registry keys used in parallel to auto detection (e.g. FrameModelNumber, FrameModelNumberOverride).
So in any case I would keep the original mainboard, it might be required for upgrades or failure recovery.
The program utility is launched after login (in HKLM/SW/Microsoft/Windows/CurrentVersion/Run) with
"C:\Program Files\Agilent Technologies\Logic Analyzer\agProgBootRom.exe" -pi -p "C:\Program Files\Agilent Technologies\Logic Analyzer"
This command can be used to check BIOS detection and firmware versions without the need to uninstall and re-install.

The factory LCD is not required for the LA. The 16900 doesn't have one and the service manual indicates that the 65552 VGA on the PCI card is automatically deactivated if no LCD is attached.

[ingowien]

Has anybody tried to change the mainboard of a 16902A? I'm trying to repair and upgrade an old machine that came with an I/O board with traces having been ripped off but I think I got it working.
- The machine works with the VP22 from a 16900A under XP with v3.83, v4.40 or v5.40. With or without the front panel attached.
- With a changed mainboard the machine works if the LCD/front panel is plugged off.
- If the front panel is connected, agLogicSvc.exe does not initialize, instead it hangs at the yellow icon with state "Logic Analyzer is Initializing".
  This is the same behaviour with different XP and Win7e images that run on my 16903A. Both with v4.40 and v5.40.
I tested various combinations and P5G41T and P5GC-MX boards. Internal VGA enabled and disabled. Tried to re-flash the FPGAs with the VP22 mainboard. But the behavior is always the same. I even swapped the front panels, both work on the 16903A an do not work on the 16902A.
Software uninstalled and re-installed several times. With Ag16900Standalone=1 I do not get the "NO VALID ID DETECTED IN FRAME" error. Just no progress in the instrument initialization. I even transferred the Windows setup from the 16903A to the 16902A. Same mainboard P5G41T. Works on 16903A, does not initialize on the 16902A. The service doesn't seem to lock up, it can be stopped and re-started without issues. It just seems to wait for some action that does not happen.
Seems to be similar to this problem that does not have a solution: https://community.keysight.com/thread/23267
I think I'll simply disconnect the front panel as the machine is unusable with the old P3 and thus convert the 16902A to a 16900A. But I'm curious if there is a simple fix. Or what the exact difference between the 16902A and the 16903A front panel interfacing are.
Any suggestions?

[charlyd]

hi ingowien, any news yet on the get version 5.90 hacked and bypass the frame ID, so it would work on not agilent boards? not that it is a must but it would be nice.

[ingowien]

I think there's no need to hack it, v5.90 seems to run on the 16900A and 16902A. I tried v5.90 in a last attempt and this fixed the issue of not initializing. It's just the 16903A that requires v5.40 if I remember correctly. Always assuming the correct FPGA binaries have already been flashed.
If not, you can try some overrides:
[HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo]
"AgFrameOverrideKey1"=dword:483c4aa9
"AgFrameOverrideKey2"=dword:3900384e
"AgFrameOverrideKey3"=dword:5af7983e
"AgFrameOverrideKey4"=dword:82100f65
"AgFrameModelNumberOverride"="16900"

[juan_ee]

Hello Everyone,  I just purchased a 16902B today with a few 16755A modules.  It came with Windows XP, version 3.83.0001 of Agilent Software and the M-880-Nitro motherboard.

I have been following this thread and it seem the 16902B is upgrade-able to Windows 7 32 bit using the existing M-880-Nitro motherboard.  Do I simply upgrade the Windows XP to Windows 7 and apply the newer version of Agilent software 5.90?  What are the best path for doing so?  (I have extra hard drives laying around to experiment).

Thanks 

[ingowien]

I'm not the expert, just playing around with my machines (and none of them was a B model), but basically this should be the way to go.
- You might want to check if there are additional licenses installed on your machine. However I don't know if or how they can be ported to a new setup.
- The LA Software setup contains almost everything except for display and touch drivers, DotNet (just the online installer) and some registry settings that are already contained in the original Agilent OS Image. Included are new FPGA binaries that are automatically flashed.
- If you then change back to XP with the old version, FPGA binaries won't match. However they are automatically downgraded (old versions are re-flashed) if you uninstall the old LA software and re-install it.
- I'd create a good backup (HDD image) of the old HDD or better use a new hard drive or SSD for experiments.
- As far as I know the 16902B doesn't use that very old 65552 VGA on the PCI card but uses an LVDS display attached to the mainboard, so the VGA setup should be easier to install. Maybe you'll need to find a suitable VGA driver. I don't know what touch controller is used in that machine. And drivers for all the other devices Win7 won't recognize except for the acquisition devices. For first tests this shouldn't matter but the touch on/off button or the internal display might refer to work as long as there are issues. I'd attach an external monitor in every case to see what's happening on both display outputs.

So I assume the install process would be
- Check all the drivers and devices that are installed in XP and document them.
- Export the settings from HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo to re-create them in Win7
- Install Windows
- Install all drivers except for the acquisition board.
- Install the Windows updates
- Not sure if you should install some registry parameters (maybe Ag16900Standalone) or simply import the XP backup from HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo.
- Install the required .Net version (unless you have the machine connected to the internet for the online installer).
- Install the LA software
 That's my usual approach for a clean setup.

In your special case it might be possible to try a Windows XP to Windows 7 upgrade install. This might preserve the license server and other settings. However I have never tried this.
best regards
Ingo

[juan_ee]

Hello ingowien,
Thank you for your reply.  I am doing the attempted upgrade today and tomorrow and will post my results here.  I will be using another hard drive to do this experiment, so I don't screw up the working WIN XP setup.  I don't think I have any additional add-on licenses, not sure where to check.

Anyone know what processor upgrades are available for the M-880-Nitro motherboard?  It seems it has an Intel Celeron D 3.2 GHz Microprocessor (Single Core).

Thanks.

[gslick]

Hello ingowien,
Thank you for your reply.  I am doing the attempted upgrade today and tomorrow and will post my results here.  I will be using another hard drive to do this experiment, so I don't screw up the working WIN XP setup.  I don't think I have any additional add-on licenses, not sure were to check.

Anyone know what processor upgrades are available for the M-880-Nitro motherboard?  It seem I have an Intel Celeron D 3.2 GHz Microprocessor (Single Core).

Thanks.

A Windows XP recovery DVD is available for 16902B analyzers with the ADLINK M-880 motherboard, so if your current hard drive died or got corrupted you could reinstall the system from scratch on a replacement hard drive.

How much memory is currently installed on your ADLINK M-880 motherboard? There were two official upgrade paths to Windows 7. One replaced the ADLINK M-880 motherboard with an ADLINK M-890 motherboard, the less expensive upgrade installed a total of 4GB of RAM on the existing ADLINK M-880 motherboard. Both upgrades provided new hard drives with Windows 7 pre-installed, with a recovery partition on the hard drives but no other recovery media.

The ADLINK M-890 runs a 64-bit version of Windows Embedded Standard 7. I don't know if the ADLINK M-880 upgrade was also a 64-bit version.

[ingowien]

In "Keysight N2753A and N2754A ... Upgrade Kit", the M880 is listed with an E8400 dual core CPU. So I'd assume most LGA775 CPUs with FSB1333 would work. Probably you could go up to an E8600 or E8700. Those are cheap, so a test shouldn't be a problem.  But the E8400 is fast enough. Such a CPU, 4GB RAM and an SSD will definitely give enough power for the analyzer. Quad cores as a Q9400...Q9700 probably will work, too. But I'd stick for higher single thread performance and a 65W CPU. The stock 65W intel cooler fits into the machine, the 95W cooler might be too large.
Changing mainboards is critical on those machines as (1) M880 and M890 boards are essentially unobtainium and (2) Agilent used different BIOS versions for different models. I'm not sure for the M880 but I've seen VP22 boards with Agilent signature with and without "16900" in it.  And if the signature is incorrect, the software might refuse to flash the FPGA binaries. At least this was the case in an 16900 with a Agilent VP22 board that maybe came from another device. Or was incorrectly flashed by Agilent in the first place. And I didn't find a single location where those Agilent BIOS versions would be shared.

[gslick]

In "Keysight N2753A and N2754A ... Upgrade Kit", the M880 is listed with an E8400 dual core CPU.

The M890 motherboard has the E8400 Core™2 Duo CPU, not the M880. I have 16901A and 16902B with M890 motherboards with E8400 CPUs. I don't have any with M880 motherboards to check the details of the chipsets on those.


Keysight N2753A and N2754A Windows XP to Windows 7 Upgrade Kits
For Infiniium 9000, 90000, and 90000 X-Series Oscilloscopes
https://www.keysight.com/us/en/assets/7018-03056/configuration-guides/5990-8569.pdf

If it says “Schooner CPU,” it’s an M890 and the motherboard will support the Windows 7 upgrade.
Keysight Technologies Schooner CPU 1.0.12611.3 Intel CoreTM Duo CPU E8400 @ 3.00 GHz

[ingowien]

You're right. E8400 is specified for the M890. I completely overlooked this, sorry.

I can't find useful information on the M880. The Celeron D is based on the later P4 with Socket 775. I find different models with 3.2GHz:
Prescott without IA64: 350: 3,20 GHz – 73W, FSB533 (4x133MHz)
Prescott with IA64: 351: 3,20 GHz – 84W, FSB533 (4x133MHz)
Cedar Mill: 352: 3,20 GHz – 86W, FSB533 (4x133MHz)
If the board uses an old 845 chipset, you might be stuck with a P4 or P4+HT with FSB533 and these are limited. I once had this problem with a PEB-7702 mainboard. The PEB-7702 at least supported HT CPUs which might not be the case for the M880. Some later 865 chipset revisions may support FSB800.
P4+HT with FSB533 are:
  P4 HT 3.06GHz/512/533 SL6xx 82W Northwood 133Mx23  (SL6K7, SL6JJ, SL6S5, SL6SM, SL6PG, SL6QC)
  P4 HT 517 2.93GHz/1M/533  84W Prescott 133Mx22 FSB533   (SL8ZY, SL9CD)
  P4 HT 524 3.06GHz/1M/533  84W Prescott 133Mx23 FSB533   (SL8ZZ, SL9CA)
I'm using an SL6S5 in an old vector network analyzer requiring an ISA slot (thus the PEB-7702) and it's more than adequate for Windows 7 and the NWA software.

@juan_ee: It would be nice if you could run CPU-z or a similar tool on your current XP, so we could get some more information on the M880 board.

[gslick]

@juan_ee: It would be nice if you could run CPU-z or a similar tool on your current XP, so we could get some more information on the M880 board.

If someone could run the attached command line utility in a command prompt window on an Agilent logic analyzer with the M880 motherboard and save the output in a file to paste here that would be interesting to look at. It dumps the device tree as enumerated by the Windows Configuration Manager.

example: "walk.exe > walk.txt" in a command prompt window, then attach the walk.txt output file to a reply or paste its contents into a reply.

[juan_ee]

Hello everyone,

I am still running updates on the Windows 7 32 bit SP1 installation... a slow and painful process.

Yes ingowien, I did start looking up stuff on the Celeron D I have, but not sure weather the motherboard will work the the P4+HT or forward with Core 2 Duo... but then I got busy with other stuff.

Someone asked how much ram I have... the original configuration is:

16902B with 3 16755A modules installed.
Windows XP, SP2, 2 GBytes Ram, 80 GBytes Hard Drive, version 3.83.0001 of Agilent Software and M-880-Nitro motherboard.

So, I did take your suggestion and ran the CPU-z, although under windows 7 since I am doing updates.

[juan_ee]

Hello gslick, Concerning the walk command... do you want me to run it under the original Windows XP installation or Windows 7?  I have never used the walk command.  Let us know...

Juan 

[gslick]

Hello gslick, Concerning the walk command... do you want me to run it under the original Windows XP installation or Windows 7?  I have never used the walk command.  Let us know...

Juan

It would be more interesting to run it on the original Windows XP installation as it outputs information about the driver loaded for each device. On Windows 7 it might take a while to get all of the drivers loaded properly.

You wouldn't have ever run that "walk" command in the attached .zip file in the previous Reply #71 as it is just a simple utility I wrote for my own use years ago.

The output looks like that shown in Reply #26 on Page 2 of this thread.

[juan_ee]

Oh, no wonder I don't know what the walk command is... it it YOURS .  I saw the walk.zip attached, but I didn't download it before, I thought it was an example of the output.

OK, I put the original hard drive back with Windows XP.  Here is the output of the walk:

Code: [Select]

+ DeviceID:
| HTREE\ROOT\0
| + DeviceID:
| | ROOT\*UPDDPNP\0000
| | HardwareIDs:
| | ->*UPDDPNP
| | Device Description:
| | ->Universal Pointer Device Driver
| | Driver:
| | ->{4D36E96F-E325-11CE-BFC1-08002BE10318}\0002
| | Service:
| | ->tbupdd
| | Capabilities: SURPRISEREMOVALOK
| + DeviceID:
| | ROOT\ACPI_HAL\0000
| | HardwareIDs:
| | ->acpiapic_up
| | CompatibleIDs:
| | ->DETECTEDInternal\ACPI_HAL
| | ->DETECTED\ACPI_HAL
| | Device Description:
| | ->ACPI Uniprocessor PC
| | Driver:
| | ->{4D36E966-E325-11CE-BFC1-08002BE10318}\0000
| | Service:
| | ->\Driver\ACPI_HAL
| | + DeviceID:
| | | ACPI_HAL\PNP0C08\0
| | | HardwareIDs:
| | | ->ACPI_HAL\PNP0C08
| | | ->*PNP0C08
| | | Device Description:
| | | ->Microsoft ACPI-Compliant System
| | | Driver:
| | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0005
| | | Service:
| | | ->ACPI
| | | Capabilities: UNIQUEID SILENTINSTALL
| | | + DeviceID:
| | | | ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_6\_0
| | | | HardwareIDs:
| | | | ->ACPI\GenuineIntel_-_x86_Family_15_Model_6
| | | | ->*GenuineIntel_-_x86_Family_15_Model_6
| | | | ->ACPI\GenuineIntel_-_x86_Family_15
| | | | ->*GenuineIntel_-_x86_Family_15
| | | | ->ACPI\GenuineIntel_-_x86
| | | | ->*GenuineIntel_-_x86
| | | | CompatibleIDs:
| | | | ->ACPI\Processor
| | | | Device Description:
| | | | ->Intel Processor
| | | | Friendly Name:
| | | | ->Intel(R) Celeron(R) D CPU 3.20GHz
| | | | Driver:
| | | | ->{50127DC3-0F36-415E-A6CC-4CB3BE910B65}\0001
| | | | Service:
| | | | ->intelppm
| | | | Capabilities: UNIQUEID SILENTINSTALL
| | | + DeviceID:
| | | | ACPI\PNP0C0C\2&DABA3FF&0
| | | | HardwareIDs:
| | | | ->ACPI\PNP0C0C
| | | | ->*PNP0C0C
| | | | Device Description:
| | | | ->ACPI Power Button
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0011
| | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| | | + DeviceID:
| | | | ACPI\PNP0A08\1
| | | | HardwareIDs:
| | | | ->ACPI\PNP0A08
| | | | ->*PNP0A08
| | | | CompatibleIDs:
| | | | ->*PNP0A03
| | | | Device Description:
| | | | ->PCI bus
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0008
| | | | Service:
| | | | ->pci
| | | | Capabilities: UNIQUEID SILENTINSTALL
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02\3&2411E6FE&0&00
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02
| | | | | ->PCI\VEN_8086&DEV_2770&SUBSYS_00000000
| | | | | ->PCI\VEN_8086&DEV_2770&REV_02
| | | | | ->PCI\VEN_8086&DEV_2770
| | | | | ->PCI\VEN_8086&DEV_2770&CC_060000
| | | | | ->PCI\VEN_8086&DEV_2770&CC_0600
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&CC_060000
| | | | | ->PCI\VEN_8086&CC_0600
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060000
| | | | | ->PCI\CC_0600
| | | | | Location Information
| | | | | ->PCI bus 0, device 0, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 945G/GZ/P/PL Processor to I/O Controller - 2770
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0015
| | | | | Capabilities: RAWDEVICEOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2772&SUBSYS_27728086&REV_02\3&2411E6FE&0&10
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2772&SUBSYS_27728086&REV_02
| | | | | ->PCI\VEN_8086&DEV_2772&SUBSYS_27728086
| | | | | ->PCI\VEN_8086&DEV_2772&CC_030000
| | | | | ->PCI\VEN_8086&DEV_2772&CC_0300
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_2772&REV_02
| | | | | ->PCI\VEN_8086&DEV_2772
| | | | | ->PCI\VEN_8086&CC_030000
| | | | | ->PCI\VEN_8086&CC_0300
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_030000
| | | | | ->PCI\CC_0300
| | | | | Location Information
| | | | | ->PCI bus 0, device 2, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 82945G Express Chipset Family
| | | | | Driver:
| | | | | ->{4D36E968-E325-11CE-BFC1-08002BE10318}\0000
| | | | | Service:
| | | | | ->ialm
| | | | | + DeviceID:
| | | | | | DISPLAY\MIT20D3\4&2DEA7F16&0&80861500&00&02
| | | | | | HardwareIDs:
| | | | | | ->Monitor\MIT20D3
| | | | | | CompatibleIDs:
| | | | | | ->*PNP09FF
| | | | | | Device Description:
| | | | | | ->Plug and Play Monitor
| | | | | | Driver:
| | | | | | ->{4D36E96E-E325-11CE-BFC1-08002BE10318}\0004
| | | | | | Capabilities: EJECTSUPPORTED REMOVABLE SILENTINSTALL RAWDEVICEOK SURPRISEREMOVALOK
| | | | | + DeviceID:
| | | | | | DISPLAY\MIT20D3\4&2DEA7F16&0&80861400&00&02
| | | | | | HardwareIDs:
| | | | | | ->Monitor\MIT20D3
| | | | | | CompatibleIDs:
| | | | | | ->*PNP09FF
| | | | | | Device Description:
| | | | | | ->Plug and Play Monitor
| | | | | | Driver:
| | | | | | ->{4D36E96E-E325-11CE-BFC1-08002BE10318}\0001
| | | | | | Capabilities: EJECTSUPPORTED REMOVABLE SILENTINSTALL RAWDEVICEOK SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_2776&SUBSYS_27728086&REV_02\3&2411E6FE&0&11
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_2776&SUBSYS_27728086&REV_02
| | | | | ->PCI\VEN_8086&DEV_2776&SUBSYS_27728086
| | | | | ->PCI\VEN_8086&DEV_2776&CC_038000
| | | | | ->PCI\VEN_8086&DEV_2776&CC_0380
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_2776&REV_02
| | | | | ->PCI\VEN_8086&DEV_2776
| | | | | ->PCI\VEN_8086&CC_038000
| | | | | ->PCI\VEN_8086&CC_0380
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_038000
| | | | | ->PCI\CC_0380
| | | | | Location Information
| | | | | ->PCI bus 0, device 2, function 1
| | | | | Device Description:
| | | | | ->Intel(R) 82945G Express Chipset Family
| | | | | Driver:
| | | | | ->{4D36E968-E325-11CE-BFC1-08002BE10318}\0001
| | | | | Service:
| | | | | ->ialm
| | | | | + DeviceID:
| | | | | | DISPLAY\MIT20D3\4&1A255B0C&0&80871400&00&22
| | | | | | HardwareIDs:
| | | | | | ->Monitor\MIT20D3
| | | | | | CompatibleIDs:
| | | | | | ->*PNP09FF
| | | | | | Device Description:
| | | | | | ->Plug and Play Monitor
| | | | | | Driver:
| | | | | | ->{4D36E96E-E325-11CE-BFC1-08002BE10318}\0003
| | | | | | Capabilities: EJECTSUPPORTED REMOVABLE SILENTINSTALL RAWDEVICEOK SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27D8&SUBSYS_27D88086&REV_01\3&2411E6FE&0&D8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27D8&SUBSYS_27D88086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27D8&SUBSYS_27D88086
| | | | | ->PCI\VEN_8086&DEV_27D8&CC_040300
| | | | | ->PCI\VEN_8086&DEV_27D8&CC_0403
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27D8&REV_01
| | | | | ->PCI\VEN_8086&DEV_27D8
| | | | | ->PCI\VEN_8086&CC_040300
| | | | | ->PCI\VEN_8086&CC_0403
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_040300
| | | | | ->PCI\CC_0403
| | | | | Location Information
| | | | | ->PCI bus 0, device 27, function 0
| | | | | Device Description:
| | | | | ->Microsoft UAA Bus Driver for High Definition Audio
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0033
| | | | | Service:
| | | | | ->HDAudBus
| | | | | + DeviceID:
| | | | | | HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_144A0000&REV_1000\4&3108D61F&0&0001
| | | | | | HardwareIDs:
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_144A0000&REV_1000
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_144A0000
| | | | | | CompatibleIDs:
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&REV_1000
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC&DEV_0883
| | | | | | ->HDAUDIO\FUNC_01&VEN_10EC
| | | | | | ->HDAUDIO\FUNC_01
| | | | | | Location Information
| | | | | | ->Internal High Definition Audio Bus
| | | | | | Device Description:
| | | | | | ->Realtek High Definition Audio
| | | | | | Driver:
| | | | | | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0017
| | | | | | Service:
| | | | | | ->IntcAzAudAddService
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&2411E6FE&0&E0
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01
| | | | | ->PCI\VEN_8086&DEV_27D0&SUBSYS_00000000
| | | | | ->PCI\VEN_8086&DEV_27D0&REV_01
| | | | | ->PCI\VEN_8086&DEV_27D0
| | | | | ->PCI\VEN_8086&DEV_27D0&CC_060400
| | | | | ->PCI\VEN_8086&DEV_27D0&CC_0604
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&CC_060400
| | | | | ->PCI\VEN_8086&CC_0604
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060400
| | | | | ->PCI\CC_0604
| | | | | Location Information
| | | | | ->PCI bus 0, device 28, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0013
| | | | | Service:
| | | | | ->pci
| | | | | + DeviceID:
| | | | | | PCI\VEN_8086&DEV_108C&SUBSYS_00008086&REV_03\4&1B41B794&0&00E0
| | | | | | HardwareIDs:
| | | | | | ->PCI\VEN_8086&DEV_108C&SUBSYS_00008086&REV_03
| | | | | | ->PCI\VEN_8086&DEV_108C&SUBSYS_00008086
| | | | | | ->PCI\VEN_8086&DEV_108C&CC_020000
| | | | | | ->PCI\VEN_8086&DEV_108C&CC_0200
| | | | | | CompatibleIDs:
| | | | | | ->PCI\VEN_8086&DEV_108C&REV_03
| | | | | | ->PCI\VEN_8086&DEV_108C
| | | | | | ->PCI\VEN_8086&CC_020000
| | | | | | ->PCI\VEN_8086&CC_0200
| | | | | | ->PCI\VEN_8086
| | | | | | ->PCI\CC_020000
| | | | | | ->PCI\CC_0200
| | | | | | Location Information
| | | | | | ->PCI bus 1, device 0, function 0
| | | | | | Device Description:
| | | | | | ->Intel(R) PRO/1000 PM Network Connection
| | | | | | Driver:
| | | | | | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0008
| | | | | | Service:
| | | | | | ->e1express
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27C8&SUBSYS_27C88086&REV_01\3&2411E6FE&0&E8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27C8&SUBSYS_27C88086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C8&SUBSYS_27C88086
| | | | | ->PCI\VEN_8086&DEV_27C8&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_27C8&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27C8&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C8
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Location Information
| | | | | ->PCI bus 0, device 29, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
| | | | | Driver:
| | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0004
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&1C12D0FB&0
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID27C8&REV0001
| | | | | | ->USB\ROOT_HUB&VID8086&PID27C8
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Driver:
| | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0005
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | Capabilities: SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27C9&SUBSYS_27C98086&REV_01\3&2411E6FE&0&E9
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27C9&SUBSYS_27C98086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C9&SUBSYS_27C98086
| | | | | ->PCI\VEN_8086&DEV_27C9&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_27C9&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27C9&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C9
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Location Information
| | | | | ->PCI bus 0, device 29, function 1
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
| | | | | Driver:
| | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0003
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&E9A8164&0
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID27C9&REV0001
| | | | | | ->USB\ROOT_HUB&VID8086&PID27C9
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Driver:
| | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0007
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | Capabilities: SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27CA&SUBSYS_27CA8086&REV_01\3&2411E6FE&0&EA
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27CA&SUBSYS_27CA8086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CA&SUBSYS_27CA8086
| | | | | ->PCI\VEN_8086&DEV_27CA&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_27CA&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27CA&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CA
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Location Information
| | | | | ->PCI bus 0, device 29, function 2
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
| | | | | Driver:
| | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0002
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&218D314D&0
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID27CA&REV0001
| | | | | | ->USB\ROOT_HUB&VID8086&PID27CA
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Driver:
| | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0006
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | Capabilities: SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27CB&SUBSYS_27CA8086&REV_01\3&2411E6FE&0&EB
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27CB&SUBSYS_27CA8086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CB&SUBSYS_27CA8086
| | | | | ->PCI\VEN_8086&DEV_27CB&CC_0C0300
| | | | | ->PCI\VEN_8086&DEV_27CB&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27CB&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CB
| | | | | ->PCI\VEN_8086&CC_0C0300
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0300
| | | | | ->PCI\CC_0C03
| | | | | Location Information
| | | | | ->PCI bus 0, device 29, function 3
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
| | | | | Driver:
| | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0001
| | | | | Service:
| | | | | ->usbuhci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB\4&C1DE8DA&0
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB&VID8086&PID27CB&REV0001
| | | | | | ->USB\ROOT_HUB&VID8086&PID27CB
| | | | | | ->USB\ROOT_HUB
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Driver:
| | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0009
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | Capabilities: SURPRISEREMOVALOK
| | | | | | + DeviceID:
| | | | | | | USB\VID_07DD&PID_0001\5&16737FCB&0&1
| | | | | | | HardwareIDs:
| | | | | | | ->USB\Vid_07dd&Pid_0001&Rev_804=
| | | | | | | ->USB\Vid_07dd&Pid_0001
| | | | | | | CompatibleIDs:
| | | | | | | ->USB\Class_03&SubClass_01&Prot_02
| | | | | | | ->USB\Class_03&SubClass_01
| | | | | | | ->USB\Class_03
| | | | | | | Location Information
| | | | | | | ->TSHARC Octopus
| | | | | | | Device Description:
| | | | | | | ->USB HID Touch Screen Controller
| | | | | | | Driver:
| | | | | | | ->{745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000
| | | | | | | Service:
| | | | | | | ->HidUsb
| | | | | | | Capabilities: REMOVABLE SURPRISEREMOVALOK
| | | | | | | + DeviceID:
| | | | | | | | HID\VID_07DD&PID_0001\6&35C35BB8&1&0000
| | | | | | | | HardwareIDs:
| | | | | | | | ->HID\Vid_07dd&Pid_0001&Rev_804=
| | | | | | | | ->HID\Vid_07dd&Pid_0001
| | | | | | | | ->HID_DEVICE_SYSTEM_MOUSE
| | | | | | | | ->HID_DEVICE_UP:0001_U:0002
| | | | | | | | ->HID_DEVICE
| | | | | | | | CompatibleIDs:
| | | | | | | | Device Description:
| | | | | | | | ->USB Touch Screen Controller
| | | | | | | | Driver:
| | | | | | | | ->{4D36E96F-E325-11CE-BFC1-08002BE10318}\0004
| | | | | | | | Service:
| | | | | | | | ->mouhid
| | | | | | | | Capabilities: SILENTINSTALL SURPRISEREMOVALOK
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27CC&SUBSYS_27CC8086&REV_01\3&2411E6FE&0&EF
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27CC&SUBSYS_27CC8086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CC&SUBSYS_27CC8086
| | | | | ->PCI\VEN_8086&DEV_27CC&CC_0C0320
| | | | | ->PCI\VEN_8086&DEV_27CC&CC_0C03
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27CC&REV_01
| | | | | ->PCI\VEN_8086&DEV_27CC
| | | | | ->PCI\VEN_8086&CC_0C0320
| | | | | ->PCI\VEN_8086&CC_0C03
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0320
| | | | | ->PCI\CC_0C03
| | | | | Location Information
| | | | | ->PCI bus 0, device 29, function 7
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
| | | | | Driver:
| | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0000
| | | | | Service:
| | | | | ->usbehci
| | | | | + DeviceID:
| | | | | | USB\ROOT_HUB20\4&141F8988&0
| | | | | | HardwareIDs:
| | | | | | ->USB\ROOT_HUB20&VID8086&PID27CC&REV0001
| | | | | | ->USB\ROOT_HUB20&VID8086&PID27CC
| | | | | | ->USB\ROOT_HUB20
| | | | | | Device Description:
| | | | | | ->USB Root Hub
| | | | | | Driver:
| | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0008
| | | | | | Service:
| | | | | | ->usbhub
| | | | | | Capabilities: SURPRISEREMOVALOK
| | | | | | + DeviceID:
| | | | | | | USB\VID_058F&PID_6387\255875F4
| | | | | | | HardwareIDs:
| | | | | | | ->USB\Vid_058f&Pid_6387&Rev_0112
| | | | | | | ->USB\Vid_058f&Pid_6387
| | | | | | | CompatibleIDs:
| | | | | | | ->USB\Class_08&SubClass_06&Prot_50
| | | | | | | ->USB\Class_08&SubClass_06
| | | | | | | ->USB\Class_08
| | | | | | | Location Information
| | | | | | | ->Mass Storage
| | | | | | | Device Description:
| | | | | | | ->USB Mass Storage Device
| | | | | | | Driver:
| | | | | | | ->{36FC9E60-C465-11CF-8056-444553540000}\0025
| | | | | | | Service:
| | | | | | | ->USBSTOR
| | | | | | | Capabilities: REMOVABLE UNIQUEID
| | | | | | | + DeviceID:
| | | | | | | | USBSTOR\DISK&VEN_GENERIC&PROD_FLASH_DISK&REV_8.07\255875F4&0
| | | | | | | | HardwareIDs:
| | | | | | | | ->USBSTOR\DiskGeneric_Flash_Disk______8.07
| | | | | | | | ->USBSTOR\DiskGeneric_Flash_Disk______
| | | | | | | | ->USBSTOR\DiskGeneric_
| | | | | | | | ->USBSTOR\Generic_Flash_Disk______8
| | | | | | | | ->Generic_Flash_Disk______8
| | | | | | | | ->USBSTOR\GenDisk
| | | | | | | | ->GenDisk
| | | | | | | | CompatibleIDs:
| | | | | | | | ->USBSTOR\Disk
| | | | | | | | ->USBSTOR\RAW
| | | | | | | | Device Description:
| | | | | | | | ->Disk drive
| | | | | | | | Friendly Name:
| | | | | | | | ->Generic Flash Disk USB Device
| | | | | | | | Driver:
| | | | | | | | ->{4D36E967-E325-11CE-BFC1-08002BE10318}\0012
| | | | | | | | Service:
| | | | | | | | ->disk
| | | | | | | | Capabilities: UNIQUEID
| | | | | | | | + DeviceID:
| | | | | | | | | STORAGE\REMOVABLEMEDIA\7&1F313D74&0&RM
| | | | | | | | | HardwareIDs:
| | | | | | | | | ->STORAGE\Volume
| | | | | | | | | CompatibleIDs:
| | | | | | | | | ->STORAGE\Volume
| | | | | | | | | Device Description:
| | | | | | | | | ->Generic volume
| | | | | | | | | Driver:
| | | | | | | | | ->{71A27CDD-812A-11D0-BEC7-08002BE2092F}\0011
| | | | | | | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| | | | | | | | | Drive Name D:
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1\3&2411E6FE&0&F0
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1
| | | | | ->PCI\VEN_8086&DEV_244E&SUBSYS_00000000
| | | | | ->PCI\VEN_8086&DEV_244E&REV_E1
| | | | | ->PCI\VEN_8086&DEV_244E
| | | | | ->PCI\VEN_8086&DEV_244E&CC_060401
| | | | | ->PCI\VEN_8086&DEV_244E&CC_0604
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&CC_060401
| | | | | ->PCI\VEN_8086&CC_0604
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060401
| | | | | ->PCI\CC_0604
| | | | | Location Information
| | | | | ->PCI bus 0, device 30, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 82801 PCI Bridge - 244E
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0016
| | | | | Service:
| | | | | ->pci
| | | | | + DeviceID:
| | | | | | PCI\VEN_104C&DEV_AC28&SUBSYS_00000000&REV_00\4&1AF1648C&0&28F0
| | | | | | HardwareIDs:
| | | | | | ->PCI\VEN_104C&DEV_AC28&SUBSYS_00000000&REV_00
| | | | | | ->PCI\VEN_104C&DEV_AC28&SUBSYS_00000000
| | | | | | ->PCI\VEN_104C&DEV_AC28&REV_00
| | | | | | ->PCI\VEN_104C&DEV_AC28
| | | | | | ->PCI\VEN_104C&DEV_AC28&CC_060400
| | | | | | ->PCI\VEN_104C&DEV_AC28&CC_0604
| | | | | | CompatibleIDs:
| | | | | | ->PCI\VEN_104C&CC_060400
| | | | | | ->PCI\VEN_104C&CC_0604
| | | | | | ->PCI\VEN_104C
| | | | | | ->PCI\CC_060400
| | | | | | ->PCI\CC_0604
| | | | | | Location Information
| | | | | | ->PCI bus 2, device 5, function 0
| | | | | | Device Description:
| | | | | | ->PCI standard PCI-to-PCI bridge
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0018
| | | | | | Service:
| | | | | | ->pci
| | | | | | + DeviceID:
| | | | | | | PCI\VEN_15BC&DEV_0505&SUBSYS_00000000&REV_00\5&34680ACF&0&0028F0
| | | | | | | HardwareIDs:
| | | | | | | ->PCI\VEN_15BC&DEV_0505&SUBSYS_00000000&REV_00
| | | | | | | ->PCI\VEN_15BC&DEV_0505&SUBSYS_00000000
| | | | | | | ->PCI\VEN_15BC&DEV_0505&REV_00
| | | | | | | ->PCI\VEN_15BC&DEV_0505
| | | | | | | ->PCI\VEN_15BC&DEV_0505&CC_0B4000
| | | | | | | ->PCI\VEN_15BC&DEV_0505&CC_0B40
| | | | | | | CompatibleIDs:
| | | | | | | ->PCI\VEN_15BC&CC_0B4000
| | | | | | | ->PCI\VEN_15BC&CC_0B40
| | | | | | | ->PCI\VEN_15BC
| | | | | | | ->PCI\CC_0B4000
| | | | | | | ->PCI\CC_0B40
| | | | | | | Location Information
| | | | | | | ->PCI bus 3, device 0, function 0
| | | | | | | Device Description:
| | | | | | | ->Agilent Technologies 16800/16900 Series Analyzer (PCI-to-SVY)
| | | | | | | Driver:
| | | | | | | ->{FA7119E6-CA6F-11D2-9B59-0060B0ECAA14}\0000
| | | | | | | Service:
| | | | | | | ->ag16900Svy
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&2411E6FE&0&F8
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01
| | | | | ->PCI\VEN_8086&DEV_27B8&SUBSYS_00000000
| | | | | ->PCI\VEN_8086&DEV_27B8&REV_01
| | | | | ->PCI\VEN_8086&DEV_27B8
| | | | | ->PCI\VEN_8086&DEV_27B8&CC_060100
| | | | | ->PCI\VEN_8086&DEV_27B8&CC_0601
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&CC_060100
| | | | | ->PCI\VEN_8086&CC_0601
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_060100
| | | | | ->PCI\CC_0601
| | | | | Location Information
| | | | | ->PCI bus 0, device 31, function 0
| | | | | Device Description:
| | | | | ->Intel(R) 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0014
| | | | | Service:
| | | | | ->isapnp
| | | | | + DeviceID:
| | | | | | ISAPNP\READDATAPORT\0
| | | | | | HardwareIDs:
| | | | | | ->ISAPNP\ReadDataPort
| | | | | | CompatibleIDs:
| | | | | | Device Description:
| | | | | | ->ISAPNP Read Data Port
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0019
| | | | | | Capabilities: UNIQUEID SILENTINSTALL RAWDEVICEOK
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C02\1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C02
| | | | | | ->*PNP0C02
| | | | | | Device Description:
| | | | | | ->Motherboard resources
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0024
| | | | | | Capabilities: UNIQUEID SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0000\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0000
| | | | | | ->*PNP0000
| | | | | | Device Description:
| | | | | | ->Programmable interrupt controller
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0021
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0200\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0200
| | | | | | ->*PNP0200
| | | | | | Device Description:
| | | | | | ->Direct memory access controller
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0027
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0100\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0100
| | | | | | ->*PNP0100
| | | | | | Device Description:
| | | | | | ->System timer
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0023
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0B00\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0B00
| | | | | | ->*PNP0B00
| | | | | | Device Description:
| | | | | | ->System CMOS/real time clock
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0025
| | | | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| | | | | + DeviceID:
| | | | | | ACPI\PNP0800\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0800
| | | | | | ->*PNP0800
| | | | | | Device Description:
| | | | | | ->System speaker
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0026
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C04\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C04
| | | | | | ->*PNP0C04
| | | | | | Device Description:
| | | | | | ->Numeric data processor
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0022
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0501\1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0501
| | | | | | ->*PNP0501
| | | | | | Device Description:
| | | | | | ->Communications Port
| | | | | | Friendly Name:
| | | | | | ->Communications Port (COM1)
| | | | | | Driver:
| | | | | | ->{4D36E978-E325-11CE-BFC1-08002BE10318}\0001
| | | | | | Service:
| | | | | | ->Serial
| | | | | | Capabilities: UNIQUEID SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0401\1
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0401
| | | | | | ->*PNP0401
| | | | | | Device Description:
| | | | | | ->ECP Printer Port
| | | | | | Friendly Name:
| | | | | | ->ECP Printer Port (LPT1)
| | | | | | Driver:
| | | | | | ->{4D36E978-E325-11CE-BFC1-08002BE10318}\0002
| | | | | | Service:
| | | | | | ->Parport
| | | | | | Capabilities: UNIQUEID SILENTINSTALL
| | | | | | + DeviceID:
| | | | | | | LPTENUM\MICROSOFTRAWPORT\5&35FB2AD7&0&LPT1
| | | | | | | HardwareIDs:
| | | | | | | ->LPTENUM\MicrosoftRawPort958A
| | | | | | | ->MicrosoftRawPort958A
| | | | | | | Location Information
| | | | | | | ->LPT1
| | | | | | | Device Description:
| | | | | | | ->Printer Port Logical Interface
| | | | | | | Driver:
| | | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0028
| | | | | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| | | | | + DeviceID:
| | | | | | ACPI\PNP0F13\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0F13
| | | | | | ->*PNP0F13
| | | | | | Device Description:
| | | | | | ->PS/2 Compatible Mouse
| | | | | | Driver:
| | | | | | ->{4D36E96F-E325-11CE-BFC1-08002BE10318}\0000
| | | | | | Service:
| | | | | | ->i8042prt
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0303\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0303
| | | | | | ->*PNP0303
| | | | | | CompatibleIDs:
| | | | | | ->*PNP030B
| | | | | | Device Description:
| | | | | | ->Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| | | | | | Driver:
| | | | | | ->{4D36E96B-E325-11CE-BFC1-08002BE10318}\0000
| | | | | | Service:
| | | | | | ->i8042prt
| | | | | | Capabilities: SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\PNP0C02\2
| | | | | | HardwareIDs:
| | | | | | ->ACPI\PNP0C02
| | | | | | ->*PNP0C02
| | | | | | Device Description:
| | | | | | ->Motherboard resources
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0017
| | | | | | Capabilities: UNIQUEID SILENTINSTALL
| | | | | + DeviceID:
| | | | | | ACPI\INT0800\4&1E5E1293&0
| | | | | | HardwareIDs:
| | | | | | ->ACPI\INT0800
| | | | | | ->*INT0800
| | | | | | Device Description:
| | | | | | ->Intel(R) 82802 Firmware Hub Device
| | | | | | Driver:
| | | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0020
| | | | | | Capabilities: SILENTINSTALL
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27DF&SUBSYS_27DF8086&REV_01\3&2411E6FE&0&F9
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27DF&SUBSYS_27DF8086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27DF&SUBSYS_27DF8086
| | | | | ->PCI\VEN_8086&DEV_27DF&CC_01018A
| | | | | ->PCI\VEN_8086&DEV_27DF&CC_0101
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27DF&REV_01
| | | | | ->PCI\VEN_8086&DEV_27DF
| | | | | ->PCI\VEN_8086&CC_01018A
| | | | | ->PCI\VEN_8086&CC_0101
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_01018A
| | | | | ->PCI\CC_0101
| | | | | Location Information
| | | | | ->PCI bus 0, device 31, function 1
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
| | | | | Driver:
| | | | | ->{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000
| | | | | Service:
| | | | | ->pciide
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&24EE2440&0&0
| | | | | | HardwareIDs:
| | | | | | ->Intel-27df
| | | | | | ->Primary_IDE_Channel
| | | | | | ->*PNP0600
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Location Information
| | | | | | ->Primary Channel
| | | | | | Device Description:
| | | | | | ->Primary IDE Channel
| | | | | | Driver:
| | | | | | ->{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002
| | | | | | Service:
| | | | | | ->atapi
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27C0&SUBSYS_27C08086&REV_01\3&2411E6FE&0&FA
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27C0&SUBSYS_27C08086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C0&SUBSYS_27C08086
| | | | | ->PCI\VEN_8086&DEV_27C0&CC_01018F
| | | | | ->PCI\VEN_8086&DEV_27C0&CC_0101
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27C0&REV_01
| | | | | ->PCI\VEN_8086&DEV_27C0
| | | | | ->PCI\VEN_8086&CC_01018F
| | | | | ->PCI\VEN_8086&CC_0101
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_01018F
| | | | | ->PCI\CC_0101
| | | | | Location Information
| | | | | ->PCI bus 0, device 31, function 2
| | | | | Device Description:
| | | | | ->Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
| | | | | Driver:
| | | | | ->{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001
| | | | | Service:
| | | | | ->pciide
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&2FBB2B14&0&0
| | | | | | HardwareIDs:
| | | | | | ->Intel-27c0
| | | | | | ->Primary_IDE_Channel
| | | | | | ->*PNP0600
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Location Information
| | | | | | ->Primary Channel
| | | | | | Device Description:
| | | | | | ->Primary IDE Channel
| | | | | | Driver:
| | | | | | ->{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004
| | | | | | Service:
| | | | | | ->atapi
| | | | | | + DeviceID:
| | | | | | | IDE\DISKHITACHI_HDS721680PLA380_________________P21OABEA\5&30D7022D&0&0.0.0
| | | | | | | HardwareIDs:
| | | | | | | ->IDE\DiskHitachi_HDS721680PLA380_________________P21OABEA
| | | | | | | ->IDE\Hitachi_HDS721680PLA380_________________P21OABEA
| | | | | | | ->IDE\DiskHitachi_HDS721680PLA380_________________
| | | | | | | ->Hitachi_HDS721680PLA380_________________P21OABEA
| | | | | | | ->GenDisk
| | | | | | | CompatibleIDs:
| | | | | | | ->GenDisk
| | | | | | | Location Information
| | | | | | | ->0
| | | | | | | Device Description:
| | | | | | | ->Disk drive
| | | | | | | Friendly Name:
| | | | | | | ->Hitachi HDS721680PLA380
| | | | | | | Driver:
| | | | | | | ->{4D36E967-E325-11CE-BFC1-08002BE10318}\0007
| | | | | | | Service:
| | | | | | | ->disk
| | | | | | | Drive Name C:
| | | | | + DeviceID:
| | | | | | PCIIDE\IDECHANNEL\4&2FBB2B14&0&1
| | | | | | HardwareIDs:
| | | | | | ->Intel-27c0
| | | | | | ->Secondary_IDE_Channel
| | | | | | ->*PNP0600
| | | | | | CompatibleIDs:
| | | | | | ->*PNP0600
| | | | | | Location Information
| | | | | | ->Secondary Channel
| | | | | | Device Description:
| | | | | | ->Secondary IDE Channel
| | | | | | Driver:
| | | | | | ->{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005
| | | | | | Service:
| | | | | | ->atapi
| | | | + DeviceID:
| | | | | PCI\VEN_8086&DEV_27DA&SUBSYS_27DA8086&REV_01\3&2411E6FE&0&FB
| | | | | HardwareIDs:
| | | | | ->PCI\VEN_8086&DEV_27DA&SUBSYS_27DA8086&REV_01
| | | | | ->PCI\VEN_8086&DEV_27DA&SUBSYS_27DA8086
| | | | | ->PCI\VEN_8086&DEV_27DA&CC_0C0500
| | | | | ->PCI\VEN_8086&DEV_27DA&CC_0C05
| | | | | CompatibleIDs:
| | | | | ->PCI\VEN_8086&DEV_27DA&REV_01
| | | | | ->PCI\VEN_8086&DEV_27DA
| | | | | ->PCI\VEN_8086&CC_0C0500
| | | | | ->PCI\VEN_8086&CC_0C05
| | | | | ->PCI\VEN_8086
| | | | | ->PCI\CC_0C0500
| | | | | ->PCI\CC_0C05
| | | | | Location Information
| | | | | ->PCI bus 0, device 31, function 3
| | | | | Device Description:
| | | | | ->Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0032
| | | | + DeviceID:
| | | | | ACPI\PNP0C02\4
| | | | | HardwareIDs:
| | | | | ->ACPI\PNP0C02
| | | | | ->*PNP0C02
| | | | | Device Description:
| | | | | ->Motherboard resources
| | | | | Driver:
| | | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0012
| | | | | Capabilities: UNIQUEID SILENTINSTALL
| | | + DeviceID:
| | | | ACPI\PNP0C01\2&DABA3FF&0
| | | | HardwareIDs:
| | | | ->ACPI\PNP0C01
| | | | ->*PNP0C01
| | | | Device Description:
| | | | ->System board
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0010
| | | | Capabilities: SILENTINSTALL
| | | + DeviceID:
| | | | ACPI\PNP0C0B\2&DABA3FF&0
| | | | HardwareIDs:
| | | | ->ACPI\PNP0C0B
| | | | ->*PNP0C0B
| | | | Device Description:
| | | | ->ACPI Fan
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0006
| | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| | | + DeviceID:
| | | | ACPI\THERMALZONE\THRM
| | | | HardwareIDs:
| | | | ->ACPI\ThermalZone
| | | | ->*ThermalZone
| | | | Device Description:
| | | | ->ACPI Thermal Zone
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0007
| | | | Capabilities: UNIQUEID SILENTINSTALL RAWDEVICEOK
| | | + DeviceID:
| | | | ACPI\FIXEDBUTTON\2&DABA3FF&0
| | | | HardwareIDs:
| | | | ->ACPI\FixedButton
| | | | ->*FixedButton
| | | | Device Description:
| | | | ->ACPI Fixed Feature Button
| | | | Driver:
| | | | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0009
| | | | Capabilities: SILENTINSTALL RAWDEVICEOK
| + DeviceID:
| | ROOT\DMIO\0000
| | HardwareIDs:
| | ->ROOT\DMIO
| | CompatibleIDs:
| | ->DETECTEDInternal\dmio
| | ->DETECTED\dmio
| | Device Description:
| | ->Logical Disk Manager
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0004
| | Service:
| | ->dmio
| | Capabilities: SILENTINSTALL RAWDEVICEOK
| + DeviceID:
| | ROOT\FTDISK\0000
| | HardwareIDs:
| | ->ROOT\FTDISK
| | CompatibleIDs:
| | ->DETECTEDInternal\ftdisk
| | ->DETECTED\ftdisk
| | Device Description:
| | ->Volume Manager
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0000
| | Service:
| | ->ftdisk
| | Capabilities: SILENTINSTALL RAWDEVICEOK
| | + DeviceID:
| | | STORAGE\VOLUME\1&30A96598&0&SIGNATURE43F043F0OFFSET7E00LENGTH12A1C90400
| | | HardwareIDs:
| | | ->STORAGE\Volume
| | | Device Description:
| | | ->Generic volume
| | | Driver:
| | | ->{71A27CDD-812A-11D0-BEC7-08002BE2092F}\0006
| | | Capabilities: SILENTINSTALL RAWDEVICEOK SURPRISEREMOVALOK
| | | Drive Name C:
| + DeviceID:
| | ROOT\LEGACY_AFD\0000
| | Device Description:
| | ->AFD
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0000
| | Service:
| | ->AFD
| + DeviceID:
| | ROOT\LEGACY_BEEP\0000
| | Device Description:
| | ->Beep
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0001
| | Service:
| | ->Beep
| + DeviceID:
| | ROOT\LEGACY_DMBOOT\0000
| | Device Description:
| | ->dmboot
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0002
| | Service:
| | ->dmboot
| + DeviceID:
| | ROOT\LEGACY_DMLOAD\0000
| | Device Description:
| | ->dmload
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0003
| | Service:
| | ->dmload
| + DeviceID:
| | ROOT\LEGACY_FIPS\0000
| | Device Description:
| | ->Fips
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0004
| | Service:
| | ->Fips
| + DeviceID:
| | ROOT\LEGACY_GPC\0000
| | Device Description:
| | ->Generic Packet Classifier
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0005
| | Service:
| | ->Gpc
| + DeviceID:
| | ROOT\LEGACY_HTTP\0000
| | Device Description:
| | ->HTTP
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0006
| | Service:
| | ->HTTP
| + DeviceID:
| | ROOT\LEGACY_IPNAT\0000
| | Device Description:
| | ->IP Network Address Translator
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0007
| | Service:
| | ->IpNat
| + DeviceID:
| | ROOT\LEGACY_IPSEC\0000
| | Device Description:
| | ->IPSEC driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0008
| | Service:
| | ->IPSec
| + DeviceID:
| | ROOT\LEGACY_KSECDD\0000
| | Device Description:
| | ->ksecdd
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0009
| | Service:
| | ->ksecdd
| + DeviceID:
| | ROOT\LEGACY_MNMDD\0000
| | Device Description:
| | ->mnmdd
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0010
| | Service:
| | ->mnmdd
| + DeviceID:
| | ROOT\LEGACY_MOUNTMGR\0000
| | Device Description:
| | ->mountmgr
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0011
| | Service:
| | ->mountmgr
| + DeviceID:
| | ROOT\LEGACY_NDIS\0000
| | Device Description:
| | ->NDIS System Driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0012
| | Service:
| | ->NDIS
| + DeviceID:
| | ROOT\LEGACY_NDISTAPI\0000
| | Device Description:
| | ->Remote Access NDIS TAPI Driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0013
| | Service:
| | ->NdisTapi
| + DeviceID:
| | ROOT\LEGACY_NDISUIO\0000
| | Device Description:
| | ->NDIS Usermode I/O Protocol
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0014
| | Service:
| | ->Ndisuio
| + DeviceID:
| | ROOT\LEGACY_NDPROXY\0000
| | Device Description:
| | ->NDProxy
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0015
| | Service:
| | ->NDProxy
| + DeviceID:
| | ROOT\LEGACY_NETBT\0000
| | Device Description:
| | ->NetBios over Tcpip
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0016
| | Service:
| | ->NetBT
| + DeviceID:
| | ROOT\LEGACY_NULL\0000
| | Device Description:
| | ->Null
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0017
| | Service:
| | ->Null
| + DeviceID:
| | ROOT\LEGACY_PARTMGR\0000
| | Device Description:
| | ->PartMgr
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0018
| | Service:
| | ->PartMgr
| + DeviceID:
| | ROOT\LEGACY_PARVDM\0000
| | Device Description:
| | ->ParVdm
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0019
| | Service:
| | ->ParVdm
| + DeviceID:
| | ROOT\LEGACY_RASACD\0000
| | Device Description:
| | ->Remote Access Auto Connection Driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0020
| | Service:
| | ->RasAcd
| + DeviceID:
| | ROOT\LEGACY_RDPCDD\0000
| | Device Description:
| | ->RDPCDD
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0021
| | Service:
| | ->RDPCDD
| + DeviceID:
| | ROOT\LEGACY_SI3112\0000
| | Device Description:
| | ->SiI-3512 SATALink Controller
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0022
| | Service:
| | ->SI3112
| + DeviceID:
| | ROOT\LEGACY_SIFILTER\0000
| | Device Description:
| | ->SATALink driver accelerator
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0023
| | Service:
| | ->SiFilter
| + DeviceID:
| | ROOT\LEGACY_TCPIP\0000
| | Device Description:
| | ->TCP/IP Protocol Driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0024
| | Service:
| | ->Tcpip
| + DeviceID:
| | ROOT\LEGACY_VGASAVE\0000
| | Device Description:
| | ->VgaSave
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0025
| | Service:
| | ->VgaSave
| + DeviceID:
| | ROOT\LEGACY_VOLSNAP\0000
| | Device Description:
| | ->VolSnap
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0026
| | Service:
| | ->VolSnap
| + DeviceID:
| | ROOT\LEGACY_WANARP\0000
| | Device Description:
| | ->Remote Access IP ARP Driver
| | Driver:
| | ->{8ECC055D-047F-11D1-A537-0000F8753ED1}\0027
| | Service:
| | ->Wanarp
| + DeviceID:
| | ROOT\MEDIA\MS_MMACM
| | HardwareIDs:
| | ->MS_MMACM
| | Device Description:
| | ->Audio Codecs
| | Driver:
| | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0002
| | Service:
| | ->audstub
| + DeviceID:
| | ROOT\MEDIA\MS_MMDRV
| | HardwareIDs:
| | ->MS_MMDRV
| | Device Description:
| | ->Legacy Audio Drivers
| | Driver:
| | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0004
| | Service:
| | ->audstub
| + DeviceID:
| | ROOT\MEDIA\MS_MMMCI
| | HardwareIDs:
| | ->MS_MMMCI
| | Device Description:
| | ->Media Control Devices
| | Driver:
| | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0000
| | Service:
| | ->audstub
| + DeviceID:
| | ROOT\MEDIA\MS_MMVCD
| | HardwareIDs:
| | ->MS_MMVCD
| | Device Description:
| | ->Legacy Video Capture Devices
| | Driver:
| | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0003
| | Service:
| | ->audstub
| + DeviceID:
| | ROOT\MEDIA\MS_MMVID
| | HardwareIDs:
| | ->MS_MMVID
| | Device Description:
| | ->Video Codecs
| | Driver:
| | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0001
| | Service:
| | ->audstub
| + DeviceID:
| | ROOT\MS_L2TPMINIPORT\0000
| | HardwareIDs:
| | ->ms_l2tpminiport
| | Device Description:
| | ->WAN Miniport (L2TP)
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0002
| | Service:
| | ->Rasl2tp
| + DeviceID:
| | ROOT\MS_NDISWANIP\0000
| | HardwareIDs:
| | ->ms_ndiswanip
| | Device Description:
| | ->WAN Miniport (IP)
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0006
| | Service:
| | ->NdisWan
| + DeviceID:
| | ROOT\MS_PPPOEMINIPORT\0000
| | HardwareIDs:
| | ->ms_pppoeminiport
| | Device Description:
| | ->WAN Miniport (PPPOE)
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0004
| | Service:
| | ->RasPppoe
| + DeviceID:
| | ROOT\MS_PPTPMINIPORT\0000
| | HardwareIDs:
| | ->ms_pptpminiport
| | Device Description:
| | ->WAN Miniport (PPTP)
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0003
| | Service:
| | ->PptpMiniport
| + DeviceID:
| | ROOT\MS_PSCHEDMP\0000
| | HardwareIDs:
| | ->ms_pschedmp
| | Device Description:
| | ->Packet Scheduler Miniport
| | Friendly Name:
| | ->WAN Miniport (IP) - Packet Scheduler Miniport
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0007
| | Service:
| | ->PSched
| + DeviceID:
| | ROOT\MS_PSCHEDMP\0001
| | HardwareIDs:
| | ->ms_pschedmp
| | Device Description:
| | ->Packet Scheduler Miniport
| | Friendly Name:
| | ->Intel(R) PRO/1000 PM Network Connection - Packet Scheduler Miniport
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0009
| | Service:
| | ->PSched
| + DeviceID:
| | ROOT\MS_PTIMINIPORT\0000
| | HardwareIDs:
| | ->ms_ptiminiport
| | Device Description:
| | ->Direct Parallel
| | Driver:
| | ->{4D36E972-E325-11CE-BFC1-08002BE10318}\0005
| | Service:
| | ->Raspti
| + DeviceID:
| | ROOT\RDPDR\0000
| | HardwareIDs:
| | ->ROOT\RDPDR
| | Device Description:
| | ->Terminal Server Device Redirector
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0029
| | Service:
| | ->rdpdr
| + DeviceID:
| | ROOT\RDP_KBD\0000
| | HardwareIDs:
| | ->ROOT\RDP_KBD
| | Device Description:
| | ->Terminal Server Keyboard Driver
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0031
| | Service:
| | ->TermDD
| + DeviceID:
| | ROOT\RDP_MOU\0000
| | HardwareIDs:
| | ->ROOT\RDP_MOU
| | Device Description:
| | ->Terminal Server Mouse Driver
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0030
| | Service:
| | ->TermDD
| + DeviceID:
| | ROOT\SYSTEM\0000
| | HardwareIDs:
| | ->root\swenum
| | Device Description:
| | ->Plug and Play Software Device Enumerator
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0001
| | Service:
| | ->swenum
| | + DeviceID:
| | | SW\{CD171DE3-69E5-11D2-B56D-0000F8754380}\{9B365890-165F-11D0-A195-0020AFD156E4}
| | | HardwareIDs:
| | | ->SW\{cd171de3-69e5-11d2-b56d-0000f8754380}
| | | Device Description:
| | | ->Microsoft WINMM WDM Audio Compatibility Driver
| | | Driver:
| | | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0015
| | | Service:
| | | ->wdmaud
| | | Capabilities: UNIQUEID SILENTINSTALL SURPRISEREMOVALOK
| | + DeviceID:
| | | SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4}
| | | HardwareIDs:
| | | ->SW\{a7c7a5b0-5af3-11d1-9ced-00a024bf0407}
| | | Device Description:
| | | ->Microsoft Kernel System Audio Device
| | | Driver:
| | | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0009
| | | Service:
| | | ->sysaudio
| | | Capabilities: UNIQUEID SILENTINSTALL SURPRISEREMOVALOK
| | + DeviceID:
| | | SW\{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4}
| | | HardwareIDs:
| | | ->SW\{b7eafdc0-a680-11d0-96d8-00aa0051e51d}
| | | Device Description:
| | | ->Microsoft Kernel Wave Audio Mixer
| | | Driver:
| | | ->{4D36E96C-E325-11CE-BFC1-08002BE10318}\0011
| | | Service:
| | | ->kmixer
| | | Capabilities: UNIQUEID SILENTINSTALL SURPRISEREMOVALOK
| + DeviceID:
| | ROOT\SYSTEM\0001
| | HardwareIDs:
| | ->root\update
| | Device Description:
| | ->Microcode Update Device
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0002
| | Service:
| | ->update
| + DeviceID:
| | ROOT\SYSTEM\0002
| | HardwareIDs:
| | ->root\mssmbios
| | Device Description:
| | ->Microsoft System Management BIOS Driver
| | Driver:
| | ->{4D36E97D-E325-11CE-BFC1-08002BE10318}\0003
| | Service:
| | ->mssmbios


[gslick]

OK, I put the original hard drive back with Windows XP.  Here is the output of the walk:

Thanks. I'll take a closer look at that device list later and see if the Windows 7 version installed on the M890 motherboard includes drivers for all of the devices on the M880 motherboard, or if drivers for any of the devices would need to be found somewhere else.

[juan_ee]

The following are my raw notes I took during the 16902B Win 7 upgrade with Agilent 5.90.x drivers and environment.  Kindly disregard any misspellings of this quick summary.  I also took many pictures but since I got it to work they probably are not needed anymore.

Original Installation:
16902B with 3 16755A cards, Windows XP SP2, Agilent Software 3.83.0001, 80 Gbyte Deskstar HD, M-880-Nitro motherboard, Intel Celeron D 3.2 GHz (Single Core), 2 GBytes RAM installed (4 512 Mbyte modules).

1.  I installing another hard drive into the 16902B, (an 80 GByte Western Digital), and restored the factory Windows XP environment using the 16902-14100.iso mentioned in this thread.
https://www.eevblog.com/forum/testgear/anyone-have-an-os-recovery-disc-for-an-agilent-16900b-series/msg2394207/
I burned the ISO to DVD and installed it using an external DVD drive via USB connection.  [I used a DVD drive from another PC and a USB to SATA adapter]).

2.  It took over an hour to restore…

3.  Once the Win XP environment is restored, verify the touch screen is working, from panel buttons, Agilent Software environment, external mouse, all other devices recognized.

4.  I then exported the following regkey from the Windows XP install environment (using regedit) to a USB flash drive:

[HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo]
"Ag16900Standalone"=dword:00000001
"NoDisplaySwitching"="true"
"FrameModelNumber"="16902B"

5.  Now, from within the Windows XP environment, I installed Windows 7 Pro 32 bit (with SP1 already applied on the DVD) from the external DVD drive.  I choose not to keep previous files, etc...  it then will create a backup of the Windows XP environment and save it in windows.old folder.  Choose NO automatic updates, I will do this manually later.

6.  Ok, now with Windows 7 installed… Touch Screen doesn’t work properly, no problem, keep going.

7.  No need to enter Windows 7 license at this time, you will have 3 days to do it… keep going.

9.  Install network cable, enable automatic updates for Windows 7.  Install updates, 173 important updates, 6 optional (about 1 Gbytes total).  Lengthy process… update got stuck on me once and a few reboots…

10. Once, windows updates are complete… the original Touch Screen drivers on the Window XP install are from Hampshire Company, TSHARC.  For the most recent drivers, they are from Microchip TSHARC, below is the link.  Install the touch drivers and calibrate the screen and reboot… keep going.  (Run as administrator).

https://www.microchip.com/design-centers/tsharc/software-drivers-and-driver-manuals

11.  Now, this is required, (it won’t work without doing this)… import the registry key saved from Windows XP to the new Windows 7 environment using regedit.

12.  If you check device manager, you should have one outstanding device not found.  This will be resolved when you install the complete Agilent 16902B Drivers and Environment, version 5.90.x from B3764-14200-AS-05901104-RC.iso DVD.

https://www.keysight.com/main/software.jspx?ckey=2222812

In retrospect, the installation of the Windows XP restore disc in step 1 may not be needed, given the only thing needed from that installation is

A.   That specific Agilent registry key.
B.   The name of the drivers for the touch screen.

Great info on this thread.  The secret is the registry key (was it ingowien that mentioned it?)  Without that scrap of information, it will not work.

Everything seems to be working, include front panel buttons.  But…

1. The 16902B seems to not have any built-in speaker for sound?  I did get sound by connecting an external speaker to the back of the 16902B.
2.  No Agilent Screen Saver or background included with update?

Juan

[gslick]

Good to know that your 16902B M880 motherboard upgrade to 32-bit Windows 7 Pro pretty much just worked without any real hassles.

You might want to look into replacing the (4x) 512MB memory with either (4x) 1GB or (2x) 2GB memory (not sure if both options work and if there would be any difference between the two) for a total of 4GB memory. The official Agilent/Keysight upgrade to Windows 7 upgraded the M880 motherboard to 4GB.

[juan_ee]

Yeah gslick, I notice on the document you refer to "Keysight Technologies Windows 7 Upgrade Kits for 16800 Series, 16901A and 16902B Logic Analyzers" that the upgrade to Windows 7 for the M880 is to only add RAM and a Windows 7 hard drive but not upgrade the CPU.

That means the 3.2 GHz Celeron is adequate to handle Windows 7 (32 bit) and the Agilent software, no CPU upgrade required.  As long as I don't run other stuff at the same time as I run the analyzer, I might just be OK keeping the original Celeron CPU.

Perhaps Agilent was only adding the additional RAM to justify charging more money $$ .  I mean, why have the customer ship their 16902B to Agilent (which is a hassle, especially if you don't have the original box), then have Agilent's techs open up the case (which is another hassle) and ONLY upgrade the RAM but not upgrade the CPU if the CPU was inadequate?

[gslick]

That means the 3.2 GHz Celeron is adequate to handle Windows 7 (32 bit) and the Agilent software, no CPU upgrade required.  As long as I don't run other stuff at the same time as I run the analyzer, I might just be OK keeping the original Celeron CPU.

On the logic analyzers with the M890 motherboard they run a 64-bit version of Windows 7. Unless someone happens to come across a logic analyzer with the M880 motherboard that had the official Agilent upgrade to Windows 7 and they can report what they find I don't know if the M880 was upgraded to a 32-bit or 64-bit version of Windows 7. The 2GB -> 4GB upgrade might make more difference on a 64-bit version than on a 32-bit version.

It might be interesting to see if something like a Core™2 Duo E6600 "Conroe" would work on the M880 motherboard. There is an E8400 "Wolfdale" on the M890 but that is a couple of years newer than the E6600 and possibly the E8400 might not be supported while the E6600 might be on the M880. Those CPUs seem to be pretty cheap now if you were up for trying that experiment.

[ingowien]

According to CPU-z it's a i945P/PL/G/GZ chipset.
945PL supports FSB533 and FSB800 and Pentium 4, D, and C2D
945P and 945G support FSB533, FSB800 and FSB1066, again P4, D and C2D where G ist the version with integrated graphic.
https://en.wikipedia.org/wiki/List_of_Intel_chipsets
A quick cross-check with e.g. the gigabyte compatibility list reveals that some of their boards support C2D, but only 2 to 5 out of 11.
https://www.gigabyte.com/Ajax/SupportFunction/GetCpuList?Value=23&SocketValue=377&Socket=Intel%20Socket%20775&Chipest=Intel%20945P&Type=Chipest
So personally I would definitely upgrade the CPU, the cost for a better processor is nothing compared to all the waiting with the old Celeron. I'd try one of the CPUs with compatiblity to most of the gigabyte boards or one of the old P4+HT CPUs. As this board will support FSB800, the list of CPUs will be much longer than for the i845 - as long as the BIOS supports Hyperthreading. 

[gslick]

According to CPU-z it's a i945P/PL/G/GZ chipset.
945PL supports FSB533 and FSB800 and Pentium 4, D, and C2D
945P and 945G support FSB533, FSB800 and FSB1066, again P4, D and C2D where G ist the version with integrated graphic.
https://en.wikipedia.org/wiki/List_of_Intel_chipsets

From the M880 motherboard device list it contains this device:
Intel(R) 945G/GZ/P/PL Processor to I/O Controller - 2770
PCI\VEN_8086&DEV_2770&REV_02

That would be either an 82945G, 82945GZ, or an 82945GC Graphics and Memory Controller Hub (GMCH) which have Revision Number 02h, but not an 82945P nor an 82945PL Memory Controller Hub (MCH) which have revision number 81h.

For reference:
Intel® 945G/945GZ/945GC/945P/945PL Express Chipset Family Specification Update
For the Intel® 82945G/82945GZ/82945GC Graphics and Memory Controller Hub (GMCH)
and Intel® 82945P/82945PL Memory Controller Hub (MCH)
January 2007, Document Number: 307503-010
https://www.intel.com/Assets/PDF/specupdate/307503.pdf

Also the M880 motherboard contains this device:
Intel(R) 82945G Express Chipset Family
PCI\VEN_8086&DEV_2772&REV_02

That is the Integrated Graphics Device present in the 82945G Graphics and Memory Controller Hub (GMCH) but not present in the 82945P Memory Controller Hub (MCH).

The 82945G supports a 533/800/1066 MHz system bus and 4GB of memory while the 82945GC and 82945GZ only support a 533/800 MHz system bus and 2GB of memory.

If the M880 motherboard can be upgraded to 4GB of memory it must be an 82945G and it can't be an 82945GC nor an 82945GZ.

For reference:
Intel® 945G/945GZ/945GC/945P/945PL Express Chipset Family Datasheet
For the Intel® 82945G/82945GZ/82945GC Graphics and Memory Controller Hub (GMCH)
and Intel® 82945P/82945PL Memory Controller Hub (MCH)
June 2008, Document Number: 307502-005
https://www.intel.com/Assets/PDF/datasheet/307502.pdf

[juan_ee]

Today, I was in the process of installing Windows 7 Pro 64 bit on a 3rd Hard Drive I have laying around since gslick mentioned  Analyzers which have the M890 motherboard did indeed have the 64 bit version install.

But as I was installing the 64 bit, I was reading the documentation for the Agilent 5.9 software.  It seems 5.9 is a native 32 bit application.

So, I decided NOT to install the 64 bit Windows.  I don't see any advantage in doing so... on the contrary, it seems the 64 bit version of Windows 7 runs 32 bit applications under some sort of emulation... perhaps requiring additional CPU and RAM resources.

So...  I am going to leave it Windows 7 32 bit.  Now, if I upgrade the hardware, it would be:

1.  SSD drive, the easiest upgrade.
2.  Additional RAM, I have 2 GBytes of RAM right now, 4 slots are all are taken (512 MBytes x 4).  An 3 GBytes may ok.  Someone mentioned that 4 GBytes may not be all usable.
3.  CPU upgrade.  I am going to have to spend some time to read the details in the research both of you (gslick and ingowien) have done, much appreciated for the info.

So, about the only thing I couldn't do is port the screen saver from the Windows XP machine to Windows 7  (I was expecting it to come with the Agilent software, but it wasn't).  The file in Windows XP I believe is agilent.scr .  It is an animation sequence with the Agilent logo.

Do any of you run an 169xx from factory with Windows 7?  Does it come with the animated screen saver?

Thanks 

[ingowien]

x32 bit apps in x64 Windows are not emulated, they run natively. They have their own x32-on-x64 subystem that is (geniously) called WoW64 which is Windows (32) on Windows 64. There are thunks to the 64 bit kernel and drivers that cost a little performance but it's not that bad. But you're right, on a machine with just 2GB or 4GB RAM there is no benefit of x64 except there are problems with older drivers.
I found several articles on XP screensavers in Win7, maybe you could one of these, e.g.
https://computerforumz.wordpress.com/2017/06/22/porting-windows-xp-screen-savers-to-windows-7-and-10/
I fould the screensaver issue, too. But I didn't try it as the only screen savers I use are monitor-off.

[juan_ee]

I was able to port the Agilent animated screensaver to another Windows XP machine by moving a few registry keys, a DLL file and the Agilent.scr file.

But have not been able to get it to work on the 16902B running Windows 7.  Will try a few other things the next few days.

To change topics, does anyone use the 90 pin to flying leads like a E5382A ?  What adapters do you use?

Is there a 90 pin to 40 pin adapter to use the lower frequency 40 pin flying leads?
Juan

[gslick]

Do any of you run an 169xx from factory with Windows 7?  Does it come with the animated screen saver?

I have three 64-bit WS7E factory restore images for M890 motherboard versions of 16800A, 16901A, and 16902B logic analyzers. I just took a look and the Agilent logo screen saver does not appear to present in any of those factory restore images that I have.

[gslick]

To change topics, does anyone use the 90 pin to flying leads like a E5382A ?  What adapters do you use?

Is there a 90 pin to 40 pin adapter to use the lower frequency 40 pin flying leads?

I have have a few 90-pin 16753A, 16754A, 16755A, or 16756A modules, I forget which and how many. I have never used them as I don't have any E5382A 90-pin flying lead sets and the asking price for the E5382A are crazy expensive.

Another option might be to use an E5380A 90-pin Mictor probe or an E5378A 90-pin Samtec probe and a breakout board for the Mictor or Samtec connector.  I have seen a few Mictor connector breakout boards listed on eBay, don't remember if I have seen Samtec connector breakout boards listed. Maybe it wouldn't be too difficult and expensive to layout your own breakout PCB and have some built.

[juan_ee]

Do any of you run an 169xx from factory with Windows 7?  Does it come with the animated screen saver?

I have three 64-bit WS7E factory restore images for M890 motherboard versions of 16800A, 16901A, and 16902B logic analyzers. I just took a look and the Agilent logo screen saver does not appear to present in any of those factory restore images that I have.

Thanks for looking gslick and verifying it does not come installed.

[juan_ee]

To change topics, does anyone use the 90 pin to flying leads like a E5382A ?  What adapters do you use?

Is there a 90 pin to 40 pin adapter to use the lower frequency 40 pin flying leads?

I have have a few 90-pin 16753A, 16754A, 16755A, or 16756A modules, I forget which and how many. I have never used them as I don't have any E5382A 90-pin flying lead sets and the asking price for the E5382A are crazy expensive.

Another option might be to use an E5380A 90-pin Mictor probe or an E5378A 90-pin Samtec probe and a breakout board for the Mictor or Samtec connector.  I have seen a few Mictor connector breakout boards listed on eBay, don't remember if I have seen Samtec connector breakout boards listed. Maybe it wouldn't be too difficult and expensive to layout your own breakout PCB and have some built.

Yeah, the E5382A is super expensive.

Yes, I did think about making an adapter board, not like the Mictor board you describe above (it seems there is one on eBay right now), but a direct 90 pin to 40 pin board.

The 16755A 90 pin female connector (on the cable) I believe is a custom Samtec connector.  A few days ago, I ordered engineering samples from Samtec for some 90 pin male headers that might just work.

[danielbriggs]

Apologies for bumping an older thread, but I feel it's relevant + not needing a new one of it's own.

Does anyone have a 16950A card to hand? If so, could you let me know the electrolytic capacitor value, rated voltage, diameter, height and lead spacing please; it would help me tremendously. 



Thanks in advance.
Dan

[gslick]

Does anyone have a 16950A card to hand? If so, could you let me know the electrolytic capacitor value, rated voltage, diameter, height and lead spacing please; it would help me tremendously. 

It appears to be a Sanyo SP-Series 120μF 20V, which could be part number 20SP120M, with size code E, diameter 8mm, height 11.5mm, lead spacing 3.5mm.

Maybe a Nichicon PLX1D121MCL1 would be a suitable replacement.
120µF 20V Aluminum - Polymer Capacitors Radial, Can 27mOhm 3000 Hrs @ 125°C

[danielbriggs]

Thank you so much! I really appricate that.

I've got a 16950A sold as "for parts" coming on its way, and I'm going to attempt a repair. The board looked in good condition apart from one area. There looked some leaky damage and the cap to be non-original, so wanted to compare against a good card + swap out if needed to repair properly. .

The card is 64M "licenced" so I'm tempted to poke around and see if I can work out where the secret sauce is stored 

My 16902A chassis (with a 16910A) is on it's way too, so will get going on all of this when all the bits arrive.
It looks like an old XP P3 mobo, so am tempted to do as others have done and upgrade using a new motherboard, thanks to everyone in advance for posting restore tips / guides on similar work.

All the best,
Dan

[gslick]

I've got a 16950A sold as "for parts" coming on its way, and I'm going to attempt a repair. The board looked in good condition apart from one area. There looked some leaky damage and the cap to be non-original, so wanted to compare against a good card + swap out if needed to repair properly.

Ah, eBay 274444686945. Shipping to you probably wasn't cheap so I hope it turns out to be functional.

The card is 64M "licenced" so I'm tempted to poke around and see if I can work out where the secret sauce is stored 

I haven't looked carefully at the various components near the FPGAs near the backplane connector. My guess is that there is an EEPROM somewhere containing the serial number and the installed license options. It would be interesting if someone figured out how that works from a hardware point of view, and also on the 16910A / 16911A modules.

From a software point of view, it's FlexLM 

[danielbriggs]

That's the one!
I'm up for doing what I can on the modules I've got, just to see if it's possible + if it helps anyone here.

@FlexLM... excellent! I'll be sure to try Option100!

All the best,
Dan

[gslick]

@FlexLM... excellent! I'll be sure to try Option100!

On the 16800 / 16900 series "Option100" is the "factory License" which appears to enable the software features such as the B4601C Serial to Parallel Analysis Package. I don't think it has any effect on the sample memory depth and state speed license options of the analyzer modules.

[ingowien]

I definitely would be interested in the 16950 license topic. I got two 16950A with 16M that could be uprgaded to 64M but Keysight refused to even discuss that.
Would you suggest to read the EEPROMs while powered by the 1690x (which probably would require soldering wires onto it) or trying some external supply?

[danielbriggs]

@ingowien

Would you be able to post an image of the restistor grids for both cards?
A/B   1/2/3/4 for your 16950A?
(Below R945, R944, R941)
Both of your 16950A's are 16M?


My 16950A arrived today (64M memory), so I can start working on this very soon.

[ingowien]

As these cards can be upgraded in software, I don't think it has something to do with the resistors. This was the case for the old 1675x cards bot not for the 16950 cards. I think this has been mentioned somewhere in this forum but maybe in a different thread. However if it helps, I can send pictures of my cards.
best regards
Ingo

[danielbriggs]

I have continued this by posting in the other thread, as seem appropriate:
https://www.eevblog.com/forum/testgear/hpagilent-1675x-logic-analyzer-card-memory-up-hack/msg3434544/#msg3434544

[danielbriggs]

Does anyone have a copy of the Chips 65550 drivers that they have working on Windows 7 32-bit for a 16902A?
I've installed a version for XP from V2.4.7 I found on the web and although Windows begrudgingly installs it, upon reboot I get about 640x480 with 16 colours and everything seems generally very unhappy.

I get much better performance out of the Windows generic driver, but then the Agilent Logic Analyser software fails to install due to failing a video related check. (I've imported all the reg keys from an old XP install, so it's not failing because of that.).

Many thanks,
Dan

[ingowien]

I think I used the standard VGA driver from Win7 with the 65550. Performance was better than in XP and I always use either remote Desktop or  an external display on the other graphics adapter. But there have been restrictions that only two VGA drivers with similar features can be loaded simultaneously.
best regards
Ingo

[Hamster]

Confirmed, Windows 7 Default drivers work great on the 6555X video card.

Question.. I just got a 16903A , fubared HDD.. i was able to recorver the drive and all the data, system just wont boot.

I am unable to restore ANY cd to it, says invalid bios version... it is a Adlink 815G and does boot up with the Agilent Logo, but i cannot get the 16901/902/903 restore disks to run.

So, have we figured out the a v5.90 version install path for this frame yet?  ( i did a 1680A with AMD Athon II + Windows 7 with out issue, i assumed i could do the same with the 16903A, but seems to not be possible )

[Hamster]

hmm.. i got windows xp sp2 installed.. go to device manager, and i don't see the PCI-PCI Bridge

PCI\VEN_104C&DEV_AC28 Texas Instruments PCI2050 PCI-to-PCI Bridge, and behind that the PCI\VEN_15BC&DEV_0505 "Agilent Technologies 16800/16900 Series Analyzer (PCI-to-SVY)"

^ that device doesn't appear to be showing up ..

 

[Hamster]

OK, removed the bridge card, reinstalled it, now it sees it  , but now i got a firmware version issue with running 3.67..  says needs to be updated? going to re-install 3.67 as it seeing the hardware this time, maybe it will do the update.

ok, on re-install, it yelled, said it appears to be be agilent hard, but the disk image is bad, telling me to restore it..

but now, that the pci bridge is working, the restore dvd is properly restoring.

ok, Used the Restore Disk, and Then Installed 3.67.1008, system rebooted a few times, did some firmware updates, and we are passing selftests!


hope i can figure out how to get 5.9 installed.

i am thinking of going to SP3 + .net 3.5 and .net 4.0 and then attempt a 5.9 direct install ..

[Hamster]

Success.. v5.90.1104 Running on 16803A w/XP SP 3

Steps to Restore:

1) Use Agilent Restore Disk
2) Install v3.67 ( to make sure firmware is up to date )
3) Reboot
4) Install XP SP3
5) Reboot
6) Install .net 3.5 sp1
7) Reboot
Install .net 4.0
9) Reboot
10) Install 5.90.1104
11) Reboot

-- Done --

[gslick]

Success.. v5.90.1104 Running on 16803A w/XP SP 3

Steps to Restore:

1) Use Agilent Restore Disk
2) Install v3.67 ( to make sure firmware is up to date )
3) Reboot
4) Install XP SP3
5) Reboot
6) Install .net 3.5 sp1
7) Reboot
Install .net 4.0
9) Reboot
10) Install 5.90.1104
11) Reboot

-- Done --

I don't think it is necessary to first install version 3.67 to update the FPGAs if necessary before installing version 5.90. It's been a while since I have gone through the software installation process on a blank hard drive on a 16900A / 16902A / 16903A. As far as I can remember during the installation of version 5.90 it will check the FPGA versions and update them if necessary.

[Hamster]

Does anybody have a link to the 5.40 Install?

Also, It seems the hardware check is not in the agHwInstall... only the Registry check, reviewing the decompile, the SecureId seems to be a bypass of some sort, need to review decompile more.

[Hamster]

Update:

So, the "Main Frame ID" is stored in the system Bios chip, it is required for the service to determine what type of frame it is.

I have the Bios images for a 1680A/D and 16903A for the same 815 Motherboard, I upgraded my 1680A and 1680AD to have a newer pc motherboard, and used one of the 1680 motherboards in a 16903a and was greeted with the "invalid frame id" , so did some checking, and found the details in the bios chips.

Also, the 16903A service will NOT start if the LCD is plugged in, and the Keyboard is not plugged in.

I am also looking for a spare 16902/3A Front Bezel,  I received a unit that was drop kicked by fedex and totally smashed in. I have been able to replace the LCD panel, and its all functional, but i need a bezel now.

[Hamster]

Just picked up a 16802A , the hdd was toast ( well, more like had a hole thru it.. )

It had the M-890 Motherboard and 4gb of ram, very clean.

installed a new SSD, fresh copy of Windows 7 SP1 , installed .net 4.0 , dump the bios and noticed no system id in the bios...  went forward with install and got no where fast... it was not happy.. Missing drives for the PLX 232... i was able to locate working drivers for this, and installed, and then did a re-install, got error about frame id... 

i ended up using the "agframeoverride" posted earlier and bam, everything worked...

However, it comes up as a 16902A   and works without issue

[gslick]

However, it comes up as a 16902A   and works without issue

Interesting that it reports itself as a 16902A. The 16900A, 16902A, and 16903A were never available with the M-890 motherboard, only later versions of the 16901A, the 16902B, and 16800A models.

As far as I know normally you can only use the 16800A versions of the 16910A and 16911A analyzer modules with the 16800A models. My guess is that there is something in the analyzer module EEPROMs that identify them as 16800A versions. As your analyzer now reports itself as a 16902A with a 16911A analyzer module, I wonder if it would recognize and work with a 1675x analyzer module.

Is your 16802A analyzer module already licensed at the max 32M-Sample / 500MHz ?

[Hamster]

However, it comes up as a 16902A   and works without issue

Interesting that it reports itself as a 16902A. The 16900A, 16902A, and 16903A were never available with the M-890 motherboard, only later versions of the 16901A, the 16902B, and 16800A models.

As far as I know normally you can only use the 16800A versions of the 16910A and 16911A analyzer modules with the 16800A models. My guess is that there is something in the analyzer module EEPROMs that identify them as 16800A versions. As your analyzer now reports itself as a 16902A with a 16911A analyzer module, I wonder if it would recognize and work with a 1675x analyzer module.

Is your 16802A analyzer module already licensed at the max 32M-Sample / 500MHz ?

This is the later Serial # 16802A , after opening it up, it was very clean, (except the destroyed HDD mount from the scrapper selling it ) after fixing the HDD mount plate ( unmangling it ) , i put in a 40gb SSD.. and its working great.

The Card when i removed it had 16911 and is identical to a 16911 i already had, but it only the base , but i already unlocked it to 32M/500mhz.

So this works on a 16802A to unlock it into a 16902A  ( I don't have Option 103 ) so no touch screen, and the EXT Display Switching doesn't seem to work.

I have also tested a 16752A and it worked fine, fully detected, fully operational...


( per post # 63 from ingowien: )

[HKEY_LOCAL_MACHINE\SYSTEM\AgMachineInfo]
"AgFrameOverrideKey1"=dword:483c4aa9
"AgFrameOverrideKey2"=dword:3900384e
"AgFrameOverrideKey3"=dword:5af7983e
"AgFrameOverrideKey4"=dword:82100f65
"AgFrameModelNumberOverride"="16900"


16911A that came in the 16802A Board ID Bits: A:1,2,4,5,6 Jumpered, 3 Open, B: 1,2,3,4,6 Jumpered, 5 Open
16911A that came out of a 16903A Board ID Bits: A:1,2,4,5,6 Jumpered, 3 Open, B: 1,2,3,4,5 Jumpered, 6 Open

Board has NO identifiers that its for a 16800 Series Frame.


I wish i could figure out where this stuck bit is:  ( this is for my spare 16911 card, not the one that came in the 16802 )

16911A Logic Analyzer(A) running...
  Analyzer Chip Memory Bus Test running...
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000001, act=00001001
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000002, act=00001002
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000004, act=00001004
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000008, act=00001008
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000010, act=00001010
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000020, act=00001020
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000040, act=00001040
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000080, act=00001080
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000100, act=00001100
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000200, act=00001200
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000400, act=00001400
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000800, act=00001800
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00002000, act=00003000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00004000, act=00005000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00008000, act=00009000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00010000, act=00011000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00020000, act=00021000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00040000, act=00041000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00080000, act=00081000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00100000, act=00101000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00200000, act=00201000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00400000, act=00401000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00800000, act=00801000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=01000000, act=01001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=02000000, act=02001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=04000000, act=04001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=08000000, act=08001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=10000000, act=10001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=20000000, act=20001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=40000000, act=40001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=80000000, act=80001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=FFFFEFFF, act=FFFFFFFF
      Slot A, Analysis Chip Data Bit Error, nChip 0, nPort 0, bits=00001000
  ...Analyzer Chip Memory Bus Test ended. Result: Failed***
...16911A Logic Analyzer(A) ended. Result: Failed***

I could recover a 16911 Card... I already replaced the Ram with no affect.

[Hamster]

Just picked up a NIB 16902B with M890 Raptor and working win7 image on SSD, its interesting how much the inside of this unit changed from the other 169xxA units.

[gslick]

Just picked up a NIB 16902B with M890 Raptor and working win7 image on SSD, its interesting how much the inside of this unit changed from the other 169xxA units.

Did you grab this one?

https://www.ebay.com/itm/265223690025

I had been watching that one for a while as the price was gradually lowered over the last 4 months. If I didn't already have more than one M890 motherboard version 16901A / 16902B I would have  been very tempted to buy that one myself. That seems like a decent deal in the current market.

The M890 motherboard Windows 7 SSD versions are a lot nicer than the earlier Windows XP versions. It's something around a minute from power on to fully booted and logic analyzer application running, compared to a lot longer on the earlier versions. Also, nice to have the DVI video output on the M890 motherboard if you want to use an external monitor instead of VGA output.

[Hamster]

Yep... It was pretty much 100% new.. it got a little beat up in shipping ( UPS Dropped it on one side so it bent one of the feet and caused a bunch of cables to get unplugged, but the display didn't break which was good. i imaged the HDD and swapped out the HDD to a newer larger one, now I have two 16xxx units with M890 Boards, I also have a few 1680AD(s) that i installed more modern PCB(s) in that work good for portable units, the 16852 i have is nice, i wish it had 2 slots, i may take my 16902A that has a busted bezel and try to hack a modern MB into it and try the registry hacks, I think the M890 Raptor units have Serial EEPROMS on the FPGA board stating what time of frame they are as the older XP units had the data in the system bios chip ( as posted earlier )

I heavily use these on my twitch feeds when fixing boards, its a very nice to have a faster unit with 1gig ethernet.

[MarkL]

...
I wish i could figure out where this stuck bit is:  ( this is for my spare 16911 card, not the one that came in the 16802 )

16911A Logic Analyzer(A) running...
  Analyzer Chip Memory Bus Test running...
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000001, act=00001001
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000002, act=00001002
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=00000004, act=00001004
 ...
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=80000000, act=80001000
      Slot A, Analysis Chip Data Bit Failed, nChip 0, nPort 0, exp=FFFFEFFF, act=FFFFFFFF
      Slot A, Analysis Chip Data Bit Error, nChip 0, nPort 0, bits=00001000
  ...Analyzer Chip Memory Bus Test ended. Result: Failed***
...16911A Logic Analyzer(A) ended. Result: Failed***

I could recover a 16911 Card... I already replaced the Ram with no affect.

Here's a hint from the Service Guide:

Analyzer Chip Memory Bus Test. The purpose of this test is to check the Analysis chip memory busses that go between the Analysis chips and the Memory Controller FPGAs.

The stuck bit might be a broken trace between one of the acquisition ASICs and its memory controller.  Broken traces are fairly common on 1675x cards and are caused by something corrosive leaching from the plastic runner adhesive.  I've removed the runners from all my cards.

I would check the continuity using (very) sharp probes from via to via on all the Analyzer Chip Memory Bus lines between the two chips.  There are two buses, and I don't know which one is associated with "nChip 0".  If the copper is good it should be around an ohm or less.  I've outlined where the two buses run, attached.  I can't tell if there are any inner-layer traces for these buses, but I can say there aren't on the 1675x cards.

Sorry for the bad picture quality.  I don't have any 169xx cards and I snatched a photo from ebay.

[Hamster]

nChip0 is the upper portion, i did pull a ram chip and confirmed nChip0 fully errored out, replacing the ram returned it the same state.. i had already pulled the runners and inspected and saw no corrosion..  the ram modules are connected via inner layers to the memory controller.

[deanclaxton]

Digging up an old thread I know, but would anyone know if the Nitro M880 motherboard could be installed in a 16902A analyser? Or are there better options to upgrade a 16902A to boost performance and maybe run Windows 7.

EDIT : looks like the rear panel cutouts are different so that is a negative (without cutting up the rear panel)

[gslick]

Digging up an old thread I know, but would anyone know if the Nitro M880 motherboard could be installed in a 16902A analyser? Or are there better options to upgrade a 16902A to boost performance and maybe run Windows 7.

EDIT : looks like the rear panel cutouts are different so that is a negative (without cutting up the rear panel)

Yeah, the horizontal layout of the three audio jacks on the Radisys SC815E, Motorola VP22, and ADLINK M-815G motherboards make it difficult to find any mechanically compatible drop in motherboard replacement. Most motherboards that are any newer seem to have switched to a vertical layout of the audio jacks. Things are moved around even more between the Radisys SC815E, Motorola VP22, and ADLINK M-815G motherboards and the Intel D915GUX and ADLINK M-880 motherboards.

My own opinion is that it is not really worth the effort to try to modernize the 16900A / 16902A / 16903A logic analyzers with hardware upgrades for any improvement you might get in return.

I picked up a 16902A a couple of months ago for what seemed like a fairly reasonable deal, maybe because it was missing a hard drive. While I was adding a hard drive and installing the software, I did some experiments. I found that for at least initial power on to application fully up and running it made very little difference swapping from an ATA hard drive to a SATA SSD attached to an SIL3112 PCI SATA controller. Not enough to be worth the bother. I found a much bigger improvement (or rather a lack of a slowdown) when reinstalling the factory XP SP2 image and the 3.67 version of the application software, instead of upgrading the factory XP SP2 image to SP3 and the 5.90 version of the application software. Something in SP3 seems to really slow down the full boot up to fully ready process. It doesn't seem to be disk bound.

The best usability experience might be to go with the XP SP2 and 3.67 versions, add the 1Gb option network card, and run the application software over the network from a much newer and faster PC, with a nice large monitor. This would be on an isolated network switch, so not much concern about the lack of security updates being installed on the XP SP2 system. I recently picked up a Dell Precision 3420 small form factor PC to use for this purpose. Cheaper than what would probably be spent trying to shoehorn any motherboard upgrade into the LA chassis, and with a better usability experience, at the cost of a little more bench space.

[deanclaxton]

Good Stuff! I won the 16902A, so I'll be giving this a go when I get it. It has 2 x 16950A cards in it. I'll be looking for some termination adapters if anyone has any to suit, so I can make up a new 65C02 adapter board for it and try get Phils inverse assembler running (I've posted about this in the inverse assembler thread).

It's got be be faster than the HP 16602A I'm currently using (turn it on, make a cup of tea, check if the X11 connection is available, tinker around with something else for a bit, try it again......). Once booted it's actually quite useable though.

[gslick]

I just did a quick power up timing test on a 16902A with the standard ADLINK M-815G, 1GHz PIII, 512MB motherboard.

The missing hard drive on this one was replaced with an HDS724040KLAT80 Hitachi Deskstar 7K400. That is a 400GB, 7200 RPM hard drive, with an 8MB buffer. I found that I had to soft resize the capacity down to around 120GB, otherwise the drive image restoration from the 16900-14121 recovery DVD would not complete successfully.

The 16900-14121 recovery DVD restores an XP SP2 image (with critical updates though 10 Jan 2007, according to the DVD label). After that I installed the 3.67.1008 version of the logic analyzer software. No other software updates were installed.

I set the system to auto login so there would be no pause at a login screen.

I found that it took around 1:40 minute total from pressing the power button to when logic analyzer service initialization was complete (that takes some time), and then to when the logic analyzer application was fully up and running.

From my notes, when I previously tried updating to XP SP3 after the 16900-14121 recovery DVD restores the XP SP2 image, and then installed the 5.90.1104 version of the logic analyzer software, it took somewhere around 4:15 minutes total from pressing the power button to when the logic analyzer application was fully up and running, with the same hardware configuration. Replacing the ATA hard drive with a SATA SSD attached to an SIL3112 PCI SATA controller only saved around 15 seconds.

Sometime I'll have to do similar power up timing tests with Intel D915GUX and ADLINK M-880 motherboard versions of the 168xxA / 16901A / 16902B with XP SP3 and 5.90.1104, and also ADLINK M-890 motherboard versions running 64-bit Windows Embedded Standard 7. If I remember correctly the ADLINK M-890 motherboard versions booting from a SATA SSD were fully ready somewhere between 1 and 2 minutes from power on. Those are by far the nicest versions.

[deanclaxton]

Is there much advantage in going to the later version of the Agilent suite?

It will be interesting to see how much a little more ram would help.

[gslick]

Is there much advantage in going to the later version of the Agilent suite?

It will be interesting to see how much a little more ram would help.

I haven't taken a detailed look at the differences between the 3.67.1008 and 5.90.1104 versions. Looking at the release notes would probably be a good place to start. There might be some of the later analyzer modules and analysis software options that require the newer version.

The ADLINK M-815G motherboard is limited to 512MB maximum. The newer Intel D915GUX, ADLINK M-880, and ADLINK M-890 support up to 4GB (the available RAM may be may be closer to 3GB on the Intel D915GUX).

Logic Analyzer Application Software Version 03.67 (July 2007) Readme
https://www.keysight.com/us/en/assets/9018-19105/release-notes/9018-19105.html

Agilent Logic and Protocol Analyzer Software (32-bit Application)
Version 5.90.1100 – September 2015 Release Notes
https://www.keysight.com/us/en/assets/9018-07879/release-notes/9018-07879.pdf

[deanclaxton]

Looks like the 5.9 release supports the U series stuff - the 3.67 supports the modules I'll have so that should be alright. It will be interesting to see what version is installed when I get it.

Hopefully the speed will be ok - like it must have been useable back in the day mustn't it? I probably should have gone for a 16902B, but this was local (which is quite rare) and a 16902B would have cost me USD$440 just for the international shipping alone (I'd been looking at one that has the M880 in it).

I'll see how it goes when I get it I guess!

[ahakman]

Is the v4.44 software available anywhere other than by asking keysight? I don't know why they don't post it on their site.

My actual LA has 4.00 and I'd like to look at saved files offline on another machine, Trying to open them with v 3.67 of the sofware it just crashes when opening. V 5.90 seems like a general PIA

[ahakman]

I also submitted a support request with Keysight to get the older software, and they just closed the request saying "16903A isn't supported anymore - last support was in 2012"

I guess Keysight has turned into one of _those_ kind of companies now... how the greats have fallen

For shame Keysight, for shame...

[ahakman]

I'm just trying out a new mobo in my 16903A. I got a Asus P5G43T-M PRO motherboard with a c2d E8500 and 4GB of ram. I installed win7 64 bit on a 500gb ssd (and sp1 / security rollups, etc etc) and the logic analysys software 5.60 (HUGE Thanks to ingowien for still having that kicking around seeing as Keysight is not even interested in handing out the software anymore).

I only have 2 slight issues - if I set the motherboard to use integrated graphics / PCI, the bios does show up on the integrated monitor, but the system just hangs at "Checking NVRAM" and won't actually boot ("Checking NVRAM" seems to be a relatively common AMI bios thing some people see if you google it, but there are really no definitive answers as to what causes it). If I change the display adapter in the bios to be only integrated graphics and not PCI, then it boots to windows. So the internal monitor works, but the system won't boot if that's the primary display device - not really the end of the world for me.

Once in windows, everything seems fine, the logic analysys service works and recognizes the frame and the cards, and starting the logic analyzer software works, but if I run a self test, I get 1 error, "System Backplane Clock Test (Failed in slots BCA)". I have a 3 card stack that's all joined together into one large module. I never saw this System Backplane Clock Test failure before, and I didn't remove (or even move) any of the cards in the backplane to swap the mobo. Has anyone seen this error before? I'm wondering if the power supply is a little overloaded - the 12V rail is at about 11.5V, which seems a bit low.

Anyone have any ideas what causes the Backplane Clock Test to fail?

[ahakman]

I fixed it, it was the 12V rail being low. I took the front panel off, took the power supply out, took the cover off, and then plugged the power supply back in. With it loaded and running windows, I adjusted the pot on the 12V module in the power supply to get 12.2V. Now the System Backplane Clock Test passes with no issues. I guess 11.5V that it was set to before while loaded was just too low a voltage, probably for the PLL on the backplane.

So, if your System Backplane Clock Test is failing, and looking at the detailed output of the test, is running about 1/3 the frequency it should be, check the 12V rail is adjusted properly!

Now I just need to cut a hole in the motherboard tray for the I/O shield, and this thing is good to go - nice and usable now, not painfully slow like it used to be!

[ahakman]

Hmm, or not - I put it all back together again (mounted the power supply properly and put the front panel back on), now it's back to the system backplane test failing agian, running at 1/3 the frequency it should be 

[heisnoble]

Hello friend i bought a agilent 16802a from ebay. the motherboard was dead. i changed it with a similar one. but after a clean re-install windows xp and installed 5.90 application software. but it is showing frame id error. i dont know what to do with. some one guide me what to do with.

[Hamster]

Hello friend i bought a agilent 16802a from ebay. the motherboard was dead. i changed it with a similar one. but after a clean re-install windows xp and installed 5.90 application software. but it is showing frame id error. i dont know what to do with. some one guide me what to do with.

the v5.90 software is drm locked to certain motherboards.

[Hamster]

So i have a 16801A and went to pull the board out to plug into another frame, and noticed its a 134 channel card... Somehow Agilent Disabled have of it?

I am going to dump the Serial EEPROM and compare board jumpers to see if there is something make it appear only as a 34 channel card.

[gslick]

So i have a 16801A and went to pull the board out to plug into another frame, and noticed its a 134 channel card... Somehow Agilent Disabled have of it?

I am going to dump the Serial EEPROM and compare board jumpers to see if there is something make it appear only as a 34 channel card.

How are you dumping the serial EEPROM of the module? Do you also have a method to write the serial EEPROM? How much effort does that take?

One thing I have wondered is what happens if the serial EEPROM is completely erased. In addition to applying hardware upgrade licenses to modules, the agHwUpdate.exe utility also has an option to initialize a module only if it is currently in the uninitialized state. I'd have to check my notes to see exactly what that option is. I wonder if that is a manufacturing option where the module initially has a blank serial EEPROM, and that is used to customize the module as a regular 16900-series 16910A or 16911A, or as a 16800-series specific 34/68/102-channel version.

If it's not too difficult to dump the current contents of the serial EEPROM and then write new contents, it would be interesting to see what happens when the agHwUpdate.exe utility is run if the serial EEPROM is completely erased.

Edit:
Maybe if the serial EEPROM is completely erased, and if you have a signed 16910_32Meg_Samples license file, then the agHwUpdate.exe utility could be used with the '-i' option to initialize the module with that license file.

Code: [Select]

C:\Program Files\Agilent Technologies\Logic Analyzer>agHwUpdate.exe -?
Usage:
  -?   print usage message
  -h   print usage message
  -i <slot letter>  -n <optional serial number>
       init the card in slot <slot letter> with serial number <serial number>
       NOTE: There must be a license file available for this serial number!
  -l <optional slot letter>
       list the contents of slot specified with slot letter,
       without the slot letter will list the contents of all slots
  -m <slot letter>
       return the card in slot <slot letter> to minimum depth and speed
       NOTE: This does not affect the serial number!
  -f <file name>
       write all output to the file specified
  -o   when used with the -f flag, indicates that it is ok to overwrite
       the file specified with the -f flag if it exists already


[Hamster]

I was removing the eeprom and using my programmer.. However, I will try that util.

i need to correct my above post:

My 16801A i picked up a few months ago ( 32 Channel ) , actually has a 64 Channel Card ( not 134... lol) , but have way disabled. Comparing it to a 16911 card, the id chip resisters are set differently.

I also picked up the beat up face busted 16803A on ebay for $20 ( $100 shipped ) , turned out the lcd was not broken, and after resetting the admin password and bios, the display works perfectly.  the LA also passes self test without issue ( 20 reputations ) .. i just need to find a new bezel for it.

Its also equipped with an Intel Desktop Board D915GUX/D915PCM/D915GNA, Supporting 4g of Ram, the LCD is connected to an Adlink PCX-8551 Bridge Card... ( 1x PCIe )

[Hamster]

Converting a 16912 -> 16911

Trying to change the Board ID & Swapping EEProm did not work, Booting Frame Results in error:

"Initialization Status: Slot A: After loading, FPGA_INIT lines not 1. exp=000C, reg=0091"

i looked at both 16911 & 16912 and saw no differences between them other then the board id resisters

[Hamster]

As for Upgrading the Motherboard in these smaller 1/2 card frames, in two of the 3 units i have, they used the PCIe feature called Serial Digital Video Out to drive the LVDS display.. it only works on 915 Intel Chipset..

[Hamster]

Correction... Looks like it SDVO will work with all these chipsets..

Intel® 946GZ Express Chipset
Intel® 945G Express Chipset
Intel® G965 Express Chipset
Intel® Q965 Express Chipset
Intel® Q963 Express Chipset
Intel® G31 Express Chipset
Intel® G33 Express Chipset
Intel® G35 Express Chipset
Intel® Q33 Express Chipset
Intel® Q35 Express Chipset
Intel® G41 Express Chipset
Intel® G43 Express Chipset
Intel® G45 Express Chipset
Intel® Q43 Express Chipset
Intel® Q45 Express Chipset

[Hamster]

So, Still trying to see what can be done to a 1680XA system to upgrade the motherboard, Now, keep in mind the mATX in it now is a single core @ 3ghz, so it actually runs XP well, and putting 3g of ram, and doing the Register mod, allows it support any card in it.

I have tried two boards now with the PCIe SVDO Adapter, the systems do output video, but don't detect the correct panel resolution, it sets it to the smaller 800x600 on the larger 1024x768 panel.. so it has bars/garbage on left and bottom of screen, there is a hint that the Intel BMP tool can be used to edit the video bios, however, that program is non-existent.  --- I only tried to get video working first before moving to any software install, but since no video solution, not going to tear down frame to put board in.

Motherboards tried
Intel DG965RY ( wont fit, its too big, wasn't paying attention )
Intel DG43GT ( would fit, but does same issue ) .. I think this Motherboard may WILL work in a 16903A , i have one here i can try it in.. , but would require cutting out the back plate to support the MB I/O  I have a parts machine with missing bezel.

So if anybody has an extra Bezel for a 16903A and 1680X and will to part with, LMK