--------------------------------------------------------------------------------
README.TXT          DPMI-RSX  (c) Rainer Schnitker          9/93
--------------------------------------------------------------------------------

Unpack this archive with unzip50 or pkunzip.
type:		C:\> unzip	 a:\dpmirsx2.zip
  or:		C:\> pkunzip -d  a:\dpmirsx2.zip

Warning: In this release some files are renamed, delete the old files
from DPMIGCC1.ZIP


WELCOME
-------
This is the second release of RSX, the DPMI-DOS-extender for EMX/GCC and DJGPP.
It allowes to run the GCC programs under DPMI-servers like MS-Windows 3.1.
This release support also EMX-0.8g and unmodified DJGPP files. Many bugs are
fixed now.


The archive contains :

1) DPMI-compatible DOS-extender for unmodified GCC/EMX 0.8[e-g] programs.
     + 387 emulator
     + builtin-debugger
     + new stub to run RSX under DPMI and EMX otherwise.

2) DPMI-compatible DOS-extender for unmodified GCC/DjDelorie 1.06-1.10 programs.
     + 387 emulator
     + builtin-debugger
     + extra library to support missing ptrace(), spawnve(), signals(), etc.
     + new linker to build smaller programs (better for MS Windows)

3) DPMILIB 1.2, the DPMI-Library for the DPMI specification 0.9 / 1.0

4) all source codes ( RSX-extender, FPU-emulator )


Please read INSTALL.TXT in this archive before using this software.




WHY USING RSX FOR EMX/GCC PROGRAMS:
-----------------------------------
RSX.EXE can run unmodified EMX/GCC 0.8e/f/g programs under DPMI 0.9/1.0.
The compiler and other EMX programs can now run under DPMI-servers like
	MS-Windows 3.1,
	QEMM+QDPMI,
	386MAX, etc.
You don't need a 387-processor. A FPU-emulator will do this job.
-> EMX doesn't support DPMI and a 387 emu.


WHY USING RSX FOR DJGPP PROGRAMS:
---------------------------------
 RSXDJ.EXE can run unmodified DJGPP 1.06-1.10 programs under DPMI 0.9/1.0.
You don't need a 387-processor. A FPU-emulator will do this job.
Also you can debug your programs under DPMI.
-> GO32/DEBUG32 1.10 doesn't support DPMI-debugging and a 387 emu.

 For better performance RSXDJ.EXE doesn't swap before a system call(); it
reorganize the memory block by resizeing it from 4-5 MB to the real used pages.
If go32/gcc need 20 seconds to compile, rsx/gcc need only 15 seconds. The
perfomance is like gcc/16bit.

 An extra library LIBRSX.A for can be used. This includes spawnve, signals,
fork, ptrace, getpid stuff. The directory source\sample contain a debugger
using ptrace() etc.

 You can also relink your object files with gccn.exe to create a new a.out file.
The new programs don't use so much memory ( DJGPP uses 4 MB code-segments,
rsxdj.exe uses only the necessary size rounded up by 64 KB).


COPYRIGHTS/LEFTS
     in the directory \rsx\doc in this archive

mail to:
     rainer@math5.uni-bielefeld.de

