Thanks :)

Regarding your previous question (upgrading program later on), you could try
using .DLLs.  You should however define the interface in advance (without
the code to support it).   Ie. define LoadJPG/SaveJPG procedures now (simple
begin;end) and when you have the time, add the actual  procedure into the
.DLL.

{$IFDEF DPMI}
const DPMIvar : boolean = true;
{$ELSE}
const DPMIvar : boolean = false;
{$ENDIF}
--
Pedt

{$IFDEF DPMI}
const DPMIvar = true;
{$ELSE}
const DPMIvar = false;
{$ENDIF}

In that way the compiler can optimize them

is IMHO better (unless you are paid by the line).

Precede it, for safety, with

{$IFDEF WINDOWS} **fail**  {$ENDIF}

Perhaps you should also consider what else the program might be compiled
with, perhaps in future, and include some IFDEFs on VER##.  I find it
useful to test some programs with Delphi 3 "DCC32 -cc", for example - it
gives useful warnings, though it is not a true superset of BP7 - whether
or not you expect to run that way.

I now often add {$I version.pas} to programs, to include
        http://www.merlyn.demon.co.uk/programs/version.pas

IIRC, that also means that one can write, rather than
     {$IFDEF DPMI} <DPMI code> {$ELSE} <non-DPMI code> {$ENDIF} ,
     if DPMIvar then <DPMI code> else <non-DPMI code> end ;
which will optimise to the same, but which has the advantage that the
compiler will check both branches for compilability, whichever option
one is currently using.  This helps one to keep the two branches
compatible when, for example, adding functionality.