Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
install:dev [2020/10/28 22:06] – [Run-time files] Add yet another note that the CVS repo is not being updated digital maninstall:dev [2024/09/23 11:25] (current) – [Run-time files] When upgrading a symlink installed, you still need the new files symlinked. deuce
Line 9: Line 9:
  
 :!: **Note**:\\ :!: **Note**:\\
-As of February 17th, 2018, Synchronet for Win32 now uses Cryptlib v3.4.4 which requires ''VCRUNTIME140.dll''. You can download the required Microsoft Visual C++ 2015 Redistributable Package (x86) [[https://www.microsoft.com/en-us/download/details.aspx?id=52685|here]].+As of February 17th, 2018, Synchronet for Win32 now uses Cryptlib v3.4.4 which requires ''VCRUNTIME140.dll''. You can download the required Microsoft Visual C++ 2015 Redistributable Package **for x86** (''vc_redist.x86.exe'') [[https://www.microsoft.com/en-us/download/details.aspx?id=52685|here]].
 ===== Step 1 ===== ===== Step 1 =====
 ==== Shutdown the BBS ==== ==== Shutdown the BBS ====
Line 38: Line 38:
 If you are using pre-built executables (from Windows-installer or archive): If you are using pre-built executables (from Windows-installer or archive):
  
-  - Download the daily built and archived executable files for [[ftp://ftp.synchro.net/sbbs_dev.zip|Win32]] or [[ftp://ftp.synchro.net/sbbs_dev.tgz|Linux-x64]] ((sorry, pre-built archives for other platforms are not currently available)+  - Download archived executable files (see table below
-  - Extract the ''sbbs_dev'' archive into your Synchronet ''[[dir:exec]]'' directory, over-writing existing files+  - Extract the archive into your Synchronet ''[[dir:exec]]'' directory, stripping any sub-directory information and over-writing existing files in the process
   - Continue with [[#step 4]] section of this page   - Continue with [[#step 4]] section of this page
 +
 +^ Platform      ^ Nightly Build ^ Continuous Build ^
 +| Windows-i386  | ''sbbs_dev.zip'' [[https://vert.synchro.net/Synchronet/sbbs_dev.zip|https]] [[http://vert.synchro.net/Synchronet/sbbs_dev.zip|http]] [[ftp://ftp.synchro.net/sbbs_dev.zip|ftp]] | [[https://gitlab.synchro.net/sbbs/sbbs/-/jobs/artifacts/master/download?job=windows-x86 [sbbs]|https]] |
 +| Linux-x64     | ''sbbs_dev.tgz'' [[https://vert.synchro.net/Synchronet/sbbs_dev.tgz|https]] [[http://vert.synchro.net/Synchronet/sbbs_dev.tgz|http]] [[ftp://ftp.synchro.net/sbbs_dev.tgz|ftp]] | [[https://gitlab.synchro.net/sbbs/sbbs/-/jobs/artifacts/master/download?job=linux-x64 [sbbs]|https]] |
 +| FreeBSD-amd64 | N/A | [[https://gitlab.synchro.net/sbbs/sbbs/-/jobs/artifacts/master/download?job=freebsd-amd64 [sbbs]|https]] |
 +
  
 Now that your "program files" (executable binaries) are updated, you need to update the run-time files next. Now that your "program files" (executable binaries) are updated, you need to update the run-time files next.
Line 47: Line 53:
 ==== Run-time files ==== ==== Run-time files ====
  
-**Note**:\\ +=== Git Method ===
-The ''sbbs_run'' archive file (''.tgz'' for *nix, ''.zip'' for Windows) contains a super-set of the files contained within the archive files referenced below. If you've already downloaded the ''sbbs_run'' archive, then you already have all the necessary files (plus a lot more) and do not need to download the smaller archives referenced below.+
  
   - If you performed a [[dev:CVS]] install (e.g. on *nix), see [[howto:Git]] for instructions on updating to the Git repo((The Synchronet CVS Repository is no longer updated)).   - If you performed a [[dev:CVS]] install (e.g. on *nix), see [[howto:Git]] for instructions on updating to the Git repo((The Synchronet CVS Repository is no longer updated)).
-  - If you performed a [[dev:Git]] install (e.g. on *nix) and you opted for symbolic links to the ''[[dir:exec]]'' and ''[[dir:text]]'' directories, the only file you might need to manually update or merge would be the ''[[dir:ctrl]]/[[custom:text.dat]]'' file. All the other files should be automatically updated with your ''git pull'' commandyou should be able to skip to the final step (''jsexec update''). +  - If you performed a [[dev:Git]] install (e.g. on *nix) and you opted for symbolic links to the ''[[dir:exec]]'' and ''[[dir:text]]'' directories, the only file you might need to manually update or merge would be the ''[[dir:ctrl]]/[[custom:text.dat]]'' file and creating any new symlinks to new files in execOther existing files should be automatically updated with your ''git pull'' command
-  - If you did **not** perform a CVS or Git install, download the daily archive of the ''[[dir:exec]]'' directory and extract into your Synchronet ''exec'' directory, over-writing existing files: [[ftp://ftp.synchro.net/sbbsexec.zip|Windows]] or [[ftp://ftp.synchro.net/sbbsexec.tgz|*nix]] format. +  - If you performed a [[dev:Git]] install (e.g. on *nix) and you did **not** opt for symbolic links, you will need to recursively copy the ''repo/exec'' and ''repo/text'' directories to your ''sbbs/[[dir:exec]]'' and ''sbbs/[[dir:text]]'' directories. 
-  - Over-write or merge-with your modified ''[[dir:ctrl]]/[[custom:text.dat]]'' file from [[https://gitlab.com/synchronet/sbbs/-/raw/master/ctrl/text.dat|here]] (if you see some corrupted text output from the terminal server or some features don't work as expected, skipping this step could be the cause+  - Over-write or merge-with your modified ''[[dir:ctrl]]/[[custom:text.dat]]'' file from [[https://gitlab.com/synchronet/sbbs/-/raw/master/ctrl/text.dat|here]]. If you see some corrupted text output from the terminal server or some features don't work as expected, skipping this step could be the cause. If you don't have have or expect to make any edits to your ''text.dat'' file, consider just using a 0-byte ''text.dat'' file to always [[custom:text.dat#use defaults]]. 
-  Download the daily archive of the ''[[dir:text]]'' directory: [[ftp://ftp.synchro.net/sbbstext.zip|Windows]] or [[ftp://ftp.synchro.net/sbbstext.tgz|*nix]] format+ 
 + 
 +=== Non-Git Method === 
 + 
 +**Note**:\\ 
 +The ''sbbs_run'' archive file (''[[https://vert.synchro.net/Synchronet/sbbs_run.tgz|sbbs_run.tgz]]'' for *nix, ''[[https://vert.synchro.net/Synchronet/sbbs_run.zip|sbbs_run.zip]]'' for Windowscontains a super-set of the files contained within the archive files referenced belowIf you've already downloaded the ''sbbs_run'' archive, then you already have all the necessary files (plus a lot more) and do not need to download the smaller archives referenced below. 
 + 
 +  - If you did **not** perform a CVS or Git install, download the daily archive of the ''[[dir:exec]]'' directory and extract into your Synchronet ''exec'' directory, over-writing existing files: [[https://vert.synchro.net/Synchronet/sbbsexec.zip|Windows]] or [[https://vert.synchro.net/Synchronet/sbbsexec.tgz|*nix]] format. 
 +  - Download the daily archive of the ''[[dir:text]]'' directory: [[https://vert.synchro.net/Synchronet/sbbstext.zip|Windows]] or [[https://vert.synchro.net/Synchronet/sbbstext.tgz|*nix]] format 
 +  - Over-write or merge-with your modified ''[[dir:ctrl]]/[[custom:text.dat]]'' file from [[https://gitlab.com/synchronet/sbbs/-/raw/master/ctrl/text.dat|here]]. If you see some corrupted text output from the terminal server or some features don't work as expected, skipping this step could be the cause. If you don't have have or expect to make any edits to your ''text.dat'' file, consider just using a 0-byte ''text.dat'' file to always [[custom:text.dat#use defaults]].
   - If you have **no** customized files in your ''[[dir:text]]'' directory, extract the ''sbbstext'' archive into your Synchronet ''text'' directory, over-writing existing files   - If you have **no** customized files in your ''[[dir:text]]'' directory, extract the ''sbbstext'' archive into your Synchronet ''text'' directory, over-writing existing files
   - If you **do** have customized files in your ''[[dir:text]]'' directory, extract the ''sbbstext'' archive into a temporary location and compare files and merge or replace as you see fit. Of particular interest should be the new ''[[module:avatars]]'' sub-directory. Definitely copy that one!   - If you **do** have customized files in your ''[[dir:text]]'' directory, extract the ''sbbstext'' archive into a temporary location and compare files and merge or replace as you see fit. Of particular interest should be the new ''[[module:avatars]]'' sub-directory. Definitely copy that one!
 +
 +=== Final Step (Git or non-git) === 
 +
   - From a command prompt (e.g. in your Synchronet ''exec'' directory), run: ''jsexec update''   - From a command prompt (e.g. in your Synchronet ''exec'' directory), run: ''jsexec update''
 +
 +**NOTE:**\\
 +The following //one-time// error message displayed by ''jsexec'' **when upgrading from Synchronet versions prior to v3.20** is expected and should be ignored:
 +  !ERROR loading configuration files: 2 (No such file or directory) opening /sbbs/ctrl/msgs.ini
 +... because later in the upgrade process, the ''msgs.ini''(and other) missing configuration files will be created (converted from ''*.cnf''):
 +  Upgrading Synchronet v3.1x config files to v3.20
 +  main.cnf -> main.ini
 +  ../node1\node.cnf -> node.ini
 +  ../node2\node.cnf -> node.ini
 +  ../node3\node.cnf -> node.ini
 +  ../node4\node.cnf -> node.ini
 +  msgs.cnf -> msgs.ini
  
 Now you are ready to re-run the BBS and enjoy the "latest and greatest"! Now you are ready to re-run the BBS and enjoy the "latest and greatest"!