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
Next revisionBoth sides next revision
faq:misc [2019/01/09 07:07] – [FTN MSGID] by -> be wkitty42faq:misc [2019/07/25 01:46] – [Migration] Mention the fact you can migrate to a different OS. Mention the xtrn sub-dir. digital man
Line 69: Line 69:
 ([[module:sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should ([[module:sbbslist]]) door on *your* BBS and add an entry for your BBS. This entry should
 be automatically exported to the DOVE-Net SYNCDATA echo which will then be be automatically exported to the DOVE-Net SYNCDATA echo which will then be
-propagated to [[bbs:Vertrauen]] and every other BBS on DOVE-Net. The ''sbbslist.html''+propagated to [[bbs:Vertrauen]] and every other BBS on DOVE-Net. The ''[[http://synchro.net/sbbslist.html|sbbslist.html]]''
 page is automatically generated on Vertrauen every night at midnight page is automatically generated on Vertrauen every night at midnight
-(Pacific time), so wait a day or so for your entry to appear on the list.+(Pacific time), so wait a day or so for your entry to appear on the list. You can also check a dynamically generated HTML BBS list [[http://cvs.synchro.net/sbbslist.ssjs|here]] or [[http://web.synchro.net/?page=More/999-sbbslist.xjs|here]].
 If it doesn't appear, verify that that your BBS entry was properly If it doesn't appear, verify that that your BBS entry was properly
 exported (as a message) to the SYNCDATA message area. The timed events exported (as a message) to the SYNCDATA message area. The timed events
Line 98: Line 98:
  
 :!: **Answer:**\\ :!: **Answer:**\\
-You can simply copy the Synchronet directory tree (e.g. ''C:\SBBS''), complete with all sub-directories, to the new computer. +You can simply copy the Synchronet directory tree (e.g. ''C:\SBBS''), complete with all sub-directories, to the new computer, even if the new computer is running a different operating system!
  
-Synchronet doesn't **require** //installation// on a computer, but if you wish to, you can [[:install:]] Synchronet on the new computer and then simply over-write the installed files with your migrated files.+Synchronet doesn't **require** //installation// on a computer, but if you wish to, you can [[:install:]] Synchronet on the new computer and then simply over-write the newly-installed files with your old/migrated files.
  
 If the target (new) computer is running Windows and you choose not to install, then you may want to create a shortcut to ''sbbsctrl.exe'' in your Windows ''Startup'' folder (so it will automatically run when you login) and/or install the [[:monitor:ntsvcs|Synchronet NT Services]] (which can run without logging-in as a user). If the target computer is running Windows //Vista// or later, then you'll also want to follow the solution to this [[:faq:win#sbbsexecdll|FAQ]] as well. For 16-bit DOS program support, the Synchronet Windows NT FOSSIL driver (''sbbsexec.dll'') must also be copied to the Windows ''System32'' folder. See [[/faq:win#sbbsexecdll|the sbbsexec.dll FAQ]] for details. If the target (new) computer is running Windows and you choose not to install, then you may want to create a shortcut to ''sbbsctrl.exe'' in your Windows ''Startup'' folder (so it will automatically run when you login) and/or install the [[:monitor:ntsvcs|Synchronet NT Services]] (which can run without logging-in as a user). If the target computer is running Windows //Vista// or later, then you'll also want to follow the solution to this [[:faq:win#sbbsexecdll|FAQ]] as well. For 16-bit DOS program support, the Synchronet Windows NT FOSSIL driver (''sbbsexec.dll'') must also be copied to the Windows ''System32'' folder. See [[/faq:win#sbbsexecdll|the sbbsexec.dll FAQ]] for details.
Line 118: Line 118:
 If you customized any of your executable modules (e.g. ''*.js''), you'll also want copy the following directory: If you customized any of your executable modules (e.g. ''*.js''), you'll also want copy the following directory:
   * ''[[dir:mods]]''   * ''[[dir:mods]]''
 +
 +If you installed any new doors in the ''xtrn'' directory or your users used any of the stock-installed doors and you'd like to retain that data, you'll also want to copy the following directory:
 +
 +  * ''[[dir:xtrn]]''
    
 **Note:** Sysop-installed (e.g. not from [[:dev:CVS]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well. **Note:** Sysop-installed (e.g. not from [[:dev:CVS]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well.

Trace: