10 ms·
Cracking BurgerTime, a 1982 game on a floppy disk
- Sanddancer 11y agoFantastic article as to how cracking was done back in the day. Plus, I've gotta give style points for it being formatted as 40 column, even if it isn't in all upper case, like files from back in the day would be. Though I was surprised he didn't check to see what that solitary bad sector was near the beginning of his explorations, because that was a pretty common way of keeping raw disk copy software from duplicating programs. All in all fascinating article.
- deleted 11y ago[deleted]
- Narishma 11y ago3 days ago, not back in the day.
- JoshTriplett 11y agoInteresting exploration and impressive persistence. This approach definitely provides more detailed information about how the process worked. This seems like the only approach that would have worked back in 1982. Reading the description of the archive.org project at https://archive.org/details/apple_ii_library_4am&tab=about https://archive.org/details/apple_ii_library_4am&tab=about makes it clear that this effort intentionally deconstructs and documents the original copy protection. Other than as an exploration of copy protection, though, I can't help but wonder if the simplest approach to preserve and run the same software today would involve an appropriate emulator, more accurate floppy drive emulation, and the unmodified original disk image. The crazy amount of self-decryption and obfuscated code wouldn't matter as long as it found what it expected on the disk; the modifications just let it run on real hardware using a copied disk. Apart from allowing the use of the original unmodified disk, emulation would also avoid the possibility of missing more subtle copy protection schemes. This particular disk made things easier by just stopping the game at the start. Some of the worse copy protection mechanisms developed later would detect a copied game, leave it somewhat playable, but make it either exceptionally difficult or intentionally broken near the end. Sometimes they would include a more obvious copy protection scheme to defeat that prevented playing the game at all, so that a prospective cracker would think themselves successful once the game starts. See http://media.earthboundcentral.com/2011/05/earthbounds-copy-protection/index.html http://media.earthboundcentral.com/2011/05/earthbounds-copy-... for an example.
- kevin_thibedeau 11y agoSome copy protection systems relied on using subtle timing errors to create disks that would read as "corrupt" by standard system software. Replicating this behavior in an emulator would be a major undertaking as well as being hard to reproduce in an image format.
- trav4225 11y agoThis.
- abrookewood 11y agoI was never very advanced at cracking, but I do remember back on the C64 I encountered a number of games that had corrupt/unreadable sectors on the disk. Many copy programs would halt when they encountered these errors meaning you couldn't copy the disk. I had one program (no idea what it was called anymore) that would skip the errors and write everything else. To beat the copy protection, I would open the sector with the read error on the original disk, swap out for my mostly complete copy, and then write the disk error to that sector. I always thought it was kind of weird that I could write an unreadable error, but it seemed to work most of the time.
- delinka 11y agoI think the ultimate problem with emulation is the disk image: how do you image a disk with these subtle timing errors? The default behavior of the software operating the drive isn't aware of half tracks; every vendor uses different tricks so you don't know which 'timing errors' to activate; etc.
- david-given 11y agoGo look into Kryoflux: http://www.kryoflux.com/?page=kf_features http://www.kryoflux.com/?page=kf_features It's a USB floppy controller which allows you to image the raw magnetic state of the disk (subject to head step and width). It allows you to record the disk and then try to figure out what the format is. It's good enough to allow you to read CLV disks, such as Mac floppies, from an image taken from a CAV drive, such as a PC one. I don't know whether it supports half tracks --- probably --- but it will certainly support all the weird timing error tricks. It's not what I would call user friendly but once you've figured it out the results are magical. I was able to image an ancient BBC Micro floppy disk once and then spend ages figuring out how to parse the sector layout and encoding density working with just the image. Not only does this avoid having to keep working with the fragile disk, but it's way faster!
- deleted 11y ago[deleted]
- incepted 11y agoI'm both impressed and terrified that most of this article makes sense to me, even thirty years later. It feels like writing the protection must have taken longer than developing the game itself. If you're curious, here is the actual game: https://www.youtube.com/watch?v=5wEWftbwSm4 https://www.youtube.com/watch?v=5wEWftbwSm4 Hard to imagine they went to that amount of trouble to protect it, but those were different days.
- Sanddancer 11y agoThis was written just a couple days ago, it's just in the formatting of files written 30 years ago. The writing and explanation style is definitely a lot more modern and detailed.
- JoshTriplett 11y ago> The writing and explanation style is definitely a lot more modern and detailed. Especially since many of the original crackers usually did not want to share all of the details, only just enough to aggrandize themselves without supporting others.
- incepted 11y agoThis is spot on, that's exactly how I remember the scene back then. "Beneath Apple DOS" (and later ProDOS) were the cracker bibles back then. It's pretty much the only official documentation you could buy that described how the floppy drives work at the lowest levels. There was no internet and BBS were reserved for the most wealthy hackers. Basically, you were on your own to figure things out. With the knowledge from this book, you could theoretically crack anything, but as the article shows, you also need to have total mastery of the 6502 and of the Apple ][ ROM layouts too.
- jacquesm 11y ago> you also need to have total mastery of the 6502 and of the Apple ][ ROM layouts too. Those were not rare skills.
- leeoniya 11y agothis one is also pretty crazy: Super Mario World Credits Warp Explained https://www.youtube.com/watch?v=vAHXK2wut_I https://www.youtube.com/watch?v=vAHXK2wut_I
- jacquesm 11y agoHehe, lots of dusty neurons firing while reading this. Wonder how many old school hackers cut their teeth on cracking games. > In Which I'd Like To Add You > To My Professional Network Of > Linked Catalog Sectors Priceless... How much wall clock time went into this? > I'm beginning to suspect that this disk > is nothing more than an infinite series > of decryption routines with a game > bolted on as an afterthought.
- Vivtek 11y agoI would guess that to the guy who did the copy protection it was his master work in decryption routines, funded by the sad necessity of putting a game written by some talentless hacks into it as the ultimate payload.
- DrTung 11y agoI remember cracking A2FS1 https://www.youtube.com/watch?v=sWIuTP_A6IQ https://www.youtube.com/watch?v=sWIuTP_A6IQ This was before floppy disks, the game came on a cassette, but it had the same style of boot0/boot1 encryption. Starting the game from a copied cassette, it just printed "STOLEN AIRCRAFT! STOLEN AIRCRAFT!" all over the display.
- abrookewood 11y agoWow .. It looks like it would have been more fun to crack the encryption than actually play that game!
- Starwatcher2001 11y agoVery much so. I remember spending many months cracking game protection, not because I wanted the game, but because I wanted to pit my wits against the guy who wrote the protection. I learned more about disk controllers and hidden opcodes on the Z80 (TRS-80) doing that that any other way. I didn't always beat the guy, but always learned something. Kudos to 4am, who has more patience than me. I'd probably have given up well before the third level of encryption.
- ddingus 11y agoFor some titles, this was definitely the case. Nothing nefarious about it. We weren't connected back then. People got bored, no new software, so... why not hack on the stuff we've got?
- acomjean 11y agoI love reading the deconstruction. Those apple copy protection schemes. Pirated software always had a "cracked by" load screen. The most interesting thing to me were the hardware copy cards. Since most software fit in RAM, and the whole software would load at once, these cards let you push a button and make a bootable disk of whatever your computer was running. When a disk failure meant trying to find another copy somewhere there was a legit fear of loosing your software. central point software made some of these cards. A little info is available online. (Being before the internet took off, the names aren't search engine friendly.). Alaska Card Advert (why settle for copying the lower 48K.. Before they called it backup..) https://s-media-cache-ak0.pinimg.com/736x/e2/70/cd/e270cdd9028e17de61c0fd204b056884.jpg https://s-media-cache-ak0.pinimg.com/736x/e2/70/cd/e270cdd90... Bottom of this page has some interesting pictures and history of these card: http://retro.icequake.net/dob/ http://retro.icequake.net/dob/
- rlonstein 11y agoI was twelve or thirteen, had a ][e and with a copy of Beneath Apple DOS and the reference manual, and cracked a lot of software for the challenge. I wrote my own nibble copier but me and my friends pooled our money and bought Copy ][+ and Locksmith, which worked better. My favorite, and easiest, trick was to use the 64k extended memory of the 80-column card to overlay the regular memory, copy the ROM and a few low pages into it, then jump to the boot routine. Then when the disk stopped spinning, I'd hit the reset button which left me with a copy of the system at that point. Sometimes I just had to dump the program from the memory, other times I would use it to disassemble how it loaded. I had a Applied Engineering RAMWorks card (Dad heavily used AppleWorks) and I recall there being tricks around that but can't remember (rigged a couple of buttons for page swapping, I think).
- boot13 11y agoNice work! Kind of hard to believe someone would go to all that trouble now, but fun is fun, right? I remember at least one game that was less fun to play than it was to remove the copy protection. Some of my old articles about removing Apple II copy protection are also posted on archive.com, like this one: http://archive.org/stream/computist-scan-14/issue14#page/n9/mode/1up http://archive.org/stream/computist-scan-14/issue14#page/n9/...
- 32bitkid 11y agoThis reminds me tangentially of the Prince of Persia bootloader/disk format[0] used for the original Apple II release. Whenever I start to think I am clever or am feeling frustrated, I have a list of articles/code to read through to remind me I'm not; this is on there, and I'll be adding this to the list. [0]: http://fabiensanglard.net/prince_of_persia/pop_boot.php http://fabiensanglard.net/prince_of_persia/pop_boot.php
- kabdib 11y agoI wrote some 6502 protection code for Atari game cartridges. The problem was that a cartridge could be copied (trivially), then loaded into RAM at the same address, then run. There were many disks running around with cracks of cartridges that you could just load and run. The goal of the protection code was to detect whether the code was running in RAM or ROM, usually by hiding writes that would cause crashes or be detected by the game logic. Once I had about two weeks to spare on a protection system; it used a couple levels of decryption and some delaying tactics so that the title would crash minutes after starting. A prolific Atari pirate lived in my apartment complex. After the cartridge shipped, I asked him about it. "Oh, that was a hard one. It took me and my friends three days to crack." Time and numbers are not on the side of DRM. (I'm also unconvinced that Atari lost much money to copying).
- ddingus 11y agoCart protection on 6502 was tough to hide. I personally never reversed one, but a friend and I did a couple for the 6809. That thing was tough! Lots of options, addressing modes, etc... Took weeks, and it was on cassette. I've often wondered about your last bit there. The way it was in my little home town is a lot of people copied stuff. But, they barely could afford the computers too. Those who did have the bucks bought most of the stuff that ended up copied. You might be right, at least early on. Later in the 80's, disk copying was massive. The C64 scene seemed to have buyers, but nearly everyone was on copied media in the Atari scene. Fewer machines, more copies, and it seemed like easier copies too... Some schemes were bad sector ones, and frankly, one could just count the beeps, open the door, wait for the error and continue. Not everyone checked the nature of the error, it seems.
- strags 11y agoI added some copy-protection to a Nintendo 64 game once. If the anti-piracy checks ever triggered, the game would do nothing at first - but after a few minutes, the frame-rate would ever-so-slowly start to get progressively worse and worse until it was unplayable. I'd like to think that I pissed at least a few people off.
- stordoff 11y agoIf you're going to do that sort of piracy check, you have to be absolutely certain that it'll never trigger on a genuine copy. Red Alert 2 had a similar idea - about 60 seconds in to a game, all of your units will explode and the game ends - but it will sometimes trigger on legitimate copies of the game (usually due to mods, but I've had it happen on a clean install as well).