T.R | Title | User | Personal Name | Date | Lines |
---|
4539.1 | for converting to ASCII | ARRODS::GOLDSTEIN | Steve G DTN: 847-5415 | Fri Feb 22 1991 08:55 | 7 |
|
First it has to be defined as a foriegn command
ie uue :== `disk`:[`acount`]uuencode.exe
and this then converts binary files to ascii type files for
transmitting over networks that don't like binary files....
|
4539.2 | Command Syntax Needed | HKFINN::MACDONALD | VAXELN - Realtime Software Pubs | Fri Feb 22 1991 09:26 | 3 |
| RE: .1 I am well beyond that point. There doesn't appear to be
any documentation. Perhaps you can tell me what the correct
command syntax is?
|
4539.3 | | KALI::PLOUFF | Ahhh... cider! | Fri Feb 22 1991 10:11 | 5 |
| uuencode filename.ext filename.uue
Isn't there documentation in the AmigaUUCP 1.XXD distribution?
Wes
|
4539.4 | | HKFINN::MACDONALD | VAXELN - Realtime Software Pubs | Fri Feb 22 1991 10:15 | 1 |
| RE: .3 Have you actually tried that command line?
|
4539.5 | YAUUD (Yet another UUDECODE) | CSSE32::SMITH | Reality, just a visible imagination? | Fri Feb 22 1991 10:16 | 17 |
| I just picked up another version of uudecode. I compiled this for VMS V5.4 and
have been using it for a few weeks now. This version has the advantage of
allowing you to just copy multi-part uue files in the correct order WITHOUT
having to strip headers and other noise characters.
Anyway, If you would like to give it a shot I've put a copy on
Directory CSSE32::NOTESPUBLIC:[PUBLIC]
MYUUD.LZH;1 (RWED,RWED,RWED,RWED)
The archive includes a short doc, the c source and a VMS .exe
Enjoy,
...Ed
|
4539.6 | | KALI::PLOUFF | Ahhh... cider! | Fri Feb 22 1991 10:22 | 9 |
| re: .4 have I actually tried that command line?
Yes, in the time between reading your note and replying to it. Now,
since I don't even remember where I found my version, it may differ
from yours.
re: .5 uudecoder which handles multipart, divided postings.
^^
Hallelujah!
|
4539.7 | | STAR::ROBINSON | | Fri Feb 22 1991 11:08 | 55 |
| FWIW, this is the DOC I have used with uuencode.exe & uudecode.exe:
--------------------------------------------------------------------
Modified once more to compile with Microsoft C V3.00, and VAX/VMS.
The CI86 code is still there, surrounded with #ifdef CI86...#endif
Usage is:
uuencode [input [output] ]
if output not specified, write to stdout
if input not specified, get input from stdin
uudecode [input]
if input not specified, get input from stdin
WARNING: Current restriction on VAX/VMS: ASCII text files get
all CR/LF combinations converted to LF only during UUENCODE.
This should not be a major problem, as ASCII text files should
not need to be "encoded".
Also note that the return status is not consistent with VAX/VMS
usage, although the error messages should be OK.
Gary Stebbins, DEC, 8/31/86
==============================================================================
The files described in the following paragraphs have been modified
for and compiled under Computer Innovations C86. Note that when
uuencoding a binary file, you must not feed the file to uuencode
through stdin--for some reason, this causes the file to only be
partially encoded (I suspect that this happens when uuencode runs
into a ^Z in the input--I have played around with putting stdin into
'raw' mode, which failed to successfully correct the problem). So
when uuencoding binary files, use the full two-argument form. Note
that uudecode is unaffected.
Brant Cheikes
Department of Computer and Information Science
University of Pennsylvania
ARPA: [email protected]
CSNET: brant%[email protected]
==============================================================================
uudecode and uuencode are easily implemented under MSDOS as well. Here
are the sources for Microsoft C v3.0, but if you have another kind of C
compiler, there should be perhaps only 1 change -- the output file of
uudecode and the input file of uuencode must be in binary format.
(ie. binary files, like .EXE files may have byte patterns that are the
same as ^Z, which signals end-of-file in non-binary (text) mode).
If you need more info, write back. Note that the included files are
*not* in "shar" format -- you will have to use an editor to cut the
files out.
Don Kneller
UUCP: ...ucbvax!ucsfcgl!kneller
ARPA: [email protected]
BITNET: [email protected]
|
4539.8 | No Luck | HKFINN::MACDONALD | VAXELN - Realtime Software Pubs | Fri Feb 22 1991 13:26 | 14 |
|
I am getting a NOMSG error at the end of the compilation.
I have tried both UUENCODE infile outfile
and,
UUENCODE infile >outfile
Perhaps someone can point me to a source that works for them?
|
4539.9 | Likely not a problem | KALI::PLOUFF | Ahhh... cider! | Fri Feb 22 1991 14:13 | 23 |
| Paul,
You may be just running into one of the peculiarities of VAX C. The
standard way to exit a C program is
exit(0);
However, in VAX C the standard way to exit a program with no concluding
message is
exit(1);
Let me suggest the following test... Starting with a text file
"in.file;1" do the following
uuencode in.file out.file
uudecode out.file
cvtarc u in.file
diff in.file;3 in.file;1
You should get back a message that there are no differences. My
advice... NOMSG is no message - if the round-trip test works, ignore
the message.
|
4539.10 | Hello | VICE::JANZEN | Tom MLO21-4/E10 223-5140 | Fri Feb 22 1991 14:15 | 10 |
| Hi I am trying to make this work, too. I had one that output
directly to the screen
$ uuencode file
so in batch mode the output would be captured in the log file.
I havn't made uuencode do the whole route yet though. Maybe 2nite.
I also wrote a funny program that
converts binary nybbles into hexadecimal ASCII for transfers.
That's for small things if you're desperate.
You'd have to compile it on the Amiga.
Tom
|
4539.11 | | HKFINN::MACDONALD | VAXELN - Realtime Software Pubs | Fri Feb 22 1991 14:28 | 1 |
| RE: .9 Can't ... no outfile is created.
|
4539.12 | TRY THIS | POLAR::GOSLING | | Fri Feb 22 1991 14:54 | 14 |
|
At $ prompt:
$ DEFINE/USER SYS$OUTPUT FOO.UU
$ UUENCODE FOO.TXT FOO.TXT
This will create FOO.UU, when decoded would recreate FOO.TXT
I have uuencode defined in my login.com as:
$ uuencode :==$mydisk:[mydir]uuencode.exe
Art
|
4539.13 | Shar (just to confuse) | ARRODS::GOLDSTEIN | Steve G DTN: 847-5415 | Fri Feb 22 1991 17:04 | 11 |
|
Just to throw a spanner in the works you could use SHAR from WJG
this converts both from ASCII to Binary and Binary to ASCII
ie if you have seen the output from some of the usenet binary
conferences..
Steve G
|
4539.14 | FOund it | DFN8LY::JANZEN | Tom MLO21-4/E10 223-5140 | Fri Feb 22 1991 18:50 | 20 |
| I found a combination that seems to work on one little file.
whew.
dfn8ly::disk$user:[janzen.public]uuencode.lzh
unpack it on the VAX, send over the uudecode.c to the amigaand
compile it. with SAS or Lattice. Ignore the warnings.
This is from Fred Fish.
For the encoder, you can use the UUENCODE.EXE in the same directory.
Define it foreign
uuencode :== disk:[dir]uuencode.exe
Just get ready to capture a text file and type
$ uuencode file
Then after the ascii capture, type on the Amiga after compiling
and linking uudecode,
CLI>uudecode file.
NOte that this will unpack the encoded filename reagardless of
what file namethe file has on the amiga. so to speak.
Tom
|
4539.15 | Is this still on-going | WELLIN::FINNIS | | Mon Feb 25 1991 19:08 | 13 |
|
The amiga has had UUJoin and UUSplit in the UUCP release for
a long time now.
shar is I believe different to UUEncode/UUDecode.
Did you get a result, ie convert a file eventually ?
I can't believe how convoluted some of the ways UUEncode is being
used to get an encoded file.
-Pete-
|