Ripguard - Revision history

Morlit at 14:39, 6 June 2026

2026-06-06T14:39:47Z

← Older revision		Revision as of 14:39, 6 June 2026
Line 7:		Line 7:
	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper. It won't split but that's not needed yet.		'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper. It won't split but that's not needed yet.

-	'''Step 2''': Put ringlock into the same folder as the dump and run ''Ringlock.exe state::dvd --state-file=[Name of state]'' (Without brackets). this should produce a list of "Bad blocks". Copy these to a text file. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down n the same text file and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)	+	'''Step 2''': Put ringlock into the same folder as the dump and run ''Ringlock.exe state::dvd --state-file=[Name of state]'' (Without brackets). this should produce a list of "Bad blocks". Copy these to a text file. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down in the same text file and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)
	29244 - 29271 = 27		29244 - 29271 = 27
	1221		1221

Morlit at 14:39, 6 June 2026

2026-06-06T14:39:21Z

← Older revision		Revision as of 14:39, 6 June 2026
Line 5:		Line 5:
	Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an Omnidrive compatible drive and a few extra steps.		Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an Omnidrive compatible drive and a few extra steps.

-	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper ~~with the~~ '~~'--force-~~split ~~--verbose --dump-read-size=1~~'~~' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more~~.	+	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper. It won't split but that's not needed yet.

-	'''Step 2''': ~~Look at your Redumper log~~ file ~~and you~~ should ~~see~~ a ~~bunch~~ of ~~SCSI errors with corresponding LBA~~. ~~Take the last LBA of each continues range and subtract the first~~ to ~~get the number of sectors each contain~~. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)	+	'''Step 2''': Put ringlock into the same folder as the dump and run ''Ringlock.exe state::dvd --state-file=[Name of state]'' (Without brackets). this should produce a list of "Bad blocks". Copy these to a text file. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down n the same text file and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)
	29244 - 29271 = 27		29244 - 29271 = 27
	1221		1221
Line 41:		Line 41:
	Notice the pattern? Like those of [http://wiki.redump.org/index.php?title=Laserlock/Laserlok Laserlock] this is believed to be an artifact from when these discs were mastered. Any other errors should be normal ones that you want to get rid of in the next step.		Notice the pattern? Like those of [http://wiki.redump.org/index.php?title=Laserlock/Laserlok Laserlock] this is believed to be an artifact from when these discs were mastered. Any other errors should be normal ones that you want to get rid of in the next step.

-	'''Step 3''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.	+	'''Step 3''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors and add together the amount in every range. This is your final error count (530 in the example above).

-	'''Step 4''': Run ''Redumper ~~Info~~ --~~image~~-~~name=[Name of ISO]'' and ''Redumper hash~~ --image-name=[Name of ISO]'' on the dump.	+	'''Step 4''': Run ''Redumper --continue=refine --force-split --image-name=[Name of ISO]'' (Without brackets) on the dump.

	'''Step 5''': Repeat the process on the second dump and make sure the hashes match.		'''Step 5''': Repeat the process on the second dump and make sure the hashes match.

-	'''Step 6''': Use MPFcheck on one of the dumps and add the ~~new~~ ranges from step 4 to comments. ~~Fill~~ in and submit as normal.	+	'''Step 6''': Use MPFcheck on one of the dumps and add the ranges from step 4 to comments. Also replace the error count with the one from step 3 and fill in and submit as normal.

Nostalgicbee: changed step numbers

2026-05-10T12:57:45Z

changed step numbers

← Older revision		Revision as of 12:57, 10 May 2026
Line 41:		Line 41:
	Notice the pattern? Like those of [http://wiki.redump.org/index.php?title=Laserlock/Laserlok Laserlock] this is believed to be an artifact from when these discs were mastered. Any other errors should be normal ones that you want to get rid of in the next step.		Notice the pattern? Like those of [http://wiki.redump.org/index.php?title=Laserlock/Laserlok Laserlock] this is believed to be an artifact from when these discs were mastered. Any other errors should be normal ones that you want to get rid of in the next step.

-	'''Step 4''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.	+	'''Step 3''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.

-	'''Step 5''': Run ''Redumper Info --image-name=[Name of ISO]'' and ''Redumper hash --image-name=[Name of ISO]'' on the dump.	+	'''Step 4''': Run ''Redumper Info --image-name=[Name of ISO]'' and ''Redumper hash --image-name=[Name of ISO]'' on the dump.

-	'''Step 6''': Repeat the process on the second dump and make sure the hashes match.	+	'''Step 5''': Repeat the process on the second dump and make sure the hashes match.

-	'''Step 7''': Use MPFcheck on one of the dumps and add the new ranges from step 4 to comments. Fill in and submit as normal.	+	'''Step 6''': Use MPFcheck on one of the dumps and add the new ranges from step 4 to comments. Fill in and submit as normal.

Morlit at 09:13, 10 May 2026

2026-05-10T09:13:42Z

← Older revision		Revision as of 09:13, 10 May 2026
Line 7:		Line 7:
	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.		'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.

-	'''Step 1.5''': Take note of the Size of the ISO. For unknown reasons Redumper will sometimes only do a partial split and if this happens. Delete the ISO and Run ''redumper --continue=split --force-split --verbose --image-name=[Name of SDRAM]'' to split again. If the issue persists, please report it on the forums or VGPC discord.	+	'''Step 2''': Look at your Redumper log file and you should see a bunch of SCSI errors with corresponding LBA. Take the last LBA of each continues range and subtract the first to get the number of sectors each contain. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)
-		+
-	'''Step 2''': Look ~~towards the end of~~ your Redumper log file and you should see a bunch of SCSI errors with corresponding LBA. Take the last LBA of each continues range and subtract the first to get the number of sectors each contain. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)	+
	29244 - 29271 = 27		29244 - 29271 = 27
	1221		1221

Morlit at 13:35, 9 May 2026

2026-05-09T13:35:48Z

← Older revision		Revision as of 13:35, 9 May 2026
Line 9:		Line 9:
	'''Step 1.5''': Take note of the Size of the ISO. For unknown reasons Redumper will sometimes only do a partial split and if this happens. Delete the ISO and Run ''redumper --continue=split --force-split --verbose --image-name=[Name of SDRAM]'' to split again. If the issue persists, please report it on the forums or VGPC discord.		'''Step 1.5''': Take note of the Size of the ISO. For unknown reasons Redumper will sometimes only do a partial split and if this happens. Delete the ISO and Run ''redumper --continue=split --force-split --verbose --image-name=[Name of SDRAM]'' to split again. If the issue persists, please report it on the forums or VGPC discord.

-	'''Step 2''': Look towards the end of your Redumper log file and you should see a bunch of ~~"warning: invalid data frame"~~ with corresponding LBA ~~like this for one with 20 ranges (It could be as low as two)~~	+	'''Step 2''': Look towards the end of your Redumper log file and you should see a bunch of SCSI errors with corresponding LBA. Take the last LBA of each continues range and subtract the first to get the number of sectors each contain. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down and the end result should be a list like this for a disc with 20 ranges (Could be as low as 2)
-		+
-	~~warning: invalid data frame (LBA: [29244 .. 29271])~~	+
-	~~warning: invalid data frame (LBA: [30492 .. 30519])~~	+
-	~~warning: invalid data frame (LBA: [144144 .. 144170])~~	+
-	~~warning: invalid data frame (LBA: [145392 .. 145418])~~	+
-	~~warning: invalid data frame (LBA: [380083 .. 380110])~~	+
-	~~warning: invalid data frame (LBA: [381331 .. 381358])~~	+
-	~~warning: invalid data frame (LBA: [594672 .. 594697])~~	+
-	~~warning: invalid data frame (LBA: [595920 .. 595945])~~	+
-	~~warning: invalid data frame (LBA: [602743 .. 602770])~~	+
-	~~warning: invalid data frame (LBA: [603991 .. 604018])~~	+
-	~~warning: invalid data frame (LBA: [900115 .. 900142])~~	+
-	~~warning: invalid data frame (LBA: [901363 .. 901390])~~	+
-	~~warning: invalid data frame (LBA: [3847857 .. 3847884])~~	+
-	~~warning: invalid data frame (LBA: [3849105 .. 3849132])~~	+
-	~~warning: invalid data frame (LBA: [3896613 .. 3896639])~~	+
-	~~warning: invalid data frame (LBA: [3897861 .. 3897887])~~	+
-	~~warning: invalid data frame (LBA: [3942138 .. 3942165])~~	+
-	~~warning: invalid data frame (LBA: [3943386 .. 3943413])~~	+
-	~~warning: invalid data frame (LBA: [4033584 .. 4033610])~~	+
-	~~warning: invalid data frame (LBA: [4034832 .. 4034858])~~	+
-		+
-	~~Note these down somewhere. Note to that you might have singular errors in between the ranges aswell~~.	+
-		+
-	~~'''Step 3''':~~ Take the last LBA of each range and subtract the first to get the number of sectors each contain. Notice to how they seem to come in pairs? Of these pairs subtract the first of the twin from the last of the first range to see how many sectors there are between them. Note all of this down and the end result should be a list like this	+
	29244 - 29271 = 27		29244 - 29271 = 27
	1221		1221

Morlit at 07:01, 9 May 2026

2026-05-09T07:01:57Z

← Older revision		Revision as of 07:01, 9 May 2026
Line 1:		Line 1:
	[WIP]		[WIP]

-	Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and ~~acting~~ as a separate layer on top of the built in CSS encryption. Functionally, it's very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified either using BOS or a MVSNRGxx string in PVD.	+	Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and acted as a separate layer on top of the built in CSS encryption. Functionally, it's very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified by either using BOS or through a MVSNRGxx string in PVD.

	Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an Omnidrive compatible drive and a few extra steps.		Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an Omnidrive compatible drive and a few extra steps.

Morlit at 09:15, 27 April 2026

2026-04-27T09:15:15Z

← Older revision		Revision as of 09:15, 27 April 2026
Line 3:		Line 3:
	Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and acting as a separate layer on top of the built in CSS encryption. Functionally, it's very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified either using BOS or a MVSNRGxx string in PVD.		Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and acting as a separate layer on top of the built in CSS encryption. Functionally, it's very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified either using BOS or a MVSNRGxx string in PVD.

-	Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an ~~OmnBW16-D1HT or BU40N running~~ Omnidrive and a few ~~of the~~ steps.	+	Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an Omnidrive compatible drive and a few extra steps.

-	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose ~~--dvd-raw~~ --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.	+	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.

	'''Step 1.5''': Take note of the Size of the ISO. For unknown reasons Redumper will sometimes only do a partial split and if this happens. Delete the ISO and Run ''redumper --continue=split --force-split --verbose --image-name=[Name of SDRAM]'' to split again. If the issue persists, please report it on the forums or VGPC discord.		'''Step 1.5''': Take note of the Size of the ISO. For unknown reasons Redumper will sometimes only do a partial split and if this happens. Delete the ISO and Run ''redumper --continue=split --force-split --verbose --image-name=[Name of SDRAM]'' to split again. If the issue persists, please report it on the forums or VGPC discord.

Morlit at 10:18, 9 April 2026

2026-04-09T10:18:01Z

← Older revision		Revision as of 10:18, 9 April 2026
Line 65:		Line 65:
	1222		1222
	4034832 - 4034858 = 26		4034832 - 4034858 = 26
		+
		+	Notice the pattern? Like those of [http://wiki.redump.org/index.php?title=Laserlock/Laserlok Laserlock] this is believed to be an artifact from when these discs were mastered. Any other errors should be normal ones that you want to get rid of in the next step.

	'''Step 4''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.		'''Step 4''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.

Morlit at 10:12, 9 April 2026

2026-04-09T10:12:06Z

← Older revision		Revision as of 10:12, 9 April 2026
Line 66:		Line 66:
	4034832 - 4034858 = 26		4034832 - 4034858 = 26

-	'''Step 4''': Refine the dump as per the DVD portion of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.	+	'''Step 4''': Refine the dump as per the DVD portion and step 4 of the [http://wiki.redump.org/index.php?title=Ringed_Disc_Dumping_Guide Ringed disc dumping guide] and make sure to pay extra notices to any single errors in between the ranges. Merge the result into the BIN a per step 5 of the ringed dumping guide. Update the list from step 3 with any recovered sectors.

	'''Step 5''': Run ''Redumper Info --image-name=[Name of ISO]'' and ''Redumper hash --image-name=[Name of ISO]'' on the dump.		'''Step 5''': Run ''Redumper Info --image-name=[Name of ISO]'' and ''Redumper hash --image-name=[Name of ISO]'' on the dump.

Morlit at 10:11, 9 April 2026

2026-04-09T10:11:16Z

← Older revision		Revision as of 10:11, 9 April 2026
Line 1:		Line 1:
	[WIP]		[WIP]

-	Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and acting as a separate layer on top of the built in CSS encryption. Functionally ~~being~~ very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified either using BOS or a MVSNRGxx string in PVD.	+	Ripguard (possibly also known as CopyBlock but could also be the name of a separate DRM) was a DRM created by Macrovision/Rovi specifically for DVD-Video discs and acting as a separate layer on top of the built in CSS encryption. Functionally, it's very similar to that of a ringed DRM though no actual rings are visible on disc and it can be identified either using BOS or a MVSNRGxx string in PVD.

-	Outside of general movie releases on DVD, Some Redump eligible TV~~-game~~ discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an OmnBW16-D1HT or BU40N running Omnidrive.	+	Outside of general movie releases on DVD, Some Redump eligible TV Game discs also makes use of Ripguard. Dumping procedure is similar to that of a ringed disc but differs in that it Requires an OmnBW16-D1HT or BU40N running Omnidrive and a few of the steps.

	'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose --dvd-raw --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.		'''Step 1''': Put the disc in the Omnidrive and run (standalone) redumper with the ''--force-split --verbose --dvd-raw --dump-read-size=1'' commands. Note that depending on the scheme used this could take between 1-5 hours and possibly even more.