Ripguard

From Redump Wiki

Latest revision as of 10:18, 9 April 2026

[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.

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.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)

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
1221
30492 - 30519 = 27
144144 - 144170 = 26
1222
145392 - 145418 = 26
380083 - 380110 = 27
1221
381331 - 381358 = 27
594672 - 594697 = 25
1223
595920 - 595945 = 25
602743 - 602770 = 27
1221
603991 - 604018 = 27
900115 - 900142 = 27
1221
901363 - 901390 = 27
3847857 - 3847884 = 27
1221
3849105 - 3849132 = 27
3896613 - 3896639 = 26
1222
3897861 - 3897887 = 26
3942138 - 3942165 = 27
1221
3943386 - 3943413 = 27
4033584 - 4033610 = 26
1222
4034832 - 4034858 = 26

Notice the pattern? Like those of 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 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 6: 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.