@Cymric
'unaligned address' Guru, indicating on the 68010- that a program has tried to access a program instruction at an odd address (Bad) and on the 68020+ that the stack was pointing at an odd address (VERY Bad).
Not quite. On 68000 and 68010 this is caused by using WORD or LONG access on odd address or by jumping to odd address or by odd supervisor stackpointer on exception.
On 68020+ this is only caused by instruction prefetch attempt from odd address (jump/branch to odd address) or by odd supervisor stackpointer during exception.
- an unpatched ramlib.handler (can be alleviated with SetPatch, IIRC)
It's no handler and SetPatch doesn't fix it (at least upto AOS 3.5, IIRC OS 3.9 SetPatch does fix it).
MMULib.lha MMULib/Fixes/RamLibFix (or MCPRamLibPatch) fixes this problem.
