OP: You should sell your 3000x immediately, sounds like a total lemon (lol).
Your 1st post ever was a reference to the wavegen on the 3000x and now this your 2nd post. Is there a real purpose to your two posts or just trying some mud raking?
I personally am super happy with my 2000x.
cheers,
george.
Is that not allowed to say critical things about Agilent or Keysight? Come on guys!
Back to the behavior: it just sucks, I was looking for a protocol error, it was tricky to get it on the screen in multiple segments and than I pushed something over my keyboard pressing the power off button down. For the first time I did not realized that it was caused by the keyboard. I thought the scope has crashed, and all my thoughts were "
why the f*ck did they picked windows for their scopes? these idi*ts!". Than some days or weeks later I realized that it was the power off button.
I told to Keysight's support september/october, last year, I thought they would fix it with the next firmware, because it wouldn't be that difficult to do it, but they didn't.
Actually I'm very happy with my 3024, I also own an Agilent DSO5014. These are the best scopes for my budget! In some terms, the DSO5014A is even slightly better than my DSO X-3024A in things like display, memory size and useability (key layout, knob quality). But the comparison of the both is off-topic here.
Funny. You're using solid AND expensive equipment and hanged a lousy el chapeau keyboard on it with fancy keys you don't need? Get a decent one like a Filco or so.
Why it is funny? Cheap things operate great with expensive ones, just take a look at your power cord
did ya try to enter a filename saving multiple screenshots? no, really, it's not funny using that small "jog shuttle".
So for only that reason, i picked up a cheap wireless keyboard which was just lying around, and it does very good job. I do not write books on it.
I wonder, is that the only reason picking windows as an operating system for a scope: to enable keyboard?