MAMEWorld Forums - EmuChat - Re: Why 20s delay when starting any game in MAME?

Thanks a lot for taking the time to respond! COM server driver timeout definitely seems to be the reason for the 20s freeze.

I don't have any exotic device plugged in, and Device Manager doesn't give much info on what is what, so after spending the last hour(s) testing I'm still puzzled if it's my mouse or my keyboard that cause the issue, or none of them.

I did find out that if I remove these four entries from "USB Input Device", the 20s freeze goes away.

Device USB\VID_0414&PID_A00C&MI_02\8&13F7E05E&0&0002 was deleted.
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}

Device USB\VID_0C45&PID_7692&MI_01\7&2FAEB158&0&0001 was deleted.
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}

Device USB\VID_0414&PID_A00D&MI_07\6&16E5B307&0&0007 was deleted.
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}

Device USB\VID_0414&PID_A00C&MI_03\8&13F7E05E&0&0003 was deleted.
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}

However, if I re-connect either my Glorious Model O- mouse, or my WASD-keyboard, or any other USB input device, the problem re-appears. So, still have to figure out what the problem really is...

I was not aware of the verbose flag, so thanks for that. The output looks like this:


E:\emu\MAME2>mame -verbose -window
Attempting load of mame.ini
Attempting load of mame.ini
Starting plugin data...
Attempting load of mame.ini
Attempting load of mame.ini
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 2747, height 2100
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce RTX 3090
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7692&MI_00#8&33a744cc&2&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7692&MI_01&Col03#8&fd0070a&8&0002#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_1038&PID_1369&MI_01&Col02#8&8ef584d&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #3: HID Keyboard Device (device id: \\?\HID#VID_1038&PID_1369&MI_02#8&1ae7e575&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: HID-compliant mouse (device id: \\?\HID#VID_1038&PID_1369&MI_01&Col01#8&8ef584d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_1038&PID_1369&MI_01&Col01#8&8ef584d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Optional memory region ':screen' not found
Starting No Driver Loaded ':'
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting No Driver Loaded ':'
Checking for icons in directory icons
No candidate icons found for machines
Attempting to parse: default.cfg
Attempting to parse: ___empty.cfg
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 2725x2044
Direct3D: Initialize HLSL

It freezes after "Input: Adding lightgun", and if I disconnect the mouse, it freezes after "Adding keyboard #3".

I'll continue to experiment, but this is definitely somehow the root cause.