Difference between revisions of "Guru codes"
EvilSpammer (talk | contribs) |
m (→System software failures) |
||
(One intermediate revision by one other user not shown) | |||
Line 5: | Line 5: | ||
− | + | ==Software failures== | |
− | + | <div style=" | |
background-color: #000; | background-color: #000; | ||
border: 2px solid #f00; | border: 2px solid #f00; | ||
Line 16: | Line 16: | ||
max-width: 350px; | max-width: 350px; | ||
white-space: nowrap; | white-space: nowrap; | ||
− | + | "> | |
Software failure. Press left mouse button to continue. | Software failure. Press left mouse button to continue. | ||
Guru Meditation #00000003.000027D2 | Guru Meditation #00000003.000027D2 | ||
− | + | </div> | |
===Trap numbers=== | ===Trap numbers=== | ||
− | + | <table> | |
− | + | <tr><td>2</td><td>Bus error(hardware)</td></tr> | |
− | + | <tr><td>3</td><td>Adress error(word access on odd byte boundary - frequent!)</td></tr> | |
− | + | <tr><td>4</td><td>Illegal instruction</td></tr> | |
− | + | <tr><td>5</td><td>Divide by zero</td></tr> | |
− | + | <tr><td>6</td><td>CHK instruction</td></tr> | |
− | + | <tr><td>7</td><td>TRAPV instruction</td></tr> | |
− | + | <tr><td>8</td><td>Privelege violation</td></tr> | |
− | + | <tr><td>9</td><td>Trace</td></tr> | |
− | + | <tr><td>A</td><td>Opcode 1010 emulation</td></tr> | |
− | + | <tr><td>B</td><td>Opcode 1111 emulation</td></tr> | |
− | + | <tr><td>20-2F</td><td>TRAP instruction</td></tr> | |
− | + | </table> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==System software failures== | ==System software failures== | ||
Line 66: | Line 58: | ||
− | Here it | + | Here it's different. The first number is divided into three parts: |
A, B, and C. A is the two first bytes, B is the next two | A, B, and C. A is the two first bytes, B is the next two | ||
bytes, and finally C is the four last bytes. | bytes, and finally C is the four last bytes. |
Latest revision as of 15:36, 8 September 2016
The gurus are divided into two kinds:
- Software failures
- System software failures
Software failures
Software failure. Press left mouse button to continue.
Guru Meditation #00000003.000027D2
Trap numbers
2 | Bus error(hardware) |
3 | Adress error(word access on odd byte boundary - frequent!) |
4 | Illegal instruction |
5 | Divide by zero |
6 | CHK instruction |
7 | TRAPV instruction |
8 | Privelege violation |
9 | Trace |
A | Opcode 1010 emulation |
B | Opcode 1111 emulation |
20-2F | TRAP instruction |
System software failures
Not enough memory. Press left mouse button to continue.
Guru Meditation #02010009.0007D6B8
Here it's different. The first number is divided into three parts:
A, B, and C. A is the two first bytes, B is the next two
bytes, and finally C is the four last bytes.
A(affected part of the system-software)
1 | Exec library |
2 | Graphics library |
3 | Layers library |
4 | Intuition library |
5 | Maths library |
6 | Clist library |
7 | AmigaDOS library |
8 | RAM Handler library |
9 | Icons library |
10 | Audio device |
11 | Console device |
12 | Game-port device |
13 | Keyboard device |
14 | Trackdisk device |
15 | Timer device |
20 | CIA resource |
21 | Disk resource |
22 | Misc resource |
30 | Bootstrap |
31 | Workbench |
B(general cause)
1 | No memory |
2 | Unable to creat library |
3 | Unable to open library |
4 | Unable to open device |
5 | Unable to open resource |
6 | Input/Output error |
Part C is viewable in the Exec.library-instruction alert. This allocates more specific where in the system-software-part the problem is.
The numbers after the dot is the adress in the memory where the failure appeared.