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


Subject :   Building The Micro-x Accessor System Version 1.5.5 GXV


[Requirements ]

{a}. To build the Micro-x Accessor System version 1.5.5 GXV 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 have installed the Allegro Graphics Library By Shawn Hargreaves,
     version 3.0 or higher. you can get the latest version of Allegro at,
     http://www.talula.demon.co.uk/allegro/ .

{e}.  With the Allegro Library, you must have installed, the DEGUI Allegro
      Graphics Library Extension, by Dug Eleveld . You will need at  least
      version 1.21 or higher. You can find the latest version of  DEGUI at,
      ftp://huizen.dds.n/~deleveld/index.htm.

{f}. 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]

To start building Micro-x, copy the jcmx155s.zip file to the Djgpp directory,
and unzip the file in this directory. Don't worry about  a directory structure,
all of the files for Micro-x should unzip in the /Djgpp/Contrib/Micro-x directory.
(note) copy the header files font.h, and mxacc.h from the Micro-x directory to
your Djgpp include directory, or edit the include lines in mx155.cc, and mxed.cc
to include the direct path to where these files are stored.

I did not build a make file for Micro-x because of the extra libraries that
is required to build 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
source files in the Micro-x directory to the Micro-x project that you open in
Rhide. If you  have met all of the requirements 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. 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.

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.

After you have success at building all of the source files into .exe files,
you must now build up all of the .CFF and .cfg files. All of the .cff files
are built using the FILE1555.EXE utility program. This utility makes a file
call ACMX155.DAT. Use this file to make copies of all of the Micro-x version
1.5.5 operational files. Copy this file into ACCMMAIN.CFF, ACCMSUB1.CFF,
ACCMSUB2.CFF, and ACCMSUB3.CFF.

You must now build all of the .CFG files. To build these files you will need
a pure ASCII text editor. The code for these files must be entered in a ASCII
code format. See your text editor's documentation on how this is done. YOU must
not use a word processor to view are edit the .cfg files, because in a word
processor some of the ASCII code will not show. Use the sample .cfg files that
comes with the sources as a guide to go by. You can use these with your program
instead of making new ones, that is if you did not alter the source files.

Now you must build up the Allegro data files. To do this you must use the data
file utilities that come with the Allegro Graphics Library. You should build two
Allegro data files, one for the program MX155.EXE, and one for the program
MXED.EXE. The data objects that go into mx155.exe is defined in the header file
MXACC.H. The data objects for the program mxed.exe is defined in the header file
FONT.H. When this is done you must compile each of the data files to the .exe files.
see the Allegro Graphics Library on how this is done this. (note) You can produce
the BMP image files with tools find in the Allegro and DEGUI graphics Library.
You can use any kind of fonts that you want, as long as the point size remain the
same as it is defined in the header files. The last three characters on the font
object's name is the point size. (note) The data file for MX155.EXE should be name
MX_ACC.DAT. The data file for MXED.EXE Should be name MXEDCFG.DAT.

When you have finished compiling the data files to the .exe files, check the Micro-x
directory for all of the files that should be there. Below is a listing of files that
you should have for Micro-x in the Micro-x directory.
......................................................................
ACCMMAIN.CFF............Main Operational File
ACCMSUB1.CFF............Sub#1 operational File
ACCMSUB2.CFF............Sub#2 operational File
ACCMSUB3.CFF............Sub#3 operational File
COPYING.................Copy of GNU general Public License
HARDWARE.TXT............Hard Ware Setup Information
MX155.DOC...............Micro-x Documentation File
MX155.EXE...............Accessor System Main Program
MX155LCH.CFG............Micro-x Configuration File
MXCFG.CFG...............Micro-x Configuration File
MXED.CFG................Editor's Configuration File
MXED.EXE................Accessor System Editor
MXLHWS.COM..............Micro-x Support File
MXLODER.EXE.............Micro-x Control Program
MXSYSINF.EXE............System Information Program
README.TXT..............Instructions To Install Micro-x

Next is a listing of all of the files that should be in the jcmx155s.zip file.
.................................................................
COPYING.................Copy of GNU general Public License
FILE1555.C..............Source File for Operational File Utility
FONT.H..................Font definition header file.
HARDWARE.TXT............Hard Ware Setup Information
MX155S.MFT..............Manifest Listings
MX155.DOC...............Micro-x Documentation File
MX155.CC................Accessor System Main Program
MX155LCH.CFG............Micro-x Configuration File
MX155S.VER..............Version Infromation
MXACC.H.................Object and Font definition header file.
MXBUILD.TXT.............Instructions to build Micro-x
MXCFG.CFG...............Micro-x Configuration File
MXED.CFG................Editors Configuration File
MXED.CC.................Accessor System Editor
MXLHWS.ASM..............Micro-x Support File
MXLODER.C...............Micro-x Control Program
MXSYSINF.C..............System Information Program
READ.ME.................Information File For Micro-x

...............................................................
One other thing to do before test running Micro-x is to copy the video driver
file VBEAF.DRV to the root directory of the drive that Micro-x is loaded on.
A copy of this file should be provided with the Allegro Graphics Library.
Next run and test your new Micro-x Accessor System. Don't forget to read the
Micro-x documentation file MX155.DOC.

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

