2024-03-28 14:35 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003760WHDLoad[All Projects] Generalpublic2020-10-27 11:24
Reporterrsn8887 
Assigned ToWeplProject InfoHD-Installer for OS-Killer
http://whdload.de/
 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
Product Version18.3 
Target VersionFixed in Version 
Summary0003760: On UAE4All2, "noMMU" message, followed by black screen crash
DescriptionI 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.

The only thing I did was replace the WHDLoad v18.2 executable files in C with files from the v18.3 usr archive. If I go back and replace the files in C with 18.2 versions again, everything works again.
Steps To ReproduceBoot up UAE4All2 (I use the Vita version), start any WHDLoad game.
TagsNo tags attached.
MachineUAE
CPU68020
CPUSpeed14
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem8 MB
WorkbenchOS 3.0
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad18.3
Attached Files

-Relationships
+Relationships

-Notes

note ~0005940

Wepl (manager)

Please check if you have a file whdload.key anywhere.

note ~0005942

rsn8887 (reporter)

No there's no whdload.key.

I checked the following directories:
S:
L:
DEVS:
LIBS:
PROGDIR: (the directory where WHDLoad is located)
path in environment variable KEYPATH

Note in my case there is no $KEYPATH set, and PROGDIR: is C:.

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

note ~0005943

Wepl (manager)

Please set option TRACE and abort when the requester appears.
Attach to this issue the created file .whdl_trace for further investigation.

note ~0005944

rsn8887 (reporter)

I am attaching the file. I started it and quit when the requestor appeared. Then I started it again and clicked ignore on the requester. The game booted to a black screen and the emulated alAmiga became unresponsive (WHDLoad quitkey didn’t work, I had to reset. I then tried two more times clicking cancel on the requester.

note ~0005945

rsn8887 (reporter)

Second try at uploading the file..,

note ~0005947

Wepl (manager)

Hmm, the reason is, that the cpu detection of whdload detects apollo hardware (detection added in 18.3) and with that a 68040.
It seems that instruction 'movec pcr,d0' does not create an illegal instruction exception, which is incorrect for a 68020.
Please ask the vendor of UAE4All2 to fix that.

note ~0005987

rsn8887 (reporter)

Thank you for the detailed response. This allowed me to patch the emulator so that it correctly throws the invalid instruction exception. Now it all works!

note ~0005991

Wepl (manager)

fine :)
+Notes

-Issue History
Date Modified Username Field Change
2017-12-13 17:41 rsn8887 New Issue
2017-12-14 11:44 Wepl Assigned To => Wepl
2017-12-14 11:44 Wepl Status new => assigned
2017-12-14 11:45 Wepl Note Added: 0005940
2017-12-15 02:57 rsn8887 Note Added: 0005942
2017-12-15 08:38 Wepl Note Added: 0005943
2017-12-16 11:05 rsn8887 File Added: whdloadtrace.zip
2017-12-16 11:05 rsn8887 Note Added: 0005944
2017-12-16 11:07 rsn8887 File Added: whdloadtrace-2.zip
2017-12-16 11:07 rsn8887 Note Added: 0005945
2017-12-19 14:55 Wepl Note Added: 0005947
2018-01-13 05:42 rsn8887 Note Added: 0005987
2018-01-14 21:56 Wepl Note Added: 0005991
2018-01-14 21:57 Wepl Status assigned => resolved
2018-01-14 21:57 Wepl Resolution open => no change required
2020-10-27 11:24 Wepl Status resolved => closed
+Issue History