Quasar
Moderator

Posts: 4615
Registered: 08-00 |
kb1 said:
Sounds as if the tools used to write the files just happened to write them that way.
On a broader view, here's my idea of a sweet project:
To "re-master" the Doom source code, with all of the DMX and other DOS-based "goodies" (heh), and use the original tools to compile it exactly like it was originally compiled. Do you think it would be possible to recreate doom.exe, and have it match byte-for-byte? Doing so would make it trivial to discover oddities like the DMX file padding mentioned above, but, basically, I think it would be fricking cool on it's own :)
Almost certainly not because the version of Watcom that id used just simply isn't available, and the code as-is is not known to compile with Open Watcom.
You could probably reverse engineer a linkable DMX library out of any of the executables, but that's about it. And that alone would be a gigantic undertaking since you'd need to de-relocate all the code and manually construct .lib data structures for it all. And that's not to mention that it's almost impenetrable code. Parts of it are written in inline assembler, other parts are total spaghetti of function pointers calling function pointers, and almost all of it is a miasma of low-level device-specific code.
In the end, what would the purpose be? All you'd do is end up with a file you already had - vanilla DOOM.EXE :P
|