Gonzo, I'm glad someone is paying attention.
1. The Freeze Bug is NOT intermittent. Some scopes have it and some +may+ not have it (I'm still not convinced that those with Boot Version 0.0.1.2 who "don't" have it are following directions exactly...). If your scope has it, then it will freeze _every time_ that the proper conditions are met. I should have thought this was evident from my videos. An "intermittent" problem happens sometimes and doesn't happen other times and is unpredictable. This problem is totally reproducible every time and is a clear defect, not an "intermittent" fault.
2. The Math error is not just "offset one division". It is more like the horizontal scale of the Math trace is different than that of the two traces that are going into it. That is, the offset is small on the left edge of the screen and is greater on the right edge of the screen. This is one reason why I use a +square wave+ pulse train to illustrate it: it is easy to see that the Math result is not just offset, it is actually _wider_ than it should be on the right edge of the screen. Look carefully at the scopeshots I've attached below. This is also NOT an "intermittent" bug, it occurs reliably whenever the conditions are met.
3. As far as the "pluses" counter goes, I showed that the counter counts pulses correctly when two channels are on but miscounts when a third channel is on, using _exactly the same_ signal. So this can't be a result of "ringing" or whatever, it's a result of turning on the third channel. Again, please see the scopeshots below. And again, the conditions for this are fairly specific. I can count manually when there are ten pulses on the screen, but can I rely on the "Pluses" counter to be correct in all cases when there are thirty or fifty "pluses" on the screen and I have three channels in use? So really, why should I use the pulse counter at all if it's going to give me a different count depending on how many channels I have turned on?
4. The Rigol USA tech Jason sent me email offering to exchange my scope for a new one that doesn't have the bug, with them paying the shipping both ways. I didn't ask for this, he offered it. So I emailed him back and said OK, fine, send me the new scope and I'll put mine in the box and send it right back to you. He came back and said.... No, I have to send them my scope _first_, with all accessories and etc. and after they receive it _then_ they will send me a new one. Since I use the scope every day, I declined this "kind" offer, and suggested that they simply provide a way to update the Boot Version on those scopes with 0.0.1.2, up to 0.0.1.3 and maybe this will fix it for all of us who have the bug. I mean, what happens if I send them my scope, and then they send me a new one, and it turns out to have unacceptable bugs, or a hardware glitch or something? Then I'm out the use of a scope for _weeks_ perhaps, and I can't abide that. I use my scope every day in my work and I can generally work around the various bugs and annoyances. I also pointed out that I've spent tens of hours tracking down and explaining and demonstrating the various bugs and that my time is worth something. Heck, if I actually billed Rigol for my time finding problems with their product that they didn't even know about, it would be for a lot more than the cost of a brand new 1054z. So I'm not sending mine back unless they send me a new one FIRST. At which point I will examine it and test it for the various bugs and annoyances, and if it works as it should, THEN I'll box mine up and ship it back to them. And I'll post how great Rigol Customer Service is and make a YT video extolling the virtues of Rigol and its CS.
So we'll see where it goes from there.
1. The scopes with Boot Version 0.0.1.3 do not seem to have the Freeze Bug.
We need a new poll to confirm that.
BTW: Do you know of the video that shows how quickly the buttons need to be pushed to get the full system info ?
I don't want to erase or reset the poll that we've already established. As far as I am aware, though, nobody with 0.0.1.3 has reported being able to reproduce the Freeze bug. I don't know about the Math error though. Hopefully if anyone with 0.0.1.3 _can_ make their scope freeze, they'll report it here, as well as reporting it to Rigol.
I also don't know of a video that shows how quickly the buttons need to be pressed. All I can say at the moment is that pressing them at "normal" speed (my normal) isn't fast enough, as I demonstrated in my last-but-one video on the topic. So my advice is to practice, and if at first you don't succeed.... press the sequence _even faster_.