In 1999 This Was a Federal Crime. In 2026 the Hardware Is $22 and the Software Is Free.

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.Every DVD pressed between roughly 1998 and 2005 was secretly carrying a second payload, and almost nobody talks about it anymore because the companies that built it have been bankrupt for twenty years. This is the story of what I found on a single disc from my own shelf.Before I get to the main thread, a short detour. While I was waiting for the Amazon drive to ship, my second instinct was to try the optical drive in my Dell PowerEdge R630 server. The server has a slimline DVD-ROM drive on the front bezel. I had it passed through to a Proxmox container running MakeMKV, libdvdcss, libaacs, Jellyfin, and the rest of a complete optical-archival stack. The whole thing took an afternoon to build and felt very clever.The PowerEdge refused to read the disc.Not failed to decrypt.

Not stalled on a bad sector. The drive looked at the inserted commercial DVD and reported back to the operating system: Incompatible medium installed. SCSI sense code 02/30/00.This is firmware-level refusal. The drive’s controller is checking whether the inserted disc is “appropriate for a server-class drive” and deciding the answer is no. Server-grade Dell/PLDS drives ship with deliberately restricted firmware that reads recovery media, OS install discs, and data CDs, but actively refuses commercial DVD-Video discs at the hardware layer before any software ever sees the bytes.The drive in your laptop does not do this. The cheap drive I had ordered off Amazon does not do this. A consumer drive’s firmware is, in the technical sense, dumb. It sees a disc, it reports the contents, it lets the OS handle whatever happens next. The server drive is the unusual one.This is worth pausing on. We have a strange world now where the cheap consumer hardware is more capable than the expensive enterprise hardware, specifically because the enterprise vendor put effort into making theirs less capable. The same logic produced printers that refuse third-party ink and tractors that refuse third-party repair tools. It is a kind of inverted progress. Pay more, get less. Pay less, get the actual thing.So now I had two pieces of expensive hardware refusing to read the same disc. The Vinpower duplicator, refusing because of CSS at the firmware level. The Dell server drive, refusing because of “is this an appropriate disc for a server” at the firmware level. Both vendor-imposed restrictions. Both bypassed, when the Amazon package finally arrived two days later, by a twenty two dollar consumer drive whose firmware did not pretend to know what should and should not be allowed.I unplugged the server drive, plugged in the Amazon drive, and the consumer hardware read the same disc with no complaints. Cost differential between what worked and what did not, summed: about a thousand dollars worth of refusing hardware versus the price of a sandwich for compliant hardware.I selected the main title in MakeMKV, started the rip, and walked away.Forty minutes later I came back to a failure log. The drive had hit a physical read error at byte offset 2,708,467,712, retried sixteen times, and given up.

I cleaned the disc with a microfiber cloth (radial wipes, center to edge, the way you are supposed to). Tried again. Failed at byte offset 2,708,580,352. The two error positions were one hundred twelve thousand bytes apart. Same spot on the disc. The defect was not a smudge. It was permanent damage in the dye layer, fifty megabytes wide, untouchable by anything short of buying another copy.I gave up on Disc 1 and switched to Disc 2.This is where the trip got interesting.Disc 2 of a two-disc set is the bonus features disc. Documentaries, deleted scenes, behind-the-scenes featurettes, scoring sessions, production stories, trailers. The bonus disc on my Gladiator set is genuinely the bonus disc. It ripped cleanly through MakeMKV in about thirty minutes and produced seven separate MKV files, one per featurette, totaling about six gigabytes:The “Strength and Honor” production documentaryHans Zimmer’s scoring session footageA “treasure chest” montage of behind-the-scenes additional footageDeleted scenes with director commentaryA series of HBO First Look-style featurettesPhoto galleriesTrailersThis is the legitimate bonus content for the 2000 Ridley Scott film. The disc is not mislabeled, it is exactly what the case says it is, and the contents are exactly the production extras that DreamWorks and Universal shipped with the original two-disc release.There is one curious branding artifact. When I pulled the first thirty seconds of VIDEO_TS.VOB (the menu domain file at the root of the DVD’s video folder) using ffmpeg, I expected to find an FBI warning and studio logos. What came back was a silent thirty second loop of the Artisan Entertainment logo cycling over and over. Disc 2 of the Gladiator set, opening with the bumper of an entirely different distributor.This is not necessarily a sign of mislabeling. Artisan Home Entertainment, a New York based distributor active until its 2003 bankruptcy and 2004 absorption by Lions Gate, handled DVD authoring and post-production work for many titles whose theatrical distributors used different brand names.

The Artisan logo on the bonus disc menu may be a credit for the authoring house, a co-distribution mark for a specific re-release, or a holdover from a partnership arrangement nobody outside the studio bookkeeping department remembers. The actual content under the menu is unambiguously Russell Crowe Gladiator material. The Artisan bumper is a footnote on a pressed disc that has been sitting in a case on my shelf for years, surfaced only because I extracted the file directly with ffmpeg and bypassed the menu navigation that would have skipped past it.Disc 2 has, of course, the same payload of dead bonus-app infrastructure as Disc 1. Same PCFriendly installer. Same drmworks folder. Same autorun.inf waiting to launch the same dead phone-home. Both discs are normal commercial DVDs from the era. They both came with the standard 1998-to-2005 secondary payload pressed onto them. Once I started looking at that payload, the actual movie became the smaller mystery.Open any DVD on any operating system and you will see the same two folders at the top level: VIDEO_TS and AUDIO_TS. The second one is always empty (it is the legacy DVD-Audio format that nobody adopted). The first one holds the actual movie.Inside VIDEO_TS you find a structured collection of files split into “title sets.” A title set is a logical grouping (the main movie is usually one title set, each bonus feature is another). For each title set there are three file types:.IFO files (information files) hold the table of contents, chapter markers, audio track definitions, subtitle stream definitions, and navigation logic..BUP files are byte for byte backups of the IFO files. The DVD spec mandates this redundancy. If the IFO is unreadable, the player falls back to the BUP automatically..VOB files (video object files) hold the actual MPEG-2 video, AC3 or DTS audio, and subpicture data. The spec caps each VOB file at exactly one gigabyte, which is why long movies are split across multiple VOBs even though the disc itself can hold seven gigabytes.This format was finalized in 1995 and has not meaningfully changed since.