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.

Wepl · 14 December 2017, 11:37

Is there anywhere a file called whdload.key?

rsn8887 · 14 December 2017, 21:59

No, I checked the following locations for whdload.key:
S:
L:
DEVS:
LIBS:
PROGDIR: (the directory where WHDLoad is located)
path in environment variable KEYPATH

(In my case PROGDIR: is C

There's an "xadmaster.key" file in s: but no "whdload.key" anywhere.

rsn8887 · 13 January 2018, 05:40

Thank you for the response in Mantis. It was indeed an emulator bug. After I patched the emu to correctly give an invalid instruction exception on "Movec PCR,D0," it now works!

13 December 2017, 09:12	#1
rsn8887 Registered User Join Date: Oct 2006 Location: USA Posts: 1,058	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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Voices8" 8 Channel Soundtracker "DemoSongI" song - "This is the Amiga with 8 Voices"	DemosongIHunter	request.Music	45	23 May 2022 20:07
Difference WHDLoad-Games "normal" & "fast"	pellewolf	project.WHDLoad	3	25 July 2017 15:38
"Reminder "Lincs Amiga User Group aka "LAG" Meet Sat 5th of January 2013"	rockape	News	4	30 January 2013 00:06
CD32 Image-Name-Bug: "...(bla)[!].zip" -> "...(bla)[" / "...[test].zip" -> "...[tes"	cfTrio	support.WinUAE	8	18 December 2012 16:31
ANSI control-code (?) bug in "all" AsmOne versions under Kick 2.0+	Photon	support.WinUAE	4	17 July 2011 19:29

14 December 2017, 11:37	#2
Wepl Moderator Join Date: Nov 2001 Location: Germany Posts: 867	Is there anywhere a file called whdload.key?

14 December 2017, 21:59	#3
rsn8887 Registered User Join Date: Oct 2006 Location: USA Posts: 1,058	No, I checked the following locations for whdload.key: S: L: DEVS: LIBS: PROGDIR: (the directory where WHDLoad is located) path in environment variable KEYPATH (In my case PROGDIR: is C There's an "xadmaster.key" file in s: but no "whdload.key" anywhere.

13 January 2018, 05:40	#4
rsn8887 Registered User Join Date: Oct 2006 Location: USA Posts: 1,058	Thank you for the response in Mantis. It was indeed an emulator bug. After I patched the emu to correctly give an invalid instruction exception on "Movec PCR,D0," it now works!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)