Paul,

One of the requirements, was to send an EOT character

Yep, I also tried sending files terminated with it. Alas, no change.

impossible.txt ends up with "0 files copied" string in it.

I found out that in my case it depends: directly after booting it doesn't
return and needs to be killed thru the taskmanager, but after having used my
beforementioned RS232 checking program (even though "mode com1" showing the
same !) it returns directly (either not displaying anything or as you
described, with a zero-length file)

The receive end is not at all happy.

Thats my assumption too.

Could this be symptoms that "port is busy" ? Probably.

As I can run that "RS232 checking program" without a problem (and it
receives the send data), I would say that the port isn't busy or owned by
another program.

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.

:-) /Something/ seems to be "broken" alright. I just wish I knew how to
fix it.

Regards,
Rudy Wieser