Hacking the Rigol MSO5000 series oscilloscopes

[BTO]

So to be clear
1. You're not even going to address anything
2. You're not even going to answer the questions that were asked
3. Nor consider what i asked you to consider

No

I'm not sure why you are stirring the pot.

tv84 clearly communicated the two licensing hack options to clear up some misinformation in your earlier posts.
You replied with a lot of long-winded nonsense that I doubt many will read in full (I didn't).

OK well, You're not sure why i'm stirring the pot because..........................

I'M NOT STIRRING THE POT
I asked 3 questions.   that's not stirring a pot,  that's called ... Asking 3 questions for clarification.

TV84  did not CLEARLY comminicate
TV84 said a few thing
then added some degree of bullshit
then assume a few things
then asked me questions
that i answered
that he then didn't address

Hardly.. clear

but , No, i'm not stirring a pot.   My comment to him was a chance for him to acknowledge what he's doing to people
and out of respect to rectify his behaviour

AGAIN............. WE NEED TO RESPECT EACH OTHER ON THE FORUM
Do you not agree ?

If you look back in the comments.  the problem starts when TV84 started throwing low blows and insults.
Prior to that , everything was fine

as for the long post........... I COULDN'T CARE LESS HOW LONG IT IS OR WHO READ IT OR WHO DIDN'T
You are not causing me any offense by tellingme you didn't read it,  what you are doing is showing me what sort of person you are.

but that aside...
Is it not reasonable to ask of ANY MEMBER regardless of their skill level,  THAT WE RESPECT EACH OTHER ?
is that not a fair call

and.... when a misunderstanding occurs,  say.. Like you assuming that i'm stirring a pot
is it not a fair ask to have the other person admit they made a mistake.
NOT..  because i want to put them in a corner,   but because  they made a mistake,   both you and him.

See.. i'm not trying to pin you in a corner,   but... TO BE HONEST  i'm not going to accept the comment that i'm stirring a pot
when i'm not.   Now.. is that not fair enough ?

and with TV8    i asked a few fair questions
TV8  just pissed off, without addressing anything............ that's a bullshit act
Where is the responsibility for one's actions

Are we idiots here, or are we intelligent people that know how to work shit out ?
Do we take responsibility for our actions, or do we run away
Do we admit that we are wrong when we are wrong or we do we hide

ARE THESE NOT FAIR POINTS ?

[BTO]

So to be clear
1. You're not even going to address anything
2. You're not even going to answer the questions that were asked
3. Nor consider what i asked you to consider

No

I'm not sure why you are stirring the pot.
tv84 clearly communicated the two licensing hack options to clear up some misinformation in your earlier posts.
You replied with a lot of long-winded nonsense that I doubt many will read in full (I didn't).

Also.... Quick question (and i'm not starting shit, i'm just asking a question)
You haven't been involved in this,   so .. why have you jumped in all of a sudden ?
What's your motivation to be here... I'm just curious

[dcac]

so... Do you have like a PTSD thing where things need to be kept brief ?  Because call me crazy, but i'm sensing a theme here.

I’m not the guy to report any posts. But can we please just keep comments like this out of this forum... you know... please!

[BTO]

so... Do you have like a PTSD thing where things need to be kept brief ?  Because call me crazy, but i'm sensing a theme here.

I’m not the guy to report any posts. But can we please just keep comments like this out of this forum... you know... please!

Sure, No problem.
this was just my way of asking him why he's wanting to censor me to a word limit,,   this also was not a rude comment.
i think part of the problem here is, that people are jumping to too many conclusions

i also want to get back on topic
i also want everyone to be fair
also notice how the last 2 people haven't responded and all i'm trying to do it fix it up, while getting accused that i did the wrong thing.

but yeah,  I'm happy to oblige your request,
Although understand let's get the other guy to also not censor people on what they want to say and how long it should be

FAIR ENOUGH ?
As i keep saying,   WE NEED TO RESPECT EACH OTHER,   Not try to dominate and control each other
and you don't need to say PLEASE,   Asking is enough,  and i can happily oblige

Now, it seems to me these guys aren't going to respond to my posts
SO.......... IF EVERYONE IS DONE WITH THIS B.S..... I'M HAPPY TO GET BACK ON TRACK WITH THE SUBJECT OF HACKING THE MSO5000


What say you all ?

[Kean]

Also.... Quick question (and i'm not starting shit, i'm just asking a question)
You haven't been involved in this,   so .. why have you jumped in all of a sudden ?
What's your motivation to be here... I'm just curious

Huh?  You are posting in a public forum with hundred if not thousands of people likely to read this.  My motivation was to hopefully make you aware that you were being disrespectful.

You keep on going on about respecting each other, but I didn't spot any significant disrespect from tv84.  I see repeated and clear disrespect in your postings with things like

YOU RESPONDED in a completely useless manner

I can respect your efforts in helping the community and the videos that you produced.  I don't have to respect your rants.

But I will stop there, as I do want us to all get back on track.  I'll wade through you prior posts and if I can answer on-topic questions I may reply further.

[Kean]

OK BTO, I went back and read through your last handful of posts and I didn't spot any clearly formulated on-topic questions.  Maybe I missed them.
While I am not at the skill level of tv84, I am honestly happy to help clear up any technical points that I do understand.

So feel free to re-ask them ... but maybe without the excessive off-topic text... 

[BTO]

Also.... Quick question (and i'm not starting shit, i'm just asking a question)
You haven't been involved in this,   so .. why have you jumped in all of a sudden ?
What's your motivation to be here... I'm just curious

Huh?  You are posting in a public forum with hundred if not thousands of people likely to read this.  My motivation was to hopefully make you aware that you were being disrespectful.

You keep on going on about respecting each other, but I didn't spot any significant disrespect from tv84.  I see repeated and clear disrespect in your postings with things like

YOU RESPONDED in a completely useless manner

I can respect your efforts in helping the community and the videos that you produced.  I don't have to respect your rants.

But I will stop there, as I do want us to all get back on track.  I'll wade through you prior posts and if I can answer on-topic questions I may reply further.

ok well, in the spirit of responding to that briefly , but also getting back on track

Mate.  I wasn't being rude, i said it was a useless comment because it was.
you say you didn't see any rude comments of his........ I DID

but let's put that aside,
Let's address this

"  I'll wade through you prior posts and if I can answer on-topic questions I may reply further."
NO NEED TO WADE
i only really had 2 points prior to all this

In Brief.....
TV84  was saying that the way i was upgrading was not actually licencing the scope but instead bypassing licencing.
My point to that was, .. since the scope said licenced, obviously i drew the conclusion (as anyone would that it was) I just asked for clarification on that


He then suggested that there was a method by another member (Can't remember his name off hand) that does permanently licence the scope.
Question 2 was...
I have a JTAGulator and Arduino boards,  the question was...  Can i use my JTAGULATOR board to execute the process required

and lastly...  My scope is currently unlocked (via patch) on version 1.3.3.0
now. if i wanted to do this process , Given that my scope is currently unlocked and up to current version, is it possible for me to do that
and if so , How (Briefly stated)

those were really the only 3 points i needed addressed

finally (in case it was missed)  he said i didn't bother to read what the other member put in as the process....
Mate, it's not a question of  DIDN'T BOTHER
it's a question of , i had 6 family members and friends recently pass, of them my dad and best friend ok,
so, have i NOT kept up ?   Yes i am guilty of that.
But i reckon i have a pretty good reason.   it's not like i didn't give a shit on purpose .

so, if you want to help,  it would be awesome if you could answer those 3 questions
thanks ahead of time

[BTO]

OK BTO, I went back and read through your last handful of posts and I didn't spot any clearly formulated on-topic questions.  Maybe I missed them.
While I am not at the skill level of tv84, I am honestly happy to help clear up any technical points that I do understand.

So feel free to re-ask them ... but maybe without the excessive off-topic text... 

already have, Read my latest post before this one

[Kean]

TV84  was saying that the way i was upgrading was not actually licencing the scope but instead bypassing licencing.
My point to that was, .. since the scope said licenced, obviously i drew the conclusion (as anyone would that it was) I just asked for clarification on that

He then suggested that there was a method by another member (Can't remember his name off hand) that does permanently licence the scope.

Question 2 was...
I have a JTAGulator and Arduino boards,  the question was...  Can i use my JTAGULATOR board to execute the process required

and lastly...  My scope is currently unlocked (via patch) on version 1.3.3.0
now. if i wanted to do this process , Given that my scope is currently unlocked and up to current version, is it possible for me to do that
and if so , How (Briefly stated)

those were really the only 3 points i needed addressed

OK, I think I can answer those in one hit as they are all related.

The "firmware hack" method of licensing the scope as mostly discussed here, and what I believe you include in your notes and videos modifies the firmware to just bypass certain license code checking and thus enables all licenses.  This means that is it not permanent in the sense that it only applies to the hacked firmware.  If new firmware is flashed via a restore or upgrade then the hack is lost and only saved & valid license keys are active.

The "FRAM hack" script by DrMefistO uses an extracted signing key to generate valid option keys for your MSO5000 serial number and saves them to the scope via direct FRAM access over a scripted SSH connection and also some SCPI commands.  I think I have that correct, but I may have some of the exact details wrong.  I haven't tried it myself.
This script is in post 2739 at https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg5372468/#msg5372468 (and possibly earlier posts)

The comment by tv84 was that it does this in a potentially unsafe way (direct FRAM access) and there is most likely some undocumented SCPI commands to do it more safely.

No need to play around with a JTAGULATOR or Arduino stuff, but if you are at all familiar with Python code then the script is in the above linked post and you are welcome to dive into how it works.

To wrap up, if you reflash or upgrade to stock firmware you will lose your current hack and have only the licensed original options.  You can then try the process by DrMefistO (if you dare) and potentially get permanent keys installed for all options that should continue through future firmware upgrades.  Please report back if you do this and succeed or fail.

already have, Read my latest post before this one

Yeah, you don't really need to respond to every post...

[BTO]

TV84  was saying that the way i was upgrading was not actually licencing the scope but instead bypassing licencing.
My point to that was, .. since the scope said licenced, obviously i drew the conclusion (as anyone would that it was) I just asked for clarification on that

He then suggested that there was a method by another member (Can't remember his name off hand) that does permanently licence the scope.

Question 2 was...
I have a JTAGulator and Arduino boards,  the question was...  Can i use my JTAGULATOR board to execute the process required

and lastly...  My scope is currently unlocked (via patch) on version 1.3.3.0
now. if i wanted to do this process , Given that my scope is currently unlocked and up to current version, is it possible for me to do that
and if so , How (Briefly stated)

those were really the only 3 points i needed addressed

OK, I think I can answer those in one hit as they are all related.

The "firmware hack" method of licensing the scope as mostly discussed here, and what I believe you include in your notes and videos modifies the firmware to just bypass certain license code checking and thus enables all licenses.  This means that is it not permanent in the sense that it only applies to the hacked firmware.  If new firmware is flashed via a restore or upgrade then the hack is lost and only saved & valid license keys are active.

The "FRAM hack" script by DrMefistO uses an extracted signing key (I think, may have the exact details wrong) to generate valid option keys for your MSO5000 serial number and saves them to the scope via direct FRAM access over a scripted SSH connection and also some SCPI commands.
This script is in post 2739 at https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg5372468/#msg5372468 (and possibly earlier posts)

The comment by tv84 was that it does this in a potentially unsafe way (direct FRAM access) and there is most likely some undocumented SCPI commands to do it more safely.

No need to play around with a JTAGULATOR or Arduino stuff, but if you are at all familiar with Python code then the script is in the above linked post and you are welcome to dive into how it works.

To wrap up, if you reflash or upgrade to stock firmware you will lose your current hack and have only the licensed original options.  You can then try the process by DrMefistO (if you dare) and potentially get permanent keys installed for all options that should continue through future firmware upgrades.  Please report back if you do this and success or fail.

already have, Read my latest post before this one

Yeah, you don't really need to respond to every post...

"OK, I think I can answer those in one hit as they are all related."
Cool, Thank you

"The "firmware hack" method of licensing the scope as mostly discussed here, and what I believe you include in your notes and videos modifies the firmware to just bypass certain license code checking and thus enables all licenses.  This means that is it not permanent in the sense that it only applies to the hacked firmware.  If new firmware is flashed via a restore or upgrade then the hack is lost and only saved & valid license keys are active."
OK You seem to be an I.T. Guy, as am i,  so its safe to say we both understand how firmware works when a new version is applied.
OK, so this is understood, Granted it was a bit misleading (of the scope, not the forum) when it said licenced... but ok, we understand each other.

"The "FRAM hack" script by DrMefistO "
That's him, thanks, i dropped his name

"The "FRAM hack" script by DrMefistO uses an extracted signing key (I think, may have the exact details wrong) to generate valid option keys for your MSO5000 serial number and saves them to the scope via direct FRAM access over a scripted SSH connection and also some SCPI commands.
This script is in post 2739 at https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg5372468/#msg5372468 (and possibly earlier posts)"
Right, .. this was the part where i was under the impression where i needed some manner of dev board to extract the key, which is why i brought up Arduino boards and JTAGulator

Also i was asking tV84 , since it's a somewhat unsafe method,    what was the success rate on it, approx.

"No need to play around with a JTAGULATOR or Arduino stuff, but if you are at all familiar with Python code then the script is in the above linked post and you are welcome to dive into how it works."
I'm a hardware guy,  but still. Yes, i'm familiar with Python

"To wrap up, if you reflash or upgrade to stock firmware you will lose your current hack and have only the licensed original options.  You can then try the process by DrMefistO (if you dare)"
Because THAT INSTILLS A LOT OF CONFIDENCE, HUH ?    LOL

" Please report back if you do this and success or fail."
OK,  i'll potentially blow up my scope and take one for the team and report back and let you guys know if i stuffed it  or got lucky,  No probs

Tell me something...
if you know

if i try this process and it doesn't work,  am i still able to revert to the upgrade and patch method if it doesn't work ?

[Kean]

OK You seem to be an I.T. Guy, as am i,  so its safe to say we both understand how firmware works when a new version is applied.

Yes, I'm an IT/embedded systems guy.  I spend about 50% of my time with hands-on electronics, and 50% on firmware or IT (coding/support/architecture/etc).

Also i was asking tV84 , since it's a somewhat unsafe method,    what was the success rate on it, approx.

Not sure if that is known.  At least one person seems to have used it with success if you read the posts following #2739 (user zauberpilz had problems at first in #2742 & 2744, then reported success in #2746)

if i try this process and it doesn't work,  am i still able to revert to the upgrade and patch method if it doesn't work ?

No idea, which is why I included some disclaimers.  I wasn't involved in the development of these, and I've only used the simple firmware hack on mine.

If I ever decide to try it, I would start by reading through the Python code to try my best to understand what it was doing.  I've only scanned the code quickly so far to get a high level overview.

I would also use an SSH session to the scope and make a backup of the FRAM via dd command to a USB drive.  I guess this could be done via direct hardware access to the FRAM chip, but that seems like it could cause more trouble.  There is already a pseudo device available in Linux to access the FRAM.

[Simon]

shall we calm down, don't try to police stuff yourselves because I am not going back pages and pages through what was said.

[thorstormlord]

I used the python way first and it just deleted my pischased add-ons and left the scope as it was originally. The "upgrades" way worked fine but I did dd my scope just to be safe,so I guess I can revert to previous state if something happens. If BTOs way is bypassing licencing then I guess the new firmware will.mwss up the licencing, since I haven't been involved in the process building I can't be sure though.
Will the new firmware go through licence checking when installed ?

[thm_w]

Will the new firmware go through licence checking when installed ?

As explained above, the commonly used hack here is a modification of the files on the scope. Any new firmware upgrade, or downgrade, will rewrite the application and bring the scope back to stock.

The chance of a new firmware release is very low, but its good to know if one is released, not to rush out and install it since you'll lose all your options.

[BTO]

OK You seem to be an I.T. Guy, as am i,  so its safe to say we both understand how firmware works when a new version is applied.

Yes, I'm an IT/embedded systems guy.  I spend about 50% of my time with hands-on electronics, and 50% on firmware or IT (coding/support/architecture/etc).

Also i was asking tV84 , since it's a somewhat unsafe method,    what was the success rate on it, approx.

Not sure if that is known.  At least one person seems to have used it with success if you read the posts following #2739 (user zauberpilz had problems at first in #2742 & 2744, then reported success in #2746)

if i try this process and it doesn't work,  am i still able to revert to the upgrade and patch method if it doesn't work ?

No idea, which is why I included some disclaimers.  I wasn't involved in the development of these, and I've only used the simple firmware hack on mine.

If I ever decide to try it, I would start by reading through the Python code to try my best to understand what it was doing.  I've only scanned the code quickly so far to get a high level overview.

I would also use an SSH session to the scope and make a backup of the FRAM via dd command to a USB drive.  I guess this could be done via direct hardware access to the FRAM chip, but that seems like it could cause more trouble.  There is already a pseudo device available in Linux to access the FRAM.

"Not sure if that is known.  At least one person seems to have used it with success if you read the posts following #2739 (user zauberpilz had problems at first in #2742 & 2744, then reported success in #2746)"

I plan to go through that, thanks

"No idea, which is why I included some disclaimers"

Understood,  Thanks

[BTO]

shall we calm down, don't try to police stuff yourselves because I am not going back pages and pages through what was said.

i believe everyone is calm, We've all moved forward, that topic is now over.
i was just asking for a bit of courtesy and respect, the others , it seems have ceased the conversation, and we have returned to the original
topic, so it's all cool

If you feel that you want to delete that part of the conversation for the sake of contiuity, (Speaking only for myself) You have my blessing
to do so, i'm cool with that.
In any case, that issue is no longer an issue. we've moved on

[BTO]

I used the python way first and it just deleted my pischased add-ons and left the scope as it was originally. The "upgrades" way worked fine but I did dd my scope just to be safe,so I guess I can revert to previous state if something happens. If BTOs way is bypassing licencing then I guess the new firmware will.mwss up the licencing, since I haven't been involved in the process building I can't be sure though.
Will the new firmware go through licence checking when installed ?

No.. From what i can gather, he is saying  or (they) are saying that when the new firmware comes out we'll have to patch it again.
They are saying that when new firmware is installed the patch won't be preserved and the current patch doesn't permanently licence the scope
but instead just applies a patch, sort of .. to trick the scope i suppose.

I'll have a read through the notes and see if i can get that SSH Method to work

i suppose this then makes me wonder, why is the MSO5000 process different to the DS2000A.
if i remember... With the DS1052E there was a pre shared key that we just had to enter
then with the DS2000A series that key had to be generated by using your serial number, Initially it was a manual process than a forum
contributor attached a piece of software that combined all the steps and made it easier, which basically installed the drivers
and did the process more or less automatically, so essentially A LEGITIMATE LICENCE WAS GENERATED AND STORED.

Now i was under the understand that Part of the job that the patch did was exactly that.
Step 1 is the back,,  that makes sense
Step 2 is the upgrade, that makese sense
Step 3 is the patch,    I guess we have now learned that the patch doesn't licence the stop but applies a temporary (Current version only)
licence and unlock.

Oh well, i guess i'll try the SSH road (perhaps) and see what happens.  However, i will first read through all the notes and examine the code
to see what's what

[BTO]

Will the new firmware go through licence checking when installed ?

The chance of a new firmware release is very low, but its good to know if one is released, not to rush out and install it since you'll lose all your options.

Not really. I can at least guarantee you 1 more future version as i'm talking to rigol at the moment on fixing a few things with the scope
that can only be fixed in firmware updates. and they have agreed they are taking these matters seriously, but have also stated they don't
know exactly when a new firmware version will be released, However they did say they do want to fix these things.
so.. there will be another coming at the least

[normi]

I think we ended up in this patch method of hacking the scope because there was a rush to unlock the scope and that was the first method that worked. I assume that there may be license key hacks out there which have not been released, not sure why the secrecy  but we need a permanent fix so that persons do not have to wait on someone to create a new patch each time a new firmware is released.

As it relates to Rigol and firmware, they are very slow with that so I would not expect anything soon.  I had an experience with support in the past where I complained about the X-Y feature which had a major flaw, and they offered me a firmware that fixed the issue. I thought a new firmware would soon be announced with the fix but it took 9 months before they released the fix, I had to create my own patch since the firmware I had was not released. You can asked them if they have any unreleased firmware which they can give customers.

[BTO]

I think we ended up in this patch method of hacking the scope because there was a rush to unlock the scope and that was the first method that worked. I assume that there may be license key hacks out there which have not been released, not sure why the secrecy  but we need a permanent fix so that persons do not have to wait on someone to create a new patch each time a new firmware is released.

As it relates to Rigol and firmware, they are very slow with that so I would not expect anything soon.  I had an experience with support in the past where I complained about the X-Y feature which had a major flaw, and they offered me a firmware that fixed the issue. I thought a new firmware would soon be announced with the fix but it took 9 months before they released the fix, I had to create my own patch since the firmware I had was not released. You can asked them if they have any unreleased firmware which they can give customers.

I think we ended up in this patch method of hacking the scope because there was a rush to unlock the scope and that was the first method that worked.

hmm i see

but we need a permanent fix so that persons do not have to wait on someone to create a new patch each time a new firmware is released.

This is true,  it does seem to be the case that the SSH method is the way to go, IT JUST DOESN'T SEEM TO BE HIGHLY RELIABLE. (at least going off what forum members are saying and how many DISCLAIMERS   LOL we seem to be getting from it .
but i agree, that the people doing is the favour of creating these fixes shouldn't be bothered EACH TIME a new firmware update comes out.
i mean we are no longer bothering with the DS1052E and the DS2000A as that's sorted and done.
Why should the MSO5000 be any different ?

As it relates to Rigol and firmware, they are very slow with that so I would not expect anything soon.

Hey.. I'm not expecting it tomorrow, But in truth, the problems are
- Bad Spelling errors in the SELF CHECK process
- Massive amounts of bad spelling and grammar in the HELP menu
(and truthfully i only encountered this because i went ahead and did those videos. the HELP menu in the DS2000A was easier to access, the
one in the MSO5000 was not obvious so i didn't pay it much mind, it wasn't until thorstormlord showed me how to access it that i became aware
of the mistakes, and at that time it was only a few mistakes, but then i actually took the time to read through it and discovered, wow..
there's like, quite a few)
Now a person may argue... who cares.
Well i reckon if we pay this much for the scope they should get it right. and Rigol has agreed that the team that do this part of the development
are in a non english speaking country. Who made that choice... god only knows.   Anyway, they are taking it seriously and have every intention
of rectifying it, and i going through the menu with a fine tooth comb and will send them a PDF of the errors.

There's also stupid crap in the menu like....
it'll say, THIS OPTION ONLY AVAILABLE IN MSO7000 
Well then... Why did you put that in a MSO5000 scope.   Kinda dumb isn't it ?

- Beyond that i've spoken to them about the slowness of COLOR GRADE  and to see if we can get that sped up so it's useful.

- As well as mentioning that if we have a timebase, that timebase should have enough memory to support a quick refresh rate.
Meaning, No one needs 1,000 sec/Div  . My suggestion was that 5 sec/Div was more than enough maybe 10 at the slowest, Who measures
those frequencies anyway ?

but yeah i expect it'll take some time before they release a new one

You can asked them if they have any unreleased firmware which they can give customers.

i could, but i think i'll let them get it out in their own time and properly test it

[mabl]

There's also stupid crap in the menu like....
it'll say, THIS OPTION ONLY AVAILABLE IN MSO7000 
Well then... Why did you put that in a MSO5000 scope.   Kinda dumb isn't it ?

If you are talking about stuff like the Eye Diagram (that also don't work), that is because you have patched the firmware. It does not show up on unpatched firmwares. The patch just short-wires the capability check to return "I can do this" on any feature check - included the ones that are normally gated by the MSO7k/5k difference.

[BTO]

There's also stupid crap in the menu like....
it'll say, THIS OPTION ONLY AVAILABLE IN MSO7000 
Well then... Why did you put that in a MSO5000 scope.   Kinda dumb isn't it ?

If you are talking about stuff like the Eye Diagram (that also don't work), that is because you have patched the firmware. It does not show up on unpatched firmwares. The patch just short-wires the capability check to return "I can do this" on any feature check - included the ones that are normally gated by the MSO7k/5k difference.

"If you are talking about stuff like the Eye Diagram"

No i actually wasn't even remotely referring to Eye diagram.

"(that also don't work), that is because you have patched the firmware."

Well, that's strange because i have patched firmware and i can use eye diagram

But what i actually was referring to (As 1 Example) see the attached photo

in the SAMPLING RATE section of the help menu it states that the Single channel Sampling rate is 10GSa/s but then says that it's
8GSa/s for the MSO5000  (this being.. in the help menu (Effectively the User Manual) of the MSO5000)
As i said, How stupid is that ?

What functional purpose is there to advising people with an MSO5000 that the bandwidth on another scope is 10GSa/s.
Even if it were written as 8GSa/s  but then in brackets (10GSa/s on the MSO7000)  at least you could argue that point to a degree because the 7000 was a subpoint to the main point.
but no here... the 10GSa/s is the main point

Clearly, they have loaded the Help menu for the MSO7000 into the MSO5000 (or are using 1 menu for both)
that also should not be the case.

so, that's what i was referring to (it happens in various places, but this is 1 example), But NO, nothing to do with eye diagram

but you raise an interesting point, that being that if the firmware is patched, some things may not work,  I'll keep an eye out for that.

SO FAR I HAVE ONLY FOUND 1 THING, But i'm not sure if it's a problem or intentionally not a feature in the scope.
that thing being.
I had a user ask me about the RECORD feature in the scope,  and.. it is there.  Unlike the DS2000A which had the record buttons on it
and this was simpler to get into . the MSO5000 does have a record feature , However the problem this user has is, he wants to save recorded data on USB for later use.
it seems to me that this should easily be possible. and i've found a video  on youtube where it's clearly seen that upon entering the Record feature there is indeed a SAVE Option.
My scope doesn't show that option.    so this may be something or it may not
but, i'll keep my eye out for other stuff,  so far, I've gone completely through the scope and have not found anything that prohibits the scope doing what it should do