4 ms·
Interesting exploration and impressive persistence. This approach definitely provides more detailed information about how the process worked. This seems like
by JoshTriplett 11y ago
Interesting 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!
- jmount 11y agoThe problem is a lot of the age machines (Apple II in particular) had a lot of direct control over the disk hardware. So they could move the head in "half track" increments (reading from positions that potentially interfere with standard disk positions) and it is uncertain what on the physical disk is the intended image without somewhat knowing how the drive head is scheduled to move. Obviously something more sophisticated than a drive of the time could image the whole floppy (and one could simulate a drive over that)- but using a drive of the time isn't enough to make usable images in all cases. I think the software that tried to do so were called "nibblers" or "nibble editors", but it has been a long time.
- MagerValp 11y agoThis is actually not a problem today, see e.g. the ipf image format and hardware such as KryoFlux: http://info-coach.fr/atari/documents/_mydoc/IPF-Documentation.pdf http://info-coach.fr/atari/documents/_mydoc/IPF-Documentatio... http://www.archiveteam.org/index.php?title=Rescuing_Floppy_Disks http://www.archiveteam.org/index.php?title=Rescuing_Floppy_D...
- JoshTriplett 11y ago"Under MAME license" is unfortunately a showstopper for FOSS. Particularly unfortunate because MAME itself has started the process of moving away from that license and towards a FOSS license (see https://github.com/mamedev/mame/blob/master/README.md#license https://github.com/mamedev/mame/blob/master/README.md#licens...). Do you know if the authors of that code would consider releasing it under a FOSS-compatible license (e.g. MIT, LGPL, or GPL, depending on preferences about copyleft)? Failing that, do you know if a FOSS library exists to read and write the IPF image format?
- jmount 11y agoNeat. I knew a superior drive could copy everything, I didn't know this had become common.