A: Yes! (You'll need to remove the Virtual Machine Additions to really see the effect, because otherwise the Virtual machine and Host machine share a clipboard, anyway.)

Q: Help! CrossClip appears not to be communicating at all.

A1: In some configurations, CrossClip does not set up the buffers properly the very first time it runs. Quitting and restarting CrossClip solves that problem completely.

A2: If the situation continues, by far the most common problem is firewall interference. To verify that, try temporarily turning off all firewalls, then quitting all copies of CrossClip, then restarting CrossClip.

If you are running a personal firewall, you will need to open two ports to allow CrossClip to communicate. The ReadMe file contains details of how to accomplish this, and is available from the program Help screen. Please read that first.

In addition, click below for troubleshooting help with:
Windows XP firewall
Norton AntiVirus firewall
PC-cillin Personal Firewall

Mac OS X Firewall

A: Oops, we just discovered that bug, and are working on it. It seems to be caused by improper mode switching: when the previous incoming communication was an image, the next outgoing text communication doesn't get recognized automatically. For the moment, just click Send manually.

A: Try turning off AutoSend and AutoGet. It's possible in some circumstances for the image to be interpreted slightly differently on the receiving end, which will trigger that computer's AutoSend again, which will trigger the AutoGet on your local machine.