MSGID: 2:310/31.3@fidonet d8da17e7   
   REPLY: 2:221/1.58@fidonet d8d05db7   
   PID: OpenXP/5.0.38 (Linux) (x86_64)   
   CHRS: ASCII 1   
   Hello August!   
      
   ## 27.05.19 at 19:23, August Abolins wrote to Martin Foster:   
      
    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! :-(   
      
    AA> Looks like JAM is not doeable with SEM.  Thank's for confirming the same   
    AA> problem.   
      
   No bother.   
      
    AA>>> The above problem does NOT happen with a Squish base.   
      
    MF>> I've seen enough with the huge .jhr file, thanks.   
      
    AA> You're giving up because of broken of JAM support in SEM?   Why not try   
    AA> Squish?   
      
   Although I may have implied that I was giving up, that's not the case     
   at all. As soon as time permits, I'll be investigating the possibilty     
   of bolting on the husky stuff.   
      
    AA> Meanwhile I found this little gem, but sadly it fails:   
      
   Ah well, it was worth a try.   
      
   [snip]   
    AA> Do you know of any other messagebase converters out there?   
      
   Sorry but no I don't, as I've never needed one.   
      
    MF>> If you still have Fido Package Deluxe installed..   
      
    AA> I do.   
      
   Great! :-)   
      
    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.   
      
    AA> I don't think I have the stamina to patch SEM with husky stuff.   
      
   Oh? :)   
      
    AA> I looks like FPD creates the "config" based on the settings in the main   
    AA> program.  I don't think I would want to re-edit that file each time there   
    AA> is a change to the echo list.   :(   
      
   If you copy all that stuff from your FPD setup into your SEM setup and     
   change all the paths etc. to suit your SEM setup, you may not need to     
   re-edit the file every time a new area arrives. There's a utility in     
   there(fconf2golded.exe) which will create a golded areas file from the     
   husky config file:   
      
   ---------- 8< ----------   
   c:\Users\martin\Fido\Binkley\hpt>fconf2golded   
   fconf2golded/w32-wc 1.3.0-cur 05-02-03   
      
   Usage:   
      fconf2golded [-a][-sn][-se][-sl][-sb][-sd]        
      []   
   >--^^^^^^^^^^^^^^^   
   >--This should be on the end of the line above.   
      
      (you may read config defaults from default.cfg)   
      (-a exports areas only)   
      (-sn skip netmail areas)   
      (-se skip echomail areas)   
      (-sl skip local areas, and so on...)   
      
   Example:   
      fconf2golded ~/golded/golded.cfg   
   ---------- 8< ----------   
      
   SEM is supposed to be capable of using a golded areas file but we all     
   know what happened when I tried this with crashmail's similar utility.     
   However, I used that on a JAM message base, perhaps better results     
   would be achieved on a squish message base with fconf2golded.   
      
    AA> Fastecho seems more practical at this juncture.   
      
   OK, fine.   
      
   Regards,   
   Martin   
      
   --- OpenXP 5.0.38   
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)   
   SEEN-BY: 1/123 15/2 154/10 203/0 221/0 226/17 229/354 426 1014 240/5832   
   SEEN-BY: 249/206 317 400 280/464 5003 292/854 310/31 317/3 322/757   
   SEEN-BY: 342/200 393/68 396/45 423/120 712/848 770/1 2452/250   
   PATH: 310/31 280/464 229/426