Serial clipboard transfer.

[Thorham]

Hi,

I'm looking for a utility that can transfer the contents of the clipboard over a null-modem cable. Basically needs to work from Windows to Amiga and the other way around as well (Win to Amiga is most important).

Any help is appreciated

[Castellen]

I've not seen anything that does that.  Another option may be to use TwinVNC on the Amiga and any VNC client (e.g. RealVNC free edition) on the windows box.  This does bidirectional clipboard sharing as standard, works well.

You just need an Ethernet adapter in the Amiga.  Or it may be possible to use a serial network from the Amiga (using Miami) to the PC; depending what software you can find to support this on the PC side.

[Thorham]

Thanks for the suggestion

Interesting software, that VNC, but I want to use the serial port because of it's simplicity (I have a PCMCIA ethernet adapter). Guess I'll write my own then, because I've found a very easy to use and small clipboard utility on Aminet. Transferring the data over the serial port is very easy on both Amiga and Windows side (Amiga: Read from SER:, Windows: Use FreeBasic), and a simple script will tie both programs together.

[mongo]

There is a program that does that over a TCP/IP connection.

http://aminet.net/package/util/sys/clipo_v0.1beta

Why use the serial port if you have an Ethernet adapter?

[Thorham]

There is a program that does that over a TCP/IP connection.

http://aminet.net/package/util/sys/clipo_v0.1beta

Thanks, but I know that one

Why use the serial port if you have an Ethernet adapter?

Why not? I only use my network for file transfers, which means it's off most of the time. The serial connection is always there.

Anyway, I've written my own utility for this in assembly language. It uses the clipboard handling program 'Clip' from aminet, and all it really does is receive a file from the pc side and output it to the console. Both programs are tied together using a script.

All in all quite simple, except for the XON/XOFF headache (not a problem for ASCII text files, but a problem for binary data, such as file sizes). Turns out that when using XON/XOFF handshaking, two characters (17 and 19) aren't available for sending data. Easy to handle, but when you don't know about it, it's a real pain.