Assembly language programmers should link together the application object modules (OBJ files) and any support libraries using the WL32 protected mode linker. The linker automatically adds the DOS extender to the resulting executable EXE file.
When running the DOS-extended application, DOS first loads the CauseWay DOS extender in conventional memory. CauseWay establishes the protected mode environment, retrieves the application from the executable file -- loading it first into extended memory, then conventional memory if extended is exhausted, then virtual (disk-based) memory if conventional is exhausted -- sets up the application for execution, and finally passes control to the application to begin operation. No additional files are required to make your application run in 386 protected mode using the CauseWay DOS extender.
CWSTUB.EXE will execute stand-alone Watcom LE-format files in the same way as DOS4GW.EXE does if the full file name, including extension, is listed after CWSTUB, e.g. CWSTUB RUNME.EXE. CWSTUB will override the extender bound to the application EXE, if any, with the CauseWay DOS extender version in CWSTUB.EXE.
DEBUGGING USING WD, THE WATCOM DEBUGGER
To debug CauseWay programs with the Watcom debugger after installing the CauseWay files, simply use the /tr=crw command line option. For example:
WD /tr=cw myprog
This process can be automated by adding /tr#cw to your WD environment variable. Use the SET WD=tr#cw command.
By default, CauseWay uses a Ctrl-Alt keypress to interrupt the WD debugger, rather than the Print-Screen key. This can be changed to any two, three, or four keypress value by modifying the ASCII file CWHELP.CFG at the BreakKeys line. See comments in this file for further detail. Note that a single keypress value will not work properly.
Go to Table of Contents