Blimey, I'd try getting out of the other side of the bed tomorrow!
I'd have thought there was enough similarity such that the input is worth noting down. They use the same firmware releases.
The -S is a daughter board and an extra button on the front panel. The MSO is a few extra populated parts on the main board, and an extra button and connector on the front panel.
The price differential is because they can get away with it, the raw cost in parts is less than $20 between a DS1054Z and an MSO1100Z. Similarly, the -S daughter board plug in is about $30.
Should you also discount DS1074Z(-S) and DS1100Z(-S) users too?
I do apologize for being terse.
But yes, the introduction of different models into the survey adds too many variables to the mix. As far as I am aware, the problem has not been reported in those models, or in yours. So you should be able to see that including a "no" vote from a population of _different_ models that have not exhibited the bug is kind of "statistically invalid". While the scopes do use (mostly) the same hardware and software, it is quite likely that they come off different production lines, have their components picked from different reels or batches, etc. I appreciate your trying the test, but even if you had reproduced the bug I still would object to including the result in _this_ poll.
If anyone with a different 1000 series model actually _can_ reproduce the bug as it is detailed here -- then we can start another poll if you like, widening the catch to all 1000 series scopes, or specifically dealing with one or the other of the models.
The DS1054Z, "hacked" to 100MHz, or "virgin" unhacked, and running Firmware revisions 04.02 and 04.03, are subject to the Bug in about 50 percent of the units tested, or perhaps even more.
I'd still like to know if those who have the Bug can reproduce the "start-up-frozen" state after shutting down an _unfrozen_ scope, as I show in the video above. It's quite easy to do, since the fact that the Mem Depth automatically resets to "Auto" means that one of the bug conditions is set for you by the scope when you start up. All you need is the three other conditions: Persistence other than Min, main timebase 1us/div or faster, and Delayed timebase (horizontal zoom) engaged. Shut down (with "last" as your power-on setup setting) in that state and when you restart... your scope is locked from the get-go.