pc micro systems

Beta Test
User's Guide
Company Info


Using NETFOSS with Mannsofts TelSrv

Installing TelSrv

Create a directory somewhere, such as c:\telsrv. Unzip the TelSrv files into this directory. If you are using PKZip then be sure to have it recreate the directory structure. You can also place a shortcut to TELSRV.EXE in your startup folder, so that windows automatically runs it at startup. TelSrv comes with an older version of NetFoss included, which should be upgraded to the latest version.


Installing NETFOSS

Create a directory to unzip the NETFOSS files into. In our example we will use the same directory: c:\telsrv
Next edit the NF.BAT file, and change all the paths to point to the directory it was unziped to. You will also need to add a " %1" to the end of the netfoss.com line, so that it will run not require a DOOR32.SYS drop file (non-door32.sys mode). The batch file should now look like:

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

Configuring TelSrv to use NETFOSS

Run TELSRV.EXE and click on the Config tab. Configure it as shown:

Listen Port is the tcp/ip port to accept incoming connections on. This is normally 23 for telnet.
Max nodes is the maximum number of nodes you will allow to run at the same time.
Program Visibility allows the nodes to be normal, minimized, or hidden when they are run.
You must select "Use External Program" in order to run a command line when a user connects.
The "Working Directory" field is the directory that the BBS is started in. It's usually a good idea
to change this to the BBS's node directory (ie: c:\ra\node*N ) but at the time this document was made TelSrv (4.00) did not allow using the *N macro in the working directory field.

The most important field is the Command line. This must run NF.BAT, and pass it the proper node number and winsock handle, followed by the command line needed by the BBS software to run. The /n*N passes the node number, and the /h*H passes the winsock handle.

In the above example, we are telling NF.BAT to run "c:\ra\ra.exe -n*N -B57600" which is the command line needed to run RemoteAccess BBS from a front-end. the -n*N tells RA which node is to be used, and the "-B57600" tells RA that there is already a caller connected, and it should assume that caller is connected at 57600 Baud rather then entering the wait-for-call mode.

Note: Not all BBS software will use the -N*N and -B57600 macros. You will need to check your BBS documentation on how to run the bbs from a front end, or check the command line switches in your BBS documentation to find the proper switches.


If you encounter problems....


Instead of running the BBS .EXE file in the command line, you can have it run another batch file instead. This will allow you to run your BBS software from this batch, and you can add a "pause" command in the batch file after the program is run so that you can see the results of any error messages it displays before the window is closed.


hot deals on computers

web hosting $9.95
Home | About NETFOSS | Download | Beta Test | Guide | Support | Company Info

Copyright © 2000 - 2008 pcmicro.com    All rights reserved