Author Topic: How do i install the MMULib version of 68040.library on AOS 3.9? (BPPC) (Read 4467 times)

AmigaMance · « **on:** October 12, 2009, 08:56:20 AM »

Hi.
I guess that on most accelarators this is a matter of copying the appropriate libraries to libs:, but the BPPC is an exception because it keeps its own 680x0.library in its FlashROM. Therefor, you need to apply a something that will disable/flush that library from the FlashROM, otherwise the OS will always use this, instead of the disk-based one.
So, after i installed the MMULib.lha package, i added the BPPCFix040 BlizKick module and it did what it suppose to do. It disabled the 68040.library in order to allow SetPatch to load the 68040.library from LIBS:.
But it doesn't appear to work! I'm using the latest version of SetPatch (from OS3.9 BoingBag #2, iirc) and it displays an error message which says that "a >=43 version of 68040.library can not be found", more or less.
What can i do about about this? Has anyone succeded to make this work on a BPPC?

EDIT: Hey, i think that i have found the root of the problem. I've just checked the version of the library and it says:

Quote

68040.library 40.16 (Monday 12 November 2001)
(c) 1999-2001 The MMU.lib development group,
THOR

Now, the error message from SetPatch is justified. But, still, what can i do about it?

AmigaMance · « **Reply #1 on:** October 13, 2009, 12:38:56 PM »

Bump

After making my initial post, i realized that the problem may be solely related to the SetPatch of 3.9 and not with the BPPC, (See edit) but i am not able to edit the subject.
Anyway, the precise error message is "No 680x0 >= V43 available.". So, anyone running AOS 3.9 has managed to install these libs?

walkero · « **Reply #2 on:** October 13, 2009, 01:50:51 PM »

I tried to install it but I had problems when I rebooted. Error messages that I couldn't see because of the requesters opening in black at the CGX screen. So, I reinstalled the backup files.

matthey · « **Reply #3 on:** October 13, 2009, 04:26:45 PM »

Quote from: AmigaMance;525787

Anyway, the precise error message is "No 680x0 >= V43 available.". So, anyone running AOS 3.9 has managed to install these libs?

The mu package has a 680x0.library that acts as a generic api for the 68040.library, 68060.library, 68030.library, etc. However, I don't think the newest Setpatch accesses it. The error message is probably a generic message for the 68040.library not having a high enough version. It's kind of confusing though. The easiest thing to do would have Thomas Richter bump the version of the 68040.library. His 68040.library should have all the functionality that is necessary. I do NOT get a similar error with my 68060 CSMK3 and the 68060.library version is 40.20. I use BlizKick as well to boot my own custom ROM. However, the flash setup is much different on the Cyberstorms than Blizzards.

The newest mu 68040.library is 40.18 which was recently uploaded on Aminet.

I just thought of a possible work around. Install the Phase5 68040dummy.library (748 bytes) as 68040.library and rename the mu 68040.library to 68040new.library. Even if this works you should probably e-mail Thomas Richter and explain the problem. It's pretty easy to bump the version number and it would save headaches like this. He still has the same e-mail address as is in the docs.

x303 · « **Reply #4 on:** October 13, 2009, 07:10:26 PM »

First try bppcfix for this site: http://powerup.amigaworld.de/index.php?lang=en&page=13
This *will* remove any 68040/68060.library from memory.
Next use the 68040 or 68060 library from the Mu package, and use the latest version of setpatch. I think Thomas Richter said you don't need to install the 680x0.library as it doesn't do anything. Setpatch should install the correct libs from now on.

x303

AmigaMance · « **Reply #5 on:** October 14, 2009, 12:23:22 PM »

@walkero
Ok.

@matthey
Thanks for the tips. The method that you suggested didn't work. I will send him a mail then.

@x303
But.. isn't this exactly what i tried to do?

x303 · « **Reply #6 on:** October 14, 2009, 12:36:45 PM »

Quote from: AmigaMance;525939

But.. isn't this exactly what i tried to do?

Well, you're trying to install the mmulib on your system. The method described is the way I did it many years ago, on my bppc machine. And it still worx today. :afro:

x303

matthey · « **Reply #7 on:** October 14, 2009, 02:58:51 PM »

@x303
AmigaMance already mentioned that he sucessfully removed the 68040.library in flash. If the Phase 5 68040.library was still being used then he probably would not have this error as the P5 68040.library has a high enough version number.

Are you using AmigaOS 3.9 with the latest SetPatch (v44.38)?

@AmigaMance
You might double check that your SetPatch is v44.38 also.

AmigaMance · « **Reply #8 on:** October 14, 2009, 03:11:01 PM »

Quote from: matthey;525950

You might double check that your SetPatch is v44.38 also.

It is: "setpatch 44.38 (Friday 8 March 2002)"

x303 · « **Reply #9 on:** October 14, 2009, 03:27:26 PM »

Yep, the lastest version of setpatch is used.

@AmigaMance
Why not give bppcfix a try instead of the blizzkick module, as the blizzkick module never really worked on my system. If it doesn't work you can always email thomas richter

x303

AmigaMance · « **Reply #10 on:** October 14, 2009, 07:18:04 PM »

Quote from: x303;525955

Yep, the lastest version of setpatch is used.

@AmigaMance
Why not give bppcfix a try instead of the blizzkick module, as the blizzkick module never really worked on my system. If it doesn't work you can always email thomas richter

You are right! For some strange reason the blizkick module doesn't really work, but the command does! Now the library is loaded by SetPatch.
Regarding the error message, it was a BIG goof of mine. It was produced by SetMemMode, which i have placed one line after SetPatch... I guess its version checking is bogus. Sorry about that.

matthey · « **Reply #11 on:** October 14, 2009, 07:56:55 PM »

@AmigaMance

Good deal. The bug looks like it's in Piru's BlizKick module. It's not really incorrect for SetMemMode to ask for a minimum version of the 68040.library if it needs functionality that is in a later version. The problem is several different 68040.library's with different version numbers and different functionality.

I use this line in my Startup-Sequence after SetPatch with Thor's CPU library...

MuFastZero MOVESSP ON

It gives a nice little speed boost on the 68060 at least. It should work on the 68040 too.

AmigaMance · « **Reply #12 on:** October 18, 2009, 01:37:27 PM »

Quote from: matthey;525983

@AmigaMance
I use this line in my Startup-Sequence after SetPatch with Thor's CPU library...

MuFastZero MOVESSP ON

It gives a nice little speed boost on the 68060 at least. It should work on the 68040 too.

I've been playing with my new software setup all these days. Reading docs, installed MuRedox. There is a fix for SetMemMode in the archive, btw.

I'm not sure if i need MuFastZero, because:
Both expansion and exec libraries are loaded in Fast RAM.
SSP points to Fast RAM by default.
VBR is relocated to Fast RAM by the MoveVBR BlizKick module.

x303 · « **Reply #13 on:** October 18, 2009, 02:25:59 PM »

I run MuFastZero too. I also run MuMove4k, MuFastrom and MuFastchip.

x303