Emu Loader is not the one doing it. The frontend doesn't steal focus while the emulator is running.
You can check the "RunProcess()" function in EL's source code (uMain.pas file). You'll see that this function enters in an endless loop, waiting for the emulator to be
closed by the user. I followed the implementation rules recommended by Microsoft.
This exec code 3221225786 is a result of termination of app by "Ctrl+C":
Here's what I found:
Code:
3221225786
0xC000013A
-1073741510 The application terminated as a result of a CTRL+C. Indicates that the application has been terminated either by user's keyboard input CTRL+C or CTRL+Break or closing command prompt window.
Source:
Code:
http://www.febooti.com/products/automation-workshop/online-help/events/run-dos-cmd-command/exit-codes/
The lose focus is probably caused by a program running in the background.
It might also be caused by a corrupt mame.exe. Where did you get the new MAME ? Always get new MAME builds from mamedev.org for safety.
I have a similar weird error code if MSI Afterburner is running while trying to run MAME. MAME crashes and game doesn't run...
Closing that app and running the emulator again, MAME work without errors.
Emu Loader uses WinAPI CreateProcessW() to execute mame.exe with full path. Its implementation is compatible even with Windows 10.
Please make sure to enable Run Game Confirmation Dialog in frontend's main menu and check the full command line that will run.
Also, make sure to uncheck all checkboxes of Hide Command Prompt Box in preferences screen, General tab.
What programs do you have running in the background ? Since you disabled the anti-virus, it's not the one causing problems with MAME.
Ciro Alfredo Consentino
home: http://emuloader.mameworld.info
e-mail: [email protected]
Edited by CiroConsentino (04/21/17 08:46 PM)