• Mystic BBS v1.12 A44 Released

    From g00r00@21:1/108 to All on Tue Feb 4 23:28:54 2020
    Mystic BBS v1.12 A44 has been released!

    You can download it at www.mysticbbs.com

    This version has a completely revamped theme system, and many stability
    changes and bug fixes, along with some other minor features.

    Supported platforms are:

    INTEL:
    Windows 32-bit
    Windows 64-bit
    Linux 32-bit
    Linux 64-bit
    macOS 32-bit
    macOS 64-bit

    ARM:
    Linux 32-bit (All Raspbery Pi models and similar)

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Wed Feb 5 20:12:23 2020
    On 04 Feb 2020 at 11:28p, g00r00 pondered and said...

    Mystic BBS v1.12 A44 has been released!

    Congrats and thanks for releasing this version :)


    You can download it at www.mysticbbs.com

    I will hatch all copies out now to FSX_MYS file echo also.

    Best, Paul.

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Wed Feb 5 11:48:58 2020
    You can download it at www.mysticbbs.com

    I will hatch all copies out now to FSX_MYS file echo also.

    Thanks. Hopefully it will be a smooth release. I don't think many people
    were using the later builds of the prealphas.

    I am excited to get to A45 if this goes smoothly.

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Zip@21:1/202 to g00r00 on Wed Feb 5 20:31:02 2020
    Hello g00r00!

    On 04 Feb 2020, g00r00 said the following...
    Mystic BBS v1.12 A44 has been released!

    Thanks a lot! Will try it out right away! :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A44 2020/01/27 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Avon@21:1/101 to g00r00 on Thu Feb 6 09:49:55 2020
    On 05 Feb 2020 at 11:48a, g00r00 pondered and said...

    Thanks. Hopefully it will be a smooth release. I don't think many
    people were using the later builds of the prealphas.

    Biggest issue I see so far will be understanding where MPLC went :)

    I am excited to get to A45 if this goes smoothly.

    Same here. I've been updating the wiki and have just started testing rescans and dupe checking using 1/995... currently pulling down 36 files from 1/100
    for importing into the test setup after running a full reset across all the bases.

    I sent a %rescan d=9999 from 1/995

    From 1/100 MUTIL

    + Feb 06 09:23:12 Results: 0 echo, 0 net, 0 dupes, 156531 tossed in 172.77s

    From 1/100 MIS

    + 2020.02.06 09:28:17 BINKP 1-R: GOT 03c73164.pkt 297 1580980910
    + 2020.02.06 09:28:17 BINKP 1-S: EOB
    + 2020.02.06 09:28:17 BINKP 1-Session ended (36 sent, 0 rcvd, 0 skip)

    From 1/995 FIDOPOLL

    Feb 06 09:28:17 S: GOT 03c73164.pkt 297 1580980910
    Feb 06 09:28:18 R: EOB
    Feb 06 09:28:18 Session ended (0 sent, 36 rcvd, 0 skip)

    From 1/995 MUTIL

    + Feb 06 09:34:12 Results: 156148 echo, 1 net, 382 dupes, 0 tossed in 151.20s


    When I checked FSX_GEN for messages (interestingly) it didn't show the early posts (circa late 2015 onwards) I see

    ┌───────────────────────────────────────────────────────────────────────────── │ ▒ Message Index Listing FSX_GEN └─────────────────────────────────────────────────────────────────────────────
    ## Subject From To
    ─────────────────────────────────────────────────────────────────────────────
    1 Bug? Andrew Hawke

    Where this post is dated

    From : Andrew Msg # : 1 of 75394
    To : Hawke Msg Date : 08/05/16 08:24
    Subj : Bug? Refer to : 0
    Stat : Echo See Also : 0 ───────────────────────────────────────────────────────────────────────────
    On Aug 5th 7:16 am Hawke said...


    In the 1/100 system I see

    ┌─────────────────────────────────────────────────────────────────────────────┐ │ ▒ Message Index Listing General Chat
    │ └─────────────────────────────────────────────────────────────────────────────┘
    ## Subject From To
    ─────────────────────────────────────────────────────────────────────────────
    1 fsxNet Avon All
    2 Re: fsxNet solaris Avon

    With the first post being...

    From : Avon Msg # : 1 of 75475
    To : All Msg Date : 11/08/15 22:18
    Subj : fsxNet Refer to : 0
    Stat : Echo See Also : 3 ────────────────────────────────────────────────────────────────────────── fsxNet is a fun, simple, experimental network that started life with this
    first post on November 8 2015 :)

    Best, Paul

    --- Mystic BBS v1.11 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (18:1/101)

    History buffs may like to note the different zone <--- fsxNet Trivia :)


    What's even stranger is that some bases came across and were imported in correct message order. I can see correct dated initial posts in the following bases FSX_MAG, FSX_HAM (but just spotted two messages with corruption in
    them, humm) FSX_ENG, and FSX_DAT also seem fine for order but others don't
    seem to be in order when imported in. I wonder what's up there?

    I'll keep playing.

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Captain Obvious@21:1/157 to g00r00 on Wed Feb 5 19:29:32 2020
    On 05 Feb 2020, g00r00 said the following...

    Thanks. Hopefully it will be a smooth release. I don't think many
    people were using the later builds of the prealphas.

    I updated most days. Last one prior to this that I used was from 2/2 I think. No problems so far.

    -=>Richard Miles<=-
    -=>Captain Obvious<=-
    -=>bbs.shadowscope.com<=-

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)
  • From Vk3jed@21:1/109 to g00r00 on Thu Feb 6 15:03:00 2020
    On 02-05-20 11:48, g00r00 wrote to Avon <=-

    Thanks. Hopefully it will be a smooth release. I don't think many
    people were using the later builds of the prealphas.

    Being on a Pi, I normally just wait until the alphas are out. :)

    I am excited to get to A45 if this goes smoothly.

    Well, A44 so far seems fine for me. Roll on A45! :)


    ... I am not conceited! I just hate mortals.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Avon on Thu Feb 6 15:08:00 2020
    On 02-06-20 09:49, Avon wrote to g00r00 <=-

    On 05 Feb 2020 at 11:48a, g00r00 pondered and said...

    Thanks. Hopefully it will be a smooth release. I don't think many
    people were using the later builds of the prealphas.

    Biggest issue I see so far will be understanding where MPLC went :)

    I aready had mplc in my Mystic directory, so the upgrade went smoothly in that department. :)


    ... BBS addiction is a terminal disease.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to g00r00 on Thu Feb 6 22:15:18 2020
    On 06 Feb 2020 at 09:49a, Avon pondered and said...

    following bases FSX_MAG, FSX_HAM (but just spotted two messages with corruption in them, humm) FSX_ENG, and FSX_DAT also seem fine for order

    The corrupted messages are a red herring. I found them also in the 1/100 base so have removed them... so they did export (albeit as corrupted) correctly.

    I'm still trying to figure out why some bases when I rinse and repeat a fresh rescan are importing in non chronological order.

    Will keep playing.

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Greg Youngblood@21:4/119.1 to Avon on Wed Feb 5 17:31:38 2020
    Congrats and thanks for releasing this version :)

    Agreed thanks for all your work on Mystic!

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: Wicked BBS|wickedbbs.com:2333 (21:4/119.1)
  • From g00r00@21:1/108 to Captain Obvious on Thu Feb 6 12:50:41 2020
    Thanks. Hopefully it will be a smooth release. I don't think many people were using the later builds of the prealphas.

    I updated most days. Last one prior to this that I used was from 2/2 I think. No problems so far.

    Good to hear! I was cranking them out so fast that it would have been difficult for anyone to keep up!

    I'm going to let A44 sit a few more days before I start working on A45 stuff, just to make sure there aren't any major issues that seem to pop up.

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to Avon on Thu Feb 6 13:26:05 2020
    following bases FSX_MAG, FSX_HAM (but just spotted two messages with corruption in them, humm) FSX_ENG, and FSX_DAT also seem fine for ord

    The corrupted messages are a red herring. I found them also in the 1/100 base so have removed them... so they did export (albeit as corrupted) correctly.

    Yep, unfortunately it can't fix the mess a previous A43 rescan made :(

    I'm still trying to figure out why some bases when I rinse and repeat a fresh rescan are importing in non chronological order.

    Will keep playing.

    What are you max packet settings for size? If I understood correctly you're doing a huge 150,000 message rescan. I am wondering if its filling up packets and then running out of "extensions" to use for new packets so messages sort of get "wrapped" into other existing packets.

    I'll think through this more once I can apply your settings into the logic.

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to Greg Youngblood on Sat Feb 8 08:27:17 2020
    On 05 Feb 2020 at 05:31p, Greg Youngblood pondered and said...

    Congrats and thanks for releasing this version :)

    Agreed thanks for all your work on Mystic!

    Not sure if that thanks was for me or g00r00 but if it was for me thanks :)

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Sat Feb 8 08:46:46 2020

    On 06 Feb 2020 at 01:26p, g00r00 pondered and said...

    What are you max packet settings for size? If I understood correctly you're doing a huge 150,000 message rescan. I am wondering if its
    filling up packets and then running out of "extensions" to use for new packets so messages sort of get "wrapped" into other existing packets. I'll think through this more once I can apply your settings into the logic.

    The settings at 1/100 for /995 are

    Address │ 21:1/995
    Domain │ fsxnet
    Session Type │ BinkP
    Archive Type │ ZIP
    Export Type │ Hold
    Route Info │ 21:1/195.*
    Max PKT Size │ 512
    Max ARC Size │ 2048
    Use Filebox │ Hold
    Filebox Dir │ c:\mystfsx\filebox\fsxnet_z21n1n995\

    Yes I am sending 1/100 a %rescan d=9999 areafix to it and getting back 36 compressed files with a ton of packets in them. I kept a copy of them so I could reset bases or delete bases at /995 to rerun the tests a few times.
    I've only had intermittent BBSing time in the last few days due to family commitments but the retossing has been inconsistent. Some bases when I
    retossed again did seem to land messages in order but other bases were
    jumbled.

    I am suspicious of the HUB bases where (so far) I have found issues with corrupt messages in two of the HUB bases and removed and packed the bases. I have yet to pull a full rescan of the HUB since doing this work. I wondered
    if those corruptions may be a contributing factor to the issue I am trying to confirm/repro. But for now it;s a time thing for me to spend enough time on this to progress is :)

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Fri Feb 7 15:23:49 2020
    Yes I am sending 1/100 a %rescan d=9999 areafix to it and getting back 36 compressed files with a ton of packets in them. I kept a copy of them so

    This sort of points to maybe what I was saying before then. There are only 36 possible bundles so what happens if you rescan so many messages that all 36 bundles are used and at your maximums. I think at that point things may be hit or miss as to where they end up when they are exported.

    Packets within a bundle are sorted and processed in date/time order but if there are packets that are spread out within many bundles, those obviously
    are not - because bundles are processed only one at a time.

    --- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Sat Feb 8 15:52:37 2020
    On 07 Feb 2020 at 03:23p, g00r00 pondered and said...


    Yes I am sending 1/100 a %rescan d=9999 areafix to it and getting bac compressed files with a ton of packets in them. I kept a copy of them

    This sort of points to maybe what I was saying before then. There are only 36 possible bundles so what happens if you rescan so many messages that all 36 bundles are used and at your maximums. I think at that
    point things may be hit or miss as to where they end up when they are exported.

    Packets within a bundle are sorted and processed in date/time order but
    if there are packets that are spread out within many bundles, those obviously are not - because bundles are processed only one at a time.

    Do you think then if we're limited to 36 compressed packets we need to
    increase the size of each compressed archive when a full rescan of a HUB such as d=9999 is called for by an areafix? It will lower the need to use all 36
    if more packets can be stuffed inside a single compressed archive. Or do we need another way to send packets when everything is wanted?

    I'm just trying to think how best to allow for a full rescan of a HUB
    (assuming it's permitted and not overridden by the default_rescan = R=250 setting in mutil.ini.

    Maybe Mystic should dynamically adjust the size of the compressed packets for a situation like this? Or perhaps there are additional settings in mutil.ini in the [ImportEchoMail] stanza to allow for differing max packet or max arc sizes and those are defined dependent upon the R or D values

    Something like this perhaps?

    msg_count <3000 | arc_size=2048
    msg_count >3001 | arc_size=5120

    day_count <1000 | arc_size=2048
    day_count >1001 | arc_size=5120

    I'm going to play some more and report back if I come up with anything
    further using testing :)

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)