MAMEWorld >> EmuChat
View all threads Index   Flat Mode Flat  

OPAQUeMeGANe
MAME Fan
Reged: 08/25/14
Posts: 1
Send PM
Re: Building MAME with Visual Studio 2013.
08/25/14 10:28 PM Attachment: Untitled-1.jpg 46 KB (0 downloads)


Did anyone figure this one out? I'm having the same problem with the same setup.

As an experiment, I tried dragging the exe I built into the folder of a working prebuilt binary, and still had the same problem.

In both cases, pressing enter does nothing, neither does pressing tab to bring up the menu, or using the arrow keys.

It does however respond to pressing letter keys for filtering/searching for games, I just can't start any of them. (image included)

I tried changing the UI select key to something else in the working binary, and then running my exe with that config file but still nothing.

Thanks! Let me know if there's any other information I can provide, or anything else I can try.

Update:
Trying to debug the build from visual studio, giving it a game name as a command line argument. First, I don't see any source files in the solution explorer. When I run the program, it gets to the menu where it asks me to type 'ok', but once again typing doesn't do anything.

(I'm following these instructions http://mamedev.org/devwiki/index.php?title=Building_MAME_using_Microsoft_Visual_Studio_compilers)

Here is the output when I try to debug-run the build:


'vmamed.exe' (Win32): Loaded 'E:\ALEX_STUFF\MahjProj3\MahjProj3\mame\vmamed.exe'. Symbols loaded.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\lpk.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\usp10.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmm.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wsock32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nsi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dsound.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\powrprof.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dinput8.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\comdlg32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shell32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dbghelp.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d9.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\version.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d8thk.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvd3dum.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\D3DX9_43.dll'. Cannot find or open the PDB file.
The thread 0xdf0 has exited with code 0 (0x0).
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\ole32.dll'
'vmamed.exe' (Win32): Loaded 'C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\clbcatq.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\MMDevAPI.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\propsys.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\AudioSes.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\avrt.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\hid.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wdmaud.drv'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ksuser.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msacm32.drv'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msacm32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\midimap.dll'. Cannot find or open the PDB file.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988EC.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988BC.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B98890.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B98890.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988EC.
The thread 0x1a58 has exited with code 2 (0x2).
The thread 0xfb4 has exited with code -1073741510 (0xc000013a).
The thread 0x14b4 has exited with code -1073741510 (0xc000013a).
The thread 0x1684 has exited with code -1073741510 (0xc000013a).
The thread 0xfa4 has exited with code -1073741510 (0xc000013a).
The thread 0x16f0 has exited with code -1073741510 (0xc000013a).
The thread 0x14d8 has exited with code -1073741510 (0xc000013a).
The thread 0x1340 has exited with code -1073741510 (0xc000013a).
The thread 0x1728 has exited with code -1073741510 (0xc000013a).
The thread 0x16e4 has exited with code -1073741510 (0xc000013a).
The thread 0x10ac has exited with code -1073741510 (0xc000013a).
The thread 0x1324 has exited with code -1073741510 (0xc000013a).
The thread 0x160c has exited with code -1073741510 (0xc000013a).
The thread 0x16dc has exited with code -1073741510 (0xc000013a).
The thread 0x870 has exited with code -1073741510 (0xc000013a).
The thread 0x153c has exited with code -1073741510 (0xc000013a).
The thread 0x128c has exited with code -1073741510 (0xc000013a).
The thread 0xa4c has exited with code -1073741510 (0xc000013a).
The program '[3500] vmamed.exe' has exited with code -1073741510 (0xc000013a).

[ATTACHED IMAGE]

Attachment

Edited by OPAQUeMeGANe (08/25/14 11:25 PM)







Entire thread
Subject Posted by Posted on
* Building MAME with Visual Studio 2013. tunstals 05/04/14 02:44 PM
. * Re: Building MAME with Visual Studio 2013. R. Belmont  05/04/14 03:17 PM
. * Re: Building MAME with Visual Studio 2013. tunstals  05/05/14 03:17 PM
. * Re: Building MAME with Visual Studio 2013. tunstals  05/12/14 10:21 AM
. * Re: Building MAME with Visual Studio 2013. sz72  05/12/14 10:49 PM
. * Re: Building MAME with Visual Studio 2013. tunstals  05/15/14 01:16 PM
. * Re: Building MAME with Visual Studio 2013. sz72  05/16/14 08:38 PM
. * Re: Building MAME with Visual Studio 2013. OPAQUeMeGANe  08/25/14 10:28 PM

Extra information Permissions
Moderator:  Robbbert, Tafoid 
1 registered and 167 anonymous users are browsing this forum.
You cannot start new topics
You cannot reply to topics
HTML is enabled
UBBCode is enabled
Thread views: 3454