Sneaky wrote to Bill McGarrity <=-
Hello everybody!
OK... been running it for about 2 hours now... and all seems good.
Okay cool were do we get a copy of this sbbsecho.exe ver 300
so if I backup sbbs\exec directory first I should be safe, just
incase same thing goes wrong.
is there any thing I sould now about the binkd/flo in sbbsecho.cfg or should things just work as normal
Digital Man wrote to Bill McGarrity <=-
Sysops should not need to run sbbsecho_upgrade.js multiple times. The
only exception is if there was a problem in the conversion from sbbsecho.cfg -> sbbsecho.ini and you know that problem was fixed in a newer version of the upgrade script. In that case, you can either fix
the problem by hand (e.g. the missing "route" values) or rename sbbsecho.cfg.old to sbbsecho.cfg and re-run the script. But note: if
you re-run the upgrade script, any changes made to your sbbsecho.ini
(by hand or using echocfg v3) will be lost.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 04:44:24 |
Calls: | 500,302 |
Calls today: | 3 |
Files: | 95,203 |
D/L today: |
265 files (23,226K bytes) |
Messages: | 465,334 |