• New Alpha

    From Crew@21:1/103 to G00r00 on Fri Feb 1 02:24:45 2019

    Just installed the new Mystic Pre-alpha 30/01/2019 and have noticed when I log on via Netrunner SSH I am getting booted off when I do a new file scan for
    all.

    It appears this only happens with a SSH connection and not with a telnet connection, I have tested both ways.

    In my node1.log I can see this message
    Flush error Timeout Timeout during flush, no data could be written before
    the timeout of 0 seconds expired.

    I rolled back to the previous Mystic alpha and could logon via SSH (Netrunner) and do the file search no probs.

    I hope this is of help, let me know if you need anymore information.

    Many thanks in advance
    Lloyd

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: - Micro Link BBS - QLD, OZ (21:1/103)
  • From g00r00@21:1/108 to Crew on Thu Jan 31 12:12:33 2019
    It appears this only happens with a SSH connection and not with a telnet connection, I have tested both ways.

    In my node1.log I can see this message
    Flush error Timeout Timeout during flush, no data could be written before the timeout of 0 seconds expired.

    Thank you for the detailed report, the error message tells me exactly what it is. I believe I have fixed this now and I will try to make a new build soon. I want to wait to hear back about the TIC CRC issue before I make another build.

    --- Mystic BBS v1.12 A42 2019/01/25 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From dream master@21:1/163 to Crew on Tue Jun 25 15:56:19 2019
    On 31 Jan 2019, Crew said the following...
    Just installed the new Mystic Pre-alpha 30/01/2019 and have noticed when
    I log on via Netrunner SSH I am getting booted off when I do a new file scan for all.

    thats an old alpha as the current one is 2019/03/03 A43 and make sure you follow the upgrade instructions.

    |08 .|05·|13∙|15Dr|07e|08am Ma|07st|15er|13∙|05·|08.
    |08 °∙|05·|13∙° |13°∙|05·|08∙°
    |11 DoRE|03!|11ACiDiC|03!|11Demonic
    |08[|15bbs|09.|15dreamlandbbs|09.|15org|08]

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From Netsurge@21:4/154 to All on Mon Apr 13 21:22:14 2020
    g00r00 released a new alpha today which addresses the following:

    QWK Networking: Gating between QWK and FTN Networks
    FPT Server: Addressed a bug that Digital Man spotted.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From Accession@21:1/200 to Netsurge on Mon Apr 13 21:34:53 2020
    On 13 Apr 2020, Netsurge said the following...

    g00r00 released a new alpha today which addresses the following:

    QWK Networking: Gating between QWK and FTN Networks
    FPT Server: Addressed a bug that Digital Man spotted.

    I believe another attempt to fix the 255 line issue being reported was also
    in there. I don't think I've noticed it from myself directly, but I've seen some posts where I wondered where the rest of the paragraph went. ;)

    Accession

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From ryan@21:1/168 to Accession on Mon Apr 13 19:52:36 2020
    I believe another attempt to fix the 255 line issue being reported was also in there. I don't think I've noticed it from myself directly, but I've seen some posts where I wondered where the rest of the paragraph went. ;)

    Well, sir, I think you've noticed it! hehe. :)

    --- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Avon@21:1/101 to Accession on Tue Apr 14 23:59:01 2020
    On 13 Apr 2020 at 05:34p, Accession pondered and said...

    I believe another attempt to fix the 255 line issue being reported was also in there. I don't think I've noticed it from myself directly, but I've seen some posts where I wondered where the rest of the paragraph went. ;)

    That would be most welcome, I have updated the NET 1 HUB to see if the fixes work. Let me know if you spot anything.

    --- Mystic BBS v1.12 A46 2020/04/13 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Netsurge on Tue Apr 14 23:59:30 2020
    On 13 Apr 2020 at 05:22p, Netsurge pondered and said...

    QWK Networking: Gating between QWK and FTN Networks

    How do we set that up?

    --- Mystic BBS v1.12 A46 2020/04/13 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Accession@21:1/200 to ryan on Tue Apr 14 20:59:50 2020
    On 13 Apr 2020, ryan said the following...

    I believe another attempt to fix the 255 line issue being reported wa also in there. I don't think I've noticed it from myself directly, bu I've seen some posts where I wondered where the rest of the paragraph went. ;)

    Well, sir, I think you've noticed it! hehe. :)

    Right. I've only noticed it from other systems. I never noticed it coming
    from my system, well, because I probably haven't written 255 characters straight in quite some time. ;)

    Accession

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From Netsurge@21:4/154 to Avon on Wed Apr 15 00:34:04 2020
    How do we set that up?

    Just enable a qwk hub for an message area. You also need to crate accounts
    for each qwk node and make sure that that account is set for qwk networking.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From Jeff Smith@21:1/128 to Netsurge on Thu Apr 16 02:19:56 2020

    Hello Netsurge!

    14 Apr 20 20:34, you wrote to Avon:

    How do we set that up?

    Just enable a qwk hub for an message area. You also need to crate
    accounts for each qwk node and make sure that that account is set for
    qwk networking.

    In setting up say Dovenet as a QWK network in Mystic. Does one need to concern oneself with network type? Or just worry about any QWK related settings?

    That suggests another question. Is there a way to import a QWK message are list into Mystic that may have numerous message areas?


    Jeff


    --- Mystic v1.12 A46 (2020/04/11) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (21:1/128)
  • From Vk3jed@21:1/109 to Jeff Smith on Tue Apr 21 20:36:00 2020
    On 04-15-20 22:19, Jeff Smith wrote to Netsurge <=-

    In setting up say Dovenet as a QWK network in Mystic. Does one need to concern oneself with network type? Or just worry about any QWK related settings?

    I have my QWK areas (I setup DOVE as a learning exercise) set as Echomail, but since there's no FTN, I've left the AKA as 0:0/0 (local)

    That suggests another question. Is there a way to import a QWK message
    are list into Mystic that may have numerous message areas?

    I kinda cheated. I used Synchronet to export a .NA file, then imported that into Mystic with mutil. I had to make some minor fixes and add the QWK networking information for each area.

    The ideal solution (which DM informs me Synchronet can do) is to be able to import selected areas from CONTROL.DAT from a QWK packet.


    ... OUT TO LUNCH - If not back at five, OUT TO DINNER!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)