[comp.sys.atari.st] TOS ERROR #35: What is it?

dddean@bluemoon.uucp (David D. Dean) (06/24/91)

Hello:

        A while ago, I went to use my FLASH program to call the local 
boards like I always do, but this time; I got a TOS ERROR #35 message and 
couldn't use this program.  Frustrated, I returned to the store I bought 
this program from, and they said I'd have to send it to the company.  So I 
did... I am now using the VT52 emulator that comes with the USA Laguage 
disk.

I am sure that when I ask this, some people will no doubt wonder too:

        Wbat does the TOS ERROR #35 mean?  I looked up the error number, 
but found it no where in any of the manuals.  

Thanks in advance for any replies.


You can send any replies to:
David D. Dean, President       David D. Dean, Vice Chairman
Explorer Post 891              Exploring Officer's Association
AT&T Systems/Bell Labs         Central Ohio Council
dddean@bluemoon.uucp           Columbus, OH  43227

**** Any opinions are that of the author, and NOT of AT&T ****

seimet@rhrk.uni-kl.de (Uwe Seimet [Chemie]) (06/24/91)

dddean@bluemoon.uucp (David D. Dean) writes:

	... stuff deleted ...

>        Wbat does the TOS ERROR #35 mean?  I looked up the error number, 
>but found it no where in any of the manuals.  

If you get this error, your program file is corrupted, i.e. TOS does not
recognize it any more as executable. A reason for this is a bad program
header or a fatal error in the relocation table.

********************************************************
*              Uwe Seimet                              *
*              seimet@rhrk.uni-kl.de                   *
*------------------------------------------------------*
* I hate this machine, I wish that they would sell it. *
* It doesn't do what I want but only what I tell it.   *
* (Programmer's lament)                                *
********************************************************

Bob_BobR_Retelle@cup.portal.com (06/26/91)

TOS Error 35 generally means the program is corrupted somehow...
 
Your FLASH disk has probably developed a bad sector which renders the
program useless...
 
The best defense against this happening is to back up every disk and only
run programs from the backup disk...  if anything happens to the programs
on that disk, you can always copy the original disk onto a new disk and
use that...
 
BobR
 
(Sorry for not quoting the original message, but my ST has died, and
I'm being forced to use an IBM system with PROCOMM..  about 10% the
functionality of an ST with FLASH...)