Using Enforcer/MuForce on WinUAE

[Honitos]

Sorry for this possibly stupid question for a developer,

... but how do I get MuForce or the former Enforcer to work on my system?


I use OS 3.2.1 on WINUAE with the following config:
* CPU: 68040 / more compatible
* MMU: MMU
* FPU: internal


In startup-sequence - after SetPatch - there is SegTracker and COP.
I installed mmu.library.


After booting, if I start MuForce via Icon oder from shell, the system freezes and i get a "bus error" beaten over the ears by COP.
Starting MuForce does float COP with LONG-READ messages.


I also tried Sashimi, nothing.


I want to examine some reported memory hits on AmiBlitz3.
But if I even doesn't make it to get this tools running, I should better quit programming, what do you think?

[Toni Wilen]

Possibly $f00000 UAE boot ROM causing those hits (if $f0 ROM is not marked as mapped in MMU config). Try changing ROM panel board type to 128k model (which disables old-style $f0000 ROM and replaces it with single 128k autoconfig board)

EDIT: and don't enable any compatibility features, some of them are not fully MMU emulation compatible. ("more compatible", cycle-exact etc)

[Honitos]

Thanks Toni, for the hint. Indeed the board type is set to "Original UAE".

But the listbox is inactive, how can I change the setting to your suggested value?
(using WinUAE 4.9.1)


EDIT:
SOLVED. The selected configuration may not be in use. After just loading the configuration without starting the emulation, I can change this setting.

[Honitos]

Yes!

Disabling COP in startup-sequence did the trick!
I thought, COP and MuForce would coexist, but obiously not!

[Thomas Richter]

Originally Posted by Honitos

Yes!

Disabling COP in startup-sequence did the trick!
I thought, COP and MuForce would coexist, but obiously not!

They certainly do, and I'm using it like that, but you need to read the COP manual. Yes, COP is complicated.