1. Forum
  2. FSXnet
  3. FSX MAG

  • Talisman v0.51

    From apam@21:1/182 to All on Tue Dec 12 09:38:11 2023
    Hi

    I've reverted (mostly) the fix to squish control lines, and have made
    changed it back to NOT have carriage returns in it.

    Sorry if you updated to v0.50 and entered messages, your bases are
    probably no longer compatible with external utilities.

    v0.51 will still work with v0.50 bases, and earlier versions.

    Oh well.

    Andrew


    --- Talisman v0.50-dev (FreeBSD/amd64)
    * Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)
  • From vorlon@21:1/195.1 to apam on Tue Dec 12 12:22:15 2023
    Hi apam,

    Sorry if you updated to v0.50 and entered messages, your bases are
    probably no longer compatible with external utilities.

    Just another git pull and compile! But working... Now to try some mods
    etc...


    \/orlon
    aka
    Stephen

    Rocking Amiga 3000 powerd, Linux M68K.



    --- Talisman v0.51-dev (Linux/m68k)
    * Origin: Vorlon Empire: Sector 550 (21:1/195.1)
  • From paulie420@21:2/150 to apam on Mon Dec 11 22:57:16 2023
    I've reverted (mostly) the fix to squish control lines, and have made changed it back to NOT have carriage returns in it.

    Sorry if you updated to v0.50 and entered messages, your bases are probably no longer compatible with external utilities.

    Yer awesome, APAM - I love the transparency - and feel for OPs who are bleeding edge enough to have felt the issue, but you are a BBS r0ckstar. Thank you for your continued wonderfulness in this community! :P



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Oli@21:3/102 to apam on Tue Dec 12 10:47:00 2023
    apam wrote (2023-12-12):

    Hi

    I've reverted (mostly) the fix to squish control lines, and have made changed it back to NOT have carriage returns in it.

    Sorry if you updated to v0.50 and entered messages, your bases are
    probably no longer compatible with external utilities.

    v0.51 will still work with v0.50 bases, and earlier versions.

    Oh well.

    I wonder if sqfix (or sqpack) from Squish can fix it.

    Btw, which third-party tool that uses CRs should we avoid? Is it fixable or closed source?


    ⁂

    ---
    * Origin: No REPLY kludge - no reply (21:3/102)
  • From Tiny@21:1/222 to apam on Tue Dec 12 06:26:03 2023

    I've reverted (mostly) the fix to squish control lines, and have made changed it back to NOT have carriage returns in it.

    Can't win for losing on this one.

    Sorry if you updated to v0.50 and entered messages, your bases are
    probably no longer compatible with external utilities.

    I was gonna pretend to be upset like a 90's era sysop but I figured it
    would take too much energy this morning and I'm on almost no sleep.

    v0.51 will still work with v0.50 bases, and earlier versions.

    I'll upgrade when it's out.


    |09S|11hawn


    --- Talisman v0.50-dev (Windows/x86)
    * Origin: Tiny's BBS - tinysbbs.com:4323/ssh:4322 (21:1/222)
  • From Blue White@21:1/997 to Oli on Tue Dec 12 09:01:14 2023
    Btw, which third-party tool that uses CRs should we avoid? Is it
    fixable or closed source?

    The issue was with Squish for DOS. I was attempting to run that here
    after having issues with postie. Squish for DOS was reading the squish
    message areas, finding that there was no "punctuation" or space between
    the end of the INTL kludge and the netmail message text. This apparently caused the last digit of the kludge to get lopped off, and caused the
    receiving system not to recognize the sending node -- meaning the sending
    node couldn't use areafix commands, for example.

    I use squish on another BBS software. It uses *.MSG bases instead of
    squish bases and, in those *.MSG files, there is a <CR> between the last
    kludge and the message text -- and areafix commands work.

    I suggested there might be an issue, but apparently the issue is
    something else.

    apam made some other changes and now both talisman and postie work great
    here, so I am no longer trying to use Squish for DOS. It might be best avoided. ;)



    --- Talisman v0.49-dev (Linux/armv7l)
    * Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:1/997)
  • From Blue White@21:1/997 to apam on Tue Dec 12 09:02:22 2023
    If we are still on v0.49, are there any benefits to upgrading? Thanks
    apam!!!

    --- Talisman v0.49-dev (Linux/armv7l)
    * Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:1/997)
  • From apam@21:1/182 to Blue White on Wed Dec 13 07:56:27 2023
    If we are still on v0.49, are there any benefits to upgrading? Thanks
    apam!!!

    yes, there are a few other bugs fixed.

    Andrew


    --- Talisman v0.50-dev (FreeBSD/amd64)
    * Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)
  • From apam@21:1/182 to Oli on Wed Dec 13 07:56:01 2023
    I wonder if sqfix (or sqpack) from Squish can fix it.

    Maybe? I doubt much would happen if you exported a message with extra
    carriage returns, perhaps the message would start a few lines down or something?

    Btw, which third-party tool that uses CRs should we avoid? Is it
    fixable or closed source?

    It was squish for dos, but I'm not convinced that the problem is in that
    and not somewhere else. I assumed it was the problem because I misread
    the spec I was reading, but having read it properly now, I'm thinking the problem was elsewhere.

    Andrew


    --- Talisman v0.50-dev (FreeBSD/amd64)
    * Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)