		Micro-x Accessor System Version 1.5.1
			By John F. Clark Jr.


Subject :   Building The Micro-x Accessor System Version 1.5.1


[Requirments ]

{a}. To build the Micro-x Accessor System version 1.5.1 you will need at
     least a 386 IBM compatible computer or higher, with a color VGA monitor.

{b}. You must install on your computer the Djgpp V2 compiler by DJ Delorie
     version  2.02 or higher. You can get the latest version of Djgpp at,
     http://www.delorie.com/djgpp/.

{c}. With your Djgpp V2 compiler you must have the Rhide IDE by Robert HoHone
     of at least version 1.4 or higher. The latest version of Rhide can be
     found at, http://www.tu-chemnitz.de/~rho/rhide.html/. 

{d}. You must also have installed the EZVGA Graphics Library by
     MATTHEW BENTLEY, at least version 1.4 . You may be able to find the 
     latest version at the DJ Delorie web site, see requirment {b} for web
     address.

{e}. The latest version of the NASM assembly language compiler and linker, or
     a compatiable. Goto the DJ Delorie web site, see requirment {b} for web
     address.


[Building  Micro-x]
First copy the Micro-x zip file to your Djgpp directory. Then use the
Pkunzip utility to unzip the file. Micro-x should unzip in the
Djgpp/Contrib/Micro-x directory. Below is a listing of required files to
build Micro-x that should be in the jcmx151s.zip file. 
......................................................................
MICROX1.CCP...........Main Accessor Program Source File.
MXLODER.C.............Accessor System Loader and Control Program Source File.
ACCSD15.DAT...........Setup Configuration Data File.
ACCSLNCH.DAT..........Operational Support Data File.
MCSUB1.CCP............Subaccessor#1 Program Source File.
MCSUB2.CCP............Subaccessor#2 Program Source File.
MCSUB3.CCP............Subaccessor#3 Program Source File.
MXLHWS.ASM............Operational Support Service Program.
MICRO-X.DOC...........Accessor System Documentation File.
MXBLD15.TXT...........Instruction for building Micro-x Ver. 1.5.1.
MICRO-X.DOC...........Accessor System Documentation File.
FLEUTIL3.C............Operational File Utility Program Source File.

.......................................................................
As of this writing, I have not built a make file for Micro-x. You must build
Micro-x using the Rhide IDE. Next you should start Rhide, and open a project,
name it Micro-x. See your Rhide documentation on how this is done. Next you
should add all of the .C AND .CPP source files in the Micro-x directory to
the Micro-x project that you open in Rhide. If you  have met all of the 
requirments above then have Rhide to build the project Micro-x, this should
compiler and link all of the source files in the Micro-x directory. If this
does not work for you, then you should load  one source file from the Micro-x
directory at a time, and compiler and link the source files until all of them
is done. When compiling and linking the Micro-x source files, there must be
no compiler warnings, or errors. There must be no linker warnings, or errors.
The executable programs for Micro-x must work without flaw. This is because
Micro-x is expected to run many different kinds of programs. If any of the
Accessor System programs have any defects, this will cause many of problems.
If you do have any warnings are errors, then you will have to find and fix
the problem. Warnings and errors can happen if you alter  or make changes to
the source files. Study the code well before making changes. The Mxlhws.asm
file can be built with the NASM assembly language compiler and linker. See
the DJ Delorie web site for the latest version of NASM. If you use something
else you may have to rework the code.

The file ACCSLNCH.DAT is the Micro-x chain link data file. You make this
file by creating a zero length file with a text editor. The editor that you
use must be a pure ASCII Text Editor. When the Accessor System start, it will
supply the needed data, are you may use the supplied ACCSLNCH.DAT file that
is supplied with the sources for Micro-x.

The next thing to do before test running Micro-x is to make sure you have a
good operational file. The utility program FLEUTIL3.EXE is use for building
the operational file. This utility will make a file call ACCSD15.DAT when it
is run. It would be a good idea to refresh your operational file with a new
copy before test running Micro-x. To do so, from the Micro-x directory, run
the program FLEUTIL3.EXE, and follow the on screen instructions. Continue to
press the enter key until the program ends. When this is done, you will have
produce a file call ACCSD15.DAT over writing the current file in the Micro-x 
directory. Don't forget to read the Micro-x documentation file MICRO-X.DOC.

When you have finished compiling and linking all of the files, and building
the data files, you should have the following list of files in your Micro-x
directory in-order for Micro-x to run. 
.................................................................
ACCSD15.DAT...................Setup Configuration Data File.
ACCSLNCH.DAT..................Operational Support Data File.
MICROX1.EXE...................Main Accessor Program File.
MXLODER.EXE...................Accessor System Loader and Control Program.
MCSUB1.EXE....................Subaccessor#1 Program File.
MCSUB2.EXE....................Subaccessor#2 Program File.
MCSUB3.EXE....................Subaccessor#3 Program File.
MXLHWS.COM....................Operational Support Service Program.
MICRO-X.DOC...................Accessor System Documentation File.
...................................................................

: From John F. Clark  ,  Enjoy Micro-x :

