GoKawiilThe Setup
I just wanted to see if I could do it.
The disc was Gladiator, a two-disc set that has been on my shelf for years. The plan was small, more curiosity than project: pull the disc into the computer, see if it would let me copy it, and if it worked, burn a fresh copy onto a blank DVD. The kind of thing every kid with a Dell tower in 2003 spent an entire weekend trying to figure out.
In 2026 the entire workflow takes about an hour. The cheap hardware costs less than a sandwich. The software is free.
There was also a practical reason. I own a Vinpower SharkCopier, a 1:11 DVD duplicator (eleven blank DVDs in eleven burners, one master in a dedicated read drive, all driven by a small LCD on the front panel). It is the kind of hardware you buy when you intend to make a lot of discs. The duplicator industry, by the way, is not dead. Churches still press their own sermon DVDs in the basement. Indie filmmakers still ship festival screener DVDs and direct-to-fan special editions. AV departments at small colleges still run runs of training videos. School districts still mass-produce graduation footage. The market for “I have one master and I need fifty copies of it by Sunday” is small but durable, and it is the market the SharkCopier was built for. Vinpower still sells current models. Their competitors do too.
The Vinpower throws Error 209 the moment you put a CSS-protected source disc in the master tray. The firmware will not duplicate a copy-protected disc, ever, under any circumstance. There is no setting to override, no firmware downgrade, nothing. So the only way to make copies of a Hollywood DVD with the Vinpower is to first strip the CSS off the source somewhere else, burn one clean master from the stripped image, and feed that clean master back into the duplicator (which will gladly clone a disc that has no copy protection).
That meant I needed a separate consumer drive. So I bought one off of Amazon. Two day shipping, twenty two dollars, no-name brand, USB 3.0, plug and play, came in a cardboard box smaller than a hardcover book. The ripping software was MakeMKV (free, perpetual beta, every release re-licensed). The CSS encryption layer that Hollywood spent the entire 1990s defending in federal court was bypassed transparently in the background by a library called libdvdcss, written by a Norwegian teenager in 1999, now bundled inside every modern media player on every operating system.
The whole stack, the thing that an entire industry deployed lawyers and federal prosecutors to suppress at the start of this century, arrived at my door in forty eight hours from a website I also use to buy paper towels.
I knew all of this going in. I have been around long enough to remember what this used to cost (in time, in legal risk, in lawsuits filed against teenagers, in DMCA threat letters). What I did not expect, when I opened up File Explorer and looked at the disc as a raw filesystem while the rip was running, was how much was on it. The video files were chopped into chunks of exactly one gigabyte each. There were folders full of stuff that had nothing to do with the movie. There was a drmworks folder that did not announce itself as DRM. There was an installer. There was an autorun.inf . There were two parallel runtime trees, one for Mac and one for Windows, full of binaries from a company I had never heard of.
The disc had way more on it than I expected. Once I started pulling threads, every thread led somewhere stranger.
... continue reading