HexaLock AutoLock: Difference between revisions
>Deterous No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:Hexalock.png|256px|thumb|right|Hexalock logo]] | |||
==General Information== | |||
DRM by Hexalock Limited based out of Israel and used mostly by publishers from said country. The best-known by far being Compedia during their "yellow box" era (~2003-2009) | |||
==Identification== | |||
No files are directly associated with Hexalock. DRM can instead be primarily identified by the offset shifts (see below) and 120 MSF erors carried by each disc. | |||
==Dumping== | |||
Hexalock pushes data into the Lead-out of a disc and the only known drive that can handle it at the moment is a Redumper-compatible JB8 ASUS/LG drive flashed with [[OmniDrive]]. To be a correct dump, one of the two following Desync patterns needs be present as well in logs. | |||
[LBA: 7562] subcode desync (shift: -20) | [LBA: 7562] subcode desync (shift: -20) | ||
[LBA: 7582] subcode desync (shift: -40) | [LBA: 7582] subcode desync (shift: -40) | ||
| Line 17: | Line 25: | ||
[LBA: 7634] subcode desync (shift: -2) | [LBA: 7634] subcode desync (shift: -2) | ||
[LBA: 7635] subcode desync (shift: -3) | [LBA: 7635] subcode desync (shift: -3) | ||
==Additional Information== | |||
Determining the exact version number of AutoLock needs to be looked into, omitting a number for now is fine. | |||
Hexalock also produced a predecessor to Autolock called Multilock that seemed to have worked very differently. [https://redump.info/disc/128079 A single disc] in Redump might carry it but this is currently unconfirmed. | |||
[[Category:Copy Protection Guides| ]] | [[Category:Copy Protection Guides| ]] | ||
Latest revision as of 22:21, 4 August 2026
General Information
DRM by Hexalock Limited based out of Israel and used mostly by publishers from said country. The best-known by far being Compedia during their "yellow box" era (~2003-2009)
Identification
No files are directly associated with Hexalock. DRM can instead be primarily identified by the offset shifts (see below) and 120 MSF erors carried by each disc.
Dumping
Hexalock pushes data into the Lead-out of a disc and the only known drive that can handle it at the moment is a Redumper-compatible JB8 ASUS/LG drive flashed with OmniDrive. To be a correct dump, one of the two following Desync patterns needs be present as well in logs.
[LBA: 7562] subcode desync (shift: -20) [LBA: 7582] subcode desync (shift: -40) [LBA: 7592] subcode desync (shift: -50) [LBA: 7681] subcode desync (shift: +0) [LBA: 7682] subcode desync (shift: -50) [LBA: 7683] subcode desync (shift: -51) ...
or
[LBA: 7631] subcode desync (shift: +50) [LBA: 7632] subcode desync (shift: +0) [LBA: 7633] subcode desync (shift: -1) [LBA: 7634] subcode desync (shift: -2) [LBA: 7635] subcode desync (shift: -3)
Additional Information
Determining the exact version number of AutoLock needs to be looked into, omitting a number for now is fine.
Hexalock also produced a predecessor to Autolock called Multilock that seemed to have worked very differently. A single disc in Redump might carry it but this is currently unconfirmed.