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.

- - - 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
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.

- - - 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