1. Forum
  2. FIDO
  3. JAMNNTPD

  • errors and how to fix?

    From Tommi Koivula@2:221/360 to Oli on Sat Apr 29 19:49:44 2023
    * Originally in fidosoft.husky
    * Crossposted in jamnntpd

    Hi Oli.

    Both are available for Debian in 64-bit. Do we have to file a bug
    report?

    In this debian 64bit I tried "sudo apt install crashmail", then created a very
    basic crashmail.prefs with one area

    area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
    keepnum 99
    keepdays 99

    crashmaint maint verbose
    Processing rbb.test.9...
    0 messages deleted by number, 4278124318 messages left
    0 messages deleted by date, 4278124318 messages left

    And the jam base is now broken. Hpt cannot work with it, Golded cannot work
    with it. :(

    So yes, we have to file a bug report. Just test by yourself and go ahead.

    I repeated the same procedure in this Raspian OS 32bit RPI 3B+ system. Works very nice. So 64bit is to blame.

    'Tommi

    --- GoldED+/LNX 1.1.5-b20220409
    * Origin: Linux 6.1.21-v7+ armv7l (2:221/360)
  • From Carlos Navarro@2:341/234.1 to Tommi Koivula on Sun Apr 30 08:35:28 2023
    29 Apr 2023 19:49, you wrote to Oli:

    In this debian 64bit I tried "sudo apt install crashmail", then
    created a very basic crashmail.prefs with one area

    area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
    keepnum 99
    keepdays 99

    crashmaint maint verbose
    Processing rbb.test.9...
    0 messages deleted by number, 4278124318 messages left
    0 messages deleted by date, 4278124318 messages left

    And the jam base is now broken. Hpt cannot work with it, Golded
    cannot work with it. :(

    So yes, we have to file a bug report. Just test by yourself and
    go ahead.

    I repeated the same procedure in this Raspian OS 32bit RPI 3B+ system. Works very nice. So 64bit is to blame.

    On the website at SourceForge (https://ftnapps.sourceforge.net/crashmail.html) there is a link to a CrashMail II port (fork):
    https://github.com/larsks/crashmail
    Includes: Support for 64-bit operating (POSIX) operating systems.

    Maybe worth checking?

    It was archived, but there is also a fork of that fork here: https://github.com/punktniklas/crashmail
    which was last updated "recently", in 2020.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)
  • From Tommi Koivula@2:221/360 to Carlos Navarro on Sun Apr 30 20:10:14 2023
    Hi Carlos.

    30 Apr 23 08:35, you wrote to me:

    It was archived, but there is also a fork of that fork here: https://github.com/punktniklas/crashmail
    which was last updated "recently", in 2020.

    I think I'm not going to spend much time anymore with these things. In 64bit environment I'll play with SMAPI-based stuff only. :)

    'Tommi

    --- GoldED+/LNX 1.1.5-b20220409
    * Origin: Linux 6.1.21-v7+ armv7l (2:221/360)
  • From Oli@2:280/464.47 to Carlos Navarro on Wed May 3 17:11:54 2023
    Carlos wrote (2023-04-30):

    And the jam base is now broken. Hpt cannot work with it, Golded
    cannot work with it. :(

    So yes, we have to file a bug report. Just test by yourself and
    go ahead.

    I repeated the same procedure in this Raspian OS 32bit RPI 3B+
    system. Works very nice. So 64bit is to blame.

    On the website at SourceForge (https://ftnapps.sourceforge.net/crashmail.html) there is a link to a CrashMail II port (fork): https://github.com/larsks/crashmail Includes: Support for 64-bit operating (POSIX) operating systems.

    Maybe worth checking?

    It was archived, but there is also a fork of that fork here: https://github.com/punktniklas/crashmail
    which was last updated "recently", in 2020.

    Looking at the commit history, there should be no differences between the forks regarding 64-bit compatibility. Commits from the larsks repo were merged into the ftnapps (Clay / Debian) repo and the additional commits punktniklas are mostly build warning fixes. I haven't tested the other versions and might have missed a critical bug fix that has not been mentioned in the commit logs.

    ---
    * Origin: This site requires JavaScript (2:280/464.47)
  • From Carlos Navarro@2:341/234.1 to Oli on Thu Oct 16 21:16:22 2025
    03 May 2023 17:11, you wrote to me:

    Looking at the commit history, there should be no differences between
    the forks regarding 64-bit compatibility. Commits from the larsks repo were merged into the ftnapps (Clay / Debian) repo and the additional commits punktniklas are mostly build warning fixes. I haven't tested
    the other versions and might have missed a critical bug fix that has
    not been mentioned in the commit logs.

    FYI, I found another separate fork:
    https://github.com/orignal/crashmail

    The README states:
    This forks fixed incompatibity of JAM database with GoldEd+

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)