MSGID: 2:310/31.3 5cc46640   
   REPLY: 2:221/1.58@fidonet d7c8355d   
   PID: APoint 1.25    
   CHRS: LATIN-1 2   
   Hello August!   
      
   On 26/04/2019 20:25:00, August Abolins wrote to Martin Foster:   
      
   MF>>>> I thought I'd box clever and convert one of my existing message    
   MF>>>> areas from the proprietary AMF format to JAM.   
      
   MF>>>> Everything appeared fine until I exited and restarted APoint..   
      
   AA> I believe you were tackling a JAM format issue with Apoint back in    
   AA> 2003:   
      
   Oh, you've been snooping ;-))   
      
   AA> ----[begin]----   
   AA> From: Martin Foster   
   AA> To: Russell Tiedt   
   AA> Date: 2003-01-14 09:12:32   
   AA> Subject: APoint   
      
   AA> Yes it does BUT I'm sorry to say that it's flawed. APoint will handle    
   AA> a JAM message base that APoint itself has created but if you hook up    
   AA> APoint to an already existing JAM message base created by another    
   AA> program, it will read the message base just fine but it will not    
   AA> write to it correctly. This has been a long-standing problem and I    
   AA> hope the author(s) will fix it for the next release.   
      
   AA> -!- Msged/BeOS 6.0.2   
                 ^^^^   
   Wow, that brings back fond memories :-)   
      
   AA>  - Origin: Bitz-Box (2:250/501.2)   
   AA> ----[end]----   
      
   AA> Was Apoint at 1.25 back then?   
      
   Yes it was and needless to say, the bug never got fixed :-((   
      
   Regards,   
   Martin   
      
   --- APoint 1.25    
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)   
   SEEN-BY: 1/123 15/2 123/1970 154/10 203/0 221/0 226/17 229/107 354   
   SEEN-BY: 229/426 1014 240/5832 249/206 317 400 280/464 5003 292/854   
   SEEN-BY: 310/31 317/3 322/757 342/200 393/68 396/45 423/120 712/848   
   SEEN-BY: 770/1 2452/250   
   PATH: 310/31 280/464 229/426