Thanks for comments... I use standard Windows x64 MAME, i.e. from https://www.mamedev.org/. This happens on a clean install, i.e. if I create a new directory, unpack MAME 0.245 and add a few ROM-files, and then try to start any of the added games, I do see that 20s delay.
This is on a high-end computer running Windows 10 x64. It might be specific to my environment, but I've no idea why that might be, which is why I'm asking here. I've tried to use different command line arguments, as it almost seems like MAME tries to detect something, like video modes, like you kind of hinted at. I did try "-video bgfx" and "-video opengl", but it's the same. I do use a local drive with a throughput of 14GB/s (yes, I'm a storage maniac that lives for benchmarks).
It should be noted that during that 20s delay that I can't alt-tab out of it, i.e. I'm, really stuck in MAME.
|