According to what I've read, ramlib loads shared libraries.
Yep... It seems to. As I understand it, it is sort of a "load resident" for libraries.
As for why it's crashing, I would guess that there is a damaged/missing/invalid version library in your LIBS: directory.
Could also be a stack issue, as mentioned. Could also be a kickstart relocator or program such as "PrepEmu" acting up.
As an anecdote, though... The 8000 000B guru is often-times related to processor functions. (early 68000-only code hitting a 68030, for example) Personally, I'd make sure you have the proper versions of all libraries, and didn't accidently use a PPC library or a very old version of a library, instead of the proper one.
