I'm going to test something out later today, I belive it should work just making the patched 'nk.bin.comp', and then re-packing all the files into a new cab file..
This cab packer seems to work awesome, I see the final created cab files look good.. so I'm going to try this out later today..this way we can just install the patched firmware from a UsB stick..
BUT, that still leaves you with having to modify the lnk file? so you may have to buy the homebrew lan board...
but if anyone wants to try this now, this tool is pretty sweet..
(you can get the full suite from here)
https://www.softpedia.com/get/File-managers/CabPack.shtml
FYI..
here's the patches for 2.50 (3000A)Code: [Select]3000A series:
firmware: 2.50
------------------
1) options patch: 0x2815f4 --> "04 00 A0 E1" --> "00 00 A0 E3"
2) nag patch: 0x2aae50 --> "CD 59 FF EB" --> "01 00 A0 E3"
Ok Guys, got it all working:Code: [Select]1) patching the nk.bin.comp, fixing the two MD5 entries in the 'recipe.xml', and re-building the cab file with little CAB builder I posted worked perfect
(just make sure to choose MSZIP for the compression type)
2) the LAN connection did NOT get shutoff for me after I upgraded to the patched 2.50 FW.. it worked fine after the scope finished bootingup..
3) The initial upgrade wiped out any existing .lnk file, it went back to the stock empty .lnk file, which is why my options disappeared..
4) So I re-copied my .lnk file over to \Secure\Startup, (renamed the orignal empty one to some garbage name to basically get rid of it, or you can just delete it), and all options are back.
So as far as I can tell, there was nothing done to the Telnet session??? at least nothing different occured for me?
If anyone wants, I can post the CAB file patched for 2.50? you'll still have to fix your .lnk file to enable options again... but telnet works fine as usual...
So PCB GUY, only thing you need to do is buy a homebrew LAN card, guys on here can sell them privately if any still have the parts, or you can make one yourself, I posted the OshPark links for one I did back in this thread, that's the board I use now.. has LAN, USB, and JTAG all on the card..
So, if you want to use the 'patched' FW image I posted, you don't have to do any of the above steps except for #1 & #2 (and BTW your lnk contents look good)...and for step 2 ONLY need to copy the .lnk' file you don't need to do anything with the 'nk.bin.comp', as that is part of the patched 2.50 FW image...
but of course you still need to Telnet in.
The IP Address of the scope you set yourself, it's in the "I/O" submenu, I think you click "utility" first, then go there, I can't remember exactly, I always just push buttons until I get there
Anyhow, you pick your IP address, gateway, & mask yourself. I always just LAN cable up my scope right to my laptop, but them both on some fake network segment you make up, obviously both at different IPs, but on the same net..
ie for mike like:
1) scope: 192.168.5.10
2) laptop: 192.168.5.1
3) mask:255.255.255.0
or something along those lines!
BTW, since you are a hardware guy, you should check out the mods on here to push your BW up to 500Mhz, just requires you taking apart the scope, breaking the warranty of course and replacing some surface mount components, it's honestly not bad if you have decent soldering tools?
I did it to mine as was not painful at all..
Also, once you get a homebrew LAN board in, it will give you a nag message that pops up about a LAN board malfunction or whatever it says, but that's just because our board doesn't have the VGA chip on it that the real board has, but doesn't matter, all we need is ethernet..
And also, your other prior question, YeS, all that LAN board really needs is the ethernet connector and a few passives, all the other crap I added was just as a bonus, but not necessary at all. And you have to open up your scope anyhow to connect up any JTAG or USB boot stuff.. so LAN is really all you need.
Also, I love Altium, its a bad-ass tool, I'm slowly doing training to try and switch over to it, as I've been using nothing but eagle the last 10+ years. So i'm sooo used to it, but Altium has so much more power.
Here ya guys go..
Patched 3000X 2.50 Firmware with 'options' and 'nag' patch already applied..
https://mega.nz/#!eqg0yYJK!l73FwnABwNBNsl_l_2fAC8Md8PCVEEBgZ-u0T1eNZ08
I have seen two different ways of doing this - one is simply running the OS from the flash drive, which I am not terribly interested in doing because I would like to be able to use a flash drive to capture screenshots. The other is a permanent change that does not require the USB drive to be plugged in for operation. Is this method the former or the latter?
So just install that update file I posted via USB drive (format it to FAT32)... you just browse to the USB drive via the I/O menu, and select the file and run it...
once it reboots you should be able to telnet in a drop your lnk file, and then reboot,and all should be there...
Firmware 2.43
There's a list of the Telnet instructions here
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/ren
I think what you posted looks correct, but I would try and rename the old one first by navigating to the secure folder then renaming it using the rename command.
I've ordered the stuff for the DIY LAN too. I have hacked my scope but want to get rid of the nag messages.
You can just add a new start.lnk file (any name you want) next to the empty official infiniiVision.lnk file.
I got the re-built CAB file to work
<command>\windows\cmd.exe /c copy \usb\infiniivision.lnk \Secure\Startup\infiniivision_ext.lnk</command>
-<onFailure>
<filePath>\usb\errorLog.txt</filePath>
<message>lnk copy from USB failed.</message>
<!-- do not continue, without new valid link file -->
<action>reboot</action>
</onFailure>
</installStep>
<!-- Move away a perhaps existing factory link -->
-<installStep>
<command>\windows\cmd.exe /c ren \Secure\Startup\infiniivision.lnk infiniivision.lnk.original</command>
-<onFailure>
<filePath>\usb\errorLog.txt</filePath>
<message>No factory lnk to move away.</message>
<action>continue</action>
</onFailure>
</installStep>
For all Keysight 3000A uses who have the startupmessage: