Pigeons are a lousy answer. It takes way too long to train them to memorize the file, and they usually make significant mistakes when asked to recite it back. :-)
Seriously, you never said machine B was more than ten feet away, and if all it takes it ten transport mechanisms to count as ten distinct answers, then the question can be answered trivially. ("Send a floppy by car/bus/train/pigeon/horse/elephant/ etc")
Here's my list:
- Retype it, using a hex editor if necessary.
- Put it on floppy/CD/zipdrive.
- Print the file, and scan it back using OCR. Use something like a uuencoding if necessary.
- Nullmodem cable across the serial/parallel port.
- Text to speech => tape recorder => voice recognition (like a modem, but more inefficient).
- Power down machine A, yank the hard drive with the file on it, re-install in drive B.
- Print bar codes & read back with a bar code reader.
- Hot-swap raid drives from A to B until the file is copied over. Keep replacing drives on A so that the system never goes down.
How's that? Do I get the job?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.