MSGID: 2:221/1.59 5cceb374   
   REPLY: 2:240/2188.31@fidonet d821eb8b   
   PID: APoint 1.25    
   CHRS: LATIN-1 2   
   Hello Martin!   
      
   On 5/5/2019, Martin Foster wrote to August Abolins:   
      
   AA>> I believe you were tackling a JAM format issue with Apoint back in   
   AA>> 2003:   
      
   AA>> ----[begin]----   
   AA>> From: Martin Foster   
   AA>> To: Russell Tiedt   
   AA>> Date: 2003-01-14 09:12:32   
   AA>> Subject: APoint   
      
   AA>> [snippity..]   
      
   AA>> .. but if you hook up APoint to an already existing JAM message base    
   AA>> created by another program, it will read the message base just fine    
   AA>> but *it will not write to it correctly*.    
      
   AA>> [..snip]   
      
   AA>> Which led you to believe that Apoint utilized a proprietary   
   AA>> version of its own JAM.   
      
   MF> Don't think it did.   
      
   OK..  you didn't say *exaclty* that.  ;)  But..  Apoint's JAM is not playing   
   nicely with the JAM spec, and breaks existing files.  Plus, it deleted all the   
   messages from it's *own* build after I added a new message with SemPoint.   
      
   AA>> Will WinPoint work with the standard JAM produced from another    
   AA>> source, or will it barf?   
      
   MF> WinPoint doesn't support JAM at all.   
      
   Oops.. sorry.  I got dizzy for a sec.  LOL.    I meant Apoint.   
      
      
   MF>>> ...but the messages are still there when you go into   
   MF>>> the message list.   
      
   ..and probably *only* if you don't add any new messages, either by edit, or   
   incoming by toss?   
      
   AA>> But who will want to embrace Apoint if it behaves like that?   
   MF> Probably nobody.   
      
   OK.. here's a test.  Convert a base to JAM, add a few messages with itself,   
   then convert it back to AMF.   Is everything kosher?   
      
      
   AA>> To me, that's "broken".   
   MF> You say "broken", I say "cosmetic" :-)   
      
   Noted.  But, in your own words way at the top: "wll not write to it   
   correcty".    Cosmetic?  More makeup can't coverup that serious problem!  LOL   
      
      
   ../|ug   
      
   --- APoint 1.25    
    * Origin: What I say, APoint says. (2:221/1.59)   
   SEEN-BY: 1/123 15/2 154/10 203/0 221/1 6 360 226/17 229/354 426 1014   
   SEEN-BY: 240/5832 249/206 317 400 280/464 5003 292/854 310/31 317/3   
   SEEN-BY: 322/757 342/200 393/68 396/45 423/120 712/848 770/1 2452/250   
   PATH: 221/1 280/464 229/426