MS>> I've got comtest working, but I'm have a few problems.

PE> Great!  I'll attach RSEND + co to you.

MS> got 'em, thanks, but you didn't need to send the same version of
MS> PDComm again.  :)

I checked, and I didn't.  I sent you PDCOM100.ZIP once as far as I can tell.

MS> What I meant is "Should I put if(ALLOK) in my pdcommWriteCh() etc".

No.

MS> I didn't think it was proper to put if(ALLOK) in comtest.c, since
MS> this requires error.h, which the DOS version doesn't use.

That's due to poor writing of comtest.c.  That's where the fault lies and
where the fault should be fixed, not in high-performance functions. But
comtest.c is designed to be used for 10 seconds and then thrown away.

PE> Just use the normal CTS/RTS for handshaking.

MS> Ok.  ATM, I accept the default of XON/XOFF.

You can't use XON/XOFF with FTS-6 sessions.

PE>> BTW, I am suspicious about mktime() or localtime() not working,
PE>> you didn't write either of those yourself did you?

MS>> I wrote the mktime() & after it calculates the time_t it uses
MS>> localtime() to put the struct tm into standard form.  I tested
MS>> my time functions VERY thoroughly - would you like to see the
MS>> test program?

PE> No, it was just something to think about whilst debugging.

MS> I just sent you the test program anyway, as a test of rsend.

Probably would have been more useful sending me mktime() itself, but
anyway, there seemed to be something very odd about the testing, you seem
to be setting "secs" to the number of seconds since 1970 or
something.  It's really meant to be 0-62 or something.  FREQ
"ANSI_C.*" from 3:711/934 if you are interested in the exact
specs for those suite of functions.

Or you can get the source code to PDPCLIB which shows you a real
"live" implementation.

PE> Or reading a message already-saved by Tobruk, ie a message from
PE> me, right?  The example you showed above was for that situation.

MS> Yes, all incoming messages appear to have bad dates.

MS> MsgEd time conversions
MS> ----------------------

MS> mktime says sec=820552612

Well, on the assumption that you are attempting to get the number of
seconds since 1970, like most implementations use, the above number is
indeed 2/1/96.  Check that mktime() got called with correct parameters, and
then find out why you got 820552612 instead of something closer to
849823996.

MS> mktime says sec=315904080

I'll assume for now that this is the garbage date of "date arrived".

BFN.  Paul.
@EOT:

---