nmlgc
cdf5141dee
th03/mainl: Initial state
2014-07-01 20:30:39 +02:00
nmlgc
bd5099f904
th03/op: Initial state
2014-06-30 00:52:27 +02:00
nmlgc
93360e2a13
th05/main: Split off segments 3 and 4 into a separate file
...
Getting rid of all the hash space hacks.
2014-06-30 00:00:24 +02:00
nmlgc
48ce5beaea
th04/main: Initial state
...
To anyone else encountering TASM's "Near jump or call to different CS" issue:
Just split off the offending segment into a different source file and include
it from the main one.
2014-06-29 23:04:24 +02:00
nmlgc
6afe3e89a3
th04/maine: Initial state
2014-06-29 18:45:48 +02:00
nmlgc
bf430e4231
th04/op: Initial state
2014-06-29 16:51:19 +02:00
nmlgc
82bc23ec58
th05/main: Identify Stage 4 boss theme strings
2014-06-29 03:21:02 +02:00
nmlgc
467a7db913
th05/main: Initial state
2014-06-29 02:43:13 +02:00
nmlgc
21b8ca62ab
th05/maine: Initial state
2014-06-28 22:13:04 +02:00
nmlgc
91cb632353
th05/op: Additional alignment fixes
...
Now, we're fully identical to the original build - save for three instructions
that are getting assembled using different, but equivalent opcodes.
2014-06-28 20:38:31 +02:00
nmlgc
224f92c77f
th05/op: Remove the duplicate segment alignment parameter for seg000
2014-06-28 20:38:30 +02:00
nmlgc
adb4a66881
Fix a typo in the build parameters
...
And I've been wondering why this didn't work anymore...
2014-06-28 20:38:14 +02:00
nmlgc
9e07c54aee
Start out with th05's OP.EXE
...
This is the raw output of IDA's initial analysis of the original OP.EXE,
touched up in order to compile to an executable identical to the original
build.
2014-06-26 22:47:15 +02:00