Conference hydra::amiga_v1

    
    You might try  UUENCODE >filename2.uue filename1
    

    The USUAL syntax is:
      uuencode [input-file] output-file
    if the input file is omitted the std-in is used.
    I think that the problem may depond on the program you're using.
    If you compiled it , be sure to have included the definition of
    the target system as an AMIGA !. I went thru the same problems.
    The last version posted around ( not verified yet ) can be found
    on    CESARE::sys$user0:[ledump]uuencode.c

    I was trying to get UUENCODE and UUDECODE to work on the Amiga,
    and I tried to compile and link it using Manx 3.20.  I compiled
    it straight (cc uuencode.c), and linked it using
    ln -lc uuencode.c ram:lib/c.lib ram:lib/m.lib ram:lib/s.lib
    
    I got an error that it couldn't resolve a reference to 
    _sys_err or something like that?  Does anyone know where I can
    link to remove that error?
    
    Derek

Not having the source, or my manx book, a big guess.
Perhaps the program references a global defined by the Lattice compiler?

If so, you'll have to re-work something.

    I went through the whole source, and couldn't find any reference
    at all to _sys_nerr and _sys_errlist, which were the two unresolved
    references.  Once again, if anyone can help please do!
    
    Derek

Here is the Ultrix MAN entry.
I don't know if either the manx or lattice environments support this stuff.
If they don't; and it's in your C code, you've got un-ported code
(or are missing files which stub these entries.)

Anyway, maybe this helps.



                                                        perror(3)



NAME
     perror, sys_errlist, sys_nerr - system error messages

SYNTAX
     perror(s)
     char *s;

     int sys_nerr;
     char *sys_errlist[];

DESCRIPTION
     The perror subroutine produces a short error message on the
         ______
     standard error file describing the last error encountered
     during a call to the system from a C program.  First the
     argument string s is printed, then a colon, then the message
                     _
     and a new-line.  Most usefully, the argument string is the
     name of the program which incurred the error.  The error
     number is taken from the external variable errno which is
                                                _____
     set when errors occur but not cleared when non-erroneous
     calls are made.  For further information, see intro(2).

     To simplify variant formatting of messages, the vector of
     message strings sys_errlist is provided; errno can be used
                     ___ _______              _____
     as an index in this table to get the message string without
     the newline.  The sys_nerr is the number of messages pro-
                       ___ ____
     vided for in the table; it should be checked because new
     error codes may be added to the system before they are added
     to the table.

SEE ALSO
     intro(2), psignal(3)

    
    	I'm having the same problem as .0, but with uudecode. After
    dowloading .uue files to my Amiga I do a "uudecode filename".
    
    	The disk drive light will blink for a couple of seconds, and
    I get the CLI prompt again. No output file produced, no messages.
    I know uudecode is "alive", because if I specify a file not located
    on the directory it will give an appropiate error message. 
    
    	Any ideas on what I'm missing ??
    
    Thanks.

    Most probably the 'nothing happens' is due to trailing <RETURN>'s.
    If you DLL using Kermit in Binary Mode you'll get those ^M at the
    end of each line. To mend the file use an editor such as uEMACS
    and remove all the CRT-M.
    My procedure is as follow:
    uEMACS filexx.uu
    
    ^S ^Q <RETURN> <RETURN>
    ESC <
    ^X ( ^S <RETURN> BACKARROW ^D ^X )
    ^U 10000 ^X E
    ^X ^S ^X ^C

    You file should now be OK !
    NOTE: ^=CONTROL KEY
    Il the file is longer the 10000 lines repeat line starting with
    ^U
    Good luck. !
    

    No problem ...
    
    
    UUENCODE >dev:filename1.UUE dev:filename2 filename3
    
    Where;
    
          >dev:filename1.UUE  is the redirected output to a file of
                              type .UUE on any device
    
          dev:filename2       is the file you want to encode
    
          filename3           is the name given to the file when
                              it is uudecoded (e.g., the name
                              that appears after "begin 777"
    
    Piece of cake.

    Re .8
    
    	Thanks Marco !  It worked perfectly.
    
    Miguel A. Alvarez