Sponsored Content
Full Discussion: C
Top Forums Programming C Post 7657 by loadc on Friday 28th of September 2001 10:47:58 PM
Old 09-28-2001
EEEKKK!!!

Okay, I've wanted to do this as well-

Here is the trick the VM mainframeers taught me, it actually did work, but keep in mind, I did this on a VM CP command env, using pipes and some VM tools translating to EBCDIC, so go easy if this doesn't translate well...

We took the binary file and converted to hex sing a converter in the editor on VM, we then took the hex and translated to EBCDIC (ascii should be a reasonable change from there, as well), and read what we could of the file.

Keep in mind, teh compiler that put the file together is going to have done some things to the file, you are WAY better off with a good de-compiler, but you didn't hear that from me...

Whatever you get back from either operation, it may not be an exact copy of the source code, unless you have a lot of time, knowledge of EXACTLY what tools were used by the developers, and the skill or luck to find a de-compiler that knows what the compiler did.


Or, maybe I'm totally out of my tree and I'm talking out of my knothole...



loadc
 
uuencode(1c)															      uuencode(1c)

Name
       uuencode, uudecode - encode/decode a binary file for transmission via mail

Syntax
       uuencode [file] remotedest | mail sys1!sys2!..!decode
       uudecode [file]

Description
       The  and  commands are used to send a binary file by uucp (or other) mail.  This combination can be used over indirect mail links even when
       is not available.

       The command takes the named source file (default standard input) and produces an encoded version on the standard output.  The encoding uses
       only printing ASCII characters, and includes the mode of the file and the remotedest for recreation on the remote system.

       The  command  reads  an	encoded file, strips off any leading and trailing lines added by mailers, and recreates the original file with the
       specified mode and name.

       The intent is that all mail to the user ``decode'' should be filtered through the program.  This way  the  file	is  created  automatically
       without	human  intervention.   This  is possible on the uucp network by either using or by making be a link to instead of In each case, an
       alias must be created in a master file to get the automatic invocation of

       If these facilities are not available, the file can be sent to a user on the remote machine who can uudecode it manually.

       The encode file has an ordinary text form and can be edited by any text editor to change the mode or remote name.

Restrictions
       The file is expanded by 35% (3 bytes become 4 plus control information) causing it to take longer to transmit.

       The user on the remote system who is invoking (often must have write permission on the specified file.

See Also
       mail(1), uucp(1c), uusend(1c), uux(1c), uuencode(5)

																      uuencode(1c)
All times are GMT -4. The time now is 02:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy