3 ms·
Sort of related: I don't remember specific examples, but I recall that several games/apps have inadvertently shipped with partial source code recoverable by an
by 0xcde4c3db 10y ago
Sort of related: I don't remember specific examples, but I recall that several games/apps have inadvertently shipped with partial source code recoverable by an undelete tool because the developers simply deleted the source/build files from the floppy that they were using for development before imaging it for production, rather than wiping a new disk and copying only the release files.
- rasz_pl 10y agoI only recall OSes. DOS SDK with email dump captured in empty space of full disk image and not completely deleted scraps of source code for Amiga Kickstart shipped on 1.0 disk.
- 0xcde4c3db 10y agoI found a reference to source code recovered from the DOS port of Double Dragon II: The Revenge [1]. I could have sworn that I heard this story about some well-liked Amiga or Atari ST game, though. [1] https://archive.org/details/DRAGONII https://archive.org/details/DRAGONII
- i336_ 10y agoOoh. Is that available anywhere??
- buzzybee 10y agoYou can find many examples of this on TCRF: https://tcrf.net/Category:Games_with_uncompiled_source_code https://tcrf.net/Category:Games_with_uncompiled_source_code It tends to be an artifact of the build process, yes. Sometimes it vacuums up other random files like the developer's porn stash.
- mmjaa 10y agoIt used to be that sources for games were required - else you couldn't run them! :) I cut my teeth on cracking stuff in the 8-bit era by writing an assembly-language "OLD" command for my platform back then (Oric-1/Atmos) that would undo the work done by the "NEW" command - i.e. replace a sentinel byte - so that I could get full sources for games that 'protected' themselves by doing a "NEW" command whenever CTRL-C was pressed. So many wonderful discoveries came to me that way ..