It is not happening on any other emulators (except DOSBox). All other emulators (over 7 of them) along with MAME (except neogeo roms) work perfectly as they always have. I re-copied the neogeo.zip bios from a known working machine as well.
I tried installing the latest version of MAME (0190b, official build) on the machine to test it, same thing happens. When trying to run a NeoGeo rom, the command prompt error is reads:
===============================
-----------------------------------------------------
Exception at EIP=0335057f (system_time::set(long)+0x001f): ACCESS VIOLATION
While attempting to read memory at 00000000
-----------------------------------------------------
EAX=00000000 EBX=0022c0d0 ECX=0022c0d0 EDX=00000000
ESI=0022c0d0 EDI=00000000 EBP=0022c088 ESP=0022c070
-----------------------------------------------------
Stack crawl:
0022c088: 0335057f (system_time::set(long)+0x001f)
0022c118: 0335765e (running_machine::run(bool)+0x015e)
0022f878: 01c10adc (mame_machine_manager::execute()+0x01dc)
0022f9e8: 01c80936 (cli_frontend::start_execution(mame_machine_manager*, std::
vector, std::allocatorhar> >, std::allocator,
std::allocator > > > const&)+0x0456)
0022fad8: 01c80e59 (cli_frontend::execute(std::vectorng, std::allocator >, std::allocatorxx11::basic_string, std::allocator > > >&)+0x
0039)
0022fb08: 01c0eb8d (emulator_info::start_frontend(emu_options&, osd_interface&
, std::vector, std::allo
cator >, std::allocatorchar>, std::allocator > > >&)+0x002d)
0022fee8: 0676664a (main+0x012a)
0022ffc0: 004013e3 (__tmainCRTStartup+0x0273)
0022fff0: 7c817067 (RegisterWaitForInputIdle+0x0049)
=====================================
This is from a fresh install and no alterations to newly generated mame.ini .
Edited by pb1592 (11/27/17 03:30 AM)
|
Previous 
Index 
Next 
Flat 
Re: Sudden problem with MAME and Neo Geo...
Reply
