Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: LP on May 01, 2003, 12:26:21 AM
-
My Workbench is really bugging me at the time...
Workbench loads fine untill a sertain point were I get this message in a requester:
"
ramlib
program failed at 8000000B
"
The only option is to freeze it or reboot...
What do I do? I get the message approx. 2 times on every startup before it somehow doesn't fail...
HELP!
-
PPC? I think I had that problem with Turboprint... bah! can't remember, nevermind
-
Nope... 68060
What does ramlib do?
-
What does ramlib do?
According to what I've read, ramlib loads shared libraries.
You might try using a program such as StackAttack to raise up the system stack. Stack issues can cause these sort of failures.
-
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.
-
Thanks to all of you guys for helping me out!!!
Keep posting though if these suggestions doesn't work I'll need more good ideas... :-)
Cheers!
-
StackAttack doesn't affect ramlib stack size.
And anyway, according to Thomas Richter, OS 3.9 don't suffer from ramlib stack issues.
quote from MMULib/Fixes/Fixes.readme
-----------------------------------------------------------------------------
RamLibFix
Fixes two bugs in the ramlib process. First of all, ramlib is too low on
stack which might cause certain problems. The mmu.library works around
this problem anyhow by swapping in its own stack, but this might be an
issue for other libraries as well. Second, ramlib uses SIGF_SINGLE as
message bit for its command message port, but the same bit has been used
for semaphore signalling. Hence, some race conditions could result if
semaphores are used in the library setup code. The bug has been reported
by Eddy Carroll (SnoopDos). Thanks, Eddy!
This program *ABSOLUTELY MUST* be copied into C:, and its name *MUST NOT
BE CHANGED*, due to the way it works.
This patch is longer required for Os 3.9.
-----------------------------------------------------------------------------
The problem looks more like some bogus library or device crashing at LIB_INIT. I'd say Warp3D, warp libs are famous for this behaviour (recursive ramlib calls). Make sure you have the latest libraries installed.
-
I occasionally have this problem aswell, although, it seems, not as often as you. It only happens when I boot from cold. To get round this, if it shows up on the first boot I reboot and boot with no startup-sequence, leave it for a minute or two, then reboot. Works everytime.
But, if you are getting this every time you reset, it probably won't work for you.
I've had this problem with 3.5 aswell (although, *very* rarely), and used the same solution
btw, I've got a 68030/40 with 16Mb ram.
-
Add a NOCACHE argument to setpatch, and then add a CPU CACHE later on on your startup-sequence.
-
Make sure the propor 68060 libraries are installed on your Amiga. Do a search for your card on Google, see if there are any extra bits of info on jumper settings per simms/dimms used.
-
thanks guys!
I'm not sure if it works now but I haven't had any proplems for the past 24 hours...
-
I've had a similar problem on my apollo 030@40, and i got a more stable system by switching on the wait stages (the jumper on the card for the simms). Give it a try, but keep in mind that if it's a problem that appeared suddenly,it might be a software cause ratherly (libs etc).
________
Shemale Thai (http://www.fucktube.com/categories/975/thai/videos/1)
-
Hi !
I ever had this problem too... In my case, it was due to BlazeWCP. I didn' t manage to solve the problem until I disinstalled it when I bought my Bvision...
I had another occurence of this problem, but you seem not to be concerned : it occured at the very startup (the AmigaROM window displayed, thes pow ! Error :) ). The problem was that I formatted my new hard disk in PFS and I... forgot to put the PFS filesystem in the RDB... :-( :-D ...
-
I would have reinstalled the whole OS3.9 setup, and installed all the right drivers for your cards within it...and an advice..Look out for the latest Boing Bag Upgrade for OS3.9, the Boing Bag 2...It should fix a bunch of bugs available at the original OS3.9-setup.
Hope you will work it out at the end..Read every information that pops up under the reinstallment very carefully...
-
Hmm... Yeah, well I tried using StackAttack... That didn't solve the problem I'm afraid... Had a failure this morning.
Just to get it sorted out;
I get that message when I boot from cold, and rarely between the boots I do after the machine is started...
I'll try the NOCACHE, CPU CACHE thing now...