pc micro systems

Beta Test
User's Guide
Company Info

                        -= NetFoss Internet FOSSIL =-
                                for Windows

                                Version  1.16
                                 May 1, 2017
                       Copyright (c) 2001-2017 PC Micro

 NetFoss is a 32-bit FOSSIL driver providing Telnet & Modem communications
 for DOS applications under 32-bit Windows 10/8/7/Vista/XP/2000 and all
 32-bit versions of Windows Server 20xx. NetFoss supports the revision 5
 FOSSIL specifications plus the extended FOSSIL functions defined in X00.

 A FOSSIL [Fido Opus Seadog Standard Interface Layer] is a driver which
 allows DOS based modem communication software to communicate through an
 interface that directs to the actual hardware (such as a dialup Modem).
 Originally FOSSIL drivers were only designed for serial communications.
 NetFoss communicates with dialup Modems, Virtual Modems, or with TCP/IP
 using its own Network Telnet Communication engine, NetCom.


        * 32-bit version of Windows 10\8\7\Vista\XP\20xx, or a
          64-bit version of Windows running "Virtual PC XP-Mode" or
          other VM software such as VMware, Hyper-V, or VirtualBox
          with a Win32 Guest OS.

        * DOS application(s) designed to communicate with a FOSSIL driver.
          For example: BBS software, BBS external door, a Terminal, etc.


        * A Third party Telnet Server can be used instead of Net2BBS.

        * A Virtual Modem such as NetSerial can be used instead of
          Net2BBS and NetCom.

        * A Command Prompt Shell such as Doorway can be used for
          remotely executing Console or DOS applications from a
          FOSSIL. (This should only be done by IT professionals aware
          of the security concerns in doing so).


        * Extremely fast, written entirely in ASM (MASM32).
        * Small footprint, uses under 16k RAM overhead per node.
        * CPU Usage detection / optimization for DOS applications.
        * Acts as a DOS TSR (Terminate and Stay Resident) driver.
        * Includes a Telnet Server (Net2BBS) supporting 256 nodes.
        * Includes a Service compatible console redirector (NetSpy). 
        * Internal Telnet and COM port or Modem support.
        * Compatible with nearly all DOS BBS and door software.
        * DESQview emulation: redirects DESQview timeslice release
          functions to Windows.
        * Enhances Zmodem transfer performance for BBS downloads.
        * Allows DOS BBS software to spawn Win32 external doors.

 Table of Contents

        Installing NetFoss
        - Door32.sys Usage
        - Non-Door32.sys Usage
        List of compatible Telnet servers
        Installing Net2BBS Telnet Server
        BBBS/D Usage
        EleBBS Usage
        EzyCom Usage
        GAP BBS Usage
        MysticBBS Usage
        Oblivion/2 Usage
        PcBoard Usage
        PC-Express Usage
        ProBoard Usage
        RemoteAccess Usage
        Searchlight Usage
        SpitFire Usage
        Synchronet Usage
        T.A.G Usage
        Telegard/Renegade Usage
        Virtual Advanced Usage
        Wildcat Usage
        WWIV Usage
        Doorway Usage
        Door Game Usage
        X00 Function 02 Kluge
        COM Port Mode
        COM Port Locking
        COM Port Release
        Compatibility Issues
        Output Speed setting
        Zmodem File Transfers
        Optimizing PD Zmodem speed
        NetCom.exe Command Line Switches
        NetCom.ini Configuration Settings       
        Frequently Asked Questions
        NETFOSS.COM Error Messages
        NETCOM.EXE Error Messages
        How NetFoss Works
        Suggestions for Door/BBS developers
        FOSSIL INT14 Function Reference
        License and Disclaimer        
        What's New



 NetFoss is a 32-bit Windows FOSSIL driver for DOS based applications
 running under the Windows NTVDM. It was originally released in 2001.

 NetFoss is compatible with COM ports and Modems (either real or virtual),
 or NetFoss can be passed active Telnet connections from a Telnet Server.
 NetFoss includes a simple Telnet Server called Net2BBS, and it can be
 used with several other other telnet servers.

 NetFoss is freeware, provided without warranty. We encourage any bug
 reports and suggestions which can be emailed to support@pcmicro.com.


 Installing NetFoss

 Make sure you are installing NetFoss in a 32-bit version of Windows, since
 64-bit Windows do not include an NTVDM (Virtual DOS Machine), which allows
 DOS software to run under Windows.

 If you are using Windows 10, be sure to configure the NTVDM Command Prompt
 to use "legacy console". To do this open a Command Prompt, right click the
 icon in the upper left corner, and select Properties. From the Properties
 Options tab, enable the "Use legacy console" checkbox, and click OK.

 NetFoss only functions under the Win32 NTVDM. It does not support DOSBox.

 Place the following files into a directory such as c:\netfoss

 NF.BAT           A batch file used to load/unload NetFoss.
 NFU.EXE          NetFoss Utilties for running DOOR32 doors.
 NETFOSS.COM      NetFoss FOSSIL TSR Interrupt handler.
 NETFOSS.DLL      The NetFoss FOSSIL Virtual Device Driver.
 NETCOM.EXE       NetCom Telnet Communication Engine for NetFoss.
 NET2BBS.ZIP      Net2BBS Telnet Server package

 If you wish to use the Net2BBS Telnet Server, then unzip NET2BBS.ZIP
 archive into the same folder. This archive contains these files:

 NET2BBS.EXE      The Net2BBS miniture Telnet Server.
 NET2BBS.INI      The Net2BBS .INI configuration file. (renamed)
 NET2BBS.TXT      The Net2BBS help file - documentation.
 NET2MON.EXE      The Net2BBS Service Monitor.
 NETSPY.EXE       The NetSpy Service Console redirector
 SocketPolicy.xml Net2BBS SocketPolicy file (For Telnet over Web Flash).

 The following files are not required for NetFoss and NetFoss operation:

 NETFOSS.TXT      The NetFoss documentation (You are reading it now).
 NFU.TXT          The NetFoss Util for DOOR32 documentation.
 FOSSIL.TXT       Technical Reference: FOSSIL implementation and use.
 FOSSIL.CHT       Technical Reference: FOSSIL command chart.
 NET2SRC.ZIP      The MASM32 Source Code for Net2BBS/Net2Mon/NetSpy.

 1. NETFOSS.DLL installation:
 *** IMPORTANT *** If You are using Windows Vista or a later version of
 Windows such as Windows 10/8/7 or Server 2008/2013, you will need to copy
 the NETFOSS.DLL library into the \windows\system32\ directory.  This can
 be done by entering the following command line:
    copy c:\netfoss\netfoss.dll c:\windows\system32\

 To open an Adminstrator Command Prompt in these versions of Windows,
 right-click on a "Command Prompt" icon and select "Run as Administrator".
 For older versions of Windows, including XP, 2000, 2003 this is not
 required as long as the directory where NETFOSS.DLL is located is
 in the Windows %Path%. 
 To view which directories are in the Windows %Path%, go to the Control
 Panel System Properties > System > Advanced > Environment Variables
 and view the "Value" assigined to the System Variable named Path.
 Or from a Command Prompt, type "set path".

 2. NET2BBS.INI Configuration:

 Rename the file NET2BBS.SAMPLE.INI to NET2BBS.INI unless you already
 have one. This is the Net2BBS configuration file.  Edit this file as
 needed. You can skip this step if using a third-party telnet server.
 See NET2BBS.TXT for detailed help. 

 3. NF.BAT configuration:

 Edit your NF.BAT batch file and change any of the paths as needed.
 Do not add any "CD\" commands to the batch file to change directories,
 or it may not be able to find a DOOR32.SYS file which it expects in
 the current directory if no /n{node} parameter was passed on the
 command line. (See section below for details on this).

 If your BBS does not support the DOOR32.SYS drop file, you will need
 to make an additional change to your NF.BAT file as shown in the
 Non-DOOR32.SYS mode section below.

 4. Firewall Configuration.

 If you are running Firewall software you will need to allow incoming
 access on TCP port 23 in order to receive incoming telnet connections.
 Newer versions of Windows allow enabling this in the Windows Firewall
 automaticly in a dialog when Net2BBS runs, while with older versions
 you have to manually go to the Windows Firewall icon in the Control
 Panel, and add a port under the Exceptions tab by selecing "Add Port"
 and enter the following data:
      Name: Telnet
      Port number:   23
      Then make sure the TCP setting is enabled for this new port.

 5. Understand basic concepts:

 A "node" is a separate process of the BBS software, run in its own
 Virtual DOS Machine (NTVDM), or Window.
 Each node accepts a single user to login and access the BBS using
 either a modem connection or a Telnet connection.
 You can optionally use NetFoss with Virtual Modems such as the ones
 created by installing NetSerial, a commercial COM port redirector
 software with a modem emulator supporting up to 256 virtual modems.

 Up to 65535 nodes can be created by NetFoss, depending on system
 resources and the software being used. Most BBS software supports up
 to 256 nodes, and the Net2BBS Telnet Server also supports up to 256

 NetFoss can function in either "Telnet Mode", or "COM port Mode".

 When used in Telnet mode, NetFoss accepts any COM port value up to
 4096, and the same COM port value can be used on all nodes, allowing
 BBS programs and doors to work on any node, even if they are limited
 to functioning on only COM1 thru COM4. To take advantage of this,
 set all nodes to use the same FOSSIL port, such as COM1. NetFoss will
 ignore the COM port number that it is passed with an INT 14h call.

 When used in Telnet mode, NetFoss requires that each node use a
 unique WinSock handle. When used in COM port mode, NetFoss requires
 that each node use a unique COM port value (or COM port handle).

 If You are using DOS based BBS software, skip the next chapter and
 continue at the Non-Door32.SYS Section further below.


 DOOR32.SYS Usage

 DOOR32.SYS is a drop file format for 32-bit BBS software or doors.
 A drop file is created by BBS software to pass information about the
 active connection to an external program.

 NetFoss supports both Reading DOOR32.SYS dropfiles created by a
 Windows BBS software, as well as writing it's own DOOR32.SYS drop files
 to allow a DOS BBS to run Win32 Doors. See further below for the later.

 DOOR32.SYS For Windows BBS Software:

 If you are using NetFoss with a Windows BBS (such as EleBBS for example)
 which can create both a DOOR32.SYS and a standard dropfile such as
 DOOR32.SYS then you do NOT need to pass the node number, or telnet socket
 handle to either NetFoss or NetCom. Instead they will be read from the
 DOOR32.SYS dropfile that the BBS software places in the current (node)
 directory before execuling the NF.BAT batch file.

 Some Windows BBS programs which support DOOR32.SYS dropfiles can not
 create a standard drop file at the same time (i.e.: MysticBBS 1.07.03
 and Synchronet 3.10). In this case DOOR32.SYS mode should not be used.

 You will need to edit the door command line for each of your doors.
 A typical type-7 command line in EleBBS would look like this:

 C:\BBS\NF.BAT c:\bbs\lord\start.bat *N
 ^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^
    |                     |
 This loads NetFoss.     This is the batch file that runs a door.

 Note that in this example NF.BAT is not passed any information on which
 node or TCP socket handle to use. That is because both NETFOSS.COM and
 NETCOM.EXE will find this information by reading the DOOR32.SYS from the
 current directory.

 In the above example EleBBS is passing the *N macro to the doors batch
 file, and the *N is replaced with the current node number by EleBBS.

 DOOR32.SYS for DOS BBS Software:

 NetFoss includes a utility called NFU.EXE, which allows DOS BBS Software
 to run Win32 software including doors that require a DOOR32.SYS drop file
 A seperate documentation file named NFU.TXT is included with detailed
 instructions on how to use it with several detailed examples.

 Non-DOOR32.SYS Usage

 To run a DOS based BBS under Windows in Telnet mode, you also need to
 install either of the following software applications:

 A. A Windows compatible Telnet Server, such as the included Net2BBS.
    Or choose one of several other freeware Telnet Servers for Windows.

 B. A Virtual Modem designed for Windows, such as NetSerial, which can
    emulate up to 256 virtual COM ports and supports Modem AT Commands.

 There is a list of free Telnet Servers compatible with NetFoss below.

 NetSerial is a commercial Virtual Modem and COM port redirector which
 creates up to 256 Virtual Modems under Windows. Each Virtual Modem can
 be assigned to a BBS node which answers the next incoming Telnet
 connection as if it was communicating with a real dialup Modem.

 NetSerial also allows outbound telnet connections to redirect to your
 application software such as a FidoNet Mailer or a Terminal program by
 "dialing" an IP address and making a Telnet or RAW TCP/IP connection as
 if it was a phone number. NetSerial includes advanced features like
 SSL Encryption, and realtime COM port tracing/logging of all data flow
 and Virtual Modem AT commands and responses.

 NetSerial is available to BBS Sysops at a discounted price of $25 USD.
 Contact sales@pcmicro.com to request the Sysop discount offer.
 NetSerial is available for download at http://pcmicro.com/netserial

 NetSerial is designed to work with NetFoss - and also works with DOS
 based FOSSIL drivers running under Windows, such as ADF, BNU and X00.
 NetSerial can also work without a FOSSIL, by allowing DOS applications
 to access it's Virtual COM ports directly.

 Please refer to the "Using NetFoss with a COM port" section of this
 guide for details on configuring NetFoss to work with NetSerial.

 For Non-DOOR32.SYS mode, you will need to change one line of the NF.BAT
 file, to pass the node number to NETFOSS.COM. This is only needed if you
 are running either A) DOS based BBS software, or B) Win32 BBS which does
 not create a DOOR32.SYS drop file when it runs a DOS door.

 NetFoss is distributed with a default NF.BAT which is configured to run
 in DOOR32.SYS mode with 32-bit Windows BBS Software. It looks like this:

               @echo off
               if errorlevel 1 goto end
               c:\bbs\netcom.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
               c:\bbs\netfoss.com /u

 In order for NetFoss to work in a Non-DOOR32.SYS environment, you will
 need to change the second line to "c:\bbs\netfoss %1" in order to pass
 the node number to NETFOSS.COM.

 Note: This change will still allow DOS BBSes to run DOOR32 doors.

 Next you will need to configure your telnet server (or a Win32 BBS) to
 pass both the node number, and the WinSock handle to the NF.BAT file,
 as parameters %1 and %2  These will need to be prefixed with the "/n"
 and "/h" switches, respectively. Here is an example:

    C:\BBS\NF.BAT /N{node} /H{handle} c:\bbs\bbsname.exe -C1 -B38400

 In which {node} and {handle} are positive numeric values representing
 the node number to use and the telnet "socket handle" to use.

 For example, Argus uses &n to pass the node number, and &h to pass the
 Winsock handle to an external program. So your Argus external command
 line (Config >Externals >Doors >Door Parameters) would look like:

  c:\path\nf.bat /n&n /h&h c:\path\bbs.bat -N&n -C1 -B38400
      |            |    |       |           |    |   |
  NetFoss-loader   node handle  bbs-loader  parameters sent to bbs.bat

 In this example, we assume the BBS software uses -C1 to pass the
 current com port, -B38400 to pass the baud rate, and -N1 to pass a node
 number to the BBS software.

 Almost all DOS BBS software allows an active call to be passed from a
 front-end mailer to the BBS in this fashion, though the BBS parameters
 such as -C -N -B will differ slightly from one BBS program to another.
 Please consult your BBS documentation on the proper parameters needed
 to pass a connected caller from a front-end mailer to the BBS.


 List of compatible Telnet servers
 The following freeware Telnet servers have been tested with NetFoss:

 * Net2BBS by PC Micro. This Telnet Server is included with NetFoss.
   It's small in size, runs as a console application or service. Supports
   log files, WAV player, IP blocking, Bot detection, anti-hammering, and
   Open Source Freeware. http://netfoss.com

 * TelSrv by Mannsoft. A simple yet elegent GUI Win32 BBS Telnet Server.
   This also includes a separate mini-bbs but works with any BBS.
   Freeware and open-source. http://pcmicro.com/netfoss/telsv412.zip

 * Argus by Ritlabs. A complete front-end mailer. Freeware, open-source.

 * Radius. An enhanced mailer based on Argus. Freeware, open-source.

 * Taurus. More advanced mailer based on Radius. Freeware, open-source.
   http://taurus.rinet.ru or

 * GameSrv by R & M software. A telnet server with an internal mini-BBS.
   Freeware. http://gamesrv.ca

 * Dumple BBS & Telnet Server (in Python) by SWT. Freeware, open-source.

 * zTelnet Server by Zoob. Freeware.

 * EleBBS Telnet Server, (Telserv/EleServ) Freeware, open-source.
   http://elebbs.com and http://pcmicro.com/elebbs/faq

 * VADV32 Telnet Server for Virtual Advanced BBS. Freeware, open source.
 * Mystic Telnet Server for Mystic BBS Win32. Freeware.

 * WWIV Win32 Telnet Server (Works with any BBS). Freeware, open-source.

 * Tornado Win32 Telnet Server. Freeware and open source.

 * Thought Project BBS Class Library. Freeware and open source.


 Installing Net2BBS Telnet Server

 Net2BBS is a Windows Telnet Server included with NetFoss.
 It has the following features:

   * Very small footprint, Net2BBS.EXE is only a few Kbytes in size.
   * Configurable Node support, up to 256 nodes.
   * Logs all IP's & hostname connections to screen and file.
   * Multimedia support, plays login.wav and logoff.wav if found.
   * Semaphore support, refuses connections when semaphore file exists.
   * IP and hostname blocking, supporting wildcards.
   * Internal firewall, to refuse answering unwanted connections at all.
   * Anti-Hammer option, adds annoying IP's to a temporary block cache.
   * A classic Console mode text interface.

 Net2BBS needs to be configured before you can run it. You can copy
 the NET2BBS.INI.SAMPLE to NET2BBS.INI, and then edit the file as needed
 using a text editor such as NotePad.

 The sample Net2BBS .INI file uses settings like these:

     Command=c:\netfoss\nf.bat /n*N /h*H c:\pcb\pcboard.bat *N
     KillMsg=You are not welcome here.
     ResolveMsg=o Net2BBS - Resolving your IP Address...
     BlockCC=156,643,392,804    ; 156=China 643=Russia 392=Japan 804=Ukraine 

 A Full description of each of these settings is listed in NET2BBS.TXT.
 The only lines you must adjust in Net2BBS.INI is the "Command="
 line. This needs to run NetFoss and your BBS software, passing the
 Node Number using the *N macro, and passing the Socket Handle using
 the *H macro. The *I macro can be used to pass the callers IP Address
 and the *R macro can be used to pass the callers resolved hostname.

 Refer to the following BBS configurations listed below for examples
 of how the "Command=" line should appear.

 With some BBS software, you may also need to configure the StartPath= line.


 BBBS/D Usage

 BBBS/D comes in DOS, Win32, OS/2 and Linux versions, but due to the way
 the Win32 version is designed it is not able to run DOS doors using telnet.
 Therefore only use the DOS version (BBBS/D) with Windows and NetFoss.

  1) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP archive into the same directory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  2) Edit your NF.BAT file, to pass the node number to NETFOSS.COM by
     changing the line that loads NETFOSS.COM to include a " %1" at the end.
     (this is explained in detail in the DOS BBS section above.)

  3) Unzip NET2BBS.ZIP into the same directory as NetFoss, and rename
  4) Edit your NET2BBS.INI to use the following Command StartPath:
           Command=c:\netfoss\nf.bat /n*N /h*H c:\bbbs\bbbs.exe 1 *N

  5) Unzip BBBS/D version 4.00 into the c:\bbbs directory.

  6) Using notepad, create a file named DOBBS.BAT in the c:\bbbs directory.
     It only needs the following line:

                 x 57600 x x Telnet
  7) From the c:\bbbs directory, type "BCFG4 1" to configure node 1,
     and select "Local: General". Then on the "FD's DOBBS.BAT option,
     enter the following:


    Notice that the slashes are in the wrong direction (unix style).
    Press ESC twice, and choose "Exit and Save". Repeat Step 7 for every
    node you wish to configure, using "BCFG 2" for node 2, and so on.

    Now run Net2BBS.exe, and it is ready to accept Telnet connections.


 EzyCom BBS Usage

EzyCom is a RemoteAccess clone which is still activly updated.
The shareware version can be downloaded from http://ezycom-bbs.com 

Here is how to install it with NetFoss:

  1) Unpack E_V300SW.RAR to temporary folder and run INSTALL.EXE
     Next run EZYCFG.EXE and set the following under System>System:
         MultiLine: Yes
         Multitasker: Desqview

     This will allow NetFoss's DesqView emulator to release unused
     timeslices, increasing multi-node performance.
     Next exit EzyCfg and save the configuration.

  2) Create a NODE directory for each node. For example:
         C:\EZY       <-Main EzyCom directory

     You don't need to create separate configuration files for each
     node. EzyCom will look for the CONFIG.EZ configuration file in
     the main EzyCom directory if it does not find a specific node's
     configuration file. It's important to configure the Environment
     Variable %EZY% to point to the main EzyCom folder. 

  3)  Run EZYIDX -BUILD to index the file areas.

  4)  Create a EZY.BAT in the main EzyCom directory which contains the
      following 2 lines:
         set EZY=c:\ezy
         c:\ezy\ezy.exe -B38400 -N%1 -IP%2 -D 

  5)  In the NetFoss directory, edit the NET2BBS.INI file and change
      the following lines:
         Command=c:\ezy\nf.bat /n*N /h*H c:\ezy\ezy.bat *N *I
  6) If you have not already done so, edit the NF.BAT file to
     make sure it has a %1 at the end of the second line like so:
         c:\netfoss\netfoss.com %1

  7) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 GAP BBS Usage

    GAP was one of the early DOS BBS programs of the 1980's which was a
    trend-setter it it's day.  In 1999 it became freeware, and is still
    available and user supported at http://gapbbs.com

    Because GAP does not provide any Command Line parameter to pass a node
    number to GAP.EXE, several steps must be taken in order to support
    a multi-node GAP configuration.

  1) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP archive into the same directory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  2) Edit your NF.BAT file, to pass the node number to NETFOSS.COM by
     changing the line that loads NETFOSS.COM to include a " %1" at the end.
     (this is explained in detail in the DOS BBS section above.)

  3) Unzip NET2BBS.ZIP into the same directory as NetFoss.
  4) Change to the C:\NETFOSS directory, rename the NET2BBS.SAMPLE.INI
     to NET2BBS.INI and then edit this file using notepad.
     For example, type this:


     Change The actual "Command=" and "StartPath=" lines like so:

           Command=c:\gap\nf.bat /n*N /h*H c:\gap\runnode.bat *N
     Then Save and Exit notepad.

  5) Install GAP BBS into C:\GAP and run GAPSETUP.EXE. Using the up/down
     arrow keys, find the "Port Configuration" Screen, and set the Interface
     setting to "Fossil". Make any other configuration changes you desire.
     Then use the right arrow to select Quit > Save Changes.

  6) From a Command Prompt, Change to the c:\GAP directory, and create a
     separate node directory for each node, and then copy the current
     configuration file into each node directory. For example, type this:

          MD NODE1
          MD NODE2
          MD NODE3

  7) For each of the node directories, you must use the CD command to change
     to that directory, and then run \GAP\GAPSETUP.EXE to edit the GAPBBS.CNF
     configuration file in that directory to have the proper node number,
     which matches that directory name, and also you should set the maximum
     number of nodes allowed. For example, type this:

         CD \GAP\NODE1

     From the GAP Configuration program, press the down arrow 9 times to reach
     the screen that allows you to define the following settings:

          Network Node Number: 1
          Maximum Nodes To Use: 3

     Once these are configured, use the right arrow to select Quit >
     Save Changes. Then repeat the same steps for each NODE directory

  8) From the Command Prompt, change back to the C:\GAP directory and use
     notepad to create a batch file named RUNNODE.BAT which contains the
     following 2 lines:

          cd \gap\node%1
          c:\gap\GAPBBS.EXE 57600 0 0 14400 0 0 0

     For example, type this:
     Once you have pasted the 2 lines into notepad, save and exit.

  9) Run NET2BBS.EXE, and it is ready to accept telnet connections.

 Due to GAP's node design, if you need to make configuration changes, you
 will need to make the changes to each node directory as shown above, unlike
 most BBS software which only requires one configuration for all nodes. To
 simplify this task we have released a small utility called GAPNODES, which
 does all the work for you.


 EleBBS Win32 Usage

 NetFoss works with the DOS version of EleBBS, as well as allowing the Win32
 version of EleBBS to run DOS doors. The Windows version of EleBBS includes
 a Telnet Server - originally named TelServ.exe and later the name was changed
 to EleServ.exe which is also a FTP and NNTP (news) Server. 

 You can optionally replace the EleBBS Telnet server with Net2BBS, by editing
 the "Command=" and "Startpath=" lines in the NET2BBS.INI file using notepad
 like so:
        Command=c:\ele\elebbs.exe -n*N -h*H -XT -XC -XI*I -B65529

 There are detailed instructions on how to configure NetFoss with EleBBS DOS
 and Windows versions at http://pcmicro.com/netfoss/support.html


 Mystic BBS Win32 Usage

 The Win32 version of Mystic includes internal telnet support, so NetFoss
 is only needed in order to run DOS doors under Mystic.  Once Mystic is
 installed, a help file with detailed instructions on how to configure
 Mystic to run DOS doors under Windows using NetFoss can be found here:

 While Mystic supports creating a DOOR32.SYS drop file, you will still
 need to configure NF.BAT to run in "non Door32.SYS" mode by adding a
 %1 after the netfoss.com command line. This is because unlike most BBS
 software, when Mystic executes a door it does not set the current
 directory to the current nodes directory (such as c:\mystic\temp1),
 where the dropfiles are located. Therefore NetFoss will never find
 the DOOR32.SYS dropfile, since it expects it to be in the current
 directory.  This also means that doors which expect the DOOR.SYS or
 DORINFO1.DEF drop file to be located in the current directory will
 require the aid of a batch file to copy the needed dropfile from the
 node directory to the current directory before executing the door .exe
 file. However most doors allow the location of drop files to be
 specified in the doors configuration file.

 As a breif example on entering a door command line into the Mystic menu
 editor, here's a command line for the door game Legend of the Red Dragon:

         c:\mystic\netfoss\NF.BAT /N%3 /H%0 C:\LORD\START.BAT %3

 Mystic will replace "%3" with the node number, and will replace "%0"
 with the socket handle.  Note that %3 is actually used twice in the
 above example, first to pass the node number to netfoss.com and
 netcom.exe in the NF.BAT, and then again to pass the node number to
 the doors own batch file.

 It is possible to replace Mystic's telnet server with Net2BBS. While
 Net2BBS was a good replacement for the original Mystic telnet server
 (TSERVER.EXE), the new and improved Mystic Internet Server (MIS.EXE)
 included in Mystic 1.10 and later is several servers rolled into one:

 If you insist on using Net2BBS, you can edit your Net2BBS.INI file
 to include the following:
         Command=c:\mystic\mystic.exe -N*N -TID*H -IP*I -HOST*R


 Oblivion/2 Usage

 Obvion/2 version 2.30 (and 2.40beta 2) were the final DOS versions.
 Beware of a fake 2.40 release, which was just a hex patched 2.30.

 Currently there is a Windows version of Obv/2 under development called
 "Obvlion/2 XRM" (Extreme Re-Make) which includes it's own telnet server.
 NetFoss is only needed with this version if you wish to run DOS doors.

 Here is how to configure the DOS versions of Obvlivion/2:

  1) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP archive into the same directory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  2) Edit your NF.BAT file as described in the non-DOOR32.SYS mode section.

  3) Install Obv/2 2.30 (or 2.40b2) into c:\obv
     and make node directories for the maximum number of nodes desired
     like so:

  4) In the c:\netfoss directory, rename NET2BBS.SAMPLE.INI to NET2BBS.INI
     Then edit the following lines in NET2BBS.INI:

       Command=c:\netfoss\nf.bat /n*N /h*H c:\obv\runobv2.bat *N
       StartPath= c:\obv\node*N

  5) In the c:\obv directory, create the following batch files:

          @ECHO OFF
          OBV.EXE -F -CONFIG

          @ECHO OFF
          OBV.EXE -F -USER

          @ECHO OFF
          OBV.EXE -F -MENU

          @ECHO OFF
          OBV.EXE -F -PROMPTS

          @ECHO OFF
          OBV.EXE -b 57600 -A -nocheck -N %1

     The first 4 batch files are used launch the configuration program, the
     User Editor, the Menu Editor, and the Prompts Editor. These files are
     needed since Obv/2 won't be running from the  WFC (Wait For Call) screen.

     The RUNOBV2.BAT file is called by Net2BBS internally to launch a BBS node
     with a connected telnet session.
  5) run CFG.BAT to start the configuration program, and set the following:

        Under "System information", set Multinode Operation = Yes
        Under "System information3", set Give Up time slices = Yes    
        Under "Communications", set COM Port = 1

     Press Ctrl-Z to exit each section, and when done configuring save changes.

  6) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 PCBoard BBS Usage

 NetFoss has been tested with PCBoard version 15.3 & 15.4beta for DOS.
 Here is how to configure it for Telnet:

  1) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP archive into the same directory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  2) Edit your NF.BAT file as described in the non-DOOR32.SYS mode section.

  3) Install PCBoard in the c:\pcb directory, and create a separate directory
     for each node, such as c:\pcb\node1 and c:\pcb\node2 etc.

  4) Run PCBSETUP.EXE > Modem Information> Modem Setup.
     Set the COMM Driver to use as "F=FOSSIL, set the COM port to any
     non zero value. Setting it to "1" will work even if you have a real
     COM1 port already. Set the Opening Baud Rate to 115200, and select
     Lock in Opening Baud Rate = Yes.

  5) Create a PCBOARD.BAT in the PCBoard directory which looks like this:

        @ECHO OFF
        SET PCB=/NODE:%1 /PORT1F:
        SET NODE=%1
        cd %pcbdir%
        if exist remote.bat REN remote.bat remote.sys
        if exist door.bat   DEL door.bat
        if exist endpcb     DEL endpcb
        c:\pcb\pcboardm /file:%pcbdat% /C:115200
        if exist remote.bat CALL remote.bat
        if exist door.bat   CALL door.bat
        if exist event.bat  CALL event.bat
        if NOT exist endpcb GOTO top

        Note that each %1 will be replaced with the node number
        when this batch file is run. The line that actually runs PCBoard
        is the "c:\pcb\pcboardm /file%pcbdat% /C:115200". The /C:115200
        tells PCB that the user is already connected at that baud rate.
        The "/PORT1F" setting tells PCBoard to use FOSSIL port COM1,
        and it is preferable to set the same FOSSIL port for all nodes.

  6) Configure a Telnet Server to run the NF.BAT and the PCBOARD.BAT
     batch files.

     If you are using Net2BBS, then just rename NET2BBS.SAMPLE.INI to
     NET2BBS.INI, as the sample is already configured for PCBoard like so:

            Command=c:\netfoss\nf.bat /n*N /h*H c:\pcb\pcboard.bat *N

  7) For maximum file transfer speed, install Public Domain Zmodem
     (PD ZModem) as an external protocol in PCBoard. This runs several
     times faster then the PCBoard internal Zmodem or FDSZ.
    This is done by editing the following batch files located in the
    main PCBoard directory:

          pcbsz.bat (to send files from the bbs)
          pcbrz.bat (to receive files to the bbs)

    Replace the PCBoard protocols ZMRECV.EXE and ZMSEND.EXE with the
    proper SZ/RZ commands as described in the PD Zmodem section below.

  8) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 PC-Express BBS Usage

 NetFoss was tested with PC-Express versions 1.3 and 1.4beta. 

  1) Install PC-Express in c:\bbs and create directories
     for each node such as c:\bbs\node1 and c:\bbs\node2 etc.

  2) Create a RUNPCX.BAT in the BBS Directory, which looks like this:

	EXPRESS -N%1 -B19200 -F

    The -B19200 switch tells PCI-Express to assume that the caller is
    already connected to the modem at that speed.
    The -N%1 passes the node number, since %1 is replaced with the
    node number when the batch file is run.

  3) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP into the same direcftory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  4) Configure a Telnet Server to run the NF.BAT and the RUNPCI.BAT
     batch files. If you are using the included Net2BBS Telnet Server,
     then rename NET2BBS.SAMPLE.INI to NET2BBS.INI, and edit the following

	Command=c:\bbs\nf.bat /n*N /h*H c:\bbs\runpcx.bat *N

  5) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 ProBoard BBS Usage
 NetFoss was tested with ProBoard BBS for DOS version 2.17 (freeware).
 Here is how to configure it:

  1) Extract ProBoard in c:\pb and create directories for each node
     such as c:\pb\node1 and c:\pb\node2 etc.

  2) Create a RUNPB.BAT in the ProBoard Directory, which looks like this:

            set proboard=c:\pb
            \pb\proboard.exe -B115200 -N%1

    The -B115200 switch tells ProBoard to assume that the caller is
    already connected to the modem at that speed.
    The -N%1 passes the node number, since %1 is replaced with the
    node number when the batch file is run.

  3) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP into the same direcftory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  4) Configure a Telnet Server to run the NF.BAT and the RUNPB.BAT
     batch files. If you are using the included Net2BBS Telnet Server,
     then edit your Net2BBS.INI file to use a command line like this:

        Command=c:\netfoss\nf.bat /n*N /h*H c:\pb\runpb.bat *N

  5) For maximum file transfer speed, install Public Domain Zmodem
     (PD ZModem) as an external protocol in ProBoard. This runs several
     times faster then the ProBoard internal Zmodem or FDSZ.

  6) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 RemoteAccess BBS Usage
 NetFoss was tested with RemoteAccess BBS for DOS version 2.62.1
 Here is how to configure it:

  1) Install RemoteAccess in c:\ra and create directories for each node
     such as c:\ra\node1 and c:\ra\node2 etc.

  2) Create a RUNRA.BAT in the RemoteAccess Directory, which looks like this:

            set RA=c:\ra
            \ra\ra.exe -B115200 -N%1

     The -B115200 switch tells RemoteAccess to assume that the caller is
     already connected to the modem at that speed.
     The -N%1 passes the node number, since %1 is replaced with the
     node number when the batch file is run.

  3) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP into the same direcftory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  4) Configure a Telnet Server to run the NF.BAT and the RUNRA.BAT
     batch files. If you are using the included Net2BBS Telnet Server,
     then edit your Net2BBS.INI file to use a command line like this:

     Command=c:\netfoss\nf.bat /n*N /h*H c:\ra\runra.bat *N

  5) For maximum file transfer speed, install Public Domain Zmodem
     (PD ZModem) as an external protocol in RA. This runs several
     times faster then the RemoteAccess internal Zmodem or FDSZ.

  6) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 Searchlight BBS Usage

 Searchlight was the first and only BBS to display RIP Graphics on the local
 side. Version 5.0x for Windows included built-in telnet support, but it is
 veru unstable aand suffers from lockups and crashes. The DOS version of
 Searchlight running with NetFoss offers considerably better performance and

  - Thanks for Chris Costakis and for providing the install details, and a
    correction by Robert Wolf.

 1) Download Searchlight 5.10 for DOS (SLBBS510.ZIP), from http:://slbbs.com
    and install it in c:\slbbs\ 

 2) Unzip NetFoss to and Net2BBS to c:\netfoss\ and copy NETFOSS.DLL to

 3) Edit the NF.BAT file, to add a " %1" to the end of the netfoss.com line,
    as described in the batch file itself.
 4) Rename NET2BBS.SAMPLE.INI to NET2BBS.INI, and edit it to change the
    following lines:

       Command=c:\netfoss\nf.bat /n*N /h*H c:\slbbs.bat 57600 1440 /C *N

 5) Create a batch file named SLBBS.BAT located in c:\slbbs\ with the
    following lines:

       set slbbs=c:\slbbs\node%4
       ..\slbbs.exe 57600 1440 /C
 6) There are 2 configuration settings you will have to change in the
    Searchligh Configuration program. Run CONFIG.EXE and from the
    Configuration menu, go into General Configuration, and select General
    Setup #2. Change option 4 "Return to DOS on Logoff", from No to Yes. 

    The other change is in the General Configuration under Communications
    Setup - Configure your first node to look like the following:

    Communication Setup

    1. COM port Number............. 1
    2. Modem Type.................. High Speed
    3. Locked Baud Rate............ 57600
    4. Hardware Flow Control....... On
    5. Speed Detect Select......... Modem Msg
    6. Minimum Connect Speed....... 2400
    7. Output Buffering Factor..... 32
    8. Buffer door programs........ Yes (or try No)
    9. Modem Init String........... ATH0M0&C1CD2S0=1!
   10. Local Init String........... ATH1!
   11. Answer String............... ATA!
   12. COM Port Setups [...]

 Once you have made the above changes, select option 12 "COM Port Setups, and
 in the new screen change each "Port Type" to "FOSSIL". You don't need to
 change the other settings, such as Base Address, IRQ, or External Port.

 Next set these same configurations with each additional node. You can even
 use the same COM Port number with each node.

 7) Because the file transfers do not work properly using Searchlight’s
    internal protocols, you will need to configure Searchlight to use the
    external protocol PDZmodem, which is designed to work very well with a
    FOSSIL driver. Download PDZModem from the NetFoss.com web site, and
    unzip it to c:\pdzm\

    In Searchlight’s CONFIG.EXE, go to General Configuration, and then go to the
    XFer Protocols Setup.  You will be setting up Zmodem.
    Remove all the other protocols. Your configurations will look as follows:

       Protocol Name........... Zmodem
       Protocol Type........... External
       External Send Command... c:\pdzm\zm.exe -f -ldDSZ.LOG sz %F
       External Recv Command... c:\pdzm\zm.exe -f -ldDSZ.LOG rz %F
       Fossil Emulation........ Off

 8) Run NET2BBS.EXE, and it is ready to accept telnet connections.

 If you need assistance or SearchLight software you can visit the Searchlight
 message forums at http://slbbs.com


 SpitFire BBS Usage

 SpitFire BBS was not designed support a FOSSIL driver, so to support
 telnet it must be used with a Virtual COM port redirector such as

 The other limitation is that normally when Spitfire runs a door,
 once the door exits, Windows NT (including 10/8/7/Vista/XP/2K) lowers
 the Carrier Detect signal on the modem, causing the connection to be
 lost. NetSerial allows ignoring the Carrier Detect signal with the
 AT&D0 init string, which works with most BBS software, but SpitFire
 gets confused by this and tries to reinitialize the modem when you
 return from a door.

 Thanks to Jim Johnson for providing this workaround:

 There is a free utility for SpitFire called "SFmenu Extended" which
 allows SpitFire to run doors from a shell which returns to Spitfire
 using an errorlevel. This prevents Spitfire from getting confused
 about the Carrier Detect signal. Download the file sfmenuext.zip and
 extract the 4 batch files it contains into your SpitFire directory,
 overwriting the default batchfiles included with Spitfire. Then when
 you press "K" from The SpitFire main menu, you will get the "sfmenu
 extended" which allows you to add an unlimited number of doors to
 it. There is separate documentation with sfmenuext.zip that will
 instruct you on how to set it up.


 Synchronet BBS 3.1x USAGE

 Synchronet already has its own FOSSIL support, but using NetFoss in place
 of the internal FOSSIL can allow DOS doors to run considerably faster,
 often by a factor more then 2 or 3 times faster then the internal speed,
 with lower CPU usage. You can use NetFoss to run all or just some or all
 of your door programs, and run others using the internal FOSSIL.

 Synchronet can create a DOOR32.SYS file, but we do not suggest running
 NetFoss in DOOR32.SYS mode because Synchronet is unable to create both a
 DOOR32.SYS and a standard drop file at the same time. For this reason the
 DOOR32.SYS mode should not be used at the time this guide was written.
 Here is how to configure the "Legend Of The Red Dragon" door in Synchronet
 3.10j using the Non-DOOR32.SYS mode:

  Name                       LORD
  Internal Code              LORD
  Start-up Directory         C:\SBBS\XTRN\LORD
  Command Line               c:\sbbs\nf.bat /N%# /H%H start.bat %#
  Clean-up Command Line
  Execution Cost             None
  Access Requirements
  Execution Requirements
  Multiple Concurrent Users  Yes
  Intercept Standard I/O     No
  Native (32-bit) Executable Yes
  Use Shell to Execute       No
  Modify User Data           No
  Execute on Event           No
  Pause After Execution      No
  BBS Drop File Type         GAP             DOOR.SYS
  Place Drop File In         Node Directory
  Time Options...

 Notice that the Native (32-Bit) Executable option is enabled. This needs
 to be turned on in order for Synchronet to not enable its own internal
 FOSSIL driver. REPEAT - even though you are not using DOOR32.SYS as your
 dropfile, Native (32-Bit) Executable must be enabled.  Additionally, make
 sure to change the command line to reflect the directory that you
 installed NetFoss and the Start-up directory should either reflect where
 your door is located if you don't use a batch file to start the door, or
 could have the startup directory point to your current node directory
 where the dropfiles are created. (If you do the later, you should launch
 the door with a batch file that first uses the CD\ command to Change the
 Directory to where the door is located.

 When using the Non-DOOR32.SYS mode, you must edit your NF.BAT file to add
 the " %1" at the end of the second line, as explained earlier in this
 document. Instructions can also be found in the NF.BAT.

 Make sure to change the Command line in NF.BAT to reflect the directory
 that you installed NetFoss in, and the Start-up directory should reflect
 where your door is installed.

 In the LORD door example above, the start.bat is the batch file located
 in the Start-up Directory which actually runs this door game.


 T.A.G. BBS Usage
 T.A.G. was originaly based on WWIV BBS source code, as were its distant
 cousins Telegard and Renegade. T.A.G was the first elite-scene software
 to support the modern JAM message base format, and it's Fidonet compatible.
 NetFoss was tested with T.A.G. 2.7 with the Y2K maintenace release applied.

 Here is how to install it:

  1) The T.A.G. Installer requires the following archives:
     (the last one is only required for FidoNet Support).

     Place these files into a temporary directory, which does not use a
     LongFileName (more then 8 characters long). Unzip the TAGS27.ZIP
     archive and leave the rest zipped. You will also need to add
     PKUNZIP.EXE to this directory.

  2) To avoid RunTime Error 200, use PatchCRT to patch INSTALL.EXE.
     See http://www.pcmicro.com/elebbs/faq/rte200.html

  3) Run INSTALL.EXE to Install T.A.G., and select C:\TAG as the main
     BBS directory, and set the COM port as COM1 before selecting
     "Start Installation".

  4) Once the installation is completed, change to the \TAG directory
     unzip the Y2K update (TAGU27D2.ZIP) to replace the TAG.EXE and
     TAG.OVR files. Next run PatchCRT on each of the following files:

  5) Run MCONFIG.EXE to setup your sysop password(s), and then select
     "Write STATUS.DAT". Next change to the AFILES directory and run
     TAGSTR.EXE to create TAGSTR.DAT.

  6) Change back to the \TAG directory and run "TAG.EXE /LOCAL".
     From the main screen, press Ctrl-Q for the Sysop Functions Menu.
     Then press S for System Configuration. At the ":" prompt enter
     the Sysop Password (Which is SYSOP if you didn't change it yet)
     and press C for Communications Configuration, then press D to
     change the "Use FOSSIL Driver" option to YES, and it will ask
     "Do you want to make use of the FOSSIL buffer, answer YES again.
     Next press Q to return to the System Configuration menu.

  7) From the System Configuration, press N for Multi-User Configuration.
     Set the following:
     A. Multiuser System: YES
     B. Network Type:     DESQVIEW
     C. Multi-user data file path: C:\TAG\DFILES\
     Desqview is selected because this will allow T.A.G. to release
     inactive timeslices to NetFoss's DesqView Emulator to improve
     multitasking performance when running several nodes.
  8) In the \TAG directory, create the following 1-line TAG.BAT file:
     This could have been placed in the Net2BBS.INI Command Line, but
     doing so would prevent you from adding your Echomail scanner
     to the batch file so it can be told to scan the messagebase when
     the ErrorLevel tag.exea returns indicates that the previous user
     wrote a message in an echo.
  9) In the NetFoss directory, Edit the NF.BAT to add a " %1" to the
     end of the netfoss.com command line, as described in the
     "Non-DOOR32.SYS mode" above. Also change the directory paths to
     netfoss.com and netcom.exe if they are not located in c:\netfoss
     Mext edit the Net2BBS.INI to use the following Command Line and
     Command=c:\netfoss\nf.bat /n*N /h*H c:\tag\tag.bat -N*N

 10) Unzip TAGD27.ZIP into C:\TAG\DOCS\ and open the MAIN26D.DOC and
     go to page 108 to review the Multi-Node setup instructions.
     Instead of using their example Blinky directory structure, we
     suggest the more logical structure used by most BBS software:
     Copy the STATUS.DAT and all the .BAT files from \TAG to each Node

 11) For maximum file transfer speed, install Public Domain Zmodem
     (PD ZModem) as an external protocol in the BBS. This runs several
     times faster then FDSZ.

 12) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 Telegard\Renegade BBS Usage
 Telegard and Renegade BBS are both very similar, because Renegade was
 based on an older version of the Telegard source code. In our testing
 Telegard performs considerably faster then Renegade under Windows, and
 offers true multi-node support. While Renegade can be run multi-node,
 it can encounter issues due to dropfiles not being created in separate
 directories for each node. Update: there is a Win32 version of Renegade
 now, which should perform better.
 NetFoss was tested with Telegard BBS for version 3.09G2 with SP4, and
 Renegade 99.044D with the Y2K hotfixes applied.

 Here is how to install NetFoss with Telegard or Renegade:

  1) Install Telegard or Renegade BBS. If installing Telegard be sure to
     also install the Service Pack 4 update, which improves performance
     under Windows.

     Download Telegard from
     Download Renegade (NetFoss now included) from http://renegadebbs.net

  2) Create a separate node directory for each node, such as \tg\node1

  3) Unzip the NetFoss files into a directory such as c:\netfoss\ and also
     unzip the included NET2BBS.ZIP into the same direcftory.
     Copy NETFOSS.DLL into the \windows\system32\ directory.
     This can only be done from a Command Prompt which was opened using
     "Run As Administator" (right click on its icon to select this).

  4) Edit the NF.BAT to add a " %1" to the end of the netfoss.com
     command line, as described in the "Non-DOOR32.SYS mode" above.
     Also change the directory paths to netfoss.com and netcom.exe if
     Netfoss is not located in c:\netfoss\

  5) Configure your telnet server with the proper command line to spawn
     when an incoming telnet connection is received.
     If you are using the included Net2BBS Telnet Server, then edit your
     Net2BBS.INI file to use a command line like this:

     For Telegard:
     Command=c:\netfoss\nf.bat /n*N /h*H c:\tg\telegard.exe -B115200 -Q -N*N

     For Renegade:
     Command=c:\netfoss\nf.bat /n*N /h*H c:\rg\renegade.exe -B115200 -Q -N*N

     The -B115200 switch tells Telegard or Renegade to assume that the user
     is already connected to the modem at that Baud rate.
     The -Q switch tells Telegard/Renegade to exit after the caller logs off.
     The -N switch passes the node number, since *N is replaced with the
     node number by Net2BBS when the command line is spawned.

     Also edit the StartPath line of your Net2BBS.INI file to start the BBS
     session in the correct directory. Since Telegard supports multiple
     nodes properly, it should be started from the current node directory.
     However Renegade lacks proper multi-node support, so it will need to
     be started from the main BBS directory.

     For Telegard:

     For Renegade:

  6) For maximum file transfer speed, install Public Domain Zmodem
     (PD ZModem) as an external protocol in the BBS. This runs several
     times faster then FDSZ.

  7) If you need Telegard/Renegade to run an external program after each
     caller logs off (such as a mail tosser/scanner to export echomail for
     example), then it would be better to have the telnet server spawn a
     batch file instead of the BBS executable, and the batch file would
     then spawn the BBS (passing any variables in %1 %2 %3 etc.) and could
     then spawn an external program after the user logs off.

   8) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 Virtual Advanced BBS Usage

 NetFoss is included with Virtual Advanced BBS, as part of the VADV32
 package available from http://vadvbbs.com

 VADV32 also includes its own Win32 Telnet Server, which is preconfigured
 to use NetFoss as its FOSSIL driver.


 Wildcat BBS Usage

 Wildcat 5.0 and later is Windows based and now known as WinServer which
 includes an internal FOSSIL driver and telnet server. As of the date of
 this document, The Windows version of Wildcat does not allow passing the
 socket handle to a door, which prevents being able to use it with NetFoss
 to run doors.

 However, NetFoss is fully compatible with Wildcat version 4.20 for DOS,
 allowing doors to run considerably faster then the later versions of
 Wildcat (WinServer) does. Wildcat 4.20 itself also performs extremly fast
 under Windows when using NetFoss.

 Here is how to configure Wildcat 4.20 with NetFoss. You will need to use
 a 32-bit version of Windows (10/8/7/Vista/XP,2K) or Windows Server.
 1) Extract the Wildcat 4.20 files to c:\wildcat
    and extract Wildcat 4.20 Y2K Update Fix to the same directory.
    Extract the NetFoss/Net2BBS files to c:\netfoss

 2) Download PatchCRT.exe, which is used to fix the "Runtime Error 200"
    which older DOS programs often encounter under faster CPUs.
    Run "PATCHCRT " on each of the following files in the
    Wildcat folder:

       and most importantly: WILDCAT.EXE

 3) Once the files have been patched, run MAKEWILD, and from the MAIN menu,
    select "Modem Settings". From there, change the "Type of Serial Port" to

 4) Create a batch file named RUNWILD.BAT located in c:\wildcat\ with the
    following lines:

       set WCNODEID=%1
       set NODEPATH=c:\wildcat\wcwork\node%1
       wildcat.exe /B 57600 CID: %2

 5)    In the NetFoss directory, copy NET2BBS.SAMPLE.INI to NET2BBS.INI
       and edit the following 2 lines:

         Command=c:\netfoss\nf.bat /n*N /h*H c:\wildcat\runwild.bat *N *I

 6) Run NET2BBS.EXE, and it is ready to accept telnet connections.



 WWIV 5.30 (Windows)
 WWIV 5.30 and is a Windows BBS which includes a modified version of the
 Synchronet FOSSIL driver to run doors, and a modified version of the
 EleBBS telnet server to accept connections.

 Some WWIV5 Sysops prefer to use Net2BBS as the telent server, which can
 be done by configuring the following two lines in the NET2BBS.INI file:
      Command=c:\WWIV\BBS.EXE -XT -H*H -N*N

 You can optionally change the StartPath to go to the node directory:

 WWIV 4.30 (DOS)
 WWIV 4.30 is the current DOS version of WWIV, and is also the only
 version which supports a FOSSIL driver.
 Here is how to configure WWIV version 4.30 with NetFoss:

 1) Extract WWIV430.ZIP to c:\WWIV, and NetFoss to c:\NETFOSS
    Also extract NET2BBS.ZIP to the C:\NETFOSS

 2) In the NetFoss directory, rename NET2BBS.SAMPLE.INI to NET2BBS.INI
    and edit these two lines:

      Command=C:\netfoss\nf.bat /n*N /h*H C:\WWIV\bbs.exe *N *I 

 3) In the same directory, edit NF.BAT to include a %1 at the end of
    the first line like so:

       c:\netfoss\netfoss.com %1

 4) In the WWIV directory, create a BBS.BAT file which contains the
    following lines:

       BBS.EXE /B115200 /N0 /O

 5) Run NET2BBS.EXE, and it is ready to accept telnet connections.


 Doorway Usage

 Doorway allows remote control of a computer's Command Prompt via a
 modem or a telnet connection. Doorway was developed by Marshall Dudley
 from 1987-1996, and in 2006 PC Micro acquired the source code and rights
 to Doorway, in an effort to revive this excellent product.
 Doorway can be purchased and downloaded from http://pcmicro.com/doorway

 The PCMicro updates to Doorway provide considerably faster FOSSIL support.

 To install doorway as a door in your BBS software, configure your BBS
 to create a DOOR.SYS drop file, and to run a DOORWAY.BAT batch file.
 The DOORWAY.BAT could contain this line:


 The "SYSF" parameter tells Doorway to read the DOOR.SYS drop file, and
 also to use the Fossil driver. (So be sure to include the "F").

 If DOORWAY.EXE is not in the PATH, you should add the full path to it's
 location in, such as c:\bbs\doorway\doorway.exe {other parameters here}

 Doorway has several different options for how the bottom display line is
 handled. If you have issues, try changing /B:M to /B:MZ which moves text
 on 25 to line 24. Read DOORWAY.DOC for details on other /B: settings.


 Door Game Usage

 It's suggested to set up all nodes of a door to use the same COM port
 value, such as COM1. When NetFoss is functioning in "Telnet Mode" it
 ignores the COM port value. This is because many FOSSIL aware doors
 only work on COM1 thru COM4, while some doors support up to COM9.
 There are a few doors that support higher COM port values, for example
 TradeWars supports up to COM255.

 Here are some notes on specific doors:

 * The Pit 

       Version 4.17 (as well as 4.16 and 4.15) has a bug which
       prevents it from functioning with a FOSSIL driver if a COM
       port UART is not found at startup. Previous versions 4.05 and
       below do not have this issue, and will work fine with NetFoss.
       If your PC has a real COM port, or a PCI modem card you can
       avoid the issue by setting all the nodes of The Pit 4.17 to
       use that COM port. Or virtual COM port(s) (COM1 - COM4 only).
       At the time of this writing, an older version of the source
       code to The Pit was recovered and is being updated by "Deuce".

 * Lunatix

       The final version 4.3a runs very fast under NetFoss due to NTVDM
       enhancements that NetFoss provides. Older versions also work well.

 * BBS Crash

       Version 5.50 and 5.60 do not support a FOSSIL driver even though
       they claim to. Version 5.10 and earlier do support a FOSSIL driver.
       The author broke FOSSIL support in the 5.50 release which was the
       following public release after 5.10.

 * Battle of the Arts

       Version 2.0 runs fine under NetFoss, but version 2.20 has broken
       FOSSIL support and never even attempts to communicate with one.

 * Fresh Water Fishing

       This runs fine under XP, but fails to 'reel in' under Windows Vista
       or later versions of Windows. It is not a NetFoss related issue.

 If you encounter any other doors that claim to support a FOSSIL driver
 but fail to work with NetFoss, please email support@pcmicro.com.


 NETFOSS.COM Command Line Parameters:

   /N{value}  Set node number
   /C{value}  Set COM port mode   (this disables Telnet mode)
   /L{value}  Set locked baud     (only use if COM port mode is set)
   /S{value}  Slow output         (1=slowest, 6000=fastest, default=1000)
   /P{value}  Status Poll Tweak   (1=slowest, 6000=fastest, default=3000)
   /K{value}  Keyboard Poll Tweak (1=slowest, 6000=fastest, default=1200)
   /Z{value}  PDZmodem Tweak      (speed of block transfers default=175)
   /D{value}  DESQview timeslice  (value 1-255, 1=yield most) default=10)
   /D0        DESQview ts disable
   /R         Allow COM release   (when FOSSIL is told to Deinitialize)
   /X         X00 status enable   (same as /X1 - default:disabled)
   /X0        X00 status disable  (turns the X00 status mode off) 
   /M         Modify Mode         (To update settings while Fossil active)
   /MR        Restore defaults    (To undo previouly modified settings)
   /U         Uninstall

 /N{value} - Set Node Number

 This parameter is required when creating a new node session. The Node value
 must be a number between 1 and 65. (If using Net2BBS, between 1 ane 255).
 A Node is a separate process of the BBS software in which a user/client can
 connect to (through a phone line and modem, or a TCP connection).

 /C{value}  - Set COM Port mode

 NetFoss can be used either in Telnet mode, or in COM port mode.

 COM port mode allows NetFoss to be used with real Modems for a legacy
 Dialup BBS, or with Virtual Modems/Virtual COM ports such as NetSerial.

 COM port Mode can only be set when creating a node.
 Example:  NETFOSS.COM /N1 /C1 This tells NetFoss to create Node1 using COM1.

 See the "COM port Mode" chapter below for more details.

 /L{value}  - Set Locked COM Port Baud

 This optional parameter is only available when COM port mode is set.
 If /L is specified without a value, the Baud rate is locked at 115200.
 If /L is not specified, the Baud rate is not locked.

 Some BBS Software, such as EzyCom, requires using a slower baud rate of
 57600, 38400 or even 19200 baud in order to function.

 Example:  NETFOSS.COM /N1 /C1 /L57600

 This creates Node 1 using COM port Mode on COM1 locked at 57600 baud.
 Any application that requests to change the baud rate will be denied.

 * The following optional tweaking commands allow fine tuning NetFoss's *
 * performance for optimum display speed and/or optimum CPU overhead.   *

      /S{slow: characters output before sleep}
      /P{Status polls before sleep}
      /K{Keyboard polls before sleep}
      /Z{Blocks output before sleep (for PDZmodem)}
      /D{DESQview timeslice setting}

 /S{value}  Slow output   (default=1000)

 NetFoss allows the character output speed to be slowed down by passing
 the optional /S parameter along with a value between 1 and 65000.
 Example NETFOSS.COM /M /S20

 The lower the number, the slower the character output speed will be.
 This is _not_ the same as a Baud Rate. The value is the number of
 characters which will be output before a Sleep occurs to lower the
 CPU usage.

 Without this parameter, NetFoss displays at a very high speed, which in
 some cases can causes ANSI-Animation sequences to be displayed much
 faster then they were intended to. In most cases, the default speed is

 /P{value}  Status Polls Tweak   (default=3000)

 DOS applications can overload the CPU usage by constantly polling the
 FOSSIL status command to check for changes. The optional /P
 parameter can adjust the number of Status polls that are allowed to
 be made before a Sleep occurs to lower CPU usage.

 The lower the value, the more often the Sleep will occur, resulting
 in lower CPU usage and less responsiveness and performance.

 In most cases, the default settings is reccomended.

 /K{value}  Keyboard Polls Tweak   (default=1200)

 DOS applications can overload the CPU usage by constantly polling the
 Keyboard status to see if a key has been pressed. The optional /P
 parameter can adjust the number of Keyboard Status polls that can
 be made before a Sleep occurs to lower CPU usage.

 The lower the value, the more often the Sleep will occur, resulting
 in lower CPU usage and less responsiveness and performance.

 In most cases, the default settings is reccomended.

 /Z{value}  PDZmodem Tweak      (default=175)

 This optional parameter tunes the PDZmodem file transfer performance.

 PDZmodem uses block reads/writes rather then transfering one character
 at a time, so the optional /Z parameter allows tuning the Zmodem speed.
 /Setting this value too high will overload the CPU usage, causing the
 transfer to slow down. Setting it too low will cause excessive Sleeps
 resulting in very low CPU usage and slow transfers. While the default
 setting should work in most cases, tuning this while testing over an
 internet connection can dramatically improve file transfer performance.
 See PDZmodem Chapter below for more info.

 /D{value}  DESQview timeslice    (default=10)

 This optional parameter tunes the DESQview timeslice release feature.
 DESQview was a DOS Multitasker, which allowed multiple DOS Windows to
 run concurrently (much like Windows does).
 DOS applications which are DESQview aware can send a command to tell
 DESQview to release the remaining timeslice to the other DV Windows. 

 NetFoss can capture these timeslice release commands, and redirect them
 to Windows. This parameter fine tune this feature, or disables it when
 set to Zero.  The lower the number, the longer period it will Sleep for
 when the timeslice command is received. The default setting may cause
 some applications to over-sleep (causing a slower then possible output).
 Passing the /D0 parameter disables this feature entirly.


 /R - COM Port Release

 The optional /R parameter is only available when setting COM Port Mode,
 which causes NetFoss to release the COM port after it receives a
 "Deinitialize Port" FOSSIL command from the application.

 By default, NetFoss will open a COM port when it receives an "Initialize
 Port" FOSSIL command, and it will hold that COM port open until NetFoss
 is told to uninstall itself from memory (using the /U parameter), or
 until the Command Prompt window it was loaded in is closed.

 While NetFoss is holding a COM port open, it is not possible for any
 other applications to access the COM port directly.

 /X /X1 - X00 Kluge

 This optional feature is disabled by default.

 NetFoss always supports the extended X00 FOSSIL commands above AH=1Bh
 regardless of this setting. The /X or /X0 parameter controls how the
 FOSSIL command 02h (Receive character with wait) returns it's results.
 The official FOSSIL rev 5 specs states that this command will always
 return with AH=0, but X00 returns with AH=status (the same status code
 returned by command 03h).

 Most FOSSIL aware programs ignore the results returned in AH after a
 command 02h (Receive character with wait), but a small number of door
 games have been found to expect either 00, or a valid status.
 To provide maximum compatibility, NETFOSS.COM can be passed a command
 line parameter /x which forces it to return from command 02 with the
 status in AH, rather then zero.

 To enable this X00 compatibility kluge, you can edit your NF.BAT file
 to add an /x parameter, like this:

   @echo off
   c:\bbs\netfoss.com /n%1 /x
   if errorlevel 1 goto end
   c:\bbs\netcom.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
   c:\bbs\netfoss.com /u

 Or when running a DOS based BBS, it can be turned on just before
 running a door, and then turned off again after the door exits by
 adding two Command Lines to your door's batch file, For example,
 the following door batch file:

    cd\bbs\doors\example\        <-- This changes to the door dir
    c:\bbs\netfoss.com /m /x     <-- This enables X00 compatible mode
    doorgame.exe /N%1            <-- This runs the door
    c:\bbs\netfoss.com /m /x0    <-- This disables the X00 compatible mode
 When /x is not present on the netfoss.com command line, then the FOSSIL
 Command 02h always returns with AH=00.

 When /x is present on the netfoss.com command line, then
 Command 02h always returns with AH={Status}

 Hint: If you run a Win32 BBS, you can create a second batch file
 which includes /x such as NFX.BAT which makes it simple to allow
 only certain doors to use this mode.

 For most door games, /x is not needed and should not be used as it can
 cause a few doors to fail.

   /M         Modify Mode         (To update settings while Fossil active)

  The /M parameter tells NetFoss to modify the currently active FOSSIL node
  with the additional parameters specified.
  Do not include the /N{node number} parameter when using the /M

  Example: To slow down the display speed only for one door, add the following
  Command Line to the beginning of the door's batch file:
        \path_to_netfoss\netfoss.com /m /s20
   and after the door exits, restore it back to normal speed:

        \path_to_netfoss\netfoss.com /mr
   If /M is _not_ included on the command line, then NETFOSS.COM will either
   attempt to install a new node, or (if /U is used), uninstall an existing node.

   /MR  Restore Defaults (To undo previouly modified settings)

  This parameter will revert all settings back to their default values, usefull
  after using the /M parameter to modify some of the settings.


 Using COM Port Mode

 NetFoss can be used either in Telnet mode, or in COM port mode.

 COM port mode allows NetFoss to be used with real Modems for a legacy
 Dialup BBS, or it can be used with Virtual Modems such as NetSerial.
 BBS Sysops can purchase NetSerial at a special sysop price of $25. 

 When using NetFoss in COM port mode, there is no need to use the NF.BAT
 file, because NetCom (The Telnet Communication Engine) is not neeeded.
 Simply run NETFOSS.COM as a TSR, by loading it with the node number and
 COM port number like this:

       NETFOSS.COM /N1 /C1

 This will install the NetFoss TSR (Terminate and Stay Resident) code
 by binding it to the current Command Prompt (Virtual DOS Machine).
 The above example uses Node 1, COM1.

 Once the TSR is installed in the current Command Prompt, you can simply
 run your BBS application or Front End Mailer from that Command Prompt,
 and it will see NetFoss is operating on INT 14h.

 When your application is finished running, you can uninstall the
 NetFoss TSR from the current Command Prompt by running:

 When the Command Prompt is closed, NetFoss is automatically uninstalled
 from it.


 It is also possible (but not suggested) to use the NF.BAT file when
 using NetFoss in COM port mode, but you would need to make some changes
 to your NF.BAT as shown below.

 To use the /C parameter to pass the COM port number, you could make the
 following changes to your NF.BAT:

 1. The line that runs netfoss.com will need both /c{value} and
    /n{value} parameters, which each need to be a value from 1 to 4096.
    i.e.: /N1 /C1
 2. The line that runs netcom.exe can optionally be removed and replaced
    with the following line:
    call %1 %2 %3 %4 %5 %6 %7 %8 %9
 3. Any batch files that NF.BAT executes (via the call command),
    may not contain an "Exit" command. This is because the call
    command is used to run one batch file from another one, but
    the exit command will prevent the original batch file from
    regaining control. This will result in nf.bat never uninstalling
    netfoss afterwards.

 The second step (#2) is optional, because NETCOM.EXE not required in
 order for NetFoss to function in COM Port Mode. NETCOM only handles
 telnet communication when NetFoss has COM port mode turned off, in
 which case a Virtual COM port could then redirect the data to its
 own telnet driver. If NETCOM.EXE is passed a /C{value} or detects the
 DOOR32.SYS is set for COM port mode, it will run in local mode, simply
 spawning the given command line much as the batch "call" command does.

 NETFOSS.COM will automaticly enable COM port mode if it finds a
 DOOR32.SYS drop file in the current directory which is configured for
 COM port mode.

 Please note that if the /C  parameter is passed to NETFOSS.COM, this
 effectively disables Telnet mode (Unless you use a virtual modem such
 as NetSerial for your telnet engine).
 Do *NOT* pass a /C  parameter to NETFOSS.COM if using a Telnet Server.


 Here is how to run NetFoss as a TSR, so a NF.BAT is not needed.
 This will *ONLY* work in COM port mode:

 Load NETFOSS.COM into memory by passing it the node number and
 the COM port number to use, like this:


 This will Install NetFoss into the current "Command Prompt" (NTVDM)
 Window, running as a TSR. 

 If you install NetFoss in multiple "Command Prompt" windows using the
 COM port mode, they will each need to use a unique Node number and a
 unique COM port number.


 When using NetFoss with NetSerial'S Virtual Modems, you should configure
 NetSerial like this:

     Connection type: Telnet
     [ ] Request Remote Telnet Echo
     [X] Accept Local Telnet Echo
     [X] Request Binary Connection
     Port Mode: Virtual Modem
     Inbound TCP Port: 23
     [X] Accept inbound connections

 The suggested BBS Init string for NetSerial is AT&D2
 This forces the virtual modem to disconnect when the BBS software
 lowers the DTR line on the virtual COM port.

 Some BBS software requires a special character at the end of an AT
 command, to signify a carriage return character.

 NetSerial can create up to 256 Virtal Modems.
 Each Virtual Modem can be controlled by NetFoss in a separate node.
 Virtual Modems do not require Windows modem drivers to work with NetFoss
 and DOS based applications including BBS programs.


 Security and AV Software

 Over the decades, a few poorly designed heuristic AV Scanners have reported
 "False-Positive" results on NetFoss executable files, with lables such as
 Evo-Generic/Suspicious, simply because they see unusually small files 
 written in Assembly Language which perform TCP/IP socket functions and spawn
 other software. When a new version is released, we've often had to report
 such false-positives to Avast to be added to their F.P. white-list.
 If you have concerns about such false postives, use an online multi-AV
 scanner such as http://virustotal.com and you will find that all the non-
 heuristic AV scanners such as Kaspersky, Symantec, AVG, ESET, and dozens
 of others give it a clean bill of health.

 In 2017, Microsoft Defender started generating "False-Positive" on both
 NETCOM.EXE and NET2BBS.EXE, so these two files now include embedded
 Code-Signing Certficiates that give these files credibility with Microsoft.
 As a result these files are considerably larger in size, yet still use very
 little memory when executed. 

 Some "security" software (anti-virus and firewalls) will interfere with
 a socket being passed from a Telnet Server to another process such as
 NetFoss. This process is known as Socket inheritance. Often such software
 has an option to add an exclusion to allow your telnet server to do this.

 ZoneAlarm Security Suite will not allow exclusions to be defined, so it
 must be uninstalled.

 Windows Server 2003 and later will fail allow socket inheritance if a
 policy to enforce QoS on created TCP sockets is enabled.


 Zmodem File Transfers

 The following FOSSIL aware Zmodem File Transfer Protocols have been
 successfully tested with NetFoss in BBS Download mode:

 PD Zmodem 1.2.6     - Peter Mandrella, Daisy Data & Information Systems
 SynZM 1.00          - Synopsis, Edge of Honor
 PDrive 2.10         - Larry Athey, Max Graphics
 FDSZ (5/20/97)      - Chuck Forsberg, Omen Technology
 AnDan Zmodem 1.04   - Anders Dannielsson, Andan Softare
 SDPF                - Thomas Thayer, Streamline Design
 CEXYZ 1.0 DOS       - George Hatchew, Cutting Edge Computing

 ZSX 3.10 was also tested, which claims to be FOSSIL compatible, but it
 failed to transfer any files.

 Zmodem benchmark results

 The following Zmodem benchmarks were performed on a Celeron 1.5Ghz CPU
 with 256 megs RAM running Windows 2000 Professional using NetFoss 0.93.
 Your results may differ under other environments.

 The Zmodem protocols were used to send files to an Mtelnet terminal
 program (version beta 12 by Dink available at http://ozone.eesc.com)
 Mtelnet was located on the same LAN to avoid any internet lag.

 Only the default block size of 1K was used in this test, because
 Mtelnet does not support the larger 8K blocks.

 The benchmark results for sending files to an Mtelnet terminal are:

 PD Zmodem    -  350,000 CPS < The Winner! >
 SynZM        -   28,500 CPS
 PDrive       -   28,500 CPS
 FDSZ         -   28,500 CPS
 SDPF         -   21,900 CPS
 AnDan Zmodem -   19,000 CPS
 CEXYZ        -    9,065 CPS
 ZSX          -   Failed

 Zmodem speeds were further enhanced in later versions. NetFoss 1.01
 will transfer at 450,000 CPS using PD Zmodem on a P4 2.0Ghz PC, and
 by adjusting the /z parameter in netfoss.com to /z600 it will will
 transfer at 1,000,000 CPS on a Core2 Duo 1.8Ghz PC.

 These are speeds which Mtelnet can receive/download the files being
 sent by a BBS using the listed protocols. Mtelnet has its own internal
 Zmodem implementation, so the protocols are only installed on the BBS.

 The result is that "Public Domain" Zmodem is by far the fastest FOSSIL
 compatible Zmodem protocol tested, by over 12 times the speed of others.

 When Mtelnet is used to send/upload files to a BBS running these Zmodem
 protocols, Mtelnet can only send at a maximum of around 200,000 CPS.
 This is because Mtelnet sends data in smaller packets causing the data
 to become buffered while the receiving protocol eventually recieves the
 data (at its fastest speed).

 This presents a problem in which Mtelnet will finish sending a large
 file long before the BBS is finished receiving the file. Mtelnet will
 wait several minutes for a confirmation from the BBS end acknowledging
 that the transfer was completed successfully. If it does not see this
 within a few minutes, the transfer will fail. The only protocol which
 can keep up with high speed transfers of large files being sent from
 mtelnet is "Public Domain" Zmodem.

 To allow a BBS to accept large Zmodem uploads using NetFoss, you *MUST*
 use the "Public Domain" Zmodem (also known as PD Zmodem) protocol.
 The "Public Domain" Zmodem protocol is freeware, and is available from

 You can download other file transfer protocols at the BBS Archives:

 Configuring PD Zmodem for use with a BBS

 Most BBS software allows external protocol drivers to be defined for
 Zmodem and other file transfer protocols. The following example
 command lines can be used:

 Download from BBS:

   ZM -f -ldDSZ.LOG sz 

 Upload to BBS:

   ZM -f -ldDSZ.LOG -r rz 

 The "-ldDSZ.LOG" parameter is not required if you define a system
 environment variable in Windows as follows:


 When using PD Zmodem with NetFoss running in telnet mode, the COM port
 parameter does not need to be specified. COM1 is assumed by default, and
 NetFoss ignores the COM port value anyways when running in telnet mode.
 The baud rate also does not need to be specified, since PD Zmodem will
 default to using the existing baud rate.


 Optimizing PD Zmodem transfer speeds

 The default settings in NetFoss should allow PD Zmodem transfer speeds
 between 300,000 CPS and 450,000 CPS. 

 You can optimize the PD Zmodem transfer speeds for maximum performance by
 using the optional /z{value} parameter, where {value} is a number between
 1 and 65000. To adjust this variable, edit your NF.BAT file as such:
 netfoss.com %1 /z175  (the %1 is only needed for non-door32 BBS's)

 If the /z{value} parameter is omitted, it will use a default of 175.

 To find the best setting, you should view the "Performance" tab in the
 Windows Task Manager (press Ctl-Alt-Del to open it), and make sure that the
 CPU usage is below 5% during a PD Zmodem transfer session. If the CPU usage
 is higher, then try again using a lower value. If the CPU usage is near 0%,
 then you might be able to get faster transfer speeds with a higher value.

 For example, on a Core2 Duo T7100 CPU running 1.8Ghz, the default setting
 allows PD Zmodem transfers at about 300,000 CPS, but by adjusting the
 speed variable to /z600, it will allow transfer speeds over 1,000,000 CPS.


 NetCom.exe optional command line switches:

 NetCom should be passed the command line for the external DOS program
 that it should spawn, and the following command line switches are available.
 The switches must be passed before the external command line.

  /N{node}          The Node number of the current session. This is only
                    required if a door32.sys file is not provided.

  /H{handle}        The telnet handle of the session. This value is obtained
                    by the telnet server that accepted the telnet session.
                    This is only required if a door32.sys file is not provided.

  /C{COM port}      This informs NetCom that NetFoss is running in COM port
                    mode, so NetCom will not perform any telnet communications
                    as COM port communications are handled by NetFoss.dll.
                    This simply makes NetCom idle after shelling to the
                    external application, as if it was running in local mode.
                    The COM port value passed is ignored.

  /D{Write Delay}   When NetCom receives data from the external application,
                    it waits a while for additional data to be received before
                    it sends a packet to the remote telnet user. This value
                    specifys the maximum time to wait since the first data was
                    received. The default is 50. (50ms)

  /B{Buffer Maximum} The maximum amount of data to buffer before sending as
                     a packet to the user. Once this value is reached, the
                     data is sent without waiting for the delay periods. The
                     default is 1250.

  /S{ignored}       This was used in early versions of NetCom.


 NetCom.ini optional configuration settings:

 NetCom.exe will look for a NetCom.ini file in the same directory, and if it
 exists then the following settings will read from it:


 Non-Blocking={value} : This value must be 0,1, or 2.
                        0 = Enable Blocking Sockets
                        1 = Enable Non-Blocking Sockets
                        2 = Leave current Socket settings

 Windows supports Blocking and Non-Blocking sockets. Non-Blocking sockets
 are faster, and therefore NetCom will enable Non-Blocking sockets by default
 if this setting is not defined in NetCom.ini. When this value is set to 2, it
 will be up to the telnet server to determine which socket mode is used. The
 Net2BBS telnet server will always set the socketz to Non-Blocking mode before
 spawning NetFoss.

 ForceClose={Value} : The number of milliseconds to wait, before forcing a
                      node's console to close. By default this is disabled,
                      and you must specify a non-zero value here to enable it.

 This value defines how long NetCom should wait for the external application
 to terminate, once the telnet connection has been closed. The value is in
 milliseconds, so for example ForceClose=5000 would wait 5 seconds for the
 application to close on it's own once the caller has disconnected. After the
 specified time, NetCom will force the application to close.
 Note: ForceClose may not work if a batch file is used on the CommandLine
 parameter in Net2BBS.ini. It will work if a specific .EXE filename is used.

 The other settings are identical to their command line counterparts, but if
 both the command line settings and .ini settings are defined, the command
 line values will be used. 

 If NetCom.ini is not found, and no command line switches define the Write
 Delay and BufferMax settings, then the above defaults are used.


 Frequently Asked Questions:

  Q:  Does NetFoss run under Windows 10, 8, 7, Vista, XP, 2000, Server?
  A:  NetFoss is compatible with all 32-bit versions of Windows NT,
      including Windows 10, 8, 7, Vista, XP, 2000 and Windows Server.
      When using a version of Windows newer then XP, the NETFOSS.DLL
      will need to be copied to c:\windows\system32\ 

      64-bit editions of Windows don't support NTVDM (Virtual DOS Machine),
      so they can not run DOS applications unless you run a 32-bit version
      of Windows inside an Virtual Machine such as "XP Mode" or VMware.

  Q:  Does NetFoss run under Windows 3.x, 95, 98, ME?
  A:  No. These versions of Windows do not offer true multitasking,
      resulting in very poor performance for running DOS applications.

  Q:  Does NetFoss allow all MS-DOS-based BBS programs and doors to
      redirect to a telnet connection?
  A:  Yes, as long as the application supports FOSSIL or INT 14h
      communications NetFoss can be used. For other applications that
      communicate directly with serial UART hardware, the NetSerial
      redirector can be used instead of or in combination with NetFoss.      

  Q:  Does NetFoss work with Windows-based BBS programs?
  A:  Yes and No. Windows-based programs don't use a FOSSIL themselves,
      so a FOSSIL is only needed to allow the BBS to shell to external
      MS-DOS-based applications (doors). This is done by the BBS handing
      over the telnet socket (or COM port) to NetFoss when a door is run,
      and after the door application exits, NetFoss releases the socket
      (or COM port) and returns control to the BBS program.

  Q:  Do I need a Telnet Server to use NetFoss?
  A:  NetFoss includes the Net2BBS Telnet Server, and can also be used
      with other Windows Telnet Servers. NetFoss is also compatible with
      modems, (real or virtual) which do not require a telnet server.

  Q:  Does NetFoss work as a FOSSIL for physical com ports?
  A:  Yes. 

  Q:  Does NetFoss work as a FOSSIL for NetSerial Virtual Com ports and
      Virtual Modem emulators under Windows?
  A:  Yes. 

  Q:  Does NetFoss work as a FOSSIL for direct Telnet?
  A:  Yes. NetFoss includes the NetCom Telnet Communication engine
      which takes over an active TCP/IP connection from the Telnet Server.

  Q:  Why do I get a "Node already in use" message from NetFoss?
  A:  See the NETCOM.EXE error messages section below.

  Q:  How can I improve Zmodem transfer speeds?
  A:  By installing PDZmodem as an external protocol in the BBS.

  Q:  Can Net2BBS be run from the System Tray?
  A:  Yes, by using the freeware TrayIt Utility downloadable from
      The NetFoss web site

  Q:  Can Net2BBS be run as a Windows Service?
  A:  Yes, read the file NET2BBS.TXT for detailed instructions.
  Q:  Does Net2BBS support SSH encryption?
  A:  No, but you can use an SSH tunnel such as OpenSSH to accept SSH
      connections on one tcp port, that redirect to Net2BBS on port 23.

  Q:  When a client is downloading from my BBS using Zmodem, I see
      FDSZ occasionally stall for 12 seconds, then continue. Why?
  A:  NetFoss sees that the TCP write buffer is being filled, because
      FDSZ is generating too many almost-empty packets, causing the
      client to receive no more then 25K-40K CPS, while FDSZ transfers
      faster on the BBS end. Each time the buffer fills, NetFoss pauses
      for 12 seconds to allow the client some time to catch up. Using
      PD Zmodem instead of FDSZ can avoid the issue.

  Q:  Does NetFoss work with DOSBox?
  A:  No. DOSBox performs considerably slower then NTVDM as a DOS emulator,
      and it is not compatible with NetFoss.

  Q:  Can I donate to NetFoss development?
  A:  Paypal donations are accepted at sales@pcmicro.com. So far no one
      has made a donation, so you could be the first one. :-)
      However NetFoss is freeware, so please don't feel obligated to pay.
      You could also show your appreciation by registering Doorway and
      NetSerial, (both are sysop priced at $25, allowing unlimited nodes).


 NETFOSS.COM Error Messages

  Node already in use

       This indicates that either the current or another DOS Window
       already has the NETFOSS.DLL file activated with the same node
       number assigned.
       The node number was either passed on the command line, or read
       from the DOOR32.SYS file.

       If you see this, try closing any DOS windows (Command Prompts)
       that are open, in case you inadvertently had installed NetFoss
       to the same node number from another window.

       Another possibility is that you loaded NetFoss before you loaded
       your Win32 BBS from the same window, in which case the BBS is
       attempting to open another instance of NetFoss from that window.

  Can't find netfoss.dll

       This means that netfoss.dll was not located in any of the directories
       listed in the Windows environment variable called "Path".
       You can change the path (a system environment variable) by going to
       the Windows Control Panel, click on "System Properties", Click on
       the "Advanced" Tab, Click on "Environment Variables" and edit the
       value for the System variable named "Path".

  Bad netfoss.dll [0x]

        This indicates netfoss.dll was found, but it was unable to load.
        The error code in the brackets should be sent to support@pcmicro.com.
  No node/handle passed

       This indicates there was not both a /n{node number} switch and a
       /h{socket handle} switch passed from the command line, so NetFoss
       was expecting to find a DOOR32.SYS in the current directory where
       it would obtain these values from.

       A DOOR32.SYS file is a "drop file" created by 32-bit BBS programs.
       Typically BBS programs create one or more "drop files" before
       running an external program (door).
       Drop files can then be read by the external program to determine
       information about the connection and user, such as speed, terminal
       type, number of minutes remaining, etc.

       On most BBS packages, Drop Files are typically created in the nodes
       default directory, which is usually the directory that the BBS node
       was started from.
       When a BBS runs an external program (known as a door), it starts
       the door (or its batch file) from this directory, and typically a
       doors batch file will then change the directory to where the door
       is actually located.
       By default this is not the case with Synchronet BBS, but Synchronet
       allows the sysop to define which directory the door starts out in.

  Low RAM
       This means there was not enough RAM for NetFoss to install itself.
       Netfoss.com requires approximately 2k of conventional memory to
       install itself, (conventional is memory below 640k) but once it is
       installed, it uses less then 1k of conventional memory.
  Needs NT

       This means an inferior version of Windows has been detected. ;)
       NetFoss requires a 32-bit version of Windows 7, Vista, XP, 2008,
       2003, or 2000. Earlier versions of NetFoss also supported NT4.

  Can't uninstall

       This means that NetFoss was told to uninstall itself from memory
       (after being run with the /u parameter), but it was either not
       previously loaded in the current NTVDM (Command Prompt) window or
       it was unable to uninstall itself for some other reason.


 NETCOM.EXE Error Messages

  Error: No command line given. Aborting.

      This means that NETCOM was not given the path\filename.exe of
      a DOS application to execute (such as a BBS or a door) or a
      Batch file (either .BAT or .CMD) to process.
      The command line given must include the extension.

  Error: No node/handle passed.

      This means that NETCOM was not passed a /n{node number}
      and a /h{telnet socket handle} value on the command line, and
      there was also no DOOR32.SYS file found in the current directory.
  Error: Node already in use.

      This means that another NetCom is already communicating with
      NETFOSS.DLL on the node number that was either passed on the
      command line or read from the DOOR32.SYS file. 

  Error: External application failed to execute.

       This means that the command line that netcom was told to
       execute failed to work. Usually this indicates the path
       or filename you specified did not exist, though there could
       be other reasons.

  Error reading DOOR32.SYS

      The DOOR32.SYS file was not readable, or was in the wrong

  COM Port Mode.

      This message is shown if the DOOR32.SYS is configured for COM
      Port mode, or if a /C{value} parameter was passed to NetFoss,
      which causes NetCom to run the external program without a TCP/IP

  Local Mode.

      This message is shown if the DOOR32.SYS is configured for local
      mode, or if the socket handle listed in DOOR32.SYS or passed on
      the command line was -1, which causes Netcom to run the external
      application without a tcp/ip interface.

 How NetFoss Works

 NETFOSS.COM is a DOS TSR (Terminate and Stay Resident) executable stub
 which intercepts specific DOS Interrupt Requests, including:
    * FOSSIL Driver requests (all INT14 interrupts).
    * Timer Tick chain requests  (INT1C interrupts).
    * DESQview requests (including INT10, INT15, and INT21 interrupts).
    * Other DOS requests (to improve DOS/NTVDM performance).
 Many of these interrupt requests are handled within NETFOSS.COM, while
 some of the requests (such as read and write FOSSIL functions), are
 transfered to NETFOSS.DLL.

 NETFOSS.DLL is the NetFoss Win32 Virtual Device Driver, which handles
 most of the INT14 requests, including reading/writing characters and
 blocks. It also handles all the Serial communications when NetFoss is
 configured for COM port mode. By default NetFoss is configured for
 telnet mode, in which case NETFOSS.DLL redirects all the data to and
 from NetCom.exe using pipes. NetFoss.dll is a shared DLL, so only one
 copy of this 6K DLL exists in memory which is shared by all the node

 NetCom.exe is the Win32 Winsock Communications Engine, which handles
 the telnet socket I/O for NetFoss.dll. NetCom is given the socket
 handle for the active telnet connection, and the path of the DOS
 application, which NetCom spawns within the same Console Window that
 NetCom is using. While the DOS application is running, NetCom's
 background threads are transmitting and receiving data between the
 telnet socket and NetFoss.dll.

 Net2BBS.exe is a Win32 Telnet Server, which is compatible with NetFoss.
 For each incoming telnet connection, it opens a new window and runs
 NF.BAT, passing it the name of the DOS application to spawn.

 Net2Mon.exe and NetSpy.exe are Monitors, which allow viewing Net2BBS
 and every running BBS node under newer versions of Windows while Net2BBS
 is running as a service. For more information see Net2BBS.TXT

 NetSpy is a DOS terminal redirector for Windows, which allows the sysop
 to spy on their users when Net2BBS is running as a service under later
 versions of Windows (such as Windows 10/8/7/Vista, or Server 2008/2012).

 NF.BAT is a Batch File for NetFoss, which loads NetFoss.COM (which in
 turn loads NetFoss.dll) and then runs NetCom.exe, passing it the telnet
 socket handle, and the name of the DOS application to spawn, along with
 any optional command line parameters.


 Suggestions for DOS Door/BBS develpers

 If you have written a DOS Door or BBS program, and you want to improve
 it's performance when running under NetFoss, here are some suggestions:

 1) Use Block Write functions, instead of sending one character at a time.
    This will considerably improve performance. Keep in mind that your
    send routine will need to attempt to send as much as desired to the
    FOSSIL, and then check how many bytes the FOSSIL reported actually
    sending, and then loop to attempt to send the remainder.

 2) Release timeslices to DOS or Windows. During loops where your software
    is polling the keyboard and/or the FOSSIL status, make the following
    call to tell DOS to release a timeslice to lower CPU usage:
      mov ax, 01680h ; INT 2Fh Command 1680h - Release DOS timeslice
      int 2Fh

    This is not only supported by NetFoss, it is supported by most most
    Virtual Machine emulators and multitaskers.

 3) Avoid using INT 14h calls for maximum speed. 
    DOS and VM's are slow at processing interupts, so instead of performing
    an INT 14h every time you make a FOSSIL call, you can instead call the
    address directly:

       mov  ax, 3514h       ; Command 35h - Request entry point for INT 14h
       int  21h             ; ES:BX points to int14h handler entry
       cmp es:[bx+6], 1954h ; Check for the FOSSIL magic number 1954h
       jne noFOSSIL         ; Get out of FOSSIL was not detected
       mov FOSSIL_ADDR,bx   ; Save the FOSSIL entry point
       mov FOSSIL_ADDR+2,es ; so it can be called directly from now on.

       mov  al, 04h         ; Send Initialize FOSSIL command
       call dword ptr FOSSIL_ADDR ; By calling the address directly

    Examples of how to do this with Pascal, C, and BASIC are provided in
    the X00 FOSSIL HLLAPI samples by Raymond Gwinn.

 FOSSIL INT14 Functions Reference

       Common Functions:
               Function 00h - Set communications parameters
               Function 01h - Transmit character and wait
               Function 02h - Get received character with wait
               Function 03h - Return Serial Port Status
               Function 04h - Activate Port
               Function 05h - Deactivate Port
               Function 06h - Raise/lower DTR
               Function 07h - Return timer tick information
               Function 08h - Flush output buffer
               Function 09h - Purge output buffer
               Function 0Ah - Purge input buffer
               Function 0Bh - Transmit no wait
               Function 0Ch - Non-destructive read-ahead (Peek)
               Function 0Dh - Keyboard read without wait
               Function 0Eh - Keyboard read with wait
               Function 0Fh - Enable / Disable Flow Control
               Function 10h - Control-C / Control-K checking
               Function 11h - Set cursor location
               Function 12h - Read cursor location
               Function 13h - Single character ANSI write to screen
               Function 14h - Enable or disable the DCD watchdog
               Function 15h - Write character to screen using BIOS
               Function 16h - Add / Delete a routine from the timer tick
               Function 17h - Reboot system (not supported by NetFoss)
               Function 18h - Block Read
               Function 19h - Block Write
               Function 1Ah - Break begin or end
               Function 1Bh - Get FOSSIL Driver information

       X00 Enhanced Functions:
               Function 1Ch - Activate Port
               Function 1Dh - Deactivate Port
               Function 1Eh - Extended line control initialization
               Function 1Fh - Extended serial port status/control
               Function 20h - Read with no wait (destructive)
               Function 21h - Stuff/Poke the receive buffer

       Layered Application Functions:
               Function 7Eh  - Install an "external application"
               Function 7Fh  - Remove an "external application"
 For detailed information on using these functions, refer to the
 FOSSIL.TXT and FOSSIL.CHT files included in the NetFoss archive.
 Additional information can be found in the X00 package.

 License and Disclaimer

 NetFoss is provided free of charge, without any warranty whatsoever.

 Use NetFoss entirely at your own risk. In no event will PC Micro Systems,
 or its agents be liable for any damages, including loss of profits or
 other consequential damages arising from the use or inability to use

 You may copy and distribute verbatim copies of NetFoss, in any medium,
 provided that none of the files in the archive are tampered with and no
 files are added or removed.

 You may bundle NetFoss with your own BBS software or telnet server, if
 you do not charge a fee for the product, and as long as all the files in
 the original NetFoss archive are placed in a separate sub directory once
 it is installed, with no changes except for the NF.BAT file which may be
 customized as needed. 

 NetFoss is a trademark of PC Micro Systems, Inc.
 Net2BBS is a trademark of PC Micro Systems, Inc.
 NetSpy is a trademark of PC Micro Systems, Inc.
 NetSerial is a trademark of PC Micro Systems, Inc.
 Doorway is a trademark of PC Micro Systems, Inc.
 PC Micro is a trademark of PC Micro Systems, Inc.
 DESQview is a trademark of Symantec Corporation.
 FrontDoor is a trademark of Definite Solutions.
 X00 is a trademark of Raymond L. Gwinn.
 Windows is a trademark of Microsoft Corporation.
 Other products mentioned are properties of their respected authors.



 A big thanks goes to Maarten Bekers for answering many Winsock related
 questions during the original NetCom development in 2001. Maarten is the
 author of EleBBS and EleCom. NetFoss began as a side project while beta
 testing Maarten's SyncFos interface and encountering issues with door
 compatibility and performance, so NetFoss was created to redirect DOS
 INT 14h calls to the experimental NetCom communication driver.

 Another big thanks go to `Hutch' for developing MASM32, the ultimate
 Macro Assembler SDK for designing Windows software in ASM, and to
 Rob Swindell for information on the C++ Virtual DOS Driver 'BOP' hooks.

 And finally, thanks to the following beta testers who reported problems
 and/or offered suggestions on improving previous versions of NetFoss:

 Andrew Grimsby       aka Andrew
 Maarten Bekers       aka Ele
 Mark Netzel          aka Kram
 Rick Parrish         aka Ree
 Marty Kazmaier       aka Surato
 Brian Zohu           aka Zoob
 Michelle Sullivan    aka SORBS
 Louis Northmore
 Corry Snow
 Jani Sirpoma         aka Dragon
 Mike Dillon          aka GSValore
 Michael Preslar      aka Z
 Christopher Evans    aka Teknopup
 Jimmy Rose           aka BlueWizard
 Loginius             aka Loginius
 Daryl Hunt           aka DeadMeat
 Chris Costakis
 Charles Ren‚ de Cotret
 Michael Everett, III aka Bobo
 George A. Roberts IV aka Sirtwist
 Eric Schwimmer       aka Uber
 Bud Younke           aka Raptor
 Doug Rhee            aka BBSFiles
 Tom Jackson          aka ACTION
 Darryl Dynnaway
 Steve Winn
 John Elite           aka Deathr0w
 Ioram Sette
 Minh Van Le
 Brian Taylor
 Rich Ringer          aka Pony
 T.J. McMillian       aka Exodus
 Alexey Fayans
 Vasya Pupkin         aka Burning Shadow
 Michael Montague     aka Tarix
 Markus Feilen
 Christian Dirks
 Luis Silva
 Hawk Hubbard
 Todd Yatzook         aka Maskreet
 Rudi Timmermans
 Kin Chan
 Ruben Figueroa
 Chris Cotrell        aka MrO/Jas
 C.G. Learn
 Antonio Rico
 Tom Swartz 
 A special thanks to Kin Chan for beta testing the new security features
 in Net2BBS 1.12, and to Todd YatZook for beta testing the DOOR32 shelling
 from DOS BBS software in NetFoss 1.14.


 Whats new:
           0.2wb      Added support for /n{node} in NetFoss.com
                      and both /n{node} and /h{handle} in netcom.exe.

           0.3wb      Optimized code, fixed win2k command line bug.

           0.4wb      Redesigned buffering routines, and in the process
                      fixed the FOSSIL peek/poke (0CH &21H) commands,
                      so now Scrabble, Axe & Fang, and any other doors
                      which previously didnt work should now be fine.
                      Fixed random input buffer garbage on first run.

           0.5        Reoptimized code for additional speed. Improved
                      status returned when reading a character to allow
                      T&J software's doors to run. Check for carrier drop
                      during a function 2 (read character /w wait)
                      command. Set function 2 timeout to 30 seconds.

           0.6        After a long pause in NetFoss development, this
                      is a minor update which adds support for NT 4.0.
                      The error messages are now always returned to the
                      DOS window rather then to a pop-up window. Fixed a
                      bug in FOSSIL Function 1B (return info in FOSSIL)
                      which was not returning everything it should.

           0.7        Forced Echo off for non Win32 BBS software.
                      Fixed the block-read function, which was not
                      compatible with PCBoard.

           0.7.1      Fixed buffer output bug on slower computers or
                      slow connections, thanks to Charles Ren‚ de Cotret
                      for reporting the issue and testing the fix.

           0.7.2      Added work around to fix CR/LF telnet bug in L.O.R.D.

           0.8        Added DESQview emulation, to release DV timeslices
                      to NT. Added detection and optimizations for poorly
                      designed doorkits. Enhanced carrier detection
                      routine to work around EasyDoor kit bugs
                      (Reported by Mark Netzel). Force non responding
                      doors to terminate 10 seconds after carrier drops.
                      Improved timeslicing release for local mode doors
                      (requested by Marty Kazmaier). Fixed INT1C Timer
                      Chain handling to work around the Fresh Water Fishing
                      door (reported by Mark Netzel). Optimized base memory
                      usage in netfoss.com. Updated docs. Added a pause to
                      all error messages.

           0.8.1      Minor Update. Fixed ANSI detection problem introduced
                      in v0.8 in which Renegade BBS and some doors created
                      using doorframe were unable to detect ANSI.
                      (Reported by Cory Snow and Marty Kazmaier).

           0.8.2b     These were private beta versions of a rewritten Netcom
            thru      released only to the beta team. They included command
           0.8.5b     line paremeters to configure the timer settings.
                      Removed the L.O.R.D. CR/LF work around since its fixed
                      in the beta version of L.O.R.D. 4.07.

           0.8.5wb    An "experimental" Wide beta of NetCom, to be used with
                      NetFoss 0.8.1. It now responds to AIC "Are you there"
                      requests, and turns on binary mode by default. Please
                      read the BETANOTE.TXT file for details on this release.

           0.8.6      The Return of NetFoss! After a year and a half pause,
                      development has now resumed. Thanks to Doug Reah for
                      testing hundreds of doors with NetFoss on his BBS, and
                      reporting which ones didn't run. It turned out that
                      several doors by "William Rountree" did not follow the
                      level 5 FOSSIL specs correctly, so a work around was
                      added. Also some doors such as Death Masters could
                      generate a blank remote display, fixed. Adjusted the
                      timing to slow down during Zmodem transfers, preventing
                      the BBS end from finishing first and timing out.
           0.8.7      Fixed issue that could cause version 0.8.6 to crash
                      PCBoard, reported today by Darryl Dynnaway.
                      Restored a small delay at startup after setting the
                      telnet options, as Mtel (and terminals running under
                      COM/IP) would sometimes experience garbage input
                      chars without this. Reported by Doug Rhee and Mark

           0.9        Adjusted block-read command to support FOSSIL Zmodems
                      (other then FDSZ) that transfer in blocks rather
                      then a character at a time.

           0.9.1      Prevented VADV BBS from hanging after a portscan is
                      done on port 23, reported by Steve Winn.

           0.9.2      It's been just over 2 years since the last update.
                      It turns out that one of the changes made to version
                      0.8.6 to allow a some doors to work which don't follow
                      the FOSSIL rev.5 specs causes certain other doors to
                      fail. The problem was that the X00 Specifications go
                      against the official FOSSIL level 5 specifications in
                      regards to what command 02 (Receive character with
                      wait) returns in AH. The Specs require AH=0, but X00
                      returns the status in AH instead. To resolve this,
                      NetFoss now follows the official specs unless the
                      netfoss.com is given the /X parameter on its command
                      line (within nf.bat) in which case it follows the X00
                      method. Both methods support extended X00 functions.
                      Worked around an issue with a certain PCBoard PPE
                      that sends invalid commands to the FOSSIL. Reported
                      by Deathr0w.
                      Improved timeslice releasing to allow certain doors
                      (BRE,FE,FH,TAL), to run at close to 0% CPU usage.
                      Slowed down binary transfers to avoid upload timeouts.

           0.9.3      Improved binary transfer speed by redesigning the
                      timeslice release handler to optimize for both FDSZ
                      and PD Zmodem transfer modes (byte or block). BBS
                      uploads should never timeout when using PD Zmodem.
                      Fixed minor NetCom issue introduced in 0.9.2 causing
                      a C/R to not be seen by the L.O.R.D. door with some
                      terminals, reported by Ioram Sette.

           0.9.4      Experimental support for COM ports added, allowing
                      NetFoss to be used with dialup Modems, and Virtual
                      Modems such as NetSerial.

           0.9.5      NetFoss now allows DOS based FTN (FidoNet Technology)
                      Mailers such as FrontDoor and D'Bridge to run over a
                      Telnet connection using NetSerial. Fixed some issues
                      introduced in 0.9.4 with status and COM port DTR
                      signals, reported by Rich Ringer. Fixed zero byte
                      write issue also issue introduced in 0.9.4, reported
                      by Ioram Sette. Added keepalive feature for unstable
                      networks and DialUp ISP connections, requested by
                      Minh Van Le.

           0.9.6      NetFoss now includes a miniture Telnet Server called
                      Net2BBS, which logs IP's, plays wav files and supports
                      semaphore file event triggers. NetFoss now runs the
                      "Kannons & Katapults" door game at lower CPU usage -
                      Requested by xbit. NetCom was ajusted to avoid an
                      issue under Windows Vista, reported by Steve Winn.

           0.9.7      Fixed issue preventing PCBoard from running with
                      NetSerial in wait-for-call mode, reported by DeathR0w.
                      When the DOOR32.SYS dropfile is configured for serial
                      communications, NetFoss now looks for the COM port
                      value by also reading DOOR.SYS. Added /R switch to
                      release a COM port during a Deinitialize Port command.
                      Net2BBS includes view-minimize and view-hidden
                      options when launching BBS sessions. Net2BBS bug fix:
                      The wrong IP could be logged during a disconnect
                      from Net2BBS, reported by Alexey Fayans.

           0.9.8      Fixed an issue introduced in version 0.9.7, which
                      did not allow the FDSZ file transfer program to be
                      shelled to from a Win32 BBS (because FDSZ never sends
                      a FOSSIL "Initialize" command) reported by Ioram
                      Sette. Added delay to telnet echo negotiation.
                      Removed internal Keepalive which should not be needed.

           0.9.9      Optimized NetCom engine uses separate Read and Write
                      Threads to minimize CPU usage while idle, and uses
                      larger buffers. NetCom now uses Windows TCP keepalive.
                      Net2BBS now displays the BBS node number in the
                      TitleBar of each Console window. Net2BBS disconnects
                      all active BBS nodes when told to exit. NetFoss now
                      allows a COM port to be passed a locked baud rate on
                      the command line, requested by Robert Wolfe.

           1.0        Optimized all EXE/DLL for Pentium-4 and later CPU's.
                      Previous builds were optimized for Pentium-3.
                      Worked around an issue with NetFoss running with
                      NetSerial and FrontDoor, reported by T.J. McMillian.
                      Net2BBS now supports wildcard blocking of IP addresses
                      and hostnames, improved logging, View=Maximize mode,
                      and other .INI configuration options were added.

           1.01       After over 2 years since the last update, this version
                      offers some minor enhancements: Added Stopnode.{node}
                      semaphore checking to allow an external program or a
                      batch to stop a BBS telnet session, requested by Steve
                      Winn. Added an optional /z{value} parameter to tweak
                      the PD Zmodem transfer speeds. Minor optimizations to
                      NetCom engine for improved performance. Added *R macro
                      to Net2BBS spawned command line to pass a resolved
                      hostname to the BBS, requested by Markus Feilen.

           1.02       Fixed issue in NetCom 1.01 causing carrier drops with
                      the latest beta of GameSrv, reported by Rick Parrish.
                      Added NetCom.ini support for NetCom optional settings.
                      Fixed Net2BBS to enforce proper exit under Windows 7.

           1.03       Fixed issue in NetCom 1.01/1.02 which under specific
                      conditions could prevent the semaphore thread from
                      closing, reported by Vasya Pupkin. Switched to using
                      Pelle Orinius's linker instead of Microsoft's, which
                      creates even smaller Win32 executables. Fixed issue
                      in Net2BBS 1.01/1.02 causing the killfile list to be
                      ignored, Reported by Christian Dirks. Added some new
                      configuration options to Net2BBS allowing additional
                      modes for the Console Window view modes, and added
                      an experimental option to set the number of console
                      lines to 25 or 50 (or any other value).

           1.04       This is the 10 year anniversary edition of NetFoss!
                      Added /s{speed} command line parameter to NETFOSS.COM
                      which allows NetFoss output to be slowed down.
                      Net2BBS 1.03 had a bugfix update 1.04b1 shortly after
                      its release to solve an issue when a users IP address
                      is sent to their terminal. Since then several minor
                      optimizations were done in 1.04 and it now features
                      a Restart command a socket policy server option.

           1.05       A minor update to NETCOM.EXE fixes an issue introduced
                      in version 1.01 that could cause a node to hang if the
                      connection is immediatly terminated. Reported by Luis
                      Silva. Added an optional parameter 'ForceClose=' to
                      the NETCOM.INI file, defining how long NETCOM should
                      wait before forcing termination of a non-responsive
                      external application after the TCP connection has
                      disconnected. No changes to NetFoss itself.
           1.05A       Net2BBS now includes Net2Mon, a Service Monitor which
                      functions as a desktop GUI when Net2BBS runs as a
                      service. Net2BBS now supports DNS-Blacklist blocking
                      of incoming telnet connections. Net2BBS has several
                      minor enhancements. No changes to NetFoss or NetCom.
                      To install Net2BBS as a Service from an Administrator
                      Command Prompt type: Net2Mon /instserv

           1.10       This is a major update to NetFoss, which includes
                      several performance enhancements, and NetFoss now
                      allows remote keyboard input to be provided by an
                      external source, such as NetSpy. NetSpy is a DOS
                      terminal redirector for Windows to allow the sysop
                      to spy on active BBS nodes while the Telnet Server is
                      running as a secure Windows service (without desktop
                      interaction) in newer versions of Windows (Vista and
                      later). In NetCom, the ForceClose= parameter now
                      defaults to never forcing a disconnected application
                      to close (Unless you define it in NETCOM.INI).
           1.10A      Packaging Error, version 1.10 went out today with
                      the wrong NETFOSS.DLL :(

           1.11       A minor update which fixes a bug in NetFoss 1.10(A),
                      in which it would report a crash error if it was
                      uninstalled within a 3 seconds of being installed.
                      NetFoss now also detects if it is running under
                      Windows Virtual PC (ie: XP Mode), and if so, the
                      default parameters are adjusted accordingly.
                      NetCom now defaults to having the ForceClose option
                      disabled (since it only works reliably on .EXE files,
                      and can cause a .BAT file to hang instead of close).
                      NetSpy.asm is now better documented (Requested by
                      Steve Winn). Net2BBS now allows Pseudo Node numbers
                      to be passed to the BBS software. See Net2BBS.txt
                      for details (Requested by Hawk Hubbard).
           1.12       This replaces the buggy NetFoss 1.11 release with
                      stable code, and includes additional optimizations
                      for even lower CPU usage with some doors. Added OS/2
                      timeslice release emulation. Net2BBS has several
                      enhancments including portscanner detection, a built
                      in firewall to block unwanted connections, and
                      support for multiple DNS Blacklists including
                      Geo-location DNSBL support to block entire countries.
                      Removed the Virtual-PC and VMware detection - due
                      to lost source code and because the performance was
                      still much slower under these environments, especially
                      when running many nodes simultaneously.                      
           1.12A      Fixed issue in NETFOSS.DLL which could cause a hang
                      only when running in "COM Port Mode" when BBS raises
                      the DTR signal. Reported by Maskreet.

           1.13       Added additional optimizations to NetFoss and changed
                      NetCom's default timing to provide even lower CPU
                      usage with most BBS software and doors.
                      Added Anti-Hammering protection to Net2BBS (requested
                      by Chris Clark), and doubled the size of the Net2BBS
                      "Bad IP" Cache. Net2BBS ignores multiple IP limits
                      (and hammering) when connections are from localhost.
                      Adjusted bot detection sensitivity (Requested by Tom

          1.14        2016 marks the 15th Aniversery of NetFoss! Added
                      support for running Win32 external doors from DOS BBS
                      software, by using the NFU Utitily which creates a
                      DOOR32.SYS drop file by reading the information from
                      a standard DOOR.SYS drop file and including the telnet
                      socket handle by reading it from the environment
                      variable named %SOCKET%. See the included NFU.TXT for
                      detailed information on how to implement this.
                      Added new options for Net2BBS to Enable/Disable the
                      Anti-Hammering feature introduced in version 1.13 and
                      was known to be unstable. Hopefully that issue is now
                      resolved though just to be safe the Anti-Hammering
                      feature is now disabled by default. Added option to
                      disable the Anti-Bot scanning detection (Requested
                      by C.G. Learn). Net2BBS now writes the socket handle
                      of a Telnet Connection to the environment variable
                      %SOCKET% to allow NFU to use it to launch Win32 doors.
                      NetFoss had some internal changes to allow Win32 doors
                      to be able to run with the FOSSIL enabled. NetSpy and
                      NetCom had minor enhancements to the Console Screen
                      size setting.

         1.14R        The initial 1.14 release had the old NETFOSS.COM 1.13
                      and it was corrected the same day in 1.14A, but a few
                      days later a bug was found in NFU which caused some
                      DOOR32 doors to fail to work. The fixed NFU was updated
                      from v0.04 to v1.14, and the other files remain the
                      same so the second re-release is zipped as v1.14R.

          1.15        Fixed bug in Net2BBS which caused the AntiHammer
                      feature to crash. AntiHammer is now enabled by default.
                      Fixed an unreported 1.14 bug in NetFoss.DLL which
                      causes excessive CPU usage.

          1.16        Added the ability to adjust configuration settings in
                      NETFOSS.COM 'on-the-fly' while a connection is active
                      using the /M (modify) parameter. This allows a DOS BBS
                      to customize settings for each door, for example to
                      allow certain doors using ANSI animation to run slower
                      then other doors. Optimized internal timeslice handler,
                      and added additional parameters to tweak performance.
                      DESQview timeslice releasing is now optional. Removed
                      OS/2 timeslice releasing. Removed unstable debuging
                      code from NetFoss.dll. Added codesigning to Net2BBS.exe
                      and NETCOM.EXE to prevent false-positive results from
                      Microsoft Defender. No other changes to Net2BBS. 


  Home | About NETFOSS | Download | Order License | Guide | Support | Company Info

Copyright © 1995 - 2010 pc micro systems, inc.