MS>> Yes, it's "under control" - I definitely can't send a ZModem
MS>> batch upload within an NComm script.

PE> Just send *.* or #? or whatever you normally use.

MS> I've already tried using wild cards - it says "file does not
exist". I've 

How's your comms?  I have a program called RSEND*.* (FREQ), which will
transfer the files.  The only thing it needs is PDCOMM (also available for
FREQ) to have an Amiga port.  I will be modifying the PDCOMM interface
soon, but I suspect the main work of comms will not change.

MS>> One thing I've noticed - the message dates are wrong. This message
MS>> had the correct date when I was creating it, now it has reverted
MS>> to 01 Jan 96. Received messages have even worse dates on the Attr
MS>> line, e.g, 01 Jan 80.

MS>> Any ideas?

PE> Hmmmm.  Can you check the .MSG files you created, and see if the
PE> date is correct inside them?

MS> The date is incorrect - 01 Jan 96.

Then it's MSGED.

PE> I have looked at Tobruk, and it seems to have code in it to read
PE> the date from the .MSG file and put it in the .PKT file.  And
PE> vice-versa.

MS> I think it's MsgEd, not Tobruk, but you're the expert.

No, I thought you were saying that Tobruk was at fault, and I was not
disbelieving you, but I wanted you to make sure.

PE> Let's start with the first problem.  Confirm that the .MSG file
PE> has the correct date in it (do a hexdump of the file), and then
PE> I'll get you to put some debugging in to tobruk.

I think you'll need to debug where in MSGED that is happening.  Can you put
some printfs into the mtime() function in date.c and see what path it is
taking, and what is being put into tmp.  BFN.  Paul. 
@EOT:

---