Virtual Advanced | Features | Download | Documentation | Support
How to configure Netmodem (v1.0b4)

This document is to help you configure Netmodem v1.0 beta 4 for use with Virtual Advanced v2.1. This version of Netmodem will not work with any versions of VBBS. To allow VBBS to accept incoming telnet calls, you must be using Netmodem v2.0 alpha 3 or above. I use this older version because it is currently the only version that you may register and use with more than one node.

Also, if you are using Windows 98, then you MUST download the Win98 patch for Netmodem 1.0b4. It will not work without this upgrade.

Netmodem:
Install Netmodem and reboot. Load Netmodem and click on the 'config' button, then click the 'comport' tab. You may edit the other settings as you like, they are not important to get Netmodem answering calls.

You want to configure Netmodem for comports that are not real. With my four node configuration, I begin with COM5, and end with COM8. At the top of the window, it list what node number you are configuring. If you have not registered the software yet, then it will only display a '1'. Otherwise, it will also list the other nodes depending on which license you purchased.

So, on node 1, you want to set it for COM5 at 115200 baud. On node 2, you set it for COM6 at 115200 baud, and so on. This is all there is to configure Netmodem.

Virtual Advanced:
Now VA is the confusing part. In channel configuration in VConfig, select the node number you want to use for telnet access (here I use node 1 through 4). The serial port in VConfig will be one less than you configured in Netmodem. So I use COM5 in Netmodem, in VConfig I have it set for Fossil Device 4 (not 5). If you have Netmodem set for COM1 you would set VConfig for Fossil Device 0 (this is not recommended, just given as an example to understand the difference in numbers).

The base address and IRQ doesn't really matter what you have them set to. Lock the baud rate at 115200 and set CTS/RTS for normal.

IMPORTANT: Your INIT Strings should be the following for best results:

Init1: ATH0
Init2: ATZ
Init3:
Off Hook String: ATH1

This concludes VConfig configuration.

Now make a batch file to run the BBS (mine is called BBSx.BAT, where x is the node number). It should at least look like:

d:
cd\va
NU x /L
BBS x
d:
cd\va

In this example, 'x' needs to be changed to what node number the batch file is loading. For node 1, change 'x' to a '1'. Node 2, change 'x' to a '2'. Change both of the x's.

'NU x /L' loads the Netmodem fossil driver (NU). The 'x' is what node number you configured in Netmodem and /L loads it into memory. 'BBS 1' loads VA node number 1.

After you do this you should be able to take calls from the internet.

I have found that if you minimize Netmodem to the tray, then there is a good chance that it will crash before long. If you keep Netmodem's window open on the desktop and do not minimize it, then it seems much more stable.

If you have any further questions, just ask.

You Can Help!
If you find these programs useful, you can show your support by donating - even a small amount. To help out, click the PayPal button below.

Home : News : Products : Downloads : Community : VirtualNET : Development : Support : About : Contact : Bug Reporting