Re: TOS ERROR 39?
From: Robert Krynak (ah292@cleveland.Freenet.Edu)
Date: 06/05/91-08:02:15 PM Z
- Next message by date: Russ Ackerman: "HARD DRIVE"
- Previous message by date: Chris Thomas: "Re: TOS ERROR 39?"
- Maybe in reply to: Luis G. Rodriguez: "TOS ERROR 39?"
- Return to Index: Sort by: [ date ] [ author ] [ thread ] [ subject ]
From: ah292@cleveland.Freenet.Edu (Robert Krynak) Subject: Re: TOS ERROR 39? Date: Wed Jun 5 20:02:15 1991 Ever wondered what those TOS error messages and 'bombs' on your monitor signified? Below is a letter, originally written by Darryl May, that John Townsend of Atari posted on GEnie in January to provide some answers. This letter also appeared in the June 1988 issue of _Current Notes_ (122 N. Johnson Rd., Sterling, VA 22170). Dear ATARI customer, The following is an official list of the errors that can appear while you are operating your ST computer. This first list gives you the GEM error messages: Error description GEM Error code ========================================= OK (no error)....................0 Fundamental error................1 Drive not ready..................2 Unknown command..................3 CRC error........................4 Bad request......................5 Seek error.......................6 Unknown media....................7 Sector not found.................8 No paper.........................9 Write fault.....................10 Read fault......................11 General error...................12 Write protect...................13 Media change....................14 Unknown device..................15 Bad sectors on format...........16 Insert other disk...............17 Invalid function number.........32 File not found..................33 Path not found..................34 No handles left.................35 Access denied...................36 Invalid handle..................37 Insufficient memory.............39 Invalid memory block address....40 Invalid drive specified.........46 No more files...................49 Range error.....................64 Internal error..................65 Invalid program load format.....66 Those bombs that appear on your screen are error messages from the 68000 micro-processor. Number Description of bombs =========================================== Reset: Initial PC2...............1 Bus Error........................2 Address Error....................3 Illegal Instruction..............4 Zero Divide......................5 CHK Instruction..................6 TRAPV Instruction................7 Privilege Violation..............8 Trace............................9 Line 1010 Emulator..............10 Line 1111 Emulator..............11 [unassigned, reserved]..........12 [unassigned, reserved]..........13 Format Error....................14 Uninitialized Interrupt Vector..15 [unassigned, reserved].......16-23 Spurious Interrupt..............24 Level 1 Interrupt Autovector....25 Level 2 Interrupt Autovector....26 Level 3 Interrupt Autovector....27 Level 4 Interrupt Autovector....28 Level 5 Interrupt Autovector....29 Level 6 Interrupt Autovector....30 Level 7 Interrupt Autovector....31 Trap Instruction Vectors.....32-47 [unassigned, reserved].......48-63 User Interrupt Vectors......64-255 Darryl May Tech Specialist --
- Next message by date: Russ Ackerman: "HARD DRIVE"
- Previous message by date: Chris Thomas: "Re: TOS ERROR 39?"
- Maybe in reply to: Luis G. Rodriguez: "TOS ERROR 39?"
----------------------------------------- Return to message index