MMU Lib MuFastZero

  • Thread starter Thread starter AndyC
  • Start date Start date
  • Replies Replies 2
  • Views Views 1048

AndyC

Member
AmiBayer
Joined
Jul 16, 2008
Posts
402
Country
United Kingdom
Region
Fife
Hi folks,

I'm making good progress on my fresh 3.1.4 installation with the Blizzard 1260.

I've turned my attention to trying to get exec.library and expansion.library into fast memory. I recall using FastExec back in the day, but I gather it was a bit of a hack and has since been superceded by the tools found in the MMULib package, specifically MuFastZero and MuMove4K.

The installation instructions aren't very clear, but from what I can tell, I need to put MuMove4k in the startup-sequence before SetPatch, then add "MuFastZero" in the sequence after this (instructions copied below):
- Copy LIBS/mmu.library to LIBS:
- Copy MuTools/MuFastZero and MuTools/MuMove4K to C:
- If you want the FastExec feature, run "MuMove4K" in front
of "SetPatch". Add the "PREPAREEMUL" option if you want to
make use of the ShapeShifter. Add "NOREBOOT" if SetPatch V44
reboots the system on startup anyhow.
- Run MuFastZero in C: with the desired options.
- Read the MMU.Guide and MuFastZero.guide/MuMove4K.guide as soon
as you've some time.
Please see a screenshot of my s:startup-sequence attached.

When I reboot, the two libraries are still in Chip RAM, and there's no discernible difference to the boot sequence.

Can anyone here give any pointers? I'm assuming I'm missing something really simple...

Thanks in advance,

AndyC.

IMG_20200607_220923.jpg

- - - Updated - - -

Ah, so, I added the FASTEXEC option to MuFastZero and SysInfo is now reporting that expansion.library and exec.library are both now in FAST RAM.

Do I need to do anything else, or is that job done?

Cheers!

AndyC
 
- If you want the FastExec feature, run "MuMove4K" in front
of "SetPatch".


This term " in front of SetPatch" always confuses me. Is "in front of" before SetPatch is run, or after ​SetPatch is run.
 
hello,

it's before.
I believe it's all in the guide.

Try:

C:MuMove4k NoReboot PrepareEmul
TLSFMemPool
Loadmodule >NIL: Libs:intuition.library
SetPatch QUIET (and your options)

"MuFastZero ON" goes AFTER SetPatch, just like the rest of the Mu toys.
MuFastZero may or may not improve your performance, try without.
Oh, and Preparemul is theoretically not necessary for 3.1.4.
 
Last edited by a moderator:
Back
Top Bottom