Hi,
The
OS 3.9 FAQ states this:
...the ramlib problem is caused by third-party libraries performing too complicated/stack-hungry tasks (opening other diskresident libs) within their init function. These libraries are therefore breaking certain programming rules; and it's not a bug in ramlib itself.
Not sure if that helps! :-?
- Ali
