User avatar

Posted Fri Jul 03, 2020 10:43 am

Look in your startup-sequence, if there is anything started that is running in the background. Remove everything that is non-essential and try to reproduce the problem.

It *might* as well be some hardware issue. As I wrote above, the gurus are in almost all cases consequences of other problems, like programming errors (overwriting memory, bad pointers, etc etc), bad memory, you name it. They are really only helpful to the programmer.

Is the other number (#81...5.XXXXXXXX, I mean the XXXX here) always the same?

User avatar

Posted Mon Sep 07, 2020 5:12 pm

Well long time since I posted on this topic but today captured some info. A500 not in heavy use most of summer now I am back into it a little. Today was making a spreadsheet in Maxiplan Plus.. Guru two times (1st one lost all work errrr)... They are

1st time - 00000004.00C027DA
2nd time -0000000B.00C05840

This good learning exercise for me.. Thoughts?


User avatar

Posted Sat Mar 27, 2021 8:45 am

A non-very well known fact: Kickstarts have a serial port debugger built-in.

If the crash is recoverable (guru before/without reboot), right mouse launches the debugger.

If the crash is non-recoverable (blinking led + reboot + guru), it is possible to enter the debugger by sending DEL character on serial port during the blinking. Right mouse on guru does nothing special on these.

Alternatively, if workbench is loaded with loadwb -debug, there's an extra menu on top of the screen to enter the debugger anytime.

My AmigaXfer serial transfer tool uses this debugger for transferring disks and files.

Return to “Software”