Subj : Grunged message cap pointer help?
To   : All
From : Mike Luther
Date : Sat Jul 21 2001 05:59 pm

Somehow, my InterMail / Fastecho combination has picked up a bad habit it never 
had before!

When it gpes to send out mail packets via NETMAIL, it jumps an order of 
magnitude in the next message number upward!

For example.

I there are four net mail messages below the number 10, such as message 4,5,6 
and 7 that are still unsent, it will choose the number 10 for the next 
available message for a new round of traffic!

Then, it will ghost export messages 8 and 9 as useless empty messages on the 
way to 10.

If this insanity starts above 10, say at message 12 and 13 .. it will export 
new ghost 'messages' all the way up to message number 99 .. to reach the magic 
next available message 100!

Of course above that it goes to 1000 and then to 10000 and then .. disaster!

Of course 9999 messages never go anywhere and take forever to spiritually toss! 
 But the queue is apparently coded with a short integer variable and when it 
hits 32767 or whatever .. it rolls around to message number ONE and starts in 
all over there ... which corrupts things.  As well, the cap counter in it isn't 
a short integer!  Thus it things that it may have 32769 as the next message, 
when it really was message number THREE by that time!

To plow around this insanity, I've temporarily put a MAX MR renumber on my 
NETMAIL area after every re-load of the batch file.  That keeps the system from 
fooling with more than 99 messages all the time!

But I'd like to fix this mess!

What did I do?


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)

.