Ramlib error while booting up

[MozzerFan]

@Matthey

Nope, you can check it with scout.
Goto tasks and doubleclick on ramlib.
The stacksize is still 2k without mcpramlibpatch (or a similiar patch).

[Amiduffer]

@MozzerFan

@Amiduffer

I would recommend staying with AmigaOS3.9 especially if you have a RTG gfx board. If you don't have a RTG board, I would recommend you get one. It makes a huge difference even on a 68030.

I have a C64/3D RTG board, but without a Buster 11, it doesn't work in the A3000.

[matthey]

@MozzerFan

I checked Scout and my ramlib stack is still set to 2k. I am using all the latest patches to a custom 3.9 BlizKicked ROM (MAPROM). I don't have stability issues. Did you get crashes from the ramlib before installing the patch? I'll have to dl and read MCP's docs now.

[MozzerFan]

@Matthey

I can vaguely recall my system giving ramlib errors with Amidock.

MCP ramlibpatch used to be included with MCP, but with the latest releases it's not included anymore.
You can find it in the RTGMaster archive on aminet though.

A similiar module is included in the blizkick archive, and the romfixes module of blizkick also includes this patch.

Anyway, it can't hurt to give it a try when your system is
giving you this error.

[matthey]

I have a C64/3D RTG board, but without a Buster 11, it doesn't work in the A3000.

I'm pretty sure I ran my CV64/3D in my 3000 without Buster 11. It was rock solid on my Amiga although I did upgrade to the Buster 11 later. I used P96 and it was more stable and bug free than the Voodoo driver I use now. The boards performance matches the 3000 well and provides a huge improvement over ECS. Maybe the problem you are having with the crashes is related to the CV64/3D not working. I think it's time to do some cleaning. You should also push down on all the socketed chips on the motherboard, especially memory chips. They work up over time from heat cycling. It could also be the power supply getting old but I would try everything else first. You might blow out the power supply though.

[matthey]

@MozzerFan

Thanks, I'll look into the ramlib patch. I thought the BlizKick romfixes was unnecessary with the latest patched AmigaOS 3.9 modules. I'll have another look.

[Amiduffer]

I'm pretty sure I ran my CV64/3D in my 3000 without Buster 11. It was rock solid on my Amiga although I did upgrade to the Buster 11 later. I used P96 and it was more stable and bug free than the Voodoo driver I use now. The boards performance matches the 3000 well and provides a huge improvement over ECS. Maybe the problem you are having with the crashes is related to the CV64/3D not working. I think it's time to do some cleaning. You should also push down on all the socketed chips on the motherboard, especially memory chips. They work up over time from heat cycling. It could also be the power supply getting old but I would try everything else first. You might blow out the power supply though.

The CV64/3D runs fine in my A4000, so I know it works. I originally bought it for the A3k, but, it refused to work in it, and from the info available online, I concluded that the Buster was the issue. All socketed chips have been firmly pushed down and I've cleaned up a lot of the dust.

[matthey]

@Amiduffer

Any change in the errors?

A Buster 11 may be worth tracking down. It fixes some bugs and it's faster at Zorro transfers.

[platon42]

Just comment everything out in s:startup-sequence & s:user-startup that might make ramlib crash, by putting a ";" (without the "") infront of the programs. After this is done and you run startup-sequence 'light', if it doesn't crash anymore you can enable line by line again.

x303

An easier approach is probably to boot without startup-sequence, enter the line

"set echo on"

and

"execute s:startup-sequence"

and see at which line the ramlib guru comes up.