Fonic

You may also want to patch the following line in `main_disassembler.py` to get the original sources structure: Replace this: https://github.com/fonic/wcdatool/blob/b4981ad181757d9b532999ea5b25040bbae18ab2/Wcdatool/modules/main_disassembler.py#L2394 With this (make sure to keep the original indentation): ```python...

Hi Simon, `FATAL.EXE` was a really good find! Its structure is SO different from the _Mortal Kombat_ executables (likely because it was originally written in C) and helps me a...

> Found this in the diff with the old version. The old version had labels for these jumps This is not right, that part should be **data**, not code. Are...

For comparison, this is how that part should look if everything is applied correctly: 

> Nevermind, I got it. My executable was lowercase `fatal.exe` whereas your hints file was uppercase `FATAL.EXE.txt` Yeah, that's it. The wrapper script looks for a hints file of _exactly_...

Regarding debugging (our discussion via email): Why not use `wd`, the debugger that is part of the Watcom toolchain? It is fully capable of debugging DOS4G applications and it is...

I just remembered what kind of setup I used to debug Mortal Kombat a few years back. OpenWatcom on Windows + DOSBox + virtual serial connection for remote debugging: ...

> There is an English version of that guide you linked on the OW2 wiki here: https://github.com/open-watcom/open-watcom-v2/wiki/Debugging Good find, thanks. > After some failures I was able to get it...

> Ok so it is trying to call `chdir_` which in turn invokes int21/3bh: http://www.ctyme.com/intr/rb-2777.htm > So it seems that there is some important code that runs in the 16bit...

BTW you could also try to build _OpenWatcom_ yourself per the instructions given in [wcdatool's README](https://github.com/fonic/wcdatool#readme=) - IIRC, this builds everything (i.e. Linux + DOS + Windows executables). Maybe that...