Draco disk #2: compiler and tools. Files on disk: README.TXT - shareware notice FILES.TXT - this file DRACO.COM - the compiler itself (this version of the compiler lacks long (prefix 0L) and float constants, but will run in a 56K TPA) DRCERR.DAT - file of error messages used by the compiler (if this isn't on your default drive, error numbers only will be printed by the compiler) LINK.COM - the link editor TRRUN.LIB - library of run-time routines (automatically searched) TRCPM.LIB - library of CP/M interface routines (automatically searched) CRT.LIB - library of CRT independent I/O routines (programs need configuring) UTIL.G - include file with some utility declarations OPDEF.G - include file with operator bits for operator types CRT.G - include file for CRT independent screen I/O FORM.G - include file for input forms part of CRT.LIB DLIB.COM - Draco librarian DAS.COM - Draco assembler DDIS.COM - Draco dissassembler XREF.COM - object file cross-referencer DED.SET - Draco screen editor (configurable) CONFIG.COM - program to manipulate terminal definitions and to configure programs which use the terminal independent I/O routines (*.SET) CONFIG.DAT - database of terminal definitions CMP.SET - visual binary/text file comparison program (configurable) HEDIT.SET - hexadecimal file viewer/editor (configurable) BIGDRACO.COM - version of compiler with long/float constants (needs a 60K TPA to run). The other version understands types 'float', 'long' and 'ulong', but only this version understands long constants (> 16 bit or with a leading '0L') and float constants. When compiling, file DRCERR.DAT should be on the currently selected drive. When link-editing, files TRRUN.LIB and TRCPM.LIB should be on the currently selected drive. A normal disk for use with Draco will contain: editor (e.g. DED.COM), DRACO.COM, DRCERR.DAT, LINK.COM, TRRUN.LIB, TRCPM.LIB, and, if needed, CRT.LIB The disk containing your source files will also normally contain: as needed, UTIL.G, OPDEF.G, CRT.G, FORM.G In brief, if you have a fairly small program, in only one source file, which doesn't have too much in the way of variables, in source file TEST.DRC on the current drive, and that drive also contains the above required files, then you can compile, link and run it with: A>draco test A>link test A>test A more complex example (see documentation for more details) could be: A>draco t1 t2 t3 (or perhaps draco * ) A>link t1 t2 t3 crt.lib -somyprog A>myprog