
		Guide to compile the sources

The sources were compiled using
Microsoft C/C++ 7.0	hm... not sure you you cuold get it 
	d:\c700
This compiler does not work under plain DOS. DPMI is required.

Microsoft MASM 6.11c	avaliable on the net (www.microsoft.com)
	d:\masm611
This compiler may work under plain DOS. 

WATCOM C/C++ 11.0c 	available on the net (www.openwatcom.org)
	d:\watcom
I believe, there is version of this compiler working under plain DOS.

The environment was DOS box under Microsoft Windows NT 4.0
The Micro X sources were placed in d:\x

Copies of the batch file used below are in \x\util\compiler
so you can reuse them. They need to be changed to reflect your
placement of compilers and then copied to respective directories.

Compiling 286 branch
  d:
  cd \c700
  c70.bat
  cd \x\286
  nmake cleanall
  nmake all

Compiling 386 branch, Microsoft part
Set envirom variables as for 286
  d:
  cd \c700
  c70.bat
Now compile
  cd \x\386 
  nmake -f makefile.msc clean
  nmake -f makefile.msc all

Compiling 386 branch, Watcom part 
Start with a clean envirom, that is not contaminated with that 
from Microsoft part
  d:
  cd \watcom
  envirom.bat
  cd \masm611
  cd binr
  new-vars.bat
  cd \x\386

		Source codes change
2003/05/02 mxsrc01.zip, mxbin01.zip
* Makefiles were created or changed where neccesary so that the whole
source tree can be now easily compiled.
* Several files were corrupted, in some case the damage was minor and source 
codes were easily fixed. In some parts (graphics drivers in the 286 part)
were only guessed.
* It was not able to recreate the source codes in 8514 graphics, so this 
card is not supported. The card is already dead on the market though.
* There is fixes.txt file in every directory where changes took place 
with more details. 
* There is no support for Novell, BW-TCP, PC-NFS, PC-TCP or TCPOPEN since  
they require commercial libraries I do not have nor plan to buy.
* There is no support for Ergo extender for the same reason.
* Unused files were placed in respective unused subdirectories.
* No effort was ever made to check sources related to X11R5.

		Possible work
I was not able to connect to a modern Linux machine using Micro-X.
I tried both original Micro-X binaries and thesse fresly compiled ones.
The X server refuses to open a window so I cannot proceed any
further. I was only able to run rsh and rexec that come with Micro-X.
I had no troubles running a Win32 demo version of MicroX.
I nned to know how Micro-X can be used to connect to a Unix machine to
continue the work.

Perhaps one should consider changong from Microsoft tools to Watcom ones.
Duplicate files should be removed.
