  
  A. Win32 Apps Compatibility List
  
  This is a list of Win32 console apps successfully tested to run with HX

    executable   version comment 
  -------------------------------------------------
  - 7Z.EXE       4.17    7-Zip
    7ZA.EXE
  - AS.EXE       2.13.90 AS (MinGW)
                 2.15.94
  - ASW.EXE      2.9.5   AS (Free Pascal [Win32])
  - BCC32.EXE    4.0     Borland C++ compiler
                 5.5.1   C++ compiler of C++ Builder Command Line Tools (free)
  - BRC32.EXE    5.02    Borland resource compiler 
                 5.40
  - CL.EXE       10.20   MS VC 4.2
                 11.00   MS VC 5
                 12.00   MS VC 6
                 13.00   MS Visual Studio.NET 2002
                 13.10   MS Visual C++ Toolkit 2003, a FREE compiler (*)
  - CVTRES.EXE   5.0     MS tool
                 7.00
  - DCC32.EXE    15.0    Borland Delphi 7 compiler
  - DUMPBIN.EXE  5.12    MS tool
                 7.00
  - DUMPLX.EXE   2.1     LE/LX file dumper
  - DUMPPE.EXE   2.1     PE file dumper
  - EXTRACT.EXE  5.1.2600
  - FBC.EXE      0.13    FreeBasic (Win32) compiler (*)
  - FPC.EXE      1.0.10  Free Pascal compiler (*)
  - FTE.EXE      0.49
  - GCC.EXE      3.3.1   GNU C++ compiler, MinGW (*)
  - H2INC.EXE    7.0     MS tool
  - HEXITW.EXE   1.57    HexIt (Win32)
  - ILINK32.EXE  5.0     linker of C++ Builder Command Line Tools (free)
  - LD.EXE       2.13.90 LD, MinGW (*)
  - LDW.EXE      2.9.5   LD, Free Pascal (Win32)
  - LIB.EXE      3.4     MS OMF 16-bit librarian  
  - LIB.EXE      5.12    MS COFF 32-bit
                 7.00
  - LINK.EXE     5.60    MS 16-bit OMF linker
  - LINK.EXE     5.12    MS 32-bit COFF linker (**)
                 7.00
                 7.10
  - LZASM.EXE    0.47    Assembler, Win32 version                 
  - ML.EXE       6,14    MS MASM
                 6.15
                 7.00
  - NASMW.EXE    0.98.38 Netwide Assembler (Win32)
  - NMAKE.EXE    1.62    MS tool
                 7.00
  - OPEN WATCOM  1.2     all executables in directory BINNT except WD.EXE
  - POCC.EXE     2.90    Pelles C compiler
  - POLIB.EXE    2.90    Pelles library manager
  - POLINK.EXE   2.90    Pelles linker
  - POMAKE.EXE   2.90    Pelles make
  - PORC.EXE     2.90    Pelles resource compiler
  - SC.EXE       8.38    Digital Mars C++ compiler
  - RAR.EXE      3.0
                 3.3
  - RC.EXE       5.0     MS resource compiler
                 5.1
  - REBASE.EXE           MS tool
  - TASM32.EXE   5.0     Borland's TASM (Win32)  
  - TDUMP.EXE    5.0     Borland tool
  - TLIB.EXE     4.5     needs a nonempty command line or will cause a GPF
  - TLINK32.EXE  2.0     Borland linker (Win32)
  - UNRAR.EXE    3.2
  - UNTGZ32.EXE  0.95
  - UNZIP.EXE    5.4     Info-ZIP (Win32)
                 5.52
  - ZIP.EXE      2.31    Info-ZIP (Win32)               

  Most of these apps will run with versions of DOSEMU >= 1.3.1 as well,
  although switch DPMILDR=8 may not work in this environment (see below).
  
  (*): requires LFN support to be installed. View Unsupp\unsupp.txt for
       more details about how to activate this support for plain DOS.

  (**): For large projects MS LINK may require a lot of file handles,
       which is a scarce resource in native DOS (set by entry FILES= in
       CONFIG.SYS, max. value is 255). In case an app exceeds this
       limitation, you may get strange error messages, so I would suggest
       to set at least FILES=80.
       

  B. Nested Execution of Win32 Apps in DOS

   Launching a Win32 app by another is a problem in native DOS if the
  second app has no relocation infos. That's because both apps would
  share one address space, so the second one most likely has to be
  relocated. The HX DOS extender DPMI server HDPMI may run in several
  instances, thus providing multiple address spaces. To activate this
  feature set environment variable DPMILDR:

    SET DPMILDR=8

   This should allow a Win32 app to launch another even if the latter
  has no relocation infos. So for example it's no problem to run
  NMAKE.EXE launching LINK.EXE which in turn launches CVTRES.EXE.
  This may work for other DPMI servers as well (but not for DOSEMU!).

  If multiple address spaces are not supported by the host, but a version
  of the calling app is available *with* relocation info, you can possibly
  rebase this first app by utility REBASE.EXE (Win32 SDK). Thus the 
  standard image base address 400000h remains free for the called app.

  Please note that it is sometimes not obvious that a nested execution
  takes place. MS LIB.EXE (COFF), for example, uses LINK.EXE for the
  real work. The same is true for EDITBIN and DUMPBIN. As well, MS LINK
  (COFF) will launch an instance of itself (!) if an export file has to
  be build.

