JNOS 2.0 - DOS Install (The Easy Way) - Last updated on Thursday, April 30, 2009
Click here to return to the root documentation page ...


The easiest and quickest way to install JNOS 2.0 on a DOS system is to use the JNOS 2.0 installer program. In my opinion, this is an excellent way for people to get introduced to JNOS 2.0. It is great for people who have never used JNOS 2.0 before, or are still struggling to get something to work for them. NOW - the installer is very simplistic, and so is the configuration generated. The idea is to start off as simple as you can, then build on the configuration as your experience with JNOS 2.0 grows. There is nothing stopping even the most experienced people from using the installer. The installer is text based, no graphics libs are required.

What Are You Given


Click here to download a self extracting ZIP file of the complete installer package. Save it to C:\TEMP if you want.


After downloading the file above, run the following commands in the order listed :
  cd c:\temp
Just answer the questions as they come. The installer will give you some usages hints at the end. The JNOS program (executable, binary) that comes with the installer is not necessarily the latest version, and may not be compiled with all the options you want. If that is the case, you could try and compile your own flavour (which is what alot of people wind up doing anyway).

Note : network connectivity requires a packet driver. Before you run JNOS, read the hints and guidelines further below.

Click here for release history of the jnos installer ...

Hints and Installation Guidelines

*  Who can use the installer

1) Anyone who wants to run JNOS on a DOS machine with a network interface
   card, allowing JNOS to have network connectivity with the rest of the
   LAN through the network interface card.

2) Anyone who wants to run JNOS in Windows XP, Windows 2000, or Windows NT4,
   and have network connectivity between the JNOS and Windows, in turn making
   it possible to have network connectivity with the rest of the LAN.

3) It is possible to use Windows 95 and Windows 98, but Windows will have to
   give up ownership of the network card so that JNOS can control it through
   a packet driver loaded when Windows first boots up. Another alternative
   is to try the old NDIS drivers (see comments further below on this).

If you're not interested in network (IP) connectivity through windows or a
network interface card on the DOS machine, no big deal ! You can still use
this installer - just be prepared to see warning messages about a missing
packet driver when you run JNOS - the TNC and other stuff will work fine.

*  Requirements

a) The TNC in KISS mode !

   This simple installer assumes that you have a TNC that is already in
   the KISS mode. Refer to your user manuals on how to do this. Most TNCs
   you can connect to with a terminal program (teraterm or hyperterm) and
   from the CMD: prompt type something in like 'KISS ON', then 'RESTART',
   then disconnect from the terminal program, and the TNC is ready to be
   used by JNOS. Make sure the baud rate you give JNOS matches what was in
   use when you ran the terminal program to put the TNC into KISS mode.

b) A DOS machine, a network interface card, and a DOS packet driver that is
   made for the particular network card. For instance, years ago the NE2000
   compatible NIC cards were very popular, as was the NE2000.COM packet driver
   that was available for it. Before running JNOS at the DOS prompt, you would
   first run the NE2000.COM program, which loaded just like a TSR program.

   Once loaded, you would then run JNOS on top of it, and JNOS would attach
   to the packet driver, typically on software interrupt 0x60 for example.


   A Windows XP, Windows 2000, or Windows NT4 machine (doesn't matter if it
   has a network card or not), you could always configure a dialup connection
   instead (even if you didn't use it, just assign a static ip address).

   In order to run JNOS in a command session (typically called a DOS window
   by many users still), you would have to load the SWSVPKT driver first, and
   then the JNOS over top of it. Similar to the DOS setup, the SWSVPKT driver
   also loads like a TSR, giving you back the command prompt to load JNOS.


   For people using Windows 95 and 98, SWSVPKT is NOT designed for those
   platforms. There are ways to interface JNOS using old NDIS drivers and
   such, but I've decided not to pursue those configurations since they are
   not reliable, are problematic, and long unsupported by now. If you really
   want to try it anyways, then do a search on GOOGLE ...

   BUT here is a trick !!! Tell Windows to relinquish all control of an
   installed network card, then follow the instructions for a DOS machine
   to load the packet driver for that card. When Windows 95 or 98 boots,
   you can have the packet driver for a network card automatically loaded,
   then run your JNOS in a *DOS* windows. The important thing is that Windows
   MUST NOT be controlling the network card (just disable in device manager).

NOTE : The installer only setups up the JNOS configuration, it does not
       modified autoexec.bat, or config.sys, neither does it load any of
       the packet drivers for you. That is up to you to do first !

*  When asked - 'Enter the IP address of your JNOS system'

   If you are running JNOS on a DOS machine with a network card, then
   this is the IP address of the network card, since JNOS will be the
   one in control of the card - via a packet driver like ne2000.com,
   or something similar. That's all there is to it for DOS installs.

   If you are running JNOS on a Windows XP, 2000, or NT4 system, then
   you will need to pick an IP address that is on the SAME subnet as
   the IP address of the Windows machine. Make sure the IP address you
   select is NOT used by any other machine on the subnet. Technically,
   this is a big NO NO, since JNOS is now hidden from machines that
   should really be able to see it (since it's on the same subnet),
   but that's just the way the SWSVPKT driver works.

   Example :

      Your home LAN has a firewall router at - your windows PC
      is at, then pick for your JNOS ip address.
      If you ever add another machine to your home LAN, then just make sure
      you do NOT use for it, that's all.

   Sooo, if you want to be able to hit JNOS from other machines on the
   network, then those machines will have to have a route added telling
   them to use the Windows machine that JNOS is running on as a gateway
   to get to JNOS. Just add a static route on those machines that you
   want to be able to access JNOS from.

   Example :

     Suppose you had another machine at, the only way you
     will be able to get it to talk to JNOS is to have a route added to
     that machine, for example :

        route add gateway

   Again, I know this goes against standard rules on subnets, but that's
   how the SWSVPKT driver works. I hope that makes sense to you all.

   Remember that due to the nature of the SWSVPKT driver, the ip address
   of the network side of JNOS is on the same subnet as that of the Windows
   PC. This is technically a no-no, since it means that any other machines
   on the network will never be able to get to the JNOS system, since the ip
   address is not DIRECTLY on the subnet, but hidden on the Windows box.

   That's just how SWSVPKT works, no big deal (read on) ...

   The solution is simple. MAKE SURE that any machine that needs to talk to
   JNOS on the network, knows that to get to JNOS they will need to gateway
   via the Windows box that the JNOS runs on.

   I hope that makes sense to most of you :-)

* When asked - 'What comm port is your TNC connected to'

   I purposely made it so that users pick either 1 or 2. That way they do
   not have to be burdened with knowing things like COM1 uses port 0x3f8,
   interrupt 4, or that COM2 uses port 0x2f8, interrupt 3. The installr
   will set the appropriate port address and interrupt for you.

   IF you have a special case that falls outside the standard above, where
   you actually need to customize the port address and interrupt used for the
   serial port on which your TNC is connected, then just go ahead and pick 1
   or 2 (it doesn't matter), then manually edit the generated autoexec.nos
   after the installr program has finished running. Look for this line :

* When asked - 'Enter the baud rate for the serial port'

   This is the baud rate of the connection between the PC and the TNC. It
   is NOT the RF baud rate, keep that in mind.

* Now that JNOS is configured

   At some point, you will see the following displayed by the installr :

       JNOS is now configured. Hit the ENTER key to continue.

   Go ahead, hit the ENTER key - use the guidelines below ...

   a) Load the appropriate packet driver

   If you are NOT interested in network (IP) connectivity, then just skip
   this section. When you run JNOS, you will see warnings about a missing
   packet driver, but they are just warnings. JNOS should still be able to
   run and use the TNC and the other stuff you have configured.

    for DOS machines

   Suppose your dos machine has a ne2000 compatible network card installed.

   In this case, at the DOS prompt you will first run the NE2000.COM program,
   which will load like a TSR. Once you see that it has successfully loaded,
   the DOS prompt will return, at which point follow the instructions from
   the INSTALLR on how to run JNOS.

    for Windows XP, Windows 2000, Windows NT4 only

   Bring up a command session, maximize it using ALT-ENTER, then load the
   SWSVPKT driver (just enter the command SWSVPKT), wait for the prompt to
   come back. I assume you've properly installed the SWSVPKT driver already
   if are at this stage. Once the command prompt returns, just follow the
   instructions from the INSTALLR on how to run JNOS.

    for Windows 95 and Windows 98

   As mentioned before, IF you tell Windows to NOT control a network card,
   then you can load a packet driver at boot time, and run JNOS in a *DOS*
   window, just as if you were running it like a DOS machine (see above).

   The SWSVPKT is not designed for Windows 95 and 98, simple as that.

   b) Run JNOS as follows :

   Do exactly what the installer tells you to do. Notice it has built
   the prompt commands for you based on your input earlier.

   c) Once JNOS is running, try to telnet to it (as the installer suggests).

   That's it ... You now have a very simple JNOS system to play with. Once
   you get the hang of it, you can start adding other services, ports, and
   commands to autoexec.nos using EDIT or NOTEPAD. Get to know the commands,
   and what they do, look at the user guide.

   For example, you can run a POP3 server on JNOS, and then use your favorite
   email client to read mail off the JNOS system. You can run the SMTP server
   on JNOS and use your favorite email client to compose mail that will then
   get put on JNOS where it can be read by people connecting through the TNC.

   The possibilities are endless. I hope you have fun in the process.

Best regards to all,

Copyright (c) 2008 - Maiko Langelaar / VE4KLM