
UDI Developer’s Toolkit
6-4
Universal Debugger Interface Specification
When built with the DOS IPC source code, both the real–mode DFEs and
TIPs and protected–mode DFEs and TIPs will interoperate in all four
combinations. This is true for both plain MS–DOS and in a DOS window
initiated from within Microsoft Windows
t
. However, a limitation of
DPMI 0.90 (which is the protected mode interface implemented by
Microsoft Windows) allows, at most, one DOS extender in a DOS window
initiated from within Microsoft Windows. The sample code has a special
work–around for this limitation if both the protected–mode DFE and
protected–mode TIP are built with the Phar Lap DOS extender. We do not
know of a solution when the protected–mode DFE and protected–mode
TIP are built with two different DOS extenders.
The DOS IPC code cannot be used to build DFEs and TIPs that are true
Microsoft Windows applications.
Directory Structure of the Toolkit
src/udi
This directory contains the sample IPC source code for both the DOS IPC
method and the UNIX socket IPC method. These include
.c
files,
.h
files, and a
few
.asm
files (for the DOS IPC method). Developers building their own DFE
or TIP would link with these
udi
files. See below for more detail on these files.
src/uditools
These are the source files used to build the TIP tester (
uditest
) and the UDI
trace utility (
uditrace
). Developers building their own DFE or TIP would not
link with these files, but may wish to use them for testing and debugging.
src/minimon
The directory structure of the MiniMON29K source tree is described in the
MiniMON29K documentation. The discussion below describes only those
parts of the tree which are relevant to UDI development.