VADV32 | Download | Documentation | Support
Other VADV32 Features and Information

This document contains information about VADV32 that may be useful in some situations, but not necessary to know for basic operation.

VADV32 Command Line

The following parameters can be passed to VADV32 from the command line:

  • /RESETWINDOW - This will force VADV32 to load on the primary monitor centered. It will also turn off the option to save window positions as well as resetting the window position that is saved. This is useful if you cannot see VADV32 when you load it.
  • /VERSION or /VER - Display VADV32's version.
  • /? - List all command line options.
VADV32 Hotkeys
VADV32 allows various hotkey combinations to be used to access features quickly. The following are function keys that are commonly used:
  • F2 - View VADV32.LOG
  • F3 - View BBS.LOG
  • F6 - Update RTBBSL
  • F9 - Toss Network Packets
Door Configurations

VADV32 will only run fossil-aware doors. When configuring your doors, setup the nodes to use a standard fossil driver. The COM port does not matter, so using COM1 for each node is fine.

The following variables are set in the environment when a node is created. These can be useful when running doors:

  • %BBSPATH% - The full path to the main BBS directory
  • %DROPPATH% - The full path to the node's drop file directory
  • %NODE% - The node number
  • %NFNODE% - The netfoss node number
  • %SOCKET% - The socket handle

Internal File Triggers

VADV32 v2.6 and later have internal file triggers that you can use to perform VADV32. The following are the available triggers. All internal file triggers are expected to be found in the main VADV directory.

  • BBSFILES.FLG - This will generate a listing of all files found in the file area and save it as BBSFILES.TXT in your main BBS directory.
  • - This will close and reset the specified node number "xxx". This can be useful if a node gets hung and you do not have access to the BBS computer to fix it.
  • REBOOT.FLG - This will reboot the computer.
  • VA32PAGE.FLG - See below.
Tray Icon

If you have the tray icon enabled in VADV32's configuration, then you can use it to access certain features.

By hovering your mouse over the tray icon, you can view the server's status, the SysOp pager's status and the server's uptime.

Double clicking the icon will maximum and minimize the main VADV32 window.

Right clicking the icon will bring up a menu to access various options. This can be useful if VADV32 runs in the background and you wish to quickly access one of these functions.


The LOADBBS.BAT is installed with VADV32 into your main BBS directory. This is the batch file that will load the BBS node when a user connects to VADV32.

As of VADV32 v2.1, the LOADBBS.BAT is optional and by default it is not used. To use LOADBBS.BAT, go to VADV32 configuration's Advanced tab and disable "Internal Node Handling."

By default, the batch file is setup for the BBS directory to be "C:\VA". If you installed VADV into a different directory, then you MUST edit this file and change all occurrences of "C:\VA" to whatever directory you chose. If you do not do this, then the BBS nodes will not load when a user connects.

The reason VADV32 uses this file to load the BBS instead of doing it automatically is because you might want to run some type of command either before or after the user session. For example, maybe you need to load an ANSI driver before the user logs in to see the session locally, or after the user logs off you might want to cleanup any temporary files left behind.


You may create a batch file named LOGON.BAT which will be executed before the node is launched. The node number is passed as a parameter. This file can be useful for doing special node cleanup routines before a user logs in.


When a user connects to VADV32, it creates a file called TCPIP.CFG in the "C:\VA\TEMP\Nx\" directory (x is the node number). This files contains information about the connection:

  1. Socket Handle
  2. User's IP Address
  3. User's Hostname
  4. VADV32 Uptime at the Time of Connection

VADV32 v4.1 and above have an option to alert you in a customized fashion when a user pages. If the interval is greater than zero, VADV32 will check for the file VA32PAGE.FLG in the main BBS directory. The format of the file is:

  • Line 1 - Notification type. This can be either "audio", "video" or "both".
  • Line 2 - The node number the page is coming from.
  • Line 3 - The username who is paging.

VADV32 will read the first line and determine the type of notification. If audio, VADV32 will play the configured WAV file. If video, VADV32 will display a small notification window in the lower right corner of the primary monitor. If line 2 and 3 are configured, that information will be displayed.

If the flag is found but contains no information, an audio notification will be performed.

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