jimdean@bnr.ca (Jim Dean) (12/19/90)
I recently downloaded the IIgs uuencode/uudecode programs from BITFTP, files APPLE2-L 90-01877 and APPLE2-L 90-01878. After unshrinking, I find that I have the source for a man page, two "c" source files, and two "EXE" files. I am trusting these EXE files to work since I don't have a C compiler. I put the EXE files in my PROSEL commands directory so I can run them from the ProSel-16 shell. However, here I get stuck. I can't get uudecode to work. Assuming a uuencoded file called "uufile, I enter the ProSel-16 shell command line and I have tried things like "uudecode uufile", "uudecode < uufile", and "uudecode < uufile > newfile". Nothing seems to work. All I get is a blank screen that accepts input but doesn't do anything, requiring the ol' three-finger reboot. Can anybody tell me what I have to do to get things to work? (ROM01 with 1.5M GS-RAM, 40M SeaGate home-built hard disk). -- Jim Dean Bell-Northern Research, Ltd |"Dear God, Please give Ph.:(613)763-2135 P.O. Box 3511, Station C | a bald guy a break." Fax:(613)763-8825 Ottawa, Ontario, Canada, K1Y 4H7| -- Homer Simpson Bitnet/NETNORTH: jimdean@bnr.ca
-Rich-@cup.portal.com (Richard Sherman Payne) (12/20/90)
>I recently downloaded the IIgs uuencode/uudecode programs from BITFTP, >files APPLE2-L 90-01877 and APPLE2-L 90-01878. After unshrinking, >I find that I have the source for a man page, two "c" source files, >and two "EXE" files. I am trusting these EXE files to work since I >don't have a C compiler. > >I put the EXE files in my PROSEL commands directory so I can run them >from the ProSel-16 shell. > >However, here I get stuck. I can't get uudecode to work. Assuming a >uuencoded file called "uufile, I enter the ProSel-16 shell command >line and I have tried things like "uudecode uufile", >"uudecode < uufile", and "uudecode < uufile > newfile". Nothing seems >to work. All I get is a blank screen that accepts input but doesn't >do anything, requiring the ol' three-finger reboot. > If these are the same files that I have, they work from the Orca shell. You enter :uudecode <filename>, and it decodes properly. I own Prosel also, but have not tried it. A few cautions, files downloaded from unix systems must have the linefeeds stripped off. And the headers and footers must be removed. Some editors will not show the linefeeds, so you may not notice them, but if they are there, you will not get anything but a 1 or 2 block output file. And large files will take a but to decode, with no indications that it is working. There was also a uudecode only posted with source, but the coding is horrible, but does compile. I found obvious problems line a missing include file (strings.h), and that it looped to the end of the file on the test for the begin. I have gotten it working, but not correctly. If I do get it working, I will repost it. >Can anybody tell me what I have to do to get things to work? >(ROM01 with 1.5M GS-RAM, 40M SeaGate home-built hard disk). > >-- >Jim Dean Bell-Northern Research, Ltd |"Dear God, Please give >Ph.:(613)763-2135 P.O. Box 3511, Station C | a bald guy a break." >Fax:(613)763-8825 Ottawa, Ontario, Canada, K1Y 4H7| -- Homer Simpson >Bitnet/NETNORTH: jimdean@bnr.ca Rich -Rich-@cup.portal.com