Using the VirtualBox Banyan VINES Server Template. 1) UnZIP the file 2) Copy the folder to where VirtualBox stores the other virtual machines. On a Mac for example it is /Users//VirtualBox VMs 3) Open VirtualBox and click Add (don't click New). 4) Browse to where you pasted the folder and click on the file VINESReadyToChangeSerial.vbox 5) Click Open 6) Select the newly imported VM and click Clone (we need to do this to get around duplicate VirtualBox UUIDs and to make copies ready to be setup). - Clone this VM multiple times if you plan to have more than one server. - The idea is you never want to setup the template VM, always make a clone, and use that clone for each new VINES server you want to build. 7) Change the name of each clone to include your server serial number e.g. VINES-1234567 (these 7 digit serials numbers MUST be unique - so each server you build MUST have a unique serial number) 8) For MAC address Policy, choose Generate new MAC addresses for all network adapters. 9) Click Next 10) Choose Full clone for Clone Type and click Next. 11) Choose Current Machine State for Snapshots and click Finish. (We need the snapshot). 12) Repeat steps 6-11 for additional servers. 13) Choose the cloned VM and click Settings. 14) Click Network. Make sure that the Name field is set to your real network card or WiFi adapter on your computer. 15) Leave it as a Bridged adapter, it won't work if you change this. 16) Click OK to save your changes. 17) Start the VM. 18) Type (without the quotes) "vi serial" Type "dw" which does a Delete Word to remove the current serial number Type "i" to enable Insert Mode Type your new server serial number Press ESC to exit Insert Mode Type ":wq" which opens the command line and does a Write, Quit. 19) Type "exit" which takes you back to the server menus. 20) Type 10 and press Enter 21) Type 4 and press Enter 22) Type 3 and press Enter (reboot doesn't work in this VM for some reason) 23) Once the server is complete ready to be turned off, close the VM window, and when prompted, choose Power off the machine. If you do not execute step 23 correctly, you'll keep loading the snapshot. Start the VM and you will be going through the regular VINES server setup. Remember to setup your first VINES server as being the first server on the network. If you already have another VINES server built and running, and setup a second server, it should see the first over VINES-IP and automatically set itself as a second server. If the first server is powered down, remember to setup your subsequent servers as being second. When you get to adding a network card, add a Novell NE1000/2000 card. Leave the default configuration, which is IRQ3, Base 300. Extra notes: Once the server is fully running, you should be able to login using one of the Windows VM's that are included. The included Windows VMs are configured to use TCP/IP and not VINES-IP for communication with the VINES servers. This means that you have to make a choice. If at least 1 VINES server is on the same physical network as your Windows workstations, either boot the Windows workstation, reconfigure the VINES client/protocol to use VINES-IP since those VINES-IP packets will get to the VINES server because switches do not care about layer 3. Or, if your VINES server is on another network that is reachable via TCP/IP, you will need to configure the VINES server to support IP encapsulation (instructions in the video and text file). Remember that the very first time you login your VINES admin password is blank. This confuses Windows 95 (because it is set for common login) and so you'll be prompted to change the Windows password. Just cancel that. Then run StreetTalk Explorer, select the admin user and change its password. Also create an STDA server as soon as you can otherwise browsing will be slow. On the Windows NT4 and Windows XP VMs you will need to separately login to VINES after logging into Windows. For reference, the Windows NT4 Administrator password is: ibanyan Have fun! Any questions or comments, please email me at ibanyan@gmail.com Craig Johnston.