Thanks
Mykle
TOS error messages
------------------
message no. meaning of message
----------- ------------------
1 general error
2 disk drive not ready
3 unknown command
4 CRC error- disk checksum wrong
5 bad request
6 seek error- track not found
7 unknown media- bootsector wrong
8 sector not found
9 out of paper
10 write fault
11 read fault
12 general error
13 disk write protected
14 media change detected
15 unknown device
16 bad sector (verify)
17 insert other disk (request)
18 insert disk
19 device not responding
32 invalid function number
33 file not found
34 path not found
35 too many open files
36 access denied
37 invalid handle
39 out of memory
40 invalid memory block address
46 invalid drive specification
48 cross device rename (not the same drive)
49 no more files
58 record is locked - (file locking and network)
59 no such lock (unlock an unlocked record)
64 GEMDOS range error- seek wrong?
65 GEMDOS internal error
66 invalid executable file format
67 memory block growth failure
80 too many symbolic links
200 mount point crossed (indicator)
BOMBS and what they mean
------------------------
no. of bombs explanation
------------ -----------
1 not applicable
2 bus error (user does something the ST doesn't
permit)
3 address error (usually error in program)
4 illegal instruction (two prgs using same memory
space)
5 division with zero
6 CHK instructional error
7 TRAPV instructional error (usually ROM error)
8 conflict with a privileged command
9 trace vector error
10 line 1010 instruction- line 'a' error
11 line 1111 instruction- line 'f' error
12 not applicable, reserved
13 FPU protocol violation (TT/Falcon)
14 format error
15 unitialized interrupt vector
16-23 not applicable, reserved
24 vector 24 error (might be MC68901 and/or GLUE
chip)
25-31 auto-vector interrupts
32-47 TRAP exception Vectors
48-55 MC68881 FPU exception vectors
56-63 MC68851 MMU exception vectors
64-79 MC68901 MFP vectors
80-95 MC68901 MFP vectors (TT only)
96-111 Zilog 86C30 SCC vectors (MegaSTE/TT/Falcon only)
112-255 undefined
** A large number of bombs might be the total of several errors.
Part of this information has been taken from the book
"The Atari A-Z" (1995, Linnhe computing) with kind permission
from the author; Mark S. Baines (msba...@cix.compulink.co.uk).
Compiled by Hallvard Tangeraas (hall...@sn.no) 24-June-1996
>After d/l Atari software thru a Mac the Atari gives me this message
>TOS Error # 35. Can someone tell me what this means?
Not sure what it means, and I have NO experience of doing this (hence
absolutely NO guarantees and everything is at your risk...), but I do
remember a discussion here some time ago about problems with files
that had been downloaded on Macs. All the following is from memory:
IIRC the problem is that the Mac adds in something to the file header
(the resource fork? - something to do with Mac icon management, and
the reason why Mac files have to be binhexed to survive storage intact
on non-Mac filesystems). IIRC (again!), the solution (at least in some
cases) is to rename the file from the Atari desktop once you have it
transferred over. You can then rename it back if necessary, but the
process of renaming seems to sort out whatever got mangled.
HTH - might be worth a try anyway,
John
__
John Whalley | UMRA: 60/35/3 M B+ G++ ?A L++ I- S- P++ CH0
jo...@whalley.demon.co.uk | Tum-te-tum-te-tum-te-tum Tum-te-tum-te-tum-tum
Everyman men's workshops: http://www.netlink.co.uk/users/everyman/
Personal home page: http://www.whalley.demon.co.uk/
This means that the content of the file length field in
the file header is not the same as the physical length. This
happens when converting binaries like ascii text (cr-crlf etc.)
or when the trnsfer program alters the file length (xmodem).
Ciao,
Till
: >> After d/l Atari software thru a Mac the Atari gives me this
: >> message TOS Error # 35. Can someone tell me what this
: >> means?
TH> : That error # can mean different things. More than likely
TH> the file is : corrupt. Does your computer have enough memory
TH> to run the program?
TH> This means that the content of the file length field in
TH> the file header is not the same as the physical length. This
TH> happens when converting binaries like ascii text (cr-crlf
TH> etc.) or when the trnsfer program alters the file length
TH> (xmodem).
I've also found that TOS error #35 appears very often when the programs don't
work with the TOS version in the computer, so if the program uses shortcuts
instead of "legal" jumps it will crash on TOS-versions that have been bug-fixed
or enhanced since the version the program was written on.
Best regards,
Claes
************ New Equipment: Philips CDD2000 CD-writer ************
e-mail cl...@dada.ct.se * Atari Falcon 030/36MHz+16MB+5.5GB+Zip
fidonet 2:200/136.5 * 6.7*CD+UPS+OL400+Samsung17GLsi+USR33600
fujinet 7:102/105.5 * Cubase Audio+FDI+JAM8+MO4+various synths
nest 90:1102/116.5 * These are essential working tools in my
saknet 79:121/103.5 * recording studio-with many other uses also
******************************************************************