One of the requirements, was to send an EOT character
https://en.wikipedia.org/wiki/End-of-Transmission_character
so that the connection could close properly.
Now, mine is all cabled up and ready to go. The two machines
already have a serial RS232 interconnect (COM1 ==> COM3), with a null modem
thingy in the center (connects TX to RX, RX to TX, so
two computers can talk to one another, without shorting a
TX to a TX).
I fired up putty to verify, on the receiving end.
Set baud rate to 57600, enabled RTS/CTS.
On sending end
mode COM1 BAUD=57600 PARITY=n DATA=8 STOP=1 RTS=on
type sample.txt >COM1
copy con: >COM1
<Enter>
ctrl-Z
<Enter> <=== flushes input at a guess
The problem seems to be mostly on the receiving end.
1) Doesn't seem to have permission to copy COM3 to anything.
2) Does see the ctrl-Z coming across the cable. Closes COPY.
copy COM3 > impossible.txt
impossible.txt ends up with "0 files copied" string in it.
The receive end is not at all happy. Could this be
symptoms that "port is busy" ? Probably.
Evidence when receiving in putty, is "it's working to the
best of puttys knowledge". Ownership issues from Command Prompt
seem an issue right now. When putty exist, you'd think COM3
could then be captured by anyone.
So, nope, doesn't work for me at the moment. Situation
"ripe" but "not harvested". All the ingredients seem to be
there, but Clippy has broken it.
HTH,
Paul