Firehawke
Firehawke
Ah, that's really too bad because it's kinda neat when you have a desktop and a laptop both. Back to Dropbox I go.
I'm using the workaround I'd previously mentioned for the time being, so this isn't an immediate need thing but I'll leave this open because I still feel expanded glob capabilities...
That doesn't seem to have helped-- either loading the workspace or directly just opening a single folder, it gives the same error.
It's on my PC. but a few of the workspace folders were from WSL2 mounted at the L: drive-- this was done because while some of the scripting requires Linux-side...
 No change. Server is running in the background but no attempt to connect was made.
Here's a re-run using the workspace:  Here's a re-run using just the folder: 
Just going to add that this game has always-online DRM, so that's probably where the choke comes in.
I know it's a year late, but here's some info that may come in handy: MAME's file formatting is ALWAYS per-chip dumps named to match the socket on the board...
To be more specific, it's a four-way interleave not two-way. That's why you're getting garbled graphics.