Greetings All!

I've finally figured out what was causing the "missing" first line of every message and the garbage under the origin line issues. It would appear that SemPoint expects 8.3 messagebase filenames and more importantly, the "8" part of the filename MUST be in UPPERCASE, although it doesn't seem to matter what case the file extension is.

I've tried this with CrashMail and the line in the config file that makes all the difference is this one:

---------- 8< ----------
AREA "DEFAULT_F" 2:310/31.3 JAM "c:\\users\\martin\\mailer\\msgbase\\%a" ---------- 8< ----------
The "%a" at the end of the line tells CrashMail to create new areas in UPPERCASE, which results in this new area:

---------- 8< ----------
AREA "POINTS" 2:310/31.3 JAM "c:\\users\\martin\\mailer\\msgbase\\POINTS" ---------- 8< ---------

Here's a directory listing of my new JAM messagebase:

---------- 8< ----------
Directory of c:\Users\martin\mailer\msgbase

04/06/2019 12:57 <DIR> .
04/06/2019 12:57 <DIR> ..
04/06/2019 12:57 681,746 POINTS.jdt
04/06/2019 12:57 5,984 POINTS.jdx
04/06/2019 13:04 361,612 POINTS.jhr
04/06/2019 13:26 16 POINTS.jlr
---------- 8< ----------

Note the file extensions are in lowercase but hey, who cares! -:))

Regards,
Martin

--- SemPoint 2.26+
* Origin: This time everything is easy (2:310/31.3)

Hello Martin!

** 04.06.19 - 13:51, Martin Foster wrote to All:

I've finally figured out what was causing the "missing" first line of
every message and the garbage under the origin line issues. It would
appear that SemPoint expects 8.3 messagebase filenames and more
importantly, the "8" part of the filename MUST be in UPPERCASE, although
it doesn't seem to matter what case the file extension is.

04/06/2019 12:57 681,746 POINTS.jdt
04/06/2019 12:57 5,984 POINTS.jdx
04/06/2019 13:04 361,612 POINTS.jhr
04/06/2019 13:26 16 POINTS.jlr
---------- 8< ----------

Very good work!

But remember, I was having THIS problem:

05/25/2019 07:19 PM 162,203 FIDOTEST.JDT
05/26/2019 05:07 PM 1,520 FIDOTEST.JDX
05/26/2019 05:13 PM 4,294,967,371 FIDOTEST.JHR
05/26/2019 05:13 PM 32 FIDOTEST.JLR

Reading existing messages and writing a new message went well. But as
soon as I went back the C)hange an message that I had previously posted
(but not yet tossed or sent), the above happend.


../|ug

--- OpenXP 5.0.39
* Origin: o,,,,o§ø`ø§o,,,,o§ø`ø§o,,,,o (2:221/1.58)

Hello August!

## 04.06.19 at 18:14, August Abolins wrote to Martin Foster:

I've finally figured out what was causing the "missing" first line of
every message and the garbage under the origin line issues. It would
appear that SemPoint expects 8.3 messagebase filenames and more
importantly, the "8" part of the filename MUST be in UPPERCASE, although
it doesn't seem to matter what case the file extension is.

04/06/2019 12:57 681,746 POINTS.jdt
04/06/2019 12:57 5,984 POINTS.jdx
04/06/2019 13:04 361,612 POINTS.jhr
04/06/2019 13:26 16 POINTS.jlr
---------- 8< ----------

Very good work!

Thanks :)

But remember, I was having THIS problem:

Yes.

05/25/2019 07:19 PM 162,203 FIDOTEST.JDT
05/26/2019 05:07 PM 1,520 FIDOTEST.JDX
05/26/2019 05:13 PM 4,294,967,371 FIDOTEST.JHR
05/26/2019 05:13 PM 32 FIDOTEST.JLR

Reading existing messages and writing a new message went well. But as soon as I went back the C)hange an message that I had previously posted (but not yet tossed or sent), the above happend.

Earlier this morning, I did a very simple test which was to delete one
single message. Doesn't get much simpler, does it?

SemPoint immediately locked up and after watching the twirly-whirly
wheel spinning round and round for something like 20 seconds, I got
control back. The message list was still there but when I hit <Enter>
on one of the messages, the message was blank, as were all the others.
I then looked at my messagebase directory and there it was in all its
glory, the infamous 4Gb file - Pah!!

From my tests so far, I conclude that the only viable message base
format is *.MSG - Hmph!

Regards,
Martin

--- OpenXP 5.0.39
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 05.06.19 - 12:57, Martin Foster wrote to August Abolins:

But remember, I was having THIS problem:

Yes.

05/25/2019 07:19 PM 162,203 FIDOTEST.JDT
05/26/2019 05:07 PM 1,520 FIDOTEST.JDX
05/26/2019 05:13 PM 4,294,967,371 FIDOTEST.JHR
05/26/2019 05:13 PM 32 FIDOTEST.JLR

Reading existing messages and writing a new message went well. But as
soon as I went back the C)hange an message that I had previously posted
(but not yet tossed or sent), the above happend.

Earlier this morning, I did a very simple test which was to delete one
single message. Doesn't get much simpler, does it?

Very simple. :)

SemPoint immediately locked up and after watching the twirly-whirly
wheel spinning round and round for something like 20 seconds, I got
control back. The message list was still there but when I hit <Enter>
on one of the messages, the message was blank, as were all the others.
I then looked at my messagebase directory and there it was in all its
glory, the infamous 4Gb file - Pah!!

The same problem should occur if you tried to C)hange a message.

From my tests so far, I conclude that the only viable message base
format is *.MSG - Hmph!

Yes.. so we can eliminate the use of JAM if used in Win7/32, or WinXP. :(

But then the jury is still out on Squish bases (via Fastecho).

Modifying, C)hange-ing a message in a Squish message base did not trigger
the 4GB bloat problem. But I still don't have Fastecho setup to fully
test incoming and outgoing prosessing.



../|ug

--- OpenXP 5.0.39
* Origin: o,,,,o§ø`ø§o,,,,o§ø`ø§o,,,,o (2:221/1.58)