These are the contents of the batch file used to build the df.com file. Several comments:

- DF MUST be built as a .COM file.  Significant changes would be required for many aspects of the code to change to .EXE file structure. (Otherwise I would have done it.)
- In part for the above reason, DF is assembled as a single file.  (For ease of working on the program, the source is broken into many files but all are pulled in with INCLUDEs.) i.e. there's a single object file.
- You will probably need an assembler and linker that have a virtual 386 mode.  Plain vanilla real mode assemblers will probably run out of memory because of the size of program. (At least the real-mode Borland Turbo Assembler did.)
- The code was written for Borland Turbo assembler.  Some changes may be required here and there if you use Microsoft's MASM. 

- The batch file I use with my Borland products to assemble and link DF are below.  (TDSTRIP strips out the symbol table and stores in as a separate file.  This is necessary for debugging a .COM file.)

@echo off
tasm -zi %1;
be ask "Continue linking? ",yn
if errorlevel 2 goto end
if errorlevel 1 goto continue
:continue
echo+
tlink /v %1;
tdstrip -s -c %1
rem exe2com %1
:end

-- Gordon Haff