From:	"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Organization:	Materials Science Centre
To:	DJGPP AT DELORIE DOT COM
Date:	Mon, 13 May 1996 11:54:47 GMT
Subject:	djgpp 2 DPMI
Message-ID:	<3F207B0739D@fs2.mt.umist.ac.uk>

  Please reply to me in person, as I had to unsubscribe from djgpp group
because of chronic email intray overload.
  What is the progress of making (programs compiled and assembled and linked
by djgpp v2) fully portable and independent of any faults or absence of
whatever DPMI is in the PC that it is run on? One way might to be to:-
  (1) Write alternative bodies for the DPMI-calling functions
(_go32_dpmi_allocate_dos_memory() _go32_dpmi_free_dos_memory(), etc) which
don't call the DPMI interrupts but do all DPMI's work themselves.
  (2) Compile these into a library file DJGPP\LIB\LIBDPMI.A .
  (3) Then, if the user puts `-ldpmi' in his djgpp call arg list, his program
will compile into an .EXE file that contains its own DPMI and won't be hostage
to any faults or absence of whatever DPMI if any is in the system of the PC
that the program's .EXE file is transported to and run on.

- Raw text -