RS>> I guess you could set TZ on your system and see what happens. It may
 RS>> be that Mark has got the story totally scrambled and its not actually
 RS>> the datestamp on the QWKs which is affected, just the checking of
 RS>> message dates.

 PE>> Ok.  I have done so.

 RS> Interesting. Now the timestamp on the QWK is 10 hours too low.

 RS> OTOH the Madhouse one I picked up at 7:46 this am is stamped 9:57pm
 RS> yesterday.

 RS> Starting to look like its just some Maximus problem with date/time.

 RS>> Use
 RS>> set tz=EST-10

 PE>> Or even AEST?

 RS> Yeah, its just text for the user, not actually used.

Dear oh deary me!  As Paul Markham pointed out to me (hanging my head in
shame), we are 10 hours ahead of UTC, not behind!

 PE>> Only shows it in some batch files.  Also I found out that it can be
 PE>> set up to pack QWK packets in advance, and move them into a file
 PE>> area.  Are you interested in doing that? BFN.

 RS> Yep definitely am. Should help heaps to the session time. I incidentally
 RS> picked up a comment about the same thing in my reading in DrDebug today,
 RS> not specific to Maximus.

Ok, I'll work on that.  That may even make these aborted downloads
acceptable, because they will restart from where they left off, unlike QWK.
 I believe QWK cannot restart, because the packet may be different from the
last one (new messages added).  Is that correct?

Paul

--- GoldED 2.40