• testing 1-char name from

    From August Abolins@21:2/138 to A00 on Sun Mar 22 01:28:00 2020
    Hi A,

    Will this be A or A0, or something else entirely?

    Other than the 3-char low limit on a name, Sempoint is quite flawless in operations.

    ..Regards,
    August

    * SeM. 2.26 * Push any key. Then push the any other key.
    --- SBBSecho 3.10-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)
  • From Vk3jed@21:1/109 to August Abolins on Sun Mar 22 17:49:00 2020
    On 03-21-20 21:28, August Abolins wrote to A00 <=-

    Hi A,

    Will this be A or A0, or something else entirely?

    Other than the 3-char low limit on a name, Sempoint is quite flawless
    in operations.

    Same result as I got - A00. :)


    ... Manufacturing contact lenses is harder than meets the eye.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Al@21:4/106 to Vk3jed on Sun Mar 22 00:16:50 2020
    Other than the 3-char low limit on a name, Sempoint is quite flawless
    in operations.

    Same result as I got - A00. :)

    Well that solves the mystery anyway. I might have to get used to Al0!

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From Vk3jed@21:1/109 to Al on Sun Mar 22 22:25:00 2020
    On 03-21-20 20:16, Al wrote to Vk3jed <=-

    Other than the 3-char low limit on a name, Sempoint is quite flawless
    in operations.

    Same result as I got - A00. :)

    Well that solves the mystery anyway. I might have to get used to Al0!

    Yeah. :) I only write using SemPoint, when I'm going back over older mail (which is in my archives). :)


    ... Death: To stop sinning suddenly.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Ogg@21:4/106.21 to Vk3jed on Sun Mar 22 14:01:00 2020
    Hello Vk3jed!

    ** 22.03.20 - 18:25, Vk3jed wrote to Al:

    ..I only write using SemPoint, when I'm going back over older mail
    (which is in my archives). :)


    Be mindful of the total number of messages in an area though. Squish is
    not too happy when the number of messages is in the high thousands (ie. 5000+)


    ../|ug

    --- OpenXP 5.0.43
    * Origin: Pointy McPointFace (21:4/106.21)
  • From Oli@21:1/151 to Ogg on Mon Mar 23 01:37:29 2020
    On Sun, 22 Mar 2020 10:01:00 -0400
    "Ogg -> Vk3jed" <21@106.4.21> wrote:

    ..I only write using SemPoint, when I'm going back over older
    mail
    (which is in my archives). :)


    Be mindful of the total number of messages in an area though. Squish
    is not too happy when the number of messages is in the high thousands
    (ie. 5000+)

    I don't think this is a problem with the Squish format, works fine in Golded.

    ---
    * Origin: (21:1/151)
  • From Ogg@21:4/106.21 to Oli on Sun Mar 22 23:11:00 2020
    Hello Oli!

    ** 22.03.20 - 21:37, Oli wrote to Ogg:

    Be mindful of the total number of messages in an area though. Squish
    is not too happy when the number of messages is in the high thousands
    (ie. 5000+)

    I don't think this is a problem with the Squish format, works fine in
    Golded.

    Then it could be the way Sempoint processes the Squish bases. I've had messages near 5000 (primarily due to not establishing a more reasonable pointer setting before downloading a QWK) and Sempoint's message list
    would just look weird: missing dates, or all the dates being 00-00-00 or something like that.


    --- OpenXP 5.0.43
    * Origin: Pointy McPointFace (21:4/106.21)
  • From Vk3jed@21:1/109 to Ogg on Mon Mar 23 20:15:00 2020
    On 03-22-20 10:01, Ogg wrote to Vk3jed <=-

    Hello Vk3jed!

    ** 22.03.20 - 18:25, Vk3jed wrote to Al:

    ..I only write using SemPoint, when I'm going back over older mail
    (which is in my archives). :)


    Be mindful of the total number of messages in an area though. Squish
    is not too happy when the number of messages is in the high thousands
    (ie. 5000+)

    Thanks for the tip. :)


    ... I refuse to be intimidated by Reality
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Oli@21:1/151 to Ogg on Mon Mar 23 13:09:58 2020
    On Sun, 22 Mar 2020 19:11:00 -0400
    "Ogg -> Oli" <21@106.4.21> wrote:

    Be mindful of the total number of messages in an area though.
    Squish is not too happy when the number of messages is in the
    high thousands (ie. 5000+)

    I don't think this is a problem with the Squish format, works
    fine in Golded.

    Then it could be the way Sempoint processes the Squish bases. I've had messages near 5000 (primarily due to not establishing a more
    reasonable pointer setting before downloading a QWK) and Sempoint's
    message list would just look weird: missing dates, or all the dates
    being 00-00-00 or something like that.

    Never experienced that with other software using Squish. IIRC Squish (and JAM) are using 32-bit for the message number and that should be the only limitation (4 million message). Maybe some bug in Sempoint or a corrupted message base (or
    a combination of both?). Have you tried sqfix or some other tool? This are just some random ideas, I really don't know what causes it and never used Sempoint (or I forgot. I was a XPoint user though).

    ---
    * Origin: (21:1/151)
  • From Ogg@21:4/106.21 to Oli on Mon Mar 23 23:10:00 2020
    Hello Oli!

    ** 23.03.20 - 09:09, Oli wrote to Ogg:

    message list would just look weird: missing dates, or all the dates
    being 00-00-00 or something like that.

    Never experienced that with other software using Squish. IIRC Squish (and
    JAM)are using 32-bit for the message number and that should be the only
    limitation (4 million message). Maybe some bug in Sempoint or a corrupted
    message base (or a combination of both?). Have you tried sqfix or some
    other tool? This are just some random ideas, I really don't know what
    causes it and never used Sempoint (or I forgot. I was a XPoint user
    though).

    I could have been the cause. I was importing a combination of BW and QWK packets from the same systems early in my use of Sempoint a few months
    ago.

    But then, Sempoint itself is a 16-bit program.


    --- OpenXP 5.0.43
    * Origin: Pointy McPointFace (21:4/106.21)