Subj : crashmail Echo JAM Base - Errors and Exporting To : Matt Bedynek From : Rick Christian Date : Fri Nov 04 2016 13:46:47 Hello Matt! 03 Nov 16 22:09, you wrote to me: MB> When I started trying to setup jamnntpd here I noticed that when MB> posting messages it would corrupt a message base or not see all the MB> messages. I concluded it was an alignment error because the int's MB> used in the library are not of size specific. the sizeof an int can MB> vary on architectures.. So when jamnntp's jamlib is built on a 64 bit MB> platform some of them are wrong size. MB> It wouldn't take much to go thru the code and fix this, or simply MB> build it with -m32 option (which I tested and works fine). DING!! DING!! Well you have spilled the beans as it were.. I've been digging through that circular bug mess on this exact issue.. That is what I think the issue is with the DEB's... they may compile, so Launchpad just takes it as GOOD TO GO! Problem is that if you run it on *64b* corruption due to exactly waht you said... be it CM II or JamNNTPd... THIS is EXACTLY why I asked... I had the ace up my sleeve the whole time! :) ;) So is the V1.3 code at the SF stuff *correct* for *64b* operation or no one knows as for some reason every one is using 32b??? And the only other working server user seems to be using OS/2 ... although his bug patch was added to the V1.3 code on 9/10/16..... I don't know but I have a hunch that if any one is running this on Linux they are using 32b for it for some reason.. maybe thats all the hardware they have for a spare... don't know... BUT.. Again, this is why I asked, I want to use JamNNTPd to do some things.. but not CORRUPT of the Jam base with something that has the same issue.. So where is this -m32 option used???? in other words this: sudo make -m32 linux (think thats lised in the compile it note) or some other edit??? Seems there IS a *magic golden* code base for JamNNTPd as well! Rick --- GoldED+/LNX 1.1.5-b20160322 * Origin: Vina's Talos Moon Base Alpha (1:135/377) .