• Re: Migrating from SBBS to Mystic - docs?

    From g00r00@1:129/215 to Dave Vandermeer on Tue Aug 22 20:21:38 2017
    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)
  • From Nicholas Boel@1:154/10 to g00r00 on Wed Aug 23 17:21:54 2017
    Hello g00r00,

    On Tue Aug 22 2017 20:21:38, g00r00 wrote to Dave Vandermeer:

    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.

    The only thing about that is that all the information that will be transferred via AREAS.BBS (links-wise) would be what links are connected to what echomail areas.

    I am open to ideas and I would like to give bigger systems a
    conversion path at least for their echomail.

    That would be awesome, if something could actually be made to work in regards to this for newer softwares. I believe Fastecho's nodes can be exported, and FMail can read that on import.. probably because they were originally started around the same time.

    I don't think SBBS or SBBSecho can export actual link information. However, SBBSecho does save link information to a text file (ie: sbbsecho.ini), as does HPT (fidoconfig).. albeit two completely different formats.. so it would probably be a pain in the ass to make anything work with more than one software. ;(

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Chad Adams@1:130/210 to All on Sun Sep 24 13:12:27 2017
    I think import for areas.bbs would be the way to go.. my two cents

    On 15:21 22/08 , g00r00 wrote:
    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)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A35 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:130/210)