Hello Martin,

On 26.05.19, you wrote..

 AA>> Apparently sysop Paul Quinn (Australia) has recently used SemPoint and
 AA>> placed a couple of "test" messages in FIDOTEST.

 AA>> It might be worth a try to drag him in here and pick his brain.

 MF> I've dropped a gentle hint ;-))

No having much luck with my JAM message base:
     
I was able to list and read and even post my own messages to my sample FIDOTEST
 area, but today when I decided I'd like to delete a bunch of the old messages,
 Sempoint crashed and produced this:

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

I originally created the set of jam files with Apoint.  Copied them over to a
place where Sempoint would use them. I configured the FIDOTEST area manually
with Sempoint.. and voila, the messages listed fine.  I even added a few of my
own messages as test posts.

So.. this is a BAD idea.

Meanwhile, I found out the SAME thing happens with an jam area created with
SEM!  I can enter/post a message fine.  But as soon as I go back to C)hange the
 message (to adjust the subject, for example)  ..the program goes ballistic and
 produces a 4GB+ .jhr file!

The above problem does NOT happen with a Squish base.

If anyone can duplicate or verify this, that would be great.

Since Crashmail only supports jam or msg, this is not looking good for SEM
w/Jam + Crashmail combo.  


../|ug

--- WinPoint Beta 5 (359.1)
 * Origin: Please write your complaint in this box [ ] - Legibly (2:221/1.59)