ml> what bbs software are you using, again? and what JAMbase code library is   
   ml> it using?? ahhh, and let's also not forget 32bit or 64bit?   
      
    NB> Mystic BBS software, not sure on the JAMbase code library, and it's   
    NB> running on a 32bit system, though I was posting from a 64bit system   
    NB> with Thunderbird (which probably doesn't matter, but I figured I   
    NB> wouldn't leave it out of the equasion).    
      
   that shouldn't matter in the equation at all... your jamnntpd is compiled the   
   same as your mystic?   
      
    NB> As of right now, I'm posting directly from my Mystic system, using   
    NB> Mystic's internal editor. Which I would think would give the same   
    NB> kind of errors if the JAM code was broken, wouldn't it?   
      
   ahh... no... each binary has its own JAMbase code... each can read its own   
   postings but has problems with the other one's...   
      
   i also forgot, this may be 16bit oriented... 16bit as in written in 16bit   
   format but being read in 32bit format... the pascal code i have just given a   
   quick look over shows me words and longints which are 2bytes and 4bytes... i'm   
   looking for the original C code that i got from joho years ago but haven't   
   been able to locate it...   
      
   i would say that jamnntpd has it right, though... my ancient RemoteAccess BBS,   
   FrontDoor editor, TimED, Fastecho all share my JAMbases with my jamnntpd using   
   the same files and paths... those are all 16bit programs and i'm going to step   
   out on a limb and say that Mystic BBS may be using larger (bytewise) versions   
   of those numerical variables...   
      
   *IF* this is the problem, then fixing it in Mystic BBS /will/ absolutely trash   
   the current JAMbases as they are _not_ compatible with the original 16bit   
   JAMbase definitions...   
      
   i am not aware of anyone having made a "super"JAMbase format that uses 32bit   
   or 64bit nomenclature where a word is a different sized storage bucket than   
   2bytes (16bits)... but the main thing is that the standard JAMbase files are   
   16bit... now, if Mystic BBS /IS/ using larger storage buckets, then jamnntpd   
   may be able to be recompiled using them, too... then those two can work   
   together BUT those bases would not be able to be simply copied to another   
   machine with other JAMbase software and work properly...   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)