• mbse 1.0.7.9

    From Vince Coen@2:250/1 to All on Friday, September 21, 2018 15:44:03
    Hello All!

    The code base at SF is now at 1.0.7.9 but I have not issued a archive containing it. However the change is as below:

    -!-
    v1.0.7.9 17-Sep-2018 - Andrew Leary

    1. Removed the requirement that incoming .TIC files have
    exactly 8 character filenames with the .TIC extension. This
    will allow processing incoming .TICs from Mystic BBS without
    manual intervention. Mystic does not comply with
    FTS-5006.001, which specifies that .TIC files be named with
    a DOS compatible 8 character filename, a dot, and the 3
    character extension TIC.
    -!-

    If you have a need to upgrade but are uncomfortable using the codebase let me know here and I will do a version generation for 1.0.7.9.

    At the moment I am currently running this version and have for some days with no adverse results but cannot say that the conditions have arisen where this fix shows up but I do have at least one downlink using
    Mystic (v1.12A39 binkp/1.0).



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Andrew Leary@1:320/219 to Vince Coen on Friday, September 21, 2018 18:04:50
    Hello Vince!

    21 Sep 18 15:44, you wrote to all:

    At the moment I am currently running this version and have for some
    days with no adverse results but cannot say that the conditions have arisen where this fix shows up but I do have at least one downlink
    using Mystic (v1.12A39 binkp/1.0).

    You won't notice anything unless a Mystic node sends you .TIC files. Mystic by default names .TIC files with the same name as the archive they relate to. ie: the .TIC file for fsxinfo.zip would be fsxinfo.tic.

    This causes problems with MBSE versions before 1.0.7.9, because MBSE expects that all .TIC files will be named with 8 character filenames followed by .TIC. The example above is only 7 characters, so it wouldn't be processed automatically. The same applies to long filenames (longer than 8 characters.)

    The changes in 1.0.7.9 will handle .TIC files with filenames of 1 character up to the maximum the OS supports.

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Deon George@3:633/509 to Vince Coen on Saturday, September 22, 2018 23:31:19

    Hello Vince!

    21 Sep 18 15:44, you wrote to all:

    At the moment I am currently running this version and have for some
    days with no adverse results but cannot say that the conditions have arisen where this fix shows up but I do have at least one downlink
    using Mystic (v1.12A39 binkp/1.0).

    I've been running it as well, and my uplinks are Mystic - and no issues with me others. Happy that all TIC's are now being processed :)

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: Chinwag | MBSE in Docker on Pi (3:633/509)
  • From Vince Coen@2:250/1 to Andrew Leary on Saturday, September 22, 2018 14:10:24
    Hello Andrew!

    Friday September 21 2018 18:04, you wrote to me:


    At the moment I am currently running this version and have for
    some days with no adverse results but cannot say that the
    conditions have arisen where this fix shows up but I do have at
    least one downlink using Mystic (v1.12A39 binkp/1.0).

    You won't notice anything unless a Mystic node sends you .TIC files.
    Mystic by default names .TIC files with the same name as the archive
    they relate to.
    ie: the .TIC file for fsxinfo.zip would be fsxinfo.tic.

    This causes problems with MBSE versions before 1.0.7.9, because MBSE
    expects that all .TIC files will be named with 8 character filenames followed by .TIC. The example above is only 7 characters, so it
    wouldn't be processed automatically. The same applies to long
    filenames (longer than 8 characters.)

    The changes in 1.0.7.9 will handle .TIC files with filenames of 1
    character up to the maximum the OS supports.

    Thanks for that, in which case I will not notice it as my master uplinks do not
    use mystic - have no idea why not!!

    Must have a look at what hatch does though as I do process some long file names
    :)

    Mind you I am fairly sure it renames them to a 8.3 - in some case very oddly :)


    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vince Coen@2:250/1 to Deon George on Sunday, September 23, 2018 22:15:14
    Hello Deon!

    Saturday September 22 2018 23:31, you wrote to me:


    Hello Vince!

    21 Sep 18 15:44, you wrote to all:

    At the moment I am currently running this version and have for
    some days with no adverse results but cannot say that the
    conditions have arisen where this fix shows up but I do have at
    least one downlink using Mystic (v1.12A39 binkp/1.0).

    I've been running it as well, and my uplinks are Mystic - and no
    issues with me others. Happy that all TIC's are now being processed :)

    i see you are using a pi, what are you doing for hard drives as i could not see
    how to remove the usage of an sd card and i have zero intention of doing so. one's advertised in the uK only have one usb port and that is v2 so still slow.

    i would like to bay and set one up for some Cobol->java development system which is free on that platform but major issues with mass storage.
    i have no intention of waiting around will it thinks that going back to the 70's and floppies.

    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Deon George@3:633/509.1 to Vince Coen on Monday, September 24, 2018 07:36:40
    On 09/23/18, Vince Coen said the following...
    i see you are using a pi, what are you doing for hard drives as i could not see
    how to remove the usage of an sd card and i have zero intention of doing so.

    I have a Pi v3+ and it has a 64GB SD card (Samsung EVO Plus) - I was reading
    in (I think) the PI echo and discovered a website that did performance on SD cards - and this one got the best review for performance.

    Since the Pi has 4 USB ports, I also have a San Disk Cruzer - but I use it
    for a local daily backup (using rdiff-backup).

    If the SD card starts to fill up, I'll probably put on a USB/Sata external caddy, with a SSD (I have a spare 128GB) - which I'm hoping is more than
    enough for what I want to use it for... And if things start to get full, I've got the NAS that I'll offload stuff to with an automount.

    i would like to bay and set one up for some Cobol->java development
    system which is free on that platform but major issues with mass storage. i have no intention of waiting around will it thinks that going back to the 70's and floppies.

    For BBSing, the PI is great - this one has 2 docker containers (MBSE +
    Mystic) and I compile MBSE (and other BBS code) and build the docker
    containers on it.

    I have another Pi - which is a 3 (not a 3+) - and its running qemu and my BBS from 1995 (ezycom). I've been setting that up over the last week, and while
    it is also slow (by todays standards) - everything works (and it's probably faster than what it was in 1995!) (I did try getting Ezycom running as a DOS virtual machine on my Intel server - it was fast, but most things didnt work
    - the Runtime Error 200. I did have the pascal TSR loaded, and that fixed somethings, but many others didnt work - like the ezymail tosser.)

    ...deon

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)
  • From Vince Coen@2:250/1 to Deon George on Tuesday, September 25, 2018 18:29:29
    Hello Deon!

    Monday September 24 2018 07:36, you wrote to me:

    I have another Pi - which is a 3 (not a 3+) - and its running qemu and
    my BBS from 1995 (ezycom). I've been setting that up over the last
    week, and while it is also slow (by todays standards) - everything
    works (and it's probably faster than what it was in 1995!) (I did try getting Ezycom running as a DOS virtual machine on my Intel server -
    it was fast, but most things didnt work - the Runtime Error 200. I did
    have the pascal TSR loaded, and that fixed somethings, but many others
    didnt work - like the ezymail tosser.)

    There is a patch for the 200 error.
    Some where on my system I do have it as I still do fixes to FileMgr when ever needed. That any thing must find the time to read up fully on FPC and convert the sources but I am rusty in Pascal and even more so in asm.


    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.9/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Deon George@3:633/509 to Vince Coen on Wednesday, September 26, 2018 08:17:58

    Hello Vince!

    25 Sep 18 18:29, you wrote to me:

    There is a patch for the 200 error.
    Some where on my system I do have it as I still do fixes to FileMgr
    when ever needed. That any thing must find the time to read up fully
    on FPC and convert the sources but I am rusty in Pascal and even more
    so in asm.

    Yeah, I tried some. tp5f5fix worked really well, and when it didnt I tried the unc and crtfix utitilities that still emitted the Runtime Error 200 but they still didnt work.

    But it's all running happily now on the Pi under QEMU - without needing any Pascal patches.

    I found too that some updated apps worked better - my Ezycom is at 1.10 and POP 0.62. Upgrading those to later versions might yield better results...

    Back in the day I used to program in Turbo Pascal as well - those brain cells are long lost :)

    ...deon

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: Chinwag | MBSE in Docker on Pi (3:633/509)
  • From Deon George@3:633/509.1 to Andrew Leary on Monday, October 01, 2018 14:53:49
    Hey Andrew,

    1. Removed the requirement that incoming .TIC files have
    exactly 8 character filenames with the .TIC extension.

    I've just noticed that I received some realy_long_filenames from an upstream, and because I didnt have the file area defined - mbfido wanted to toss them into the badtic dir, but couldnt because it had truncated the filename to the first 12 chars.

    ? 02-Oct-2018 00:38:30 mbfido[6490] Failed to move /opt/mbse/data/inbound/1-5_lxk1-en- to /opt/mbse/data/badtic/1-5_lxk1-en-: No such file or directory

    The filename was 1-5_lxk1-en-manual.tic

    Issue seems to be around line 230 of mbfido/tic.c

    strncpy(TIC.TicName, tfn, 12);

    But there also seems to be other cases where strncpy is used to populate a variable with only 12 chars... (line 376 and 498 - first one might be valid, but not sure about the second one...

    ;)

    ...deon

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)