Subj : [SemPoint] Message areas not showing To : Martin Foster From : August Abolins Date : Mon May 27 2019 19:23:00 Hello Martin! ** 27.05.19 - 13:10, Martin Foster wrote to August Abolins: AA>> 05/26/2019 05:13 PM 4,294,967,371 FIDOTEST.JHR AA>> 05/26/2019 05:13 PM 32 FIDOTEST.JLR MF>Yep, same thing happened with me after deleting a bunch of messages. MF>---------- 8< ---------- MF>27/05/2019 09:52 4,294,967,371 points.jhr MF>---------- 8< ---------- MF>Oh Joy! :-( Looks like JAM is not doeable with SEM. Thank's for confirming the same problem. AA>> The above problem does NOT happen with a Squish base. MF>I've seen enough with the huge .jhr file, thanks. You're giving up because of broken of JAM support in SEM? Why not try Squish? Meanwhile I found this little gem, but sadly it fails: C:\SEM\MESSAGES\test>fmacopy FMA Message base copy utility built Mar 21 2003, 21:38:18 Written by Pete Kvitek of JV Dialogue 1st BBS, 2:5020/6@fidonet Usage: FmaCopy [options] /A[areatag] - add ^aAREA: kludge /N[z:n/n.p] - default network address (from Fts, Pkt) /O[z:n/n.p] - origination network address (to Pkt) /D[z:n/n.p] - destination network address (to Pkt) /C - clear target base before copy /V - verbose mode /G[file|*|#] - log to file, * to debugger, # to console Message base type is specified using the base path extension. Supported bases: *.msg (add backslash), Squish, JAM and Pkt. C:\SEM\MESSAGES\test>fmacopy fidotest.jdt fidotest.sqd Copying 192 msgs in fidotest (JAM) to fidotest (Squish)... Copying msg 1 of 192 Can't save target message 0, error=7 Done... 0 msgs in fidotest (Squish) C:\SEM\MESSAGES\test> ----------8<---------- Do you know of any other messagebase converters out there? MF>If you still have Fido Package Deluxe installed.. I do. MF>...all the husky stuff MF>is in there. There's everything you want(and more) in \Binkley\hpt MF>including an already configured and working hpt config file. Just copy MF>it all over to your SemPoint setup and then change the paths in the MF>hpt config file accordingly. There may be other bits 'n bobs that need MF>editing too. I don't think I have the stamina to patch SEM with husky stuff. I looks like FPD creates the "config" based on the settings in the main program. I don't think I would want to re-edit that file each time there is a change to the echo list. :( Fastecho seems more practical at this juncture. ../|ug --- OpenXP 5.0.38 * Origin: o,,,,o§ø`ø§o,,,,o§ø`ø§o,,,,o (2:221/1.58) .