"One of them is as simple as overwriting one file on the harddisk with a hacked one."
It's not actually a hack. A "hack" is an unknown cobble to get around something. What I provided is a patch, or
the patched binary (mackieos.exe). The patch was the easiest way to "move forward" with supposed end of life
d8b's, and a side effect of a "hack" is that it may or may not be doing only what is desired. The patch is a cheeky
bypass of the crypto routine that is used to check any crypted key string; If it's valid, a "true" is returned. The patch replaces an instruction at that point to "JMP" to the true condition as soon as it's called, programatically.
It's impossible to fail, as, there is no longer a crypto verify routine, just some redundant code and a "return true
always" routine + some padding to correct for the changes. It's a sort-of happy lobotomy.
A corrupt disk, an over-written data file are just as likely to go wrong in reality. I just HAD to comment there. I still love my d8b, and use it regularly on fine work. It *never* lets me down in a warm, dry studio environment.
With a hex editor, this is the MackieOS.EXE patch:
Offset: from-value to-value
0003580C: 52 B0
0003580D: FF 01
0003580E: 75 90
0003580F: 08 90
00035810: E8 90
00035811: 17 90
00035812: 00 90
00035813: 00 90
00035814: 00 90
00035815: 83 90
00035816: C4 90
00035817: 08 90
001082A1: 50 B0
001082A2: E8 01
001082A3: 85 90
001082A4: D5 90
001082A5: F2 90
001082A6: FF 90
001082A7: 83 90
001082A8: C4 90
001082A9: 08 90
write, save. done.
There. It's out!
