If installing or upgrading-to Synchronet v3.16 (in development as of October 20, 2011), you will need to download and install the Microsoft Visual C++ 2010 Redistributable Package (x86) which contains the required file:
MSVCR100.DLL (Microsoft Visual C++ Run-time Library v10.0).
After downloading the Synchronet distribution file (e.g.
ftp://synchro.net/Synchronet/sbbs316c.zip), you will need to extract the archive file that you downloaded into a temporary directory on your hard drive. You may need WinZip or an equivalent archive program to uncompress and extract the installation files.
Once you've extracted the installation files, go to the directory you extracted the compressed files to and run
SETUP to start the installation.
The default installation directory is recommended for most users. If you choose to change the installation directory, it is critical that you DO NOT use a path with long filenames or spaces or some 16-bit DOS utilities which require DOS-compatible 8.3 file and directory names will not function. It is recommended you use a directory named “SBBS” off of the root directory on one of your hard drives (e.g.
After completing your selection and the installation is completed you will find a new Icon on your Desktop and in your StartUp Folder in your Start Menu. If you do not want Synchronet to start automatically during boot, you may safely delete the Synchronet shortcut from your StartUp Folder.
The Synchronet Control Panel and Configuration Wizard will automatically launch after installation.
On NT-based operating systems (e.g. Windows 2000, XP, 2003, Vista, 2008, and Windows 7), you can alternatively run Synchronet in the background as a set of Windows Services (a.k.a. NT services). See the Synchronet Windows Services page for details.
Note: This process worked for me on the Split Infinity BBS. PLEASE make sure you backup your existing system and keep it safe as the same process may not work for you. If you have an existing 3.16c system running on Windows, you can do the following to do an in-place upgrade to the latest dev build (Currently V3.17). Remember, 3.17 is still in development, at this writing, and should not be used on a production system. This is a manual procedure that results in an upgraded system without overwriting existing configurations.
jsexec update.jsfrom a command prompt after updating the files in your
NOTE: sbbsecho commandline options have changed. You'll need to change them to match in your timed events (FIDOIN and FIDOOUT as well as any batchfile you may have written.