IBM PC Compatible Moderation Guide - Revision history

Morlit: Ubisoft Exclusive info

2026-07-19T12:13:32Z

Ubisoft Exclusive info

← Older revision		Revision as of 12:13, 19 July 2026
Line 29:		Line 29:
	=== Sold Out Software ===		=== Sold Out Software ===
	Dumpers will occasionally mistakenly add e.g. "SOV. 2.5.4" to either the serial or version fields. This should be removed, as this is an internal publisher reference and is not a serial nor does it relate to the true version number of the software.		Dumpers will occasionally mistakenly add e.g. "SOV. 2.5.4" to either the serial or version fields. This should be removed, as this is an internal publisher reference and is not a serial nor does it relate to the true version number of the software.

			=== Ubisoft Exclusive===
			Ubisoft Exclusive releases with the [https://m.media-amazon.com/images/I/51ExjHfO0vL._AC_UF1000,1000_QL80_.jpg large "X"] logo gets added as "Ubisoft eXclusive". As to differentiate them with [https://img.tradera.net/large-fit/474/638375474_6b630ff6-45a4-4d8c-9635-03b99fde9e76.jpg those without].

	== Notes on specific copy protections ==		== Notes on specific copy protections ==

Morlit: We no longer track Pre-gap weirdness

2026-07-19T12:02:10Z

We no longer track Pre-gap weirdness

← Older revision		Revision as of 12:02, 19 July 2026
Line 35:		Line 35:
	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.		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.		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==~~
	~~CD-ROMs can have weird mastering quirks which present themselves in the listed pregap for Track 2 in the cuesheet.~~
	*01:73 pregap with 2 audio silence sectors at the end of Track 1 = "Last 2 sectors of Track 1 contain audio silence."<br>
	*01:74 pregap with 1 audio silence sector at the end of Track 1 = "Last sector of Track 1 contains audio silence."<br>
	*02:01 pregap with 1 scrambled data sector = "Track 2 pregap contains 1 scrambled data sector."<br>
	*03:00 pregap with 75 scramble data sectors = "First 75 sectors of Track 2 contain scrambled data."<br>
	*04:00 pregap with 150 scramble data sectors = "First 150 sectors of Track 2 contain scrambled data."<br>

	==Periodic Checks==		==Periodic Checks==

Morlit: Moved SecuROM info to the relevant page. Also note on OEM regions.

2026-07-19T11:55:14Z

Moved SecuROM info to the relevant page. Also note on OEM regions.

@@ Line 24: / Line 24: @@
 If the distributor is known, add their name to the edition: e.g. "Bundle Version '''Gateway''' OEM"<br>
 Add (OEM) to the datfile name of the disc, if there is more than one OEM for that disc, you may add the distributor too (e.g. Gateway OEM). If distributor is not known, (OEM) (Alt) or (OEM) (PVD Date) can be used instead.
 === Sold Out Software ===
@@ Line 79: / Line 81: @@
 If you find an erroneous barcode, but the barcode field is locked, then ask the admins to fix it.
 It should be possible to make this check scripted/automated, or to build a validation check into the forms.
 [[Category:Moderation Guides]]

Sadikyo: Protected "IBM PC Compatible Moderation Guide" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2026-06-24T14:15:18Z

Protected "IBM PC Compatible Moderation Guide" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 14:15, 24 June 2026
(No difference)

>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: