Agilent 16902A logic analyzer touch screen driver for windows XP needed

[keitheevblog]

I've recently added a SATA card and SSD to an Agilent 16902A, which required some Windows XP finessing in order to get the proper drivers installed for the OS to boot. I did this previously on a 16900A without issue, but there was no touch screen present.

I can't, for the life of me, locate the proper Windows XP 32-bit drivers for the touchscreen. The DISPLAY portion works just fine at proper resolution, etc. I see (2) Agilent errors on bootup that say "the touchscreen failed to start."

There are no obvious missing drivers, errors in device manager, etc. I see various references, and I haven't fully unpacked the companies, relationships, who made what part.

When it boots I see a "CHIPS 65550 PCI & VL Accelerated VGA BIOS" screen. This is "Chips and Technologies" (then later Asiliant). I also see a reference to 3M Touchsystems SC4 in the UPDD control panel -- which appear to be detected on a COM port.

So far I've tried:

• eGalaxTouch_5.12.0 from MicroTouch
• MT7.14.9 from a 3M touchscreen provider
• UPDD 6.0.0.433

I saw some reference in another post saying the "3M touch driver v3.8.34" works fine on related equipment, but google turns up nothing for me.

Help!@#

Thanks

[optotester]

The 3M driver you mentioned is attached, feel free to try it.

[gslick]

When I experimented with adding a SATA drive to a 16900A / 16902A / 16903A analyzer I used an Sil3112 chipset SATA adapter card, which didn't require anything special to get a clean install of Windows XP from the OS recovery DVD. The OS recovery DVD image included the drivers for the Sil3112 adapter card, and the touch sreeen. The only thing I had to do after a clean install from the OS recovery DVD was to install the logic analyzer application.

In the end, I found that switching to a SATA SSD installation didn't make that much difference in the total elapsed time from power on to boot to the desktop with the logic analyzer application fully initialized and ready to go. Maybe most of the performance limitation comes from the 1GHz PIII processor and only 512MB of system memory.

[keitheevblog]

Thanks Glen.

I used a Sil3114 card in both my 16900A and 16902A. In both cases, when using the recovery CD, the LA blue screened a 0x7B stop error, which means inaccessible boot device. I'd think the drivers for the Sil3112 and Sil3114 have to be very similar, so I'm surprised, and a bit perplexed, to hear that works. 16900-14121 for the system os refresh disc, right?

I think you're probably right about the perf limitation being the CPU/RAM but replacing these hard drives that are 15 to 20 years old has merit, at least from a reliability standpoint. When I look at the power on hours, I'm pretty sure these often ran 24/7 for at least some of their lifetime. My experience with HDDs seem that once we get over about 50K service hours, then it's definitely time to replace them. This one has 70k hours, or 8 years of run time.

Appreciate the reply!

[Pilatus]

...SATA SSD installation didn't make that much difference in the total elapsed time...

Same here; however, to my relief, the high frequency whine from the HDD was gone when using the SSD.

I originally thought it was the fans making the whining noise ... or maybe it was me :-)

[keitheevblog]

The 3M driver you mentioned is attached, feel free to try it.

You rock! This worked, including autodetecting that it was serial-port-attached, the COM port (COM2), it was the 3M Touch Systems SC4. It uses 9600 8N1.

How did you end up finding it? Perhaps I struggled because it was like 4am, and I should have went to bed hours before.

I couldn't even find anything that used a similar version numbering scheme...... but I was all over the place.

Thanks!

[keitheevblog]

Same here; however, to my relief, the high frequency whine from the HDD was gone when using the SSD.

I originally thought it was the fans making the whining noise ... or maybe it was me :-)

Right. I think it's a useful upgrade, and worth my messing around time. It's less noise, less power, more reliable, faster and more consistent access times, and faster/easier off-line imaging.

Now I end up with a slightly non-standard installation because I use the recovery CD first, then repair it with a generic WinXP SP2 installation CD, using F6 and a USB floppy drive to load Sil3114 drivers. This repair obviously breaks some things, like the touch driver for whatever random reason.

Ideally the recovery CD would just work by itself, so I'm interested to know why it works fine for Glen, but not for me. And I've got two different units exhibiting the same behavior. Both cards were Sil3114, but not the same (advertised) manufacturer, AFAIK.

Is it something like the Sil3112 is supported, but the Sil3114 identifies just different enough?

Keith

[keitheevblog]

Ideally the recovery CD would just work by itself, so I'm interested to know why it works fine for Glen, but not for me. And I've got two different units exhibiting the same behavior. Both cards were Sil3114, but not the same (advertised) manufacturer, AFAIK.

Is it something like the Sil3112 is supported, but the Sil3114 identifies just different enough?

AAANNNDD, I think I found the smoking gun already.

I checked C:\Windows\system32\drivers folder on a regular deployment installation.....and lo and behold, the 3112 is present but not the 3114.

See attachment.

Gotta be it.....

[optotester]

Sometimes, when you have a very specific version number, it is better to look for just that in Google rather than the name (typing "3.8.34 driver" return the correct driver on the first result). But I do agree that when we are tired we may often miss simple things 

[keitheevblog]

Thanks -- appreciate the tips!

[gslick]

I used a Sil3114 card in both my 16900A and 16902A. In both cases, when using the recovery CD, the LA blue screened a 0x7B stop error, which means inaccessible boot device. I'd think the drivers for the Sil3112 and Sil3114 have to be very similar, so I'm surprised, and a bit perplexed, to hear that works. 16900-14121 for the system os refresh disc, right?

If you have a 16902A with the ADLINK M-815G motherboard, then the 16900-14121 OS recovery DVD is the correct one to use.

Code: [Select]

168xA/AD Win XP     MY41000801-MY41000899   Radisys SC815E  01680-14100
                    MY41000901-MY41001099   Motorola VP22   01680-14104
                    MY41001101-later        ADLINK M-815G   01680-14106

168xxA              MY46000101-MY46000999   Intel D915GUX   16800-14102
                    MY46001000-later        ADLINK M-880    16800-14103

16900A, 16902A      MY43000001-MY43001999   Motorola VP22   16900-14109
                    MY43002000-later        ADLINK M-815G   16900-14121

16901A              MY46000101-MY46000399   Intel D915GUX   16901-14101
                    MY46000400-later        ADLINK M-880    16901-14102

16902B              All                     ADLINK M-880    16902-14100

16903A              MY43000001-MY43000199   Radisys SC815E  16903-14100
                    MY43000200-MY43001999   Motorola VP22   16903-14104
                    MY43002000-later        ADLINK M-815G   16903-14107

If your serial number starts with SG, then the same number ranges apply.
For example, SG43000001 is the same as MY43000001


[gslick]

The 3M driver you mentioned is attached, feel free to try it.

You rock! This worked, including autodetecting that it was serial-port-attached, the COM port (COM2), it was the 3M Touch Systems SC4. It uses 9600 8N1.

How did you end up finding it? Perhaps I struggled because it was like 4am, and I should have went to bed hours before.

I couldn't even find anything that used a similar version numbering scheme...... but I was all over the place.

Thanks!

The driver installed in the 16902A system OS recovery image is version 03.08.54P

After a quick look I couldn't find an install package for that driver version online. But if you do a clean install from the recovery DVD that driver should already be installed.

[gslick]

Is it something like the Sil3112 is supported, but the Sil3114 identifies just different enough?

If you do a clean install from the 16902A system OS recovery DVD, the drivers for the following Sil3112 and Sil3512 SATA controllers are preinstalled in the system image. A system image restored to a SATA drive attached to one of these 3 controller versions should be bootable without any further actions necessary after the system image restoration completes.

The only difference between the two Sil3112 versions is whether the firmware on the controller card is the raid version or the non-raid version.

Code: [Select]

PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02
"DeviceDesc"="Silicon Image SiI 3112 SATALink Controller"
"LocationInformation"="PCI bus 1, device 15, function 0"


PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02
"DeviceDesc"="Silicon Image SiI 3112 SATARaid Controller"
"LocationInformation"="PCI bus 1, device 15, function 0"


PCI\VEN_1095&DEV_3512&SUBSYS_35121095&REV_01
"DeviceDesc"="Silicon Image SiI 3512 SATALink Controller"
"LocationInformation"="PCI bus 1, device 15, function 0"

If you pick up a random Sil3112 or Sil3512 controller card it might have vendor specific PCI SubSys values that don't exactly match one of the three pre-installed hardware ID entries above.

The PCI SubSys values are typically stored in a 24C02 or similar serial EEPROM on the controller card. The Sil3112 and Sil3512 chips contain embedded mechanisms to update the serial EEPROM by the host writing to PCI configuration registers in the Sil3112 and Sil3512 chips.

If someone is looking for an Sil3112 SATA controller to use in a 16900A-series logic analyzer and wants a name brand card instead of some random card, one option is an Adaptec ASH-1205SA. I bought a couple of as-new ASH-1205SA cards on eBay a while ago for experiments. I was able to update the serial EEPROM on the cards to change the PCI SubSys ID from the Adaptec vendor value of 02509005 to the generic Sil3112 value of 31121095. After doing that I had no issues booting from a SATA drive on a 16902A after booting from the OS recovery DVD and doing a clean system install on the SATA driver attached to the ASH-1205SA card.

[keitheevblog]

Thanks Glen for the additional details. That slightly older 3.8.34 version linked in this thread seems to work fine. It looks like the official driver is 03.08.54P as you said.

I did find another way tonight to solve this problem.

After using the 16900-14121 recovery DVD, with a $20 Amazon SI3114 card (which we've determined is not directly supported in the recovery image), Windows XP blue screens with the 0x7B stop error. This is why I was investigating doing essentially a ground-up install. This works fine.....although it requires a couple hoops, and gives something less than the official version. I did this previously with my 16900A, and practically speaking there's no issues.

Tonight, I decided to try to fix the broken Windows XP recovery install and have what I believe is a great solution.

https://superuser.com/questions/1738250/recovering-a-windows-xp-system-gives-error-0x0000007b-in-the-bsod

This solution uses Hiren's Boot CD version 15.2, which is available here https://www.hirensbootcd.org/old-versions/

After using the recovery disk, boot this "boot cd", using the very cool mini XP environment, use the "fix hard disk controller" option. It boots in a minute or two, and the fix is essentially immediate.

Then, just eject the disk, and reboot.

That's it. The LA will boot normally, go through the Windows XP setup wizard, and off you go.

Hiren's had the 3114 drivers "built in", which was convenient for my purposes, but I noticed an available F6 option for adding drivers via floppy, which would help if you were dealing with an HDD controller that isn't directly supported.