Send(BYTE,TIME) sends one byte. Keeps checking if the other calc wants to Get a byte until it times out. Returns 1 on success. Returns 0 when no byte was sent.
Get receives one byte. Never waits. Returns the byte on success. Returns -1 when no byte was received.

Mind that axe variables are two bytes long. When you send data using Send you only send the lower byte of a variable.'

You should use the linkport on the left. It says I/O on the back

On Sender calc:
Send(A,some amount of time)

On Reciever calc:
Get->A

 I dont see why one cant send a file? Is there an axiom for it?
Yah! Posted 40!!!! 

To ensure that everything remains in sync and to be sure the game doesn't break if one calc is accidentally disconnected, would having each calc wait until the other sent new coordinate data work? That way, it would be slower, but if one calc is disconnected, gameplay would pause (with the ability to exit if it takes too long), then when the cable is connected again, gameplay would resume. Kinda like in Starcraft when a player is lagging.

This would also solve the problem about newer 84+ calcs having a clock speed that is slightly higher than older ones. (eg hardware A calcs run at 14.9 MHz instead of 15.1 or something)