File transfer trouble between mac and aux?

[Bob Lantz]

rprohask at orion.oac.uci.edu (Robert Prohaska) writes:

[Frequently Asked Question # 117:]

>What does it take to move a binary file from the mac os to aux?  Does 
>drag copying work in general (I know it works sometimes)?  The file
>does not acquire the usual icon of a non executable binary file and fails 
>checksum tests on the aux side, but I don't know how to test it on 
>the mac side.

;-) I expect most people on the newsgroup now know that A/UX converts
Macintosh files of type 'TEXT' to Unix text files, by changing carriage
returns to line feeds.  And, vice versa.  This occurs when you drag files
between Macintosh and Unix volumes.  If you don't want this to 
occur, the easiest thing to do is to change the file's type to something
other than 'TEXT.' This can be accomplished using setfile(1) or (if you
have it) ResEdit, for example.

Another way to move a file from a Mac OS machine to an A/UX machine is
to ftp it (e.g. using NCSA Telnet or SU-MacIP.)  You can even transfer
Macintosh files this way, if you use MacBinary or BinHex format file
transfer, and convert it back on the A/UX side using fcnvt(1).

>thanks, 

>bob prohaska

sure,

Bob

p.s. This is documented in the now-famous manual _A/UX Toolbox: Macintosh
     ROM Interface_.