Conference 7.286::atarist

	--- This description of ST bombs was posted to usenet some time ago ---

Here's a list of what the various numbers of bombs mean...
 
 1 - Impossible.  If you get 1 bomb, take your ST to a repair shop.
 2 - Bus error.  This means you have tried to access memory outside the
     computer's valid address space (or tried to access a protected area
     in user mode).
 3 - Address error.  This usually results from doing a word or long
     operation on an odd byte boundary.
 4 - Illegal instruction.  You figure it out.
 5 - Divide by 0.  Usually generated by the divs and divu instructions,
     though if I recall correctly some others can cause it as well.
 6 - CHK instruction trap.  If a chk instruction returns an illegal value,
     this trap is executed.  Chk is actually pretty dumb, in my opinion,
     unless you're using Pascal.
 7 - TRAPV instruction.  You get this by executing a trapv instruction
     when the overflow bit is set.  Most programs don't use trapv, so this
     one shouldn't pop up much.
 8 - Privilege violation.  This one appears when a supervisor-only instruction
     is encountered in user mode.
 9 - Trace.  If you've got the trace bit set, this trap will occur after
     each instruction.  Great for debuggers.
10 - Line-A.  You shouldn't get this, as it's the interface Atari uses to get
     to graphics routines.
11 - Line-F.  This is supposed to be a hook for math coprocessors, but Atari
     (DRI?) used it for GEM instead.  I would have preferred a coprocessor.
 
The others are pretty much undefined; if you get one, something weird is
going on.  From 32 to 47 bombs mean that you made a trap call whose vector
wasn't set.
 
Note that the number of bombs is equivalent to the 68000 exception number.

	--- end of usenet excerpt ---

Note that if the ST gets an error while (or just after) it is drawing bombs,
it will sometimes draw bombs for the 2nd error as well (on the "same line").
For example if you see 11 bombs it is most likely that two errors occured, for
example; 5 bombs followed by 6 bombs.

	Ray

	--- Again this list of TOS errors is from a usenet posting ---

Following a large number of requests, I have decided to post this rather
than email everyone
 
 
Tos Error Number 		Meaning
----------------		-------
	  0			Ok, No error
	 -1			General error
	 -2			Drive not ready
	 -3			Unknown command
	 -4			CRC error
	 -5			Bad request (invalid command)
	 -7			Seek error (track not found)
	 -8			Sector not found
	 -9			Printer error (no paper?)
	-10			Write error
	-11			Read error
	-12			General error
	-13			Disk write-protected
	-14			Disk was changed
	-15			Unknown device
	-16			Bad sector encountered during verify
	-17			No disk in drive
	-32			Invalid function error
	-33			File not found
	-34			Path not found
	-35			Too many files open
	-36			Access not possible
	-37			Invalid handle number
	-39			Not enough memory
	-40			Invalid memory block address
	-46			Invalid drive spec
	-49			No more files
 
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.
 
I hope this has been of some use.
 
Andie Ness . Department of Computer Science 
              EDINBURGH University.

	--- End of usenet extract ---

    
    Good idea Ray.
    
    Re .2:
    
    I have checked against my own info sources (Atari ST Programmer's
    Reference Guide by Katherine Peel, ST Internals from Abacus, and the
    Dlibs PD C library ERRNO.H definitions) and found the following:-
    
    All disagree with .2 on the meaning of code -7, and list these instead:
    
    	-6	seek error
    	-7	unknown media
    
    The following are additional codes listed:
    
    	-41	insufficient memory
    	-42	insufficient memory
    	-47	invalid operation
    	-48	rename to different drive
    	-64	range error
    	-65	internal error	
    	-66	invalid program format
    	-67	setblock failure
    
    Anyone else care to share their information - presumably the developer's
    kit contains the *definitive* list?
    
    
    Re .1:
    
    47 bombs on the screen - now that's what I call a really chatty error
    message !
    
    Regards, Brian 

    I've a question on an error/informational message I get when I boot up
    my machine, so I thought this note would be the place to ask about it.
    
    I've just bought a 1040STE and when I boot it I get the following:
    
    "ERROR: This STE ROM does not need the patch"
    
    ..the machine then carries on and displays the desktop.
    
    Has anybody seen this before, and is it anything to be worried about ?
    
    
    Paul (based in the UK).
    

    
    The message is not produced by TOS, look at your AUTO-Ordner in the
    boot-drive. There must be some programs like PATCHFIX etc. which are
    loading first. And one of this programs are not necessary!!!
    (After internal version-check the program produce the message!)
    
    RALF
    

    Thanks for the pointer Ralf, I'll have a look at what's on the disk
    this evening...
    
    Paul.