Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!nikhefh!t68
From: t68@nikhefh.UUCP (Jos Vermaseren)
Newsgroups: comp.sys.atari.st
Subject: Re: TOS ERRORS.
Message-ID: <277@nikhefh.UUCP>
Date: Tue, 19-May-87 10:24:48 EDT
Article-I.D.: nikhefh.277
Posted: Tue May 19 10:24:48 1987
Date-Received: Wed, 20-May-87 05:52:40 EDT
References: <407@its63b.ed.ac.uk>
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 16
Summary: TOS ERROR 35

In article <407@its63b.ed.ac.uk>, csan@its63b.ed.ac.uk (Andie) writes:
> Following a large number of requests, I have decided to post this rather
> than email everyone ...........
> There may be ones I have missed out and perhaps someone in the know could
> let me know . Why -35 is returned when a corrupt program is attempted I
> have no idea.
> 
The error number -66 indicates an invalid program format. In the old
MS-DOS notation this is error number 35. When porting GEM/AES they must
have forgotten to switch the error messages around, or at least this one.
In short: TOS error #35 is usually indicating a corrupt program but I
think I saw it once when I was really out of handles, so the other error
number got ported properly.

Jos Vermaseren
T68@nikhefh.uucp