[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Lode Runner P8? Might be simpler, might be harder.
- Subject: Lode Runner P8? Might be simpler, might be harder.
- From: Steve Nickolas <lyricalnanoha@usotsuki.hoshinet.org>
- Date: Wed, 11 Jan 2012 02:46:54 +0100
- Cancel-lock: sha1:BxdzTEIR3PY7nBsUyoDohpmqrL0=
- Injection-info: mx04.eternal-september.org; posting-host="e+ps7ncblM4Oh3tsFEgATA"; logging-data="20438"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19v06qglTm6cSUA2bTeoXPZwGOvnkvQ7P4="
- Newsgroups: comp.sys.apple2
- Organization: A noiseless patient Spider
- User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
Here's some stuff I dug up while tweaking around with Lode Runner. You'll
need a disk image of the game itself for it to work very much, and I'm
still poking around to find stuff.
http://xtra.usotsuki.info/lrrl.zip
"postmortem.bin", which is a RAM dump, is the most important piece here.
There is also a packed version that loads as a file. They only contain
the code, not the data.
Well, I know how the data is stored, and it's easy as cake.
http://www.brutaldeluxe.fr/crack/LODERUNNER.DSK
The data is stored in DOS Order, starting from Track 3 Sector 0, one level
per sector. Level "151" is blank, and "152-154" contain the 3 levels that
are looped in the demonstration. 155 contains garbage and that's end of
data.
Being that I made this editor - http://xtra.usotsuki.info/lodehax.dsk.gz
it may be possible to compact the code further by removing the one in the
program. (Mine uses Flex Type.)
-uso.