The DOS version of JNOS is once again in sync with the Linux version - 2.0f !

BEFORE you go any further ...

 * Ask yourself if there is any benefit using JNOS 2.0f over the
   original JNOS 1.11f in the DOS environment. The executable is
   larger with JNOS 2.0f, and available memory is important !

1) There is NO incremental update from previous versions, too much
   has changed, and a mass compile is required anyways.

   Put the zip file into an EMPTY directory, then unzip it. This will
   create a folder called jnos20f, change directory into the folder.

2) Edit the config.h and set your preferences. More experienced people may
   be tempted to put their own config.h into the current folder. I suggest
   you don't. If you do and things don't work, then sorry I can't help.

   I suggest you make a backup copy of config.h before you edit it :

      copy config.h config.bak

   Keep in mind, it can be a challenge to edit the config.h for DOS
   installations. Getting the size of the executable under 450 MB is
   a challenge, so picking options can be a bit of an exercise.

   * Again, ask yourself if JNOS 1.11f will serve you just as well.
   
3) I have compiled this under 2 different compilers, they are :

  Borland C++ 3.0 Copyright (c) 1991, TLIB 3.02, Turbo Link 5.0, Make 3.6
  Borland C++ 3.1 Copyright (c) 1992, TLIB 3.02, Turbo Link 5.1, Make 3.6 

   That means if you are trying to do this with any other compiler, you're
   on your own. In other words, please don't ask me to help you, since I
   have no other compilers, nor the time to try other ones out. Thanks.

   This install assumes that the Borland compiler is installed under :

       c:\borlandc

4) IF the Borland C++ compiler commands are NOT in the PATH already, then
   from inside the JNOS source folder, run the following command :

    setcomp.bat

   That will modify the PATH environment variable to include the path to
   the Borland C++ compiler commands. NOTE, depending on which Borland C++
   you are using, you may have to FIRST edit the setcomp.bat and make sure
   the path is set properly (default is c:\borlandc).

   Before you compile, also check the MAKEFILE, and look for a PATH define
   around line # 40, make sure it points to the proper directory where the
   Borland C++ compiler is installed (default is c:\borlandc).

   Finally, to compile the source, just issue the following commands :

    make clean
    make

   Please note that warnings will happen, I know about them already, so
   please ignore them. There is NO need to run 'make depend', even though
   it does work now, I never use it, and don't see the need right now.

   NOTE: I've forced compiler flags to assume an 8086 architecture. If you
   want 80486, then you'll have to set your own flags in the MAKEFILE. For
   those that don't know how to do this - sorry. When I get some free time,
   I will write down some options for you in this file, but not today.

5) That's it, if all goes well, you should have a new 'NOS.EXE' executable.

January 25, 2008, Thursday
Maiko Langelaar / VE4KLM
JNOS 2.0f released