Building the source tree in either DOS or Unix is nearly identical.

There ARE a few prerequisites, though...
	DOS:	The DJGPP compiler - Borland is no longer supported
		The DJGPP GNU make (might work with others)

	Unix:	TCL (tclsh)
		GCC compiler (probably works with others)
		GNU make (might work with others)
		Complete header files (for Linux, this means that the
		   Kernel sources need to be installed)

The actual compile is as easy as 1-2-3.........


1) Set up for proper makefile...

	DOS:	configure.bat
		(Sets up for proper makefile, and creates dummy make.inc and
		 depend files, and creates config.h file)

	Unix:	./configure
		(Sets up for proper makefile, and runs build-make.inc and
		mkconfig.tcl)

	Other functions may be added to the configure scripts at a later time.

	For both configure.bat and configure, you can add a new default
	installation directory to the command line, to override the
	default one of '/nos', like:
		configure.bat <nosdir>
	or
		./configure <nosdir>


2) [Optional step] Site-specific configuration

	This customization should NOT include editing the Makefile.
	Instead, all customizations should be placed in a file
	named 'make.inc', which will be included within the Makefile's
	processing, and commands in make.inc will be treated the same
	as if they were in the Makefile. This way ALL changes specific
	to your site are in make.inc, and will not have to be RE-DONE
	when you upgrade to later releases of TNOS.

	Edit the make.inc to your needs. Anything that you WOULD change
	in the Makefile, instead override it in make.inc by including it
	in make.inc.

	For example, if you wish to use a different directory for installing
	TNOS other than the default of '/nos', you could add a new NOSDIR
        (and NOSDIRCMD, for MSDOS) line in make.inc.

	Please consult the Makefile for what things you COULD change in
	make.inc, what values are valid, and what affect certain changes
	might have on other items. Consider the Makefile as the reference
	for make.inc changes.

	All changes/additions to the make.inc file should be made NOW, before
	moving to the next step.


3) Make it....

	make
	make install

Can't make it any easier!


NOTE: the 'make' utility MAY be named something different than 'make' on
your system, depending on the compiler, etc. For instance, some BSD users
have GNU's make named 'gmake'. I can't help you here, it should be
named 'make' ;-)


Under Linux, the compiles SHOULD be clear of errors and warnings, except for
two when linking (for newer Linux releases). These warnings are harmless.

Under DOS, the compiles SHOULD be clear of errors.


Note: You can cross-compile for DOS under Linux, using the i386-pc-msdosdjgpp
cross-compiler components. If you have those installed, you can do a:
	make dos
and make a compile MSDOS set of executables. These will be built in a
'msdos' subdirectory (that will be automatically created) within your
TNOS source directory. The executables can be found in that directory.

To change the options used to compile this cross-compiled version, edit
the config.dos file in the main TNOS source directory. This is used as the
'config.h' file for MSDOS compiling. The 'nospc.h' file is used for the MSDOS
compile as the 'hardware.h' file, and the 'makeinc.dos' file is used for the
MSDOS compile's 'make.inc' file.

When cross-compiling for DOS under Linux, there should be a WHOLE LOT of
warnings, do to minor problems with the i386-pc-msdosdjgpp header files.
These warnings are harmless.


-------------------------------------------------------------------------

There are some special notes below for BSD/OS compilation.

These are PROBABLY obsolete, since the current 'configure' script SHOULD
produce a proper 'make.inc' file. If you have problems under BSD, then
consult the README.BSD file, to see if any of those older notes apply.
