Dolphin 8.1.0 does not run on AMD64 Windows (running in Parallels on Apple Silicon)

[GrumpyOldGandalf]

Describe the bug
Perhaps it shouldn't, but the latest Dolphin 7.1.30 runs (as far as I can tell) just fine on my Parallels VM running Windows 11 (ARM64). Unfortunately, Dolphin 8.1.0 does not run on it, at all. A brief "busy" icon appears after clicking the desktop icon and disappears and then nothing.

To Reproduce
Steps to reproduce the behavior:

1. Uninstall Dolphin 7
2. Install Dolphin 8
3. Try to double click on the desktop icon.
4. See error. Or to be more precise, after a brief "busy" icon, see nothing.
5. Uninstall Dolphin 8 and Reinstall Dolphin 7. :)

Expected behavior
I expect the Splash window and System Folder both to appear.

Screenshots
There are no screenshots, because nothing pops up.

Please complete the following information):

• OS: Windows 11 (ARM64) running in Parallels on Mac OS X Sonoma 14.2.1.

Additional context
Not sure what additional context is needed, but if there is a hidden log somewhere that might illuminate what is happening, I'm happy to hunt for it.

I did try to start the application at the command line, and separately by double-clicking the image icon, and also right-clicking and Open with -> Dolphin Launcher. Same - brief busy icon, then nothing. No information is dumped to the console when attempting to run via command line.

To be clear, I'm not expecting this to be a supported platform, but since Dolphin 7 works via the 32-bit emulator on Windows 11 ARM64, I suppose it would be interesting to find out why Dolphin 8 is failing.

Anything I can do to help sleuth, debug and fix this, I'm happy to learn. In general, I'd like to help get Dolphin on 64-bit, period, for both Intel and ARM. If nothing else, I can offer testing support.

[blairmcg]

I suppose it is possible that the emulation doesn't support the later instruction set that Dolphin 8 is built with, or that the startup uses some API that is missing, or called in a way that is not supported by the platform. I've no means to find out personally, so I'm afraid you are on your own with this one unless someone else with a similar setup can help.

You could check to see if it wrote a dump file, which happens in most circumstances where there is a crash. Only rarely is the VM unable to do that, such as when there is an unrecoverable stack overflow. The errors files should be in the same folder in as the image, so if you are running from a installed version (as opposed to building it yourself), it would be "\Dolphin Smalltalk 8\DPRO.Errors".

If you can't locate the errors file, or in case there is any other debug output, try running DebugView and then try running Dolphin 8. The Dolphin VM writes a debug log entry when it writes to the dump file and reports the path. If it can't open the log file, it writes the full dump to the debug log. The debug log is transient and not persisted anywhere, so you'll have to recreate the issue after starting DebugView.

To debug it properly follow the instructions in the readme to build the VM with VS2022. You could then launch it under the debugger to see where it blows up.

[GrumpyOldGandalf]

Ok thanks - I'll try out each of the steps you recommend, and report here if I find anything helpful.