🚀 go-pugleaf

We can't diagnose your problem without more information.  Can you
tell us everything you do exactly in sequence right down to how you
move the file from the net to whatever and how you prepare the file for
decoding.  I have tried uudecode several times and it has always worked.
If we get to the bottom of this in public alot of people should benefit.

Whatever you do - do not destroy the original files - there is still
hope.


"Where there is a will there is a way"
                   - mothers all across America


P.S.  include all equipment involved

One last thing - it is very important that we all get together and figure
out this UUDECODE problem because a whole lot more UUENCODED stuff is
coming down the pike real soon now!

> 
> Has anyone been able to move uuencoded files from the net to a 520ST and
> get them to run? 
	I use uudecode all the time (the one posted about November with
atari ifdefs), and have had no problem with any uuencoded programs, both
with and without the ROM TOS.
--
Dr. Bruce E. Wampler
University of New Mexico
Department of Computer Science
Albuquerque, NM 87131

..{ucbvax | seismo!gatech | ihnp4!lanl}!unmvax!wampler

>
>Has anyone been able to move uuencoded files from the net to a 520ST and
>get them to run?
>

With the exception of the first uuencoded posting of micro-emacs, I've
had no difficulty in getting the uuencoded stuff to run on my ST.  In
case you are curious, I have been using the uudecode on our UNIX (tm, etc. :-)
system - not the uudecode posted a while back to run on the ST - and
then downloading the binary files to my ST using XMODEM protocol.

--
Richard E. Sansom
TRW Electronics and Defense Sector
...{decvax,ucbvax,ihnp4}!trwrb!trwrba!sansom

In article <118@druxu.UUCP> rwb@druxu.UUCP (BlackR) writes:
>
>Has anyone been able to move uuencoded files from the net to a 520ST and
>get them to run?  I've downloaded the assembler, the clock, and micro
>EMACS, uudecoded them and tried to run them.  The screen clears (micro
>EMACS asks for parameters since it is a .TTP file), the disk whirls,
>then I get the desk top back.  I would suspect the uudecode program, but
>a dump of the decoded files show character strings that are readable among
>a lot of stuff that is not readable.  Since I just received the TOS ROMs, I'm
>going to install those and see if they make any difference.  Any other
>suggestions?

You probably haven't yet removed the desk accessories. They take up bunches
of memory, and if the ST doesn't have enough memory to run a program, it
just returns to the desktop. Make a copy of your system disk and remove
anything ending with ".ACC", then boot up with that disk and try again.

-- 

+----------------------------------------------------------------------------+
|Whatever I write are not the opinions or policies of Digital Research, Inc.,|
|and probably won't be in the foreseeable future.                            |
+----------------------------------------------------------------------------+

Bruce Holloway

....!ucbvax!hplabs!amdahl!drivax!holloway
(I'm not THAT Bruce Holloway, I'm the other one.)

In article <118@druxu.UUCP> rwb@druxu.UUCP writes:
> Has anyone been able to move uuencoded files from the net to a 520ST and
> get them to run?  I've downloaded the assembler, the clock, and micro
> EMACS, uudecoded them and tried to run them.  The screen clears (micro
> EMACS asks for parameters since it is a .TTP file), the disk whirls,
> then I get the desk top back.

This can happen if you uudecode first, and then transfer the files with
kermit without using image mode. Then extra characters get inserted in the
binary, and anything can happen.

Steven Pemberton, CWI, Amsterdam; steven@mcvax.uucp