I borrowed a LeCroy Wavesurfer 44XS scope.
I had used LeCroy scopes previously, and know they are very high performing instruments.
But never used one with a Windows interface. Windows XP.
From a cold start to the time one can actually start manipulating the controls, it takes 6 minutes and 20 seconds to boot.
This is normal as these scopes came with painfully slow 2.5" Fujitsu and Toshiba hard drives, and if your scope still had the original one then there's also a good chance it was fighting with an increasing number of bad sectors (common for these drives).
In addition, LeCroy skimped a bit when it came to RAM (IIRC the WRXs has 256MB standard) and CPU (IIRC a Celeron-M) in these scopes which didn't help.
Luckily, these problems are easily fixable with an EIDE SSD, more RAM and a faster CPU, and for little money.
Even after boot, the screen freezes from time to time.
Which may hint to the hard drive being on its way out.
I had previously used another Windows scope, an Agilent if I remember correctly, and had also despised it.
If that was one of the early Infiniium generation scopes (548xx Series) then this is understandable, as these scopes came with similarly slow hard drives and little RAM, and on top of came with a clunky UI that was designed for mouse operation.
What is your experience with Windows scopes?
Very good, actually.
Yes, boot times are, even with SSDs, longer than with a cheap embedded platform scope, but considering that any scope only reaches its full spec compliance after a warm-up period (usually around 20mins) who cares? These scopes are made for professional environments where they are normally powered on in the morning and switched off at night (or remain powered 24/7).
But Windows allows me to run other software on the scope without the need for a separate PC. We often use MathLab or our own software to perform specialist signal analysis, which even on older LeCroy scopes was made easy thanks to a set of APIs.
Then there's mundane stuff like how easy it is to network the scope and access or provide data shares, remotely access the scopes (although embedded scopes got some way to that thanks to their built-in web interface, which is still much slower than RDPing into a Windows scope), or the simple fact that I can access pretty much any size of USB storage media, no matter if it's formatted in FAT32, NTFS or exFAT.
The problem I see to embed Windows on a piece of equipment, is that the OS may become obsolete while the instrument itself could still be a high performance one.
And yet no Windows XP based scope stopped working because Microsoft ended all XP support, but instead continues to function as well as it did when XP was still a supported OS.
You probably also didn't spend much time thinking in the often creepy software that is lingering in embedded devices, including the crop of cheap embedded platform scopes running some antique version of the Linux kernel with some similar dated versions of other FOSS packages, most of which won't ever see any update.
A test instrument, even if it runs Windows, is not a PC, it's a piece of kit that fullfills a function. And it does this no matter if the OS is current or old.