Products > Test Equipment
Rohde & Schwarz RTO1024 upgrade ??
jjoonathan:
I forgot how many screws were in this thing -- this is probably the last time I volunteer to go inside out of generosity alone. Here is the EEPROM. Good luck!
TRN:
Does anybody know if it is possible to upgrade an RTO1000 from Win7 to Win10?
jjoonathan:
Ah, you were asking about Win 7->10 not Win XP->7, so this thread doesn't actually answer your question. My bad!
I do have some info for you, though: the "firmware" installer works on Win10 in that it drops the app and drivers in place. I ran it in one of those free-from-Microsoft Internet Explorer compatibility test VMs once, so there was no actual oscilloscope hardware and as a result the app did not run, but their coding style is very by-the-book (stub drivers, communication through COM) so I bet it Just Works if you install Windows 10.
I didn't actually go forward with installing Windows 10 on my scope because Win7 works and I don't want Win10-isms like background updates to Candy Crush or bundled advertisements to tank my framerate.
TRN:
Thanks and no problem.
The reason I am asking is that I actually installed win10 on my RTO, and to avoid issues with background updates and other installations of win10 bogus bloatware, I installed the Enterprise 2019 LTSC version, which should not have this problem.
The installation went well, but while installing firmware version 3.70, a win10 error popped up initiating a restart, after which the operating system refused to boot.
All win10 repair attempts failed, so the only way to get Win10 to boot was to restore it to before the firmware installation.
I also tried to install firmware version 4.75, and this installation actually completed, but after the required reboot Win10 ran into the same problem
jjoonathan:
Good call on the LTSC version. Sounds like the drivers really are incompatible, though. Since neither 3.7 nor 4.5 drivers prevented my win10 VM from booting, I suspect it's actual code that's breaking, not just a silly metadata version compatibility check or something. Bummer.
In addition to the critical drivers and services (a PCIe driver for the analog front end, a SPI driver (over USB, maybe?) to load EEPROMs and such, and a service to read licenses off the smartcard) there are a bunch of less-necessary ones. If the problem is with one of those, there might be hope. I'd check by booting into safe mode and disabling the critical stuff in device manager. If that fixes the boot, it's bad news, and means the problem is with a critical driver. If not, it's good news, and you could track down the non-critical culprit, disable it, and be good to go.
Even if that didn't work, permissions are another "silly" thing that tends to mess with compatibility and ultimately be fixable. There might be some hope down that road, but I'm not a windows driver guy, so I don't know if there are "compatibility" flags to set on drivers like there are on EXEs.
Obviously I'm just throwing things at the wall, here. It really depends how far you want to chase this down. Good luck and keep us updated if you decide to give it another round!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version