UUCJEFF@ECNCDC.BITNET (01/22/88)
I downloaded the uuencode.c and tried compiling it in Alycon C and Mark Williams C. Alycon C just hangs up, while Mark Williams does an exit #2, USAGE error. Has anybody been able to get this to work with the compiler's I have? I tried the UUENCODE.BAS using the ST Basic I got with the ST, and that runs the program, but doesn't do anything. Anyhelp will be appreciated. Also, assuming I get a uuencode.prg working, i notice there sometimes are directives at the begining or end of the .uue files. Are these left in? Exactly what should be left in in when I edit out the headers? Jeff Beer. UUCJEFF@ECNCDC.BITNET round up the usual disclaimers.....
bshuste@pacsbb.UUCP (Bob Shuster) (09/10/88)
I am new to the USENET and I see lots of programs listed in various comp.binaries.etc. newsgroups. My question (and problem) is: How do I take advantage of these files? Is there a specific program I need to use these programs, and where could I obtain it? - Bob Shuster {ihnp4,att-cb,rutgers}!{bpa,cbmvax}!temvax!pacsbb!bshuste
trb@stag.UUCP ( Todd Burkey ) (09/11/88)
In article <433@pacsbb.UUCP> bshuste@pacsbb.UUCP (Bob Shuster) writes: > > I am new to the USENET and I see lots of programs listed in various >comp.binaries.etc. newsgroups. My question (and problem) is: How do I >take advantage of these files? Is there a specific program I need to use >these programs, and where could I obtain it? It kind of depends on whether you are on a Unix system or not. If pacsbb is a Unix box, then just use the uudecode command (standard on most Unix systems.) Most versions of uudecode require that the input file be in one piece, so if you get a multipart file, you will sometimes have to cat the files together and then go in and remove the header information between the uudecode'ed blocks. Another approach is to move the comp.binaries.etc files over to the ST first and run Dumas's uud software (available on my BBS's worldwide). This software is set up so you don't have to concatenate the files first (iff the original multi-part file was encoded with Dumas's software). I generally prefer to uudecode everything on the Unix system, since that is faster...1) the uudecode runs faster, 2) the files are smaller by 50% after uudecoding, and 3) I can un-arc the files on the Unix box and see if I still want the program after reading the docs. In answer to a previous post about hdscan...I am guessing that you either need the dumas software (i.e. you don't have a Unix system to uudecode it on), or you are on a Unix system and didn't realize you have to concatenate the files. I think I did that one in three parts and they did uudecode OK here after they came back through the binaries group. -Todd Burkey "A member of STdNET-The ST developers' Network" trb@stag.UUCP -> to join, mail to ftg!dwm@stag.UUCP <- P.S.: I just remembered that at one time I had the dumas software running on my Unix system, so the sources are probably floating around, too.
hyc@math.lsa.umich.edu (Howard Chu) (02/27/89)
Standard Unix uuencode/uudecode does not know anything about the include directives. That's part of your problem. If you concatenate the multi-part encodings by hand and still get errors, one can only presume you did something wrong - put them in the wrong order, left in a line you should have deleted, or deleted a line you should have left intact. A multi-part encoded file begins at the begin blahhh and ends at the include blah2 You should delete all the "include" lines when concatenating by hand, as well as all but the first "begin" line. Usually every encoded line begins with 'M' - when you finish, there should be one "begin," one "end," and a lot of lines starting with 'M', but nothing else. (There may be a line beginning with a space, immediately preceding the end line. This is generated by a [harmless] off-by-one error in the test conditions of standard uuencode. Since it only results in 3 extra bytes, I guess no one has ever bothered to fix it.) The easier thing to do is to grab the sources for the ST uuencode/uudecode programs and install the programs on your Unix machine. They run fine, and then you never have to worry about those includes ever again. -- / /_ , ,_. Howard Chu / /(_/(__ University of Michigan / Computing Center College of LS&A ' Unix Project Information Systems