Subj : Re: exec/sbbsecho_upgrade To : Lord Time From : Digital Man Date : Mon Apr 18 2016 12:00:00 Re: Re: exec/sbbsecho_upgrade.js By: Lord Time to rswindell on Tue Apr 12 2016 10:26 pm > > exec sbbsecho_upgrade.js 1.7 1.8 > > Update of /cvsroot/sbbs/exec > > In directory cvs:/tmp/cvs-serv5083 > > > Modified Files: > > sbbsecho_upgrade.js > > Log Message: > > After converting sbbsecho.cfg to sbbsecho.ini, rename sbbsecho.cfg to > > sbbsecho.cfg.old to avoid confusion and make sure any other > > software/scripts that might use sbbsecho.cfg are now directed not to (and > > hopefully use sbbsecho.ini instead). > > DO NOT RUN THIS SCRIPT until you are ready to upgrade to SBBSecho v3 > > (which is not yet in CVS). > > If you upgrade to SBBSecho v3 without running this script, you won't have > > any of your previous settings (you can run the script after running > > SBBSecho v3). If you run the script witOUT upgrading to SBBSecho v3, > > you'll lose your settings, but you can just rename sbbecho.cfg.old to > > sbbsecho.cfg to get them back. > > Good Warning. > > Now about a month or two back, I made a bat file for running > sbbsecho_upgrade.js (after I added a new node number to sbbsecho and made > sure that there was no problems when the new node I ran the > jsexec sbbsecho_upgrade.js, if you want me to send it over, let me know (it > delete the old sbbsecho.ini and then make a new one)? If you ran sbbsecho_upgrade.js before (using a revision before 1.9), you should run it again. Some of the .ini section and key names have changed. digital man Synchronet "Real Fact" #49: JAM and Squish were considered before developing Synchronet Message Base format Norco, CA WX: 57.1øF, 78.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .