IBM PC Compatible Moderation Guide - Revision history

>Lizard at 19:42, 22 April 2025

2025-04-22T19:42:51Z

← Older revision		Revision as of 19:42, 22 April 2025
Line 85:		Line 85:
	https://redump.info/discs/quicksearch/securom/protection/only/media/cd/errors/null/		https://redump.info/discs/quicksearch/securom/protection/only/media/cd/errors/null/

			===SecuROM discs with redumper===
			Some SecuROM discs (only OLD SecuROM, pre-v4? unconfirmed tbh) might show subcode desyncs in the logs, usually early sectors near the start of the disc, where the protection information it's actually contained. Even if we're asking for redump when we see subcode desyncs, it's usually fine and expected to show there if it's a SecuROM disc.

			Example:
			<pre>
			[LBA: -1] subcode desync (shift: +1)
			[LBA: 8] subcode desync (shift: +0)
			[LBA: 5000] subcode desync (shift: +1)
			[LBA: 5009] subcode desync (shift: +0)
			[LBA: 5331] subcode desync (shift: +1)
			[LBA: 5340] subcode desync (shift: +0)
			[LBA: 8623] subcode desync (shift: +1)
			[LBA: 8632] subcode desync (shift: +0)
			[LBA: 11721] subcode desync (shift: +1)
			[LBA: 11730] subcode desync (shift: +0)
			[LBA: 12258] subcode desync (shift: +1)
			[LBA: 12267] subcode desync (shift: +0)
			[LBA: 14713] subcode desync (shift: +1)
			[LBA: 14722] subcode desync (shift: +0)
			[LBA: 15092] subcode desync (shift: +1)
			[LBA: 15101] subcode desync (shift: +0)
			[LBA: 15545] subcode desync (shift: +1)
			[LBA: 15554] subcode desync (shift: +0)
			[LBA: 15695] subcode desync (shift: +1)
			[LBA: 15704] subcode desync (shift: +0)
			[LBA: 16713] subcode desync (shift: +1)
			[LBA: 16722] subcode desync (shift: +0)
			</pre>

	[[Category:Moderation Guides]]		[[Category:Moderation Guides]]

>NovaAurora at 20:48, 23 January 2025

2025-01-23T20:48:26Z

@@ Line 29: / Line 29: @@
 == Notes on specific copy protections ==
 As a general guideline, for multi disc releases please add the protection only to the disc that actually contains the protected executable file, usually it's just the first or the last disc.
 For example, on a 3 disc release, if the main executable is on the first disc, only the first disc should have the protection field filled.
 ==Mastering Characteristics==

>NovaAurora: /* HexaLock AutoLock */

2025-01-22T16:10:54Z

HexaLock AutoLock

← Older revision		Revision as of 16:10, 22 January 2025
Line 78:		Line 78:
	=== HexaLock AutoLock ===		=== HexaLock AutoLock ===
	Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with [https://web.archive.org/web/20231007213714/https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin Ribshark's custom firmware].		Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with [https://web.archive.org/web/20231007213714/https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin Ribshark's custom firmware].

			Determining the exact version number of AutoLock needs to be looked into, omitting a number for now is fine.

	HexaLock can be identified via the two following subcode desync patterns:		HexaLock can be identified via the two following subcode desync patterns:

>NovaAurora: /* HexaLock */

2025-01-22T16:02:06Z

HexaLock

← Older revision		Revision as of 16:02, 22 January 2025
Line 76:		Line 76:
	If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.		If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.

	=== HexaLock ===		=== HexaLock AutoLock ===
	Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with [https://web.archive.org/web/20231007213714/https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin Ribshark's custom firmware].		Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with [https://web.archive.org/web/20231007213714/https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin Ribshark's custom firmware].

>NovaAurora: /* HexaLock */

2025-01-22T15:55:39Z

HexaLock

← Older revision		Revision as of 15:55, 22 January 2025
Line 94:		Line 94:
	[LBA: 7635] subcode desync (shift: -3)		[LBA: 7635] subcode desync (shift: -3)
	...		...
	Additionally they may be identified if 120 MSF errors are present in the .log file:		Additionally they may be identified if approximately 120 MSF errors are present in the .log file:
	CD-ROM [Disc.bin]:		CD-ROM [Disc.bin]:
	sectors count: 7682		sectors count: 7682

>NovaAurora: /* HexaLock */

2025-01-22T15:34:54Z

HexaLock

← Older revision		Revision as of 15:34, 22 January 2025
Line 77:		Line 77:

	=== HexaLock ===		=== HexaLock ===
	Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with Ribshark's custom firmware.		Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with [https://web.archive.org/web/20231007213714/https://cdn.discordapp.com/attachments/429374270607720461/960431754357927946/ASUS-BW-16D1HT-3.10-WM01601-211901041014_MK_edited.bin Ribshark's custom firmware].

	HexaLock can be identified via the two following subcode desync patterns:		HexaLock can be identified via the two following subcode desync patterns:

>NovaAurora: /* Hexalock */

2025-01-22T15:33:27Z

Hexalock

← Older revision		Revision as of 15:33, 22 January 2025
Line 76:		Line 76:
	If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.		If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.

	=== ~~Hexalock~~ ===		=== HexaLock ===
	~~Experimental guide for Hexalock protection, may result in incorrect dumps but the dumps are functional~~.		Must be dumped (as of 2025-01-01) with a Redumper-compatible JB8 ASUS/LG drive flashed with Ribshark's custom firmware.

	*1. Create Audio Trap disc for Dreamcast		HexaLock can be identified via the two following subcode desync patterns:
	*2. Insert Audio Trap disc into Kreon drive		[LBA: 7562] subcode desync (shift: -20)
	*3. Run discimagecreator.exe stop <drive letter>		[LBA: 7582] subcode desync (shift: -40)
	*4. Remove top of disc drive and swap to Hexalock disc		[LBA: 7592] subcode desync (shift: -50)
	*5. ~~Run discimagecreator~~.~~exe swap <drive letter> <filename~~.~~bin> <speed>~~		[LBA: 7681] subcode desync (shift: +0)
	*6. ~~Load <filename~~.~~IMG> into Isobuster 5~~.0		[LBA: 7682] subcode desync (shift: -50)
	*7. ~~Right click~~ CD ~~> Extract CD Image > Raw (.bin)~~ [~~Or ISO, then change extension to~~ .bin ~~in save prompt~~]		[LBA: 7683] subcode desync (shift: -51)
	*8. Mount the generated .bin/.~~cue in Daemon Tools Pro (Lite might work?) as IDE Drive~~		...
			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)
			...
			Additionally they may be identified if 120 MSF errors are present in the .log file:
			CD-ROM [Disc.bin]:
			sectors count: 7682
			mode1 sectors: 7682
			MSF errors: 120
			All new discs must, as always, be dumped twice to ensure accuracy.

	==Mastering Characteristics==		==Mastering Characteristics==

>NovaAurora: /* Notes on specific copy protections */

2024-10-30T17:20:43Z

Notes on specific copy protections

← Older revision		Revision as of 17:20, 30 October 2024
Line 75:		Line 75:

	If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.		If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.

			=== Hexalock ===
			Experimental guide for Hexalock protection, may result in incorrect dumps but the dumps are functional.

			*1. Create Audio Trap disc for Dreamcast
			*2. Insert Audio Trap disc into Kreon drive
			*3. Run discimagecreator.exe stop <drive letter>
			*4. Remove top of disc drive and swap to Hexalock disc
			*5. Run discimagecreator.exe swap <drive letter> <filename.bin> <speed>
			*6. Load <filename.IMG> into Isobuster 5.0
			*7. Right click CD > Extract CD Image > Raw (.bin) [Or ISO, then change extension to .bin in save prompt]
			*8. Mount the generated .bin/.cue in Daemon Tools Pro (Lite might work?) as IDE Drive

	==Mastering Characteristics==		==Mastering Characteristics==

>Mictlantecuhtle: /* SecuROM */

2024-10-10T08:45:51Z

SecuROM

← Older revision		Revision as of 08:45, 10 October 2024
Line 64:		Line 64:

	Discs with 99 SecuROM sectors dumped by DIC may have an erroneous offset of -59 reported initially in _disc.txt, followed by the correct offset of -647. Any PC disc with reported offset -59 should be carefully checked as a result.		Discs with 99 SecuROM sectors dumped by DIC may have an erroneous offset of -59 reported initially in _disc.txt, followed by the correct offset of -647. Any PC disc with reported offset -59 should be carefully checked as a result.

			==== Correct sector count ====
			Different versions of SecuROM have known sector counts as follows:
			* Pre-v3 - 216
			* v3 - 90
			* v4 - 99
			* post-v4 - 11

			Any dumps with SecuROM should be checked carefully to ensure that the "SecuROM data" section contains an accurate number of sectors.

			If not, the dumper should be asked to redump using DIC with the <code>/np /nq /nr</code> flags, and to then manually extract the SecuROM sectors from the .sub file with <code>psxt001z --libcrypt</code>. It may also be worth asking for a dump to be done with IsoBuster or CloneCD to verify.

	==Mastering Characteristics==		==Mastering Characteristics==

>Mictlantecuhtle: /* SecuROM */

2024-09-25T20:21:15Z

SecuROM

← Older revision		Revision as of 20:21, 25 September 2024
Line 61:		Line 61:
	SecuROM discs with active protection always have one single error in the data track, always in the third from the last sector.		SecuROM discs with active protection always have one single error in the data track, always in the third from the last sector.

	However, this does not meet the official redump definition of an error (following the redumper / edccchk error count), and SecuROM discs should have a 0 error count.		However, this does not meet the official redump definition of an error (following the redumper / edccchk error count), and SecuROM discs should have a 0 error count (unless any other, non-SecuROM error sectors are also present).

	Discs with 99 SecuROM sectors dumped by DIC may have an erroneous offset of -59 reported initially in _disc.txt, followed by the correct offset of -647. Any PC disc with reported offset -59 should be carefully checked as a result.		Discs with 99 SecuROM sectors dumped by DIC may have an erroneous offset of -59 reported initially in _disc.txt, followed by the correct offset of -647. Any PC disc with reported offset -59 should be carefully checked as a result.