Thanks! I will admit, I'm new to this forum and the post is so huge I struggled to find that sort of full explanation - used the first one I found that seemed do-able. I will make a note to use that better method before I update firmware in the future.
Thanks!
You're Welcome
I will admit, I'm new to this forum
1. We can see that by your status
2. No No.. it's ok, You're fine , it's not a problem
and the post is so huge
well, just so you know, These "How to Hack your [Insert Scope here]" Posts usually tend to be massive and out of control.
they tend to start on topic with troubleshooting
then maybe 15 pages into it the members find the solution to the hack
(Now.... 50 pages later, How are you supposed to find the solution on page 15) Ya know ?
and then everyone starts activating
and then after a while... everyone just sort of drifts off topic
The post gets long and then someone like me comes across and starts a new post to abbreviate everything .
that's more or less how these things evolve
Also i'm very familiar with dealing with Newbies, I've helped Literally, Hundreds of you guys activate your scopes. so.. No need to apologize
I struggled to find that sort of full explanation - used the first one I found that seemed do-able
and the Patch method is still DO-ABLE
However it has limitations, You need to understand how it started
Before the MSO5000 we were all pre occupied with the DS2000A and after that there was an influx of DS1054z
Now the 1054Z was easy.. You just went to a website, Entered a code and you were done, Sort of like how we did it with the DS100E series
Now with the DS2000A Series
Stage 1 was remoting into the scope and entering commands (i think it was via ultra sigma)
Stage 2 evolved to a program being made that did 3 things (i think it was)
1. it installed the necessary scope drivers
2. You had to enter your serial number
3. It would combine your serial number with another key and then generate an activation key for you (Based also on the options that you selected, i think the Option was AAA)
so when we got to the MSO5000 we thought the encryption would work the same way.........IT DIDN'T
so then they started to use some old tricks to bypass activation and this was THE PATCH
so the patch makes the scope think that it's unlocked.
so you'll see things like EYE ANALYSIS , But it won't actually work because the MSO5000 doesn't actually support that feature
so the PATCH METHOD.... Tricks the scope into thinking something , While the license file is still not activated
THE NEW METHOD _Dr Mefist0 Licensing method........ ACTUALLY LICENSES THE FILE IN THE SAME WAY THAT IT WOULD IF YOU WENT TO RIGOL AND PAID THEM AND THEY INSERTED THE USB STICK
AND RAN THEIR SCRIPT TO ACTIVATE IT (which you would pay approx $300 for each option)
so to bring this home..... Appreciate the fact that DrMefist0 really did something cool here
and then let's not forget ASP who then took us from the first 2 versions through the next 10 versions of the script and did a whole bunch of stuff that is too long to mention here.
but some of the highlights are
- Made the activation time much much shorter
- This in turn reduced the risk of people bricking their scopes
- We also put in safety features so they didn't brick their scopes
- he put in lines of code so the scope rebooted itself instead of just sitting there after activation
- He added diagnostic features to the script
- Then Jointly we looked into unlocking the scope to 500MHz
so yeah..the patch thingy is way way way outdated
it still technically works, but you shouldn't use it because at this stage it's very old and theres' no reason to use it since... on the next firmware update you're gonna lose all your options
at which point
1. You will re patch again (don't know why you would that )
2. You'll run the properly licensed method (in which case, why not just do it now)
I will make a note to use that better method before I update firmware in the future.
Sure, do whatever you like, it's your scope. i recommend you do it now since you're doing this anyway.
but.. it is ultimately up to you
a few things in that pdf you read
RE Restore Default (and where it's mentioned that you have to do that before the upgrade)
NO... that was a rumour that went around for a while, it's not actually true or required, it's just one of those things that people incorrectly conclude
along the way and sort of becomes a thing
I personally tested that one and went from the lowest version to the highest version without ever resetting defaults.
it's not a requirement for upgrading
although it's handy to know that you can do it if you have a problem with your scope