Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!usc!hacgate!gryphon!jdm
From: jdm@gryphon.COM (John Mesiavech)
Newsgroups: comp.sys.amiga
Subject: Re: atari st
Summary: Don't worry about it, it don't work nohow.
Message-ID: <21472@gryphon.COM>
Date: 26 Oct 89 11:00:41 GMT
References: <2273@nigel.udel.EDU> <1989Oct23.165531.18529@uunet!unhd>
Reply-To: jdm@gryphon.COM (John Mesiavech)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 48

In article <1989Oct23.165531.18529@uunet!unhd> lcc770@unhd.UUCP (Layton C Cote) writes:
>In article <2273@nigel.udel.EDU> C05089%AKRONVM.BITNET@cornellc.cit.cornell.edu (don) writes:
>>ok, ok, here it is the atari st for the amiga, understand you need a dos disk
>> (bla bla bla about the st)
>
>>p.s. you need uuencode and warp to get this one, and after uudecodeing it
>               ^^^^^^^^
>	      you meant uudecode, of course, right?
>
>>you must rename it i called it atari.warp and it should be atari.wrp!
>
>I tried multiple times to get this file to warp properly, but no luck...
>Has anyone managed to uudecode and warp write this properly?
>I tried uudecoding it both on our unix(VAX) system where it was posted
>and on ami, and the uudecoded files were both the same size,  which was
>32170 bytes.  (fine so far)  
>   Next after the "short file" message from uudecodeing it, I renamed

Being that I've gotten it to unWarp properly, think that the "short file"
message should be teling you something.  Our Xenix UUDECODE and
a native Amiga UUDECODE both had no troubles with the file, which came
out to 32039 bytes.  Looks like you got some extra junk there.

At any rate, it doesn't work.  Took it to a local store that sells both
Amiga and Atari ST, tried it out with an ST PD disk that they had.
The disk was bootable (saw it boot on a 520ST).
 
When the emulator booted, it came up with a dark maroon background and 
medium blue text (yecchy preferences).  It gave about three screens worth 
of info, the said "Wait for screen to blank, then insert Atari disk".
 
(note well the ambiguity there...TOS disk or oldstyle ROM disk?)

So, waited for a bit, and got a dark blue screen with the disk drive
going (tick, tick).  Since these were the conditions specified in
the startup screens for Atari disk insertion (blank screen, drive 
chatter), inserted Atari disk and got a Guru.
 
So, tried again.  Same thing happened.  It's bogus.
 
Tried it with two Amigas (a 500 and a 2000HD).
 
Only problem may have been if it needs more than 1MB.  If so, why?
and why wouldn't it be documented?
 
John

(.sig under reconstruction)