Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini. This script can
be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g.
jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
The objective is to retain all your settings (though some of them are going away, e.g. store_seenby, store_path, store_kludge, as these are just going be mandatory in future versions) but any comments you may have added by hand in your sbbsecho.cfg, unfortunately, won't be retained.
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made via areafix won't be so damaging to any manual changes you've made.
I hope you find the new config file easier to read and manage. I've tried to retain as many key-words as the old sbbsecho.cfg, so it should feel familiar. Feedback is welcome.
rswindell wrote to CVS commit <=-
exec sbbsecho_upgrade.js NONE 1.1
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv23422
Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and
the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini.
This script can be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec
sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g. jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
The objective is to retain all your settings (though some of them are going away, e.g. store_seenby, store_path, store_kludge, as these are
just going be mandatory in future versions) but any comments you may
have added by hand in your sbbsecho.cfg, unfortunately, won't be
retained.
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made
via areafix won't be so damaging to any manual changes you've made.
I hope you find the new config file easier to read and manage. I've
tried to retain as many key-words as the old sbbsecho.cfg, so it should feel familiar. Feedback is welcome.
exec sbbsecho_upgrade.js NONE 1.1
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv23422
Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and
the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini.
This script can be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec
sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g. jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made
via areafix won't be so damaging to any manual changes you've made.
I hope you find the new config file easier to read and manage. I've
tried to retain as many key-words as the old sbbsecho.cfg, so it
should feel familiar. Feedback is welcome.
One question though, In the soon to be old cfg, I have NOCIRCULARFWD, which I thought meant if sbbsecho sees a circular path, it won't
forward it. In the newer version I see fwd_circular = true. Does
this need to be false as to not fwd circular messages?
Re: exec/sbbsecho_upgrade.js
By: rswindell to CVS commit on Sun Jan 17 2016 01:39:27
Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini. This script can
be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g. jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
The objective is to retain all your settings (though some of them are going away, e.g. store_seenby, store_path, store_kludge, as these are just going be mandatory in future versions) but any comments you may have added by hand in your sbbsecho.cfg, unfortunately, won't be retained.
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made via areafix won't be so damaging to any manual changes you've made.
I hope you find the new config file easier to read and manage. I've tried to retain as many key-words as the old sbbsecho.cfg, so it should feel familiar. Feedback is welcome.
Got this after I ran it the first time on my test system.
C:\sbbs\exec>jsexec sbbsecho_upgrade.js
JSexec v3.16c-Win32 (rev 1.169) - Execute Synchronet JavaScript Module Compiled Aug 14 2015 22:34:48 with MSC 1800
Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 8388608 bytes
JavaScript: Initializing context (stack: 16384 bytes)
Reading script from C:\sbbs\exec\sbbsecho_upgrade.js C:\sbbs\exec\sbbsecho_upgrade.js compiled in 0.00 seconds
!Unrecognized cfg line: SEND_NOTIFY 1:249/303.1 1:249/134 1:249/179 1:249/202 1:
249/203 1:249/204 1:249/205 1:249/206 1:249/304 1:229/308 1:229/426 1:3828/7 2:2
03/0 2:280/464
!JavaScript C:\sbbs\exec\sbbsecho_upgrade.js line 183: TypeError: hub is undefi
ned
C:\sbbs\exec\sbbsecho_upgrade.js executed in 0.04 seconds
rswindell wrote to CVS commit <=-
exec sbbsecho_upgrade.js NONE 1.1
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv23422
Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini. This script can be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g. jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
The objective is to retain all your settings (though some of them are going away, e.g. store_seenby, store_path, store_kludge, as these are just going be mandatory in future versions) but any comments you may have added by hand in your sbbsecho.cfg, unfortunately, won't be retained.
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made via areafix won't be so damaging to any manual changes you've made.
I hope you find the new config file easier to read and manage. I've tried to retain as many key-words as the old sbbsecho.cfg, so it should feel familiar. Feedback is welcome.
Done and converted like a charm. I like the new layout, especially the nodes section.
One question though, In the soon to be old cfg, I have NOCIRCULARFWD, which I thought meant if sbbsecho sees a circular path, it won't forward it. In the newer version I see fwd_circular = true. Does this need to be false as to not fwd circular messages?
Hello rswindell,
On 17 Jan 16 01:39, rswindell wrote to CVS commit:
exec sbbsecho_upgrade.js NONE 1.1
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv23422
Added Files:
sbbsecho_upgrade.js
Log Message:
I'm working on a major SBBSecho overhaul (to be dubbed version 3) and the old sbbsecho.cfg file is going to be replaced with sbbsecho.ini. This script can be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with a different filename) to an sbbsecho.ini (or other filename if desired). Either just run "jsexec sbbsecho_upgrade.js" or you can pass the cfg filename and the ini filenames on the command-line (e.g. jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
As far as I can tell, it looks like it converted perfectly. It cleared out the store_seenby, store_path, and store_kludge lines I had in sbbsecho.cfg (which seems is intended now) and kept all my other settings in tact.
I like the fact that all the links are separated with all their information stored with them, instead of having to enter the node number 3-4 times as we have to do now. Looking good!
If you would still like to see the end result, let me know and I'll email it to
you. Otherwise, I can't see anything out of the ordinary.
On the bright side, the sbbsecho.ini *will* retain your comments when edited with the future version of echocfg and the modifications made via areafix won't be so damaging to any manual changes you've made.
Is that what would happen? I've noticed at times my sbbsecho.cfg (which I used to edit completely manual, so that everything was in correct orders and such) would be completely rearranged and would have to re-do it all. Ever since I went to using echocfg it hasn't been rearranged, but things remain out of order.
By out of order, I just mean like there would be 10 listings of zone one stuff,
10 listings of zone 46 stuff, then go back to some other zone 1 links, etc. It wouldn't stay ordered 1: through the highest zone number I have.. No biggie, just my own visual thing. As long as it's parsed correctly I try not to look at
sbbsecho.cfg as much anymore. :)
I hope you find the new config file easier to read and manage. I've tried to retain as many key-words as the old sbbsecho.cfg, so it
should feel familiar. Feedback is welcome.
Hell yes. Having each link's config all in one section is great. I like the way
it looks so far!
Digital Man wrote to Bill McGarrity <=-
Done and converted like a charm. I like the new layout, especially the nodes section.
One question though, In the soon to be old cfg, I have NOCIRCULARFWD, which I thought meant if sbbsecho sees a circular path, it won't forward it. In the newer version I see fwd_circular = true. Does this need to be false as to not fwd circular messages?
Yes, that was a bug in the conversion. Thanks!
Nicholas Boel wrote to Bill McGarrity <=-
On 17 Jan 16 11:13, Bill McGarrity wrote to rswindell:
One question though, In the soon to be old cfg, I have NOCIRCULARFWD, which I thought meant if sbbsecho sees a circular path, it won't
forward it. In the newer version I see fwd_circular = true. Does
this need to be false as to not fwd circular messages?
Ah, good catch Bill! I have this same thing as well. Maybe it's
supposed to be "no_fwd_circular = true", otherwise it would be a
complete reversal of the true/false. *shrug*
Okay, thanks, that's good feedback.
Fix bugs reported in first runs of this script by SBBSecho sysops.
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me
Re: exec/sbbsecho_upgrade.js
By: rswindell to CVS commit on Sun Jan 17 2016 01:39 am
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me
Sending your way -- I like the format a lot more than the .cfg file. One pet peeve of mine has been not being able to sort the nodes list, I'm hoping that sorting the .ini file entries would sort the display in sbbsecho v3?
rswindell wrote to CVS commit <=-
@TZ: 41e0
exec sbbsecho_upgrade.js NONE 1.1
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv23422
Added Files:
sbbsecho_upgrade.js
Log Message:
Before I commit v3, I wanted to have some SBBSecho sysops give this converter a test run. The sbbsecho.ini file won't be used by anything today, I just want you to examine the resulting file or send it to me (with redacted pwds if you like).
exec sbbsecho_upgrade.js 1.6 1.7
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv15308
Modified Files:
sbbsecho_upgrade.js
Log Message:
Updated to reflect my latest decisions on key names in sbbsecho.ini: VerboseAndCamelCase instead of terse_c_style names.
Hello rswindell,
On 25 Feb 16 00:52, rswindell wrote to CVS commit:
exec sbbsecho_upgrade.js 1.6 1.7
Update of /cvsroot/sbbs/exec
In directory cvs:/tmp/cvs-serv15308
Modified Files:
sbbsecho_upgrade.js
Log Message:
Updated to reflect my latest decisions on key names in sbbsecho.ini: VerboseAndCamelCase instead of terse_c_style names.
While you're revamping sbbsecho, I was thinking about a possible feature request.
While I understand I'm able to read netmail/email with Golded+ by linking to /ctrl/mail.shd, could it be possible to be able to write to that base using external editors as well?
Maybe I should rephrase that. Like JAM message areas, there is a separate area/sub-board for NETMAIL that can be accessed, read, and posted to. Linking to mail.cnf seems to have every single piece of internet mail as well as netmail to any and all users all mixed into one, all readable by me.
If everything for everyone goes through that one section, and won't be changed in that regard, can we have the option to setup a personal netmail sub-board to use like JAM software can do?
Even having the versatility of linking multiple node numbers to that netmail area/sub-board would be nice, so you only have to have one netmail area/sub-board for any/all networks, but also with the ability to setup multiple for separating networks' netmail as well..
I guess I'd basically like to be able to separate Fido-style netmail from the rest of the internet mail, and be able to post to it externally (via smbutil) or even access it via an external program like Golded.
Kinda winged it there on describing it.. but I hope that's enough for you to understand where I'm going with that. lol If not, ask away and I'll answer as best I can.
While you're revamping sbbsecho, I was thinking about a possible
feature request.
While I understand I'm able to read netmail/email with Golded+ by
linking to /ctrl/mail.shd, could it be possible to be able to write
to that base using external editors as well?
You alrady can. There's nothing in Synchronet (or SBBSecho) prenting
an SMB-aware message editor from writing messages to the mail base. smbutil can be used for this purpose even.
Maybe I should rephrase that. Like JAM message areas, there is a
separate area/sub-board for NETMAIL that can be accessed, read, and
posted to. Linking to mail.cnf seems to have every single piece of
internet mail as well as netmail to any and all users all mixed
into one, all readable by me.
If GoldEd+ is displaying all messages to you, that's a
feature/function of GoldEd+ and has nothing to do with SBBSecho or Synchronet.
If everything for everyone goes through that one section, and won't
be changed in that regard, can we have the option to setup a
personal netmail sub-board to use like JAM software can do?
Synchronet already does that. If you read the mail base using a Synchronet-supported method (not GoldEd+) you'll normally only see
*your* messages. What you're describing just sounds like a bug (or a feature, depending on how you look at it) of GoldEd+.
I have no plans to decouple different *types* of personal mail into separate message bases. All the personal mail goes in the mail base. That's the Synchronet design. And it really has nothing to do with SBBSecho.
I have no plans to decouple different *types* of personal mail into separate message bases. All the personal mail goes in the mail base. That's the Synchronet design. And it really has nothing to do with SBBSecho.
Ok. Thanks.
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.
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)?
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.
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.
going to (just download the sbbs_dev.zip), the bat file was if you want to add it the cvs, to help out other sbbs sysop
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.
going to (just download the sbbs_dev.zip), the bat file was if you want to add it the cvs, to help out other sbbs sysop
I'm not sure why a bat file would be needed. You want to just paste it here?
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.
going to (just download the sbbs_dev.zip), the bat file was if you want to add it the cvs, to help out other sbbs sysop
I'm not sure why a bat file would be needed. You want to just paste it here?
ok, here it is (I called it sbbsecho.bat and I keep in in the \sbbs\exec dir.) :
@echo off
d: <- replace with your drive letter
cd \Sbbs\ctrl
del sbbsecho.ini
cd \sbbs\exec
jsexec sbbsecho_upgrade.js
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.
going to (just download the sbbs_dev.zip), the bat file was if you want to add it the cvs, to help out other sbbs sysop
I'm not sure why a bat file would be needed. You want to just paste it here?
ok, here it is (I called it sbbsecho.bat and I keep in in the \sbbs\exec dir.) :
@echo off
d: <- replace with your drive letter
cd \Sbbs\ctrl
del sbbsecho.ini
cd \sbbs\exec
jsexec sbbsecho_upgrade.js
sbbsecho_upgrade.js will overwrite (replace) your ctrl/sbbsecho.ini file if it exists,
so the file deletion is unnecessary. So the value of the batch
file seems questionable to me. If it helps other sysops, then there it is. :-) They can just copy and paste it into a file and run it.
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 14:24:45 |
| Calls: | 508 |
| Messages: | 219974 |