When I try to use the Agilent firmware updater (from the website) for my E4406A, I get warnings about the ancient MS JVM it tries to run.? If I mess with the path, I can get it to run, but although the updater runs and netstat shows has a listening port on 0.0.0.0 UDP for BOOTP, it doesn't respond to the BOOTP request from the 4406 during the upgrade.? If I run a different bootp agent in place of the updater, it issues a good IP to the 4406.? This is the same on a Win7 and two Win10 platforms. (Firewalls and AV disabled in all cases)
All three can read the current cal and config files before I reboot into the bios.? After a SEA (02), I see option 0 is the LAN card, so I pick that (03), and then select no interactive (down arrow), and the 4406 asks the LAN for the IP but never gets it.
On the LAN, I have a router, but very oddly, if I remove it and just run a bare Cisco switch with the 4406 and a PC, the 4406 doesn't detect the LAN interface at all.? No sign of any obvious broadcast traffic or discovery packets, but I've not (yet) done a port monitor and captured all the L2 traffic on Wireshark. Pings, ftp and telnet all work fine with the 4406 running normally.
If I try to run the updater using the latest javaw.exe (update 181) or java.exe, it throws the usual errors about not being able to find the main class in the .jar
Is there a workaround I can use?? Maybe unzip the .jar and put the classes into a folder and tell java to search there?? Maybe run an ancient XP VM, or run the thing in Linux? Or can I use PXEboot or tftp with separate bootp, or some other way to get this thing updated?? Any hints would be very much appreciated (other than time travel).
Current firmware is from 2000, the one I am trying to use is from 2007.? Oh, and of course, the 4406 backlights are totally dead, so I have to use a LED torch to try to read the display.
Neil
