Doing nodes however is going to be a manual task as SBBSEcho uses a text configuration and Mystic has it's own built-in system, unless James
writes a SBBS->Mystic conversion program
This might be something that can happen. Are you talking about
importing echomail node setups from a SBBSecho file?
I know there have been one or two other requests for something like
this, which makes it more reason to do it. :)
Or maybe the AREAS.BBS importer can be updated to do it or something.
I am open to ideas and I would like to give bigger systems a
conversion path at least for their echomail.
Doing nodes however is going to be a manual task as SBBSEcho uses a text configuration and Mystic has it's own built-in system, unless James writes a SBBS->Mystic conversion program
This might be something that can happen. Are you talking about importing >echomail node setups from a SBBSecho file?
I know there have been one or two other requests for something like this, >which makes it more reason to do it. :)
Or maybe the AREAS.BBS importer can be updated to do it or something.
I am open to ideas and I would like to give bigger systems a conversion path >at least for their echomail.
--- Mystic BBS v1.12 A35 (Windows/32)
# Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
* Origin: Region 15 HQ (1:15/0)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,049 |
Nodes: | 15 (0 / 15) |
Uptime: | 83:26:15 |
Calls: | 235,751 |
Calls today: | 1 |
Files: | 60,336 |
D/L today: |
33 files (763K bytes) |
Messages: | 20,616,130,317 |