In article <118305@muvms3.bitnet>, rcbi110@muvms3.bitnet (R. ALAN MONROE) writes:
> I'm having trouble getting programs to my Amiga from this vax. A friend of
> mine can get files through his computer at work, but we've both tried using
> kermit to send a file to our Amigas with no luck. When at the FTP site, I type > BINARY and then GET <filename>. Then, I go to Kermit and type SEND <filename>
> and I recieve a file by the at name on my Amiga at the right size, but it
> doesn't work. I've tried this with .lzh, .dms, and maybe even .lha files, and
> I can't even uncompress them (I get CRC errors with both LhA and DMS.) I'm
> using VLT v5.517.
I have a (not very good) solution : I use VLT and I connect to an Unix system.
To get binary files (typically .lzh files) from there, I uuencode them, I
select the "Capture session" option on VLT, and I send the uuencoded file.
After that I select "End capture", I go to CLI/Shell and I uudecode the
received file.
Example :
I select "Capture Session", generally I capture in the file "RAM:received" .
Then I type at the Unix prompt : "uuencode snoopdos.lzh snoopdos.lzh" .
Then I wait for the end of the file (I get a flow of ASCII caracters).
Then I select "End Capture".
Then I go to a Shell, type "uudecode received", and have my file snoopdos.lzh .
I am forced to do that because my modem only support 7 bits, so by uuencoding
a binary file I just send printable ASCII. The drawback of this method is that
it takes one third time more to transmit the file, because uuencode takes 3
binary bytes and produces 4 printable ASCII bytes.
For a Vax system, I don't know if there is a uuencode (or equivalent) function,
but you can have the sources (in C) for uuencode/uudecode or write your own.
For example you can imagine a coding system with a better ratio than 3 -> 4
caracters, considering that the printable caracters are in the range 32..126
