Jerry,

I've emailed you a sample using XCOMM. A couple of things to watch out for:

Fixed length 128 byte packets, so the received file will be packed with CTRL-Z to fill the last block. You may want to change this if sending/receiving binary data. You could also create your own preamble, sending the file name and size prior to initiating the transfer, and clean up on the receiving end. This also cleans up the receiver status display as a result (ReceivedFileSize).

I believe as a result of the above, the MSCOMM EOFEnable property is gone. Very useful for text transfers.

All in all, this approach is much easier than constructing your own transfer protocol.

As an aside, try replying directly to this message vs to your message. That way I get a notification of your response.

>Thanks! I couldn't get Grier's form to work any better than my own, and none of the bells and whistles worked (thermometer, transfer rate, etc.).