MaLa errors

[Onyx_PghPA]

I posted this over in the Software forum, but it was, um, "suggested" that I put it here. Tried to get it moved, but no luck, so I'm re-posting:

Having two problems with MaLa; after spending weeks finally fixing all of my other emulation problems.

1)  It seems whenever I exit a game using ESC (either the ESC button on a keyboard or the control panel button I have programmed for ESC), I get an error message:

http://www.flickr.com/photos/pctech714/4686280823/#

2)  Whenever I first load MaLa, have DAPHNE selected as my emulator and right-click and select options, a bunch of error messages pop up:

http://www.flickr.com/photos/pctech714/4686932782/#

Anyway, anybody encounter these problems and know of a solution.  #2 is fairly minor -- I know just to avoid making changes to options in DAPHNE, but the first one kinda sucks.

Thanks,


Joe


My arcade cabinet hardware:

MSI K9N6PGM2-V motherboard (onboard video and 10/100 networking)
AMD 64 X2 4800+ CPU
2GB DDR2 800 RAM
16GB solid state hard drive
27" D9800 Wells Gardner arcade monitor
Windows 7 Ultimate 32-bit

MaLa and Ultramap are on the cabinet's hard drive, but the emulators, ROMs, etc. are all on a shared network drive on my server PC.  Control of the cabinet (for making changes and so forth) is done through PC Anywhere, so I don't need a keyboard or mouse. I'm using MAME v0.138 (the most recent, command-line, full version). I have also deleted all of the .cfg files for each game. All drivers are current.
 

[loadman]

1) I have not seen that Mame error before. I just used 138

2) The error says to ckeck the mala logs. What do the logs say?


- Are you using the latest mala beta? I suggest doing that and setting the logging level to verbose and sending the relevant log section.

[Onyx_PghPA]

2) The error says to ckeck the mala logs. What do the logs say?

I eliminated the redundancy, but the following error messages were repeated multiple times when run on different dates:

2010/04/21  17:10:23.99   Error: Object Class: TTimer, Object Function: PlaySound, Exception Class: EAccessViolation, Exception Message: Access violation at address 0044D1A8 in module 'MaLa.exe'. Read of address 00000004

2010/04/22  20:34:18.55   Error: Object Class: TTimer, Object Function: LoadLEDConfig, Exception Class: EAccessViolation, Exception Message: Access violation at address 005613B3 in module 'MaLa.exe'. Write of address 00000010

2010/06/09  19:14:14.17   Error: Object Class: TPopupList, Object Function: LoadLEDConfig, Exception Class: EAccessViolation, Exception Message: Access violation at address 0044D1A8 in module 'mala.exe'. Read of address 00000004

There was a stack overflow after all of the above, but I lost it somewhere. Guessing the huge number of the above error messages caused it.

- Are you using the latest mala beta? I suggest doing that and setting the logging level to verbose and sending the relevant log section.

This was from using the most current full release. I just installed the beta and will follow up later in the week with my results from that.


Joe

[empardopo]

Windows 7 could be the problem. Have you checked the same configuration in another SO? I recommend windows XP to have less problems.

[Onyx_PghPA]

Have you checked the same configuration in another SO? I recommend windows XP to have less problems.

I'm guessing you meant O/S.  Just for the heck of it, I wiped the drive clean and did a new XP SP3 32-bit installation.  MAME is still crashing whenever I exit a game.

Also, I'm now using the most recent MaLa beta and getting the same result.

I'm starting to think it's a MAME problem.  I might revert to a previous release to see if that works.


Joe

[Onyx_PghPA]

Reverted to 0.136 and the problem goes away.