Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page
   Networked Database  Support Echo For JAMNNTPD NNTP S...   [82 / 238] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    Matt Bedynek   crashmail Echo JAM Base - Errors and Exporting   November 4, 2016
 11:31 AM *  

03 Nov 16 22:09, you wrote to rick christian:

 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.

ahhh... 64bitness hasn't been indicated... i've been compiling my jamnntpd on
OS/2 with EMX so at best, only 32bit...

 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).

definitely something to remember... especially if one is, as i am, using the
original jamlib instead of the MAPI or SMAPI libraries...

 MB> For jamnntpd, I just went with the smapi version (though it had bad
 MB> bugs too) which are now corrected.  It builds as a 64bit binary too...
 MB> no issues.  I used golded, hpt, and jamnntpd together.  I just need to
 MB> get off my butt and release what I have but there is one more thing I
 MB> want to correct before I do as well as test building on windows.

that's kind of my situation, too... but i did post patches or code to this echo
 for others to grab and add to their code bases... it is just easier that way
for me since i'm not going to fight trying to add repo stuffs to my production
OS/2 box ;)

 MB> The state of fido software is that once someone gets something working
 MB> they tend to not share it outright.  Not out of malice - just out of
 MB> time constaints.  they also don't tend to make things "release grade"
 MB> such that a novice user can simply install them.  I do believe some
 MB> people want and would come back.  We need to figure out how to make
 MB> this great modern software more easy to use and understand.

agreed :)

PS: it is good to see you again, matt!

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... The smallest good deed is better than the grandest intention.
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.1292 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_u8pqj2tgqgtgf7blej70a0j4n3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_u8pqj2tgqgtgf7blej70a0j4n3, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_u8pqj2tgqgtgf7blej70a0j4n3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0