VBS1 comes packaged as the main 'VBS1 Core' on a single CD, and add-on modules on separate CDs. VBS1 uses Marx USB-key encryption as an anti-piracy measure, meaning that a USB key must be present in the computer prior to VBS1 being launched.

VBS1 comes in two versions: single-user license and network license. Each version requires a specific type of USB key in order for it to run. The single-user version requires a single-user USB key on every machine running the single-user license. The network license requires one network USB key in a machine located somewhere on the network.

Single-user Installation

• Install VBS (blue CD). If installing on multiple computers, ensure you enter a different serial number on each computer or else VBS1 may crash during multiplayer.
• Once the installation is complete leave the 'Install Marx Drivers' box checked to install the USB key drivers. Otherwise you can run CD setup (CbSetup.exe) located in the Marx folder on the installation CD.
• Install add-on modules (other CDs).
• Insert USB key, allow Windows to search for required drivers and the driver installation will complete.

Network Installation

• Install VBS on all computers (red CD). Ensure you enter a different serial number on each computer or else VBS1 may crash during multiplayer.
• Once the installation is complete leave the 'Install Marx Drivers' box checked to install the USB key drivers. Otherwise you can run CD setup (CbSetup.exe) located in the Marx folder on the installation CD.
• Run CBSetup.exe on all computers on the network (even if they are not going to have a USB key installed in them).
• Install add-on modules on all computers (other CDs).
• Choose a USB key server machine. It can be any computer on the network, and it doesn't have to be your game server. The USB key server is not the same as the game server; one machine can perform both functions if required.
• Insert USB key on the USB key server. Allow Windows to complete the driver installation.
• Run CbNetSrv.exe (located in the Marx folder on the installation CD - copy it somewhere on the hard drive) on the USB key server. Place a shortcut to CbNetSrv.exe in the Startup programs folder on the server so it starts automatically when the server starts.

If running with a network installation, ensure CBNetSrv.exe is running on the USB key server.

Ensure USB keys are inserted either on a) the USB key server or b) all machines depending on the type of installation (network or single user respectively).

Run VBS1. If running a network install, start each client machine one at a time, with a pause of 5 seconds between each. This will ensure that the USB key in the USB key server doesn't get overloaded. Also, ensure you only double click the VBS1 shortcut once. Otherwise multiple instances of the program will run. It takes 5 - 10 seconds for anything to happen after starting VBS1. It is recommended that soldiers be banned from starting the application - have staff members start the program prior to the arrival of participants and don't shut the application down unless you have to.

The first time VBS1 is run you'll be presented with a preferences dialog. Simply press 'Autodetect' once and then 'Start'.

There is a bug in the program whereby double-mouse pointers will be visible (if Windows and VBS1 resolution and refresh rates are the same). If this happens, Alt-tab out of and then back into VBS1.

Ensure:

a) If running a single-user license, check the USB key is inserted in the computer.

b) If running a network license, check that a USB key is inserted in the USB key server and that CBNetSrv.exe is running (on the USB key server). Also ensure that CBSetup.exe has been run on the client machine where the error occurred.

Note that the network USB key requires a computer with an active network connection. The network USB key will not work on stand-alone computers. There may also be issues with dynamic IP addressing - if all else fails try assigning static IPs.

The USB key on the server has filled. This may occur if you a) start too many instances of VBS1 at once on a machine (doubled clicked on a VBS1 shortcut more than once) or b) you've started VBS1 on too many machines without allowing a pause between each launch.

You have two options: a) you can shutdown VBS1 on all machines and start again, or b) run AdminApp.exe (located with CBNetSrv.exe) to determine if there are any duplicate users. (Click 'Get/Update Servers', click on a server, click 'Login to Server', press 'OK', click 'Users Connected'. Look for multiple instances of the same user. Remove duplicate users by clicking on the user, click 'User Info' and then 'Disconnect User').

"VBS1: vbs1.bin - Application Error … The memory could not be 'read'. Click on OK to terminate the program."

This is normal, and will always occur when existing a VBS1 network session. Press OK.

To run a networked session, firstly ensure that the appropriate scenario exists in the 'mpmission' folder on the game server. There are two types of game servers: dedicated and non-dedicated.

Dedicated Server

A dedicated server is faster as the server computer will not display a graphical user interace whilst it is running. It is harder to administer however.

To start a dedicated server, run VBS1 with the -server option. Eg, Copy VBS1.bat, and rename it VBS1 dedicated.bat. Edit the batch file. At the end of the line insert a space and then type -server. Save the file and close notepad. Run the batch file to start a dedicated server. This has already been done for you - use VBS1 Server.bat.

Once started, client machines will see the server within VBS1 on the 'Networking Screen'. They then double-click on the server in that interface to join the server (or they click 'Join').

One machine needs to be administrator if using a dedicated server (a machine controlled by a staff member is preferred). To log in as admin, join the server, and then type (note / brings up the chat window):

/#login admin

You can then control various aspects. For example, to restart the scenario:

/#restart

To go to the assignment screen (all computers on the network will go to the assignment screen):

/#reassign

To go to the mission selection screen (all computers on the network will display 'Waiting for Server' except for the machine that is administrator):

/#missions

Non-dedicated Server

To start a non-dedicated server click 'New' on the network interface within VBS1 on the server. Use the interface to select a map and scenario and otherwise control the networked session. Client machines will be able to see the server on the network interface (once it has been started on the server) and will be able to join the session by double-clicking on the server or clicking 'Join'.

Starting a Scenario

Carry out the following steps to start a multiplayer scenario:

• Select a terrain area and mission. Click 'OK'.
• You are now looking at the assignment screen. Wait for all participants to join (the box on the right will fill up with names).
• Once all participants are joined, drag each into a position (the box on the left). Note you can cycle through BLUEFOR, OPFOR, Resistance and Noncombatant positions via the buttons on the far left.
• Once all participants are in position, click 'OK'.
• The mission will load. It will be sent from the server to all the clients which might take some time.
• All participants will arrive at the mission briefing screen. If using a dedicated server, all clients must click 'I'm ready' for the mission to begin. If using a non-dedicated server the mission will begin when the server selects 'Start Mission'.

Note that it is impossible for participants to join a mission once it has begun (you'll need to go back to the assignment screen as start over).

Supported Scenarios

On a 10/100 network it is not recommended that you play with more than 35 - 40 machines in the one networked game. Gigabit can support up to 60 users.