Hello Bob!

Oct 15 15:04 03, Bob Jones wrote to Bo Simonsen:

 BJ>> Ok.  I'll need to add that file to what I should look at over the 
 BJ>> weekend.

 BS>> Take a coding weekend :-)

 BJ> I'm going to try to allocate a few hours to look at the code and see 
 BJ> if I can come up with what's causing the problem.....

That would be nice.

 BJ>> With the start of the new school year, I have been busier (sp?) than 
 BJ>> I expected.  

 BS>> So you do actually teach?

 BJ> No.  I'm working substituting for classified not certified positions 
 BJ> within the school district.  Such items as the (front) office 
 BJ> positions, class room aids (para-educators, instructional aids, 
 BJ> student monitors, etc.  

Okay.

 BJ> The office positions required a typing 
 BJ> (speed) test that I passed (with ease on the first try).  [Only 
 BJ> needed 35 WPM for sub office positions.  I passed the required WPM 
 BJ> for some of the perminate office positions.....]  

Oh that's not mutch, as a programmer you can do it. :) It's only a half of
a line on a normal monitor.

 BS>>>> The file upload doesn't work at all1

 BJ> Can max not find the file for the upload?  What error message is 
 BJ> generated.  I thought this worked under OS/2 as a read of the file 
 BJ> from a local disk.  I remember there are some upload/download items 
 BJ> that don't work from the local console loggin, but I thought QWK 
 BJ> worked based on file names and location....

Not problem at that kind, CRC errors and so on.. So data isn't beeing send correctly.

 BS>> It should parse double CR, LF and NULL. Also known as 
 BS>> Byte stuffing if it's what I'm thinking of.

 BJ> There is a CR/LF issue between VT-100 terminals (i.e. Maximus BBS 
 BJ> users), DOS (OS/2 & Win32 also) based Max systems and Unix / Linux 
 BJ> based max systems, so we are probably thinking the same things 
 BJ> here.....

I hope so.

 BS>> Bingo.

 BJ> Finally getting towards an agreement on stradegy.....

It tooks it's time.

 BJ>> This is just the start of my thoughts on debugging this issue.

 BS>> And I follow them.

 BJ> Good luck.  Let me know the outcome of logging stuff.  We may want to 
 BJ> add a log level of 6 (or what ever the next higher number is) -- or a 
 BJ> higher number -- for sending our debugging stuff to the max log file. 
 BJ>  Then we can control this via the log level in the max control 
 BJ> file.....

Indeed the one there is, isn't good enough.

Regards,
Bo

--- Msged/LNX 6.1.2 (Linux/2.4.18-586tsc (i586))