|
Sudden problem with MAME and Neo Geo...
#371315 - 11/23/17 09:37 PM
|
|
|
I have two different versions of MAME running on my arcade machine. For years it has worked flawlessly. I just noticed recently that when I try to run Neo Geo games I get an error message and they will not run. This happens on both versions of MAME and ONLY on Neo Geo roms.
The error in the command prompt is:
---------------------------------------------
Exception at EIP=009B2CE2: ACCESS VIOLATION
While attempting to read memory at 00000000
---------------------------------------------
As stated, all other roms work great, its only Neo Geo roms that cause this and it happens in BOTH versions of MAME I have installed. I am running Windows XP SP3.
All I can remember doing in the last year was attempting to update a video driver.
Any ideas?
|
|
|
| Sune |
|
Connected
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 5648
|
|
Loc: Lagoa Santa, Brasil
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371321 - 11/24/17 01:55 AM
|
|
|
> I have two different versions of MAME running on my arcade machine. For years it has
> worked flawlessly. I just noticed recently that when I try to run Neo Geo games I get
> an error message and they will not run. This happens on both versions of MAME and
> ONLY on Neo Geo roms.
Which versions of MAME?
Try deactivating cheats and remove highscore.dat. Try changing video renderer settings.
Post your mame.ini.
S
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371322 - 11/24/17 01:58 AM
|
|
|
Have you tried turning cheats off, or updating/removing the cheat file? That was a common problem back then when it comes to MAME and Neo Geo.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371325 - 11/24/17 08:53 AM
|
|
|
> All I can remember doing in the last year was attempting to update a video driver.
Do you have an older Nvidia video card?
There was an issue a while back with newer Nvidia drivers on older cards crashing MAME. It was a driver issue, not a MAME issue. I think it was happening on all games though, not just Neo Geo.
Are you doing any overclocking? Maybe running those specific games are causing the CPU to crash for whatever reason due to overclocking.
|
GroovyMAME support forum on BYOAC
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371330 - 11/24/17 07:28 PM
|
|
|
It's probably an old release that crashed with -cheat rather than having it enabled with plugin option.
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6118
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: B2K24]
#371332 - 11/24/17 07:52 PM
|
|
|
> It's probably an old release that crashed with -cheat rather than having it enabled
> with plugin option.
All have to do is to move that cheat.dat file out of the MAME folder then. 
I deleted my old post. I should've thought of this begin with.
Sorry pb I wasn't thinking about this.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Sune]
#371344 - 11/25/17 02:23 PM
|
|
|
Sorry for the late response. I am running MAMEPlus v0.148 and MAME 0128b. The pc is an old E-Machines box running XP with SP3, that does indeed have a NVIDIA video card.
A while back I was trying to get Nidhogg and Towerfall to run on the cab, knowing full well that I shouldn't expect newer games to run on old hardware and obsolete OS, but I was determined. I installed all of the latest video driver and directX updates to the pc with no success. I didn't notice till much later that Neo Geo games crashed after this. I am assuming all of this is connected.
Just for the heck of it I'll try erasing hiscore.dat, and check the status of the cheat setting, although I can't imagine this is the problem since it has worked perfectly for all these years, and no settings were changed in either version of MAME.
I will post my mame.ini files tonight.
If it is a video driver or directx issue, is there any way to narrow it down or known fixes? Keep in mind it only happens with Neo Geo roms. I'm so confused.
Lastly, if I enable MAME error log, here is all I get:
The MAME error log file says:
---------------------------------------------
Physical width 1024, height 768
AY-3-8910/YM2149 using single output!
AY-3-8910/YM2149 using legacy output levels!
---------------------------------------------
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371349 - 11/25/17 08:36 PM
|
|
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371355 - 11/26/17 03:22 AM
|
|
|
Why are you using such an ancient version of MAME?
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: krick]
#371356 - 11/26/17 03:30 AM
|
|
|
> > The pc is an old E-Machines box running XP with SP3, that does indeed have a NVIDIA
> video card.
>
> Give this specific Nvidia driver version a try...
>
> http://www.nvidia.com/object/winxp-258.96-whql-driver.html
those drivers are if there is a BSOD problem, that isn't what is being reported so I'd be surprised if it helps.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371358 - 11/26/17 06:26 AM
|
|
|
What is the likelihood that updating DirectX drivers could have caused this? I know for certain I updated it during the time this problem most likely started.
I am going to try re-installing fresh nvidia driver set directly from nvidia's website, although I don't think this is going to fix it. Will doing this actually replace/overwrite existing driver files or simply skip copying them if the installer sees that the same apparent driver files (with same names) have already been installed? I think I ran into this once before with an unrelated problem.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: jonwil]
#371360 - 11/26/17 06:36 AM
|
|
|
I built my MAME cab a long time ago. Everything worked perfectly for years and had no reason to update. Updating MAME wouldn't really have benefited me in any way (if it ain't broke, don't fix it) and would have required me to endlessly correct, rename, download new rom sets, along with recompiling it to disable the "TYPE OK" nag screen. Maybe this has changed in recent years but everything worked just the way I wanted so I never bothered to risk screwing something up by updating when it wasn't necessary. In fact, installing an update is what caused this problem, I should have left well enough alone!
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371363 - 11/26/17 09:35 AM
|
|
|
For what its worth I also noticed that DOSBOX 0.74 will not work either now. I reinstalled it from scratch and deleted the config file so the first run created a brand new default config. It now crashes in XP, when before it'd emulate perfectly and run all of my old DOS games. I can't even get to command prompt on a fresh install, it just crashes before the command prompt window opens with a default config. Pretty sure the issue is related. This has worked perfect for years.
I tried re-installing the nvidia drivers fresh from the install file directly off of the website. I reinstalled directx from the install file from my other MAME cab backup (also running XP and works perfectly with all same software). This did not work. Same problem.
Should I be convinced driver files were actually replaced with fresh copies during "successful install"?
Keep in mind all other NON neogeo roms still work perfect in MAME (both installed versions) on this system along with NES, ATARI, GENESIS, SNES, MASTER-SYSTEM, TG16, PSX, and N64 emulators and roms.
I also tried completely disabling sound emulation in DOSBOX and MAME config to rule out sound card issues.
Is there anything else SPECIFIC to the neogeo.zip rom that is unlike other typical roms from a graphics standpoint? It happens with ALL neogeo games so it has to be related to the neogeo.zip bios rom somehow. UGHHHH!!!
PS: I also re-downloaded a fresh version of neogeo.zip and also tried replacing the current one with the neogeo.zip from my other working machine to rule out file corruption.
Edited by pb1592 (11/26/17 09:38 AM)
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371368 - 11/26/17 03:09 PM
|
|
|
well it sounds like you're using a hacked version of MAME with the 'nag' screens removed, which means all bets are off and basically you're on your own. Many of those patches introduced other bugs meaning a lot of those builds will also be suppressing warnings that might tell you something useful and instead are crashing because the people making such hacks are idiots.
it's 99.9% likely to be the cheat problem already pointed out, especially if other stuff runs just fine in MAME.
but since you've admitted to running a hacked version, I'm no longer providing any support.
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6118
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371369 - 11/26/17 03:39 PM
|
|
|
> well it sounds like you're using a hacked version of MAME with the 'nag' screens
> removed, which means all bets are off and basically you're on your own. Many of those
> patches introduced other bugs meaning a lot of those builds will also be suppressing
> warnings that might tell you something useful and instead are crashing because the
> people making such hacks are idiots.
>
> it's 99.9% likely to be the cheat problem already pointed out, especially if other
> stuff runs just fine in MAME.
>
> but since you've admitted to running a hacked version, I'm no longer providing any
> support.
If I were that person. Replace that hacked MAME build for the Official MAME build. Trash everything from that folder except for the ROM's, Artworks and Samples. All he need is the same version that he have. He gonna have to check those ROM's for correction though. Other wise he will be upset that the ROM's doesn't match at all on some of those sets. Not only that. A game might not load at all because there no hack patch on the driver. When he do this then he is all good. Other wise he is done with MAME DEV support completely. But he will have to show where he gotten the replacement from the MAME website.
Note to others: Do not give him a link. He will have to link the page on his own. The page that have all the older released.
He isn't the only one. There are others out there using those hack MAME builds.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Dullaron]
#371372 - 11/26/17 06:11 PM
|
|
|
I apologize if I have broken a code of ethics using a recompiled version of MAME. This was not my intent and was done because someone suggested it long ago as a quick way to decrease the time it took for setup and config of my (then) new cab.
I understand I will probably not receive any more help here but for what its worth the version of MAME Plus I am using is an official build and since this has happened I did install a fresh, official build of 0128b into a separate folder with a separate set of roms and no paths in the default mame.ini pointing to the 'hacked' version.
Again, the exact same thing happens with both official builds of Plus and 0128b.
My MAME setup is literally a direct copy-and-paste of my other MAME cabinet which works perfectly and has for years. In the mame.ini -cheat is set to 0 and a cheat.dat file does not exist anywhere in any installation of MAME on my machine that I am able to find.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371374 - 11/26/17 06:48 PM
|
|
|
It's not like there's any code of ethics exactly, if that would be true Dullaron broke it a long time ago with that MAME Retroarch crap he loves to advertise for free. However the chances to get support for what you are using are slim because people here usually don't use derivative builds. You have better chances getting support from wherever you download it.
Given you know how to use command line, what do you get from using the "-verifyroms" parameter?
Code:
C:\Emus\MAME>mame64.exe fatfury1 -verifyroms
romset fatfury1 [neogeo] is good
1 romsets found, 1 were OK.
You should also try the "-verbose" parameter.
Code:
C:\Emus\MAME>mame64.exe fatfury1 -verbose >log.txt
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6118
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: BIOS-D]
#371381 - 11/26/17 11:23 PM
|
|
|
> It's not like there's any code of ethics exactly, if that would be true Dullaron
> broke it a long time ago with that MAME Retroarch crap he loves to advertise for
> free.
I only uses MAME Retroarch on my Chromebook Plus. MAME Retroarch just a temp until the Official MAME for the Android come out. Least it better than that out of date MAME(Four)All. So far there isn't Official MAME for the Android yet. Probably will never see the light of day on the release. Because the project is no longer being work on. It hard get someone to work on it from the MAME Dev when they are working on the source for Windows. It too much work for them. I don't blame them. The source is there so that others can use for their own builds. For example https://github.com/libretro/mame
I still using the Official MAME for Windows. I do not use MAME Retroarch on Windows.
Not all working games will work right on the MAME Retroarch anyway. For example Tempest sounds is imperfect.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
| Foxhack |
|
Furry guy
|
|
|
|
|
Reged: 01/30/04
|
|
Posts: 2409
|
|
Loc: Spicy Canada
|
|
|
|
Send PM
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371383 - 11/26/17 11:35 PM
|
|
|
> I apologize if I have broken a code of ethics using a recompiled version of MAME.
> This was not my intent and was done because someone suggested it long ago as a quick
> way to decrease the time it took for setup and config of my (then) new cab.
>
> I understand I will probably not receive any more help here but for what its worth
> the version of MAME Plus I am using is an official build and since this has happened
> I did install a fresh, official build of 0128b into a separate folder with a separate
> set of roms and no paths in the default mame.ini pointing to the 'hacked' version.
>
> Again, the exact same thing happens with both official builds of Plus and 0128b.
>
> My MAME setup is literally a direct copy-and-paste of my other MAME cabinet which
> works perfectly and has for years. In the mame.ini -cheat is set to 0 and a cheat.dat
> file does not exist anywhere in any installation of MAME on my machine that I am able
> to find.
If the same issue is happening on other emulators then I suspect the video card may be going bad.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Foxhack]
#371398 - 11/27/17 03:28 AM
|
|
|
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)
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371399 - 11/27/17 04:11 AM
|
|
|
Somewhat unrelated question here, but assuming perhaps maybe a dll or windows system file was somehow altered or corrupt, if I were to do an XP re-install over the existing install of windows (not a clean wipe) such that it retained all of my programs, settings, registry etc, does this physically overwrite and replace existing windows system and dll files or does it simply skip over anything already there?
I do seem to recall monkeying around with replacing msvcrt.dll with a newer version or something of the like because Nidhogg or Towerfall needed it. Maybe this is causing the problem. But would re-installing Windows on top of the the existing copy (again, so nothing is erased) overwrite and replace system files (a potentially corrupt or incorrect versioned one)? I hope what I am asking makes sense, I'm not sure if I am wording this correctly.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371400 - 11/27/17 04:12 AM
|
|
|
> 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 const&)+0x0456)
> 0022fad8: 01c80e59 (cli_frontend::execute(std::vector&)+0x
> 0039)
> 0022fb08: 01c0eb8d (emulator_info::start_frontend(emu_options&, osd_interface&
> , std::vector >&)+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 .
you see that's actually more interesting, because you have the crash backtrace / map due to having the correct files in the installation.
I suspect other systems with a calender will also crash. Things like PGM?
As for why, I'm not sure. Is the date on the PC in question set to something completely invalid? I've literally never seen this crash before, so something very screwy has happened on your PC, it could indeed be that you've badly broken your Windows installation.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371401 - 11/27/17 04:18 AM
|
|
|
> I suspect other systems with a calender will also crash. Things like PGM?
>
> As for why, I'm not sure. Is the date on the PC in question set to something
> completely invalid? I've literally never seen this crash before, so something very
> screwy has happened on your PC, it could indeed be that you've badly broken your
> Windows installation.
Maybe the CMOS battery died or maybe the motherboard BIOS was flashed without resetting to defaults. This could leave things in a wonky state.
|
GroovyMAME support forum on BYOAC
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: krick]
#371402 - 11/27/17 04:23 AM
|
|
|
> > I suspect other systems with a calender will also crash. Things like PGM?
> >
> > As for why, I'm not sure. Is the date on the PC in question set to something
> > completely invalid? I've literally never seen this crash before, so something very
> > screwy has happened on your PC, it could indeed be that you've badly broken your
> > Windows installation.
>
> Maybe the CMOS battery died or maybe the motherboard BIOS was flashed without
> resetting to defaults. This could leave things in a wonky state.
it's possible. MAME uses gmtime and localtime.
It looks like there are certain situations in which that can return NULL, and MAME won't handle those cleanly as it doesn't check for NULL.
This could be due to the date on the PC being invalid, or maybe some Windows file if it relies on that to get the time, and is returning NULL due to bad files.
Quote:
The gmtime, mktime, and localtime functions use the same single, statically allocated structure to hold their results. Each call to one of these functions destroys the result of any previous call. If timer represents a date before midnight, January 1, 1970, gmtime returns NULL. There is no error return.
Quote:
localtime
Return Value
Return a pointer to the structure result, or NULL if the date passed to the function is:
Before midnight, January 1, 1970.
After 03:14:07, January 19, 2038, UTC (using _time32 and time32_t).
After 23:59:59, December 31, 3000, UTC (using _time64 and __time64_t).
Either way, the MAME code could probably be made safer, the backtrace given points very much at it being likely one of those calls is returning NULL tho.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: BIOS-D]
#371403 - 11/27/17 04:33 AM
|
|
|
Per your advice, when I used -verbose >log.txt, here is what the log file says. This was trying to run a neogeo game that crashes:
==========================
Parsing mame.ini
Parsing mame.ini
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = NVIDIA GeForce 6150SE nForce 430
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Device created at 1024x768
Direct3D: Max texture size = 4096x4096
RawInput: APIs detected
Input: Adding Mouse #1: \??\HID#Vid_195d&Pid_1009#6&b3f474&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\HID#Vid_195d&Pid_1009#6&b3f474&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\HID#Vid_1a2c&Pid_0002&MI_00#7&239576ee&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #2: \??\HID#Vid_413c&Pid_2003#6&1246c8c7&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
===========================================
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371404 - 11/27/17 04:35 AM
|
|
|
Yes, actually, I checked and for some reason the system date was set to 2098 haha.
I'll try setting it to the correct date and see what happens and report back.
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371405 - 11/27/17 04:47 AM
|
|
|
> Yes, actually, I checked and for some reason the system date was set to 2098 haha.
>
> I'll try setting it to the correct date and see what happens and report back.
yeah, I'd be interested in knowing if that actually fixes it
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: Haze]
#371406 - 11/27/17 05:27 AM
|
|
|
HOLY CRAP THAT FIXED IT!!!!!!!! Corrected the CMOS date and now it works perfect. DOSBox works again as well.
THANK YOU THANK YOU THANK YOU so much for the help!
Any idea why that would only affect neogeo games?
|
|
|
|
Re: Sudden problem with MAME and Neo Geo...
[Re: pb1592]
#371407 - 11/27/17 10:02 AM
|
|
|
Apparently it affects any system that handles an internal calendar. MAME tries to get the date from your PC and then passes it to the emulated system BIOS. This is so you don't set the date every time you boot the system as if the PCB battery fails (just like your motherboard battery). You can see the date right there when you enter service mode (by default press F2 key).
NEOGEO in specific uses an internal clock to keep track of statistics operators can consult in service mode. Also there is at least one game (Art of Fighting 3) that makes use of the internal calendar for setting in-game events on certain dates (i.e. a character birthday).
|
|
|
Index 
Threaded 
Sudden problem with MAME and Neo Geo...
Reply
[Re: 
