Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!orsvax1!pyrnj!caip!daemon
From: local-info-amiga-request@ics.UCI.EDU
Newsgroups: net.micro.amiga
Subject: Re: encoded source codes
Message-ID: <2007@caip.RUTGERS.EDU>
Date: Tue, 22-Apr-86 14:35:03 EST
Article-I.D.: caip.2007
Posted: Tue Apr 22 14:35:03 1986
Date-Received: Thu, 24-Apr-86 00:09:37 EST
Sender: daemon@caip.RUTGERS.EDU
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 24

From: Mike Schwartz <3comvax!mykes@caip.rutgers.edu>

In article <760@ccird2.UUCP> rb@ccird2.UUCP (Rex Ballard) writes:
>There have been several public domain versions of uuencode and
>uudecode posted to net.micro, net.micro.atari and (I believe)
>net.sources.  This is the preferred format for exchanging
>atari binaries because they can be converted on the unix host
>or on the micro itself.
>
>Now that landon dyer has been so kind as to submit an atari->amiga
>translator, there are a number of atari binaries already available
>that could be used on the amiga.  All you need is the above mentioned
>uudecode.

I realize that both the ST and the Amiga use 68000 processoros, but I find 
it hard to believe that ST binaries will run on the Amiga.  The operating
systems are real different, and the Amiga hardware does things in a 
much different way than the ST.  Landon Dyer's atari->amiga translator
is great if you are writing code for the ST, using the Amiga to edit and
compile.  

I saved away the Atari-Amiga translator, but have not unpacked it yet.  I
figure it might be a uuencoded program to erase my floppies or something
(read net.sources.d for more related topics).