English Amiga Board - View Single Post - WHDLoad bug introduced in 18.3: requester "noMMU"

rsn8887 · 13 December 2017, 09:12

I am running WHDLoad on UAE4All2 Vita using A1200 config (68020 + Kick 31, WHDLoad default prefs). With WHDLoad version 18.2 everything works absolutely perfect.

I decided to update to WHDLoad version 18.3 today and now none of the games work anymore.

Every game I try causes a requestor to pop up. The requestor text is completely nonsensical. It reads verbatim:
"
The option NoMMU has been activated,
but the current MMU setup does
- contains invalid descriptors
The installed program will very probably
not work with this setup!
Try to use a different 68040/60.library
"

What does "- contains invalid descriptors" mean? Why does it talk about 68040/60.library when I don't even have it? The emulated 68020 doesn't even have an MMU.

If I dismiss the window by clicking "ignore," WHDLoad shows a black screen and hangs. This happens for every game I tried.

None of the various MMU and cache options seems to fix this.

13 December 2017, 09:12	#1
rsn8887 Registered User Join Date: Oct 2006 Location: USA Posts: 1,059	WHDLoad noMMU "bug" introduced in 18.3 I am running WHDLoad on UAE4All2 Vita using A1200 config (68020 + Kick 31, WHDLoad default prefs). With WHDLoad version 18.2 everything works absolutely perfect. I decided to update to WHDLoad version 18.3 today and now none of the games work anymore. Every game I try causes a requestor to pop up. The requestor text is completely nonsensical. It reads verbatim: " The option NoMMU has been activated, but the current MMU setup does - contains invalid descriptors The installed program will very probably not work with this setup! Try to use a different 68040/60.library " What does "- contains invalid descriptors" mean? Why does it talk about 68040/60.library when I don't even have it? The emulated 68020 doesn't even have an MMU. If I dismiss the window by clicking "ignore," WHDLoad shows a black screen and hangs. This happens for every game I tried. None of the various MMU and cache options seems to fix this. Last edited by rsn8887; 13 December 2017 at 17:27. Reason: EDIT: re-worded for clarity.