Broken in recent Mala release: nested Malas *Fixed*

[Gray_Area]

This doesn't work since at least Mala 1.73. When clicking on a nested Mala, it says 'Mala is already running'.


....of course, this would be a non-issue if 'other emus' had an xml feature/entry box.

[loadman]

This doesn't work since at least Mala 1.73. When clicking on a nested Mala, it says 'Mala is already running'

....of course, this would be a non-issue if 'other emus' had an xml feature/entry box.

Hi, yes it is deliberate that I don't support multiple MaLa's running , more pain than gain from a support point of view...

What is the feature box of which you speak?

[Gray_Area]

Hi, yes it is deliberate that I don't support multiple MaLa's running , more pain than gain from a support point of view...

1.05 did, though.

What is the feature box of which you speak?

The "ROM info file (XML)" in the MAME configuration. If other emulators had this, multiple Malas would be super easy, via 'other emus'. (Of course, any other emulator could benefit from it, too.)

[loadman]

Hi, yes it is deliberate that I don't support multiple MaLa's running , more pain than gain from a support point of view...

1.05 did, though.

What is the feature box of which you speak?

Yes 1.05 caused me pain (from a support point of view), I have little time to do MaLa stuff as it is without getting weird questions due to unexpected results as users were loading one than mala at a time by mistake.

The only simple solution I can offer is that I make it configurable that MaLa not allow other MaLa's to run, but default it would not. What do you think?

The "ROM info file (XML)" in the MAME configuration. If other emulators had this, multiple Malas would be super easy, via 'other emus'. (Of course, any other emulator could benefit from it, too.)

Who would create these XML's for 'other emu's? MAME creates the XML upon request.

[Gray_Area]

I'm more interested in native rom info file support for other emus, so let's discuss that for a moment. I don't know what kind of rom info file type other emus use. It just happens to be xml in the case of MAME, but does Mala need it to be xml?

[loadman]

I'm more interested in native rom info file support for other emus, so let's discuss that for a moment. I don't know what kind of rom info file type other emus use. It just happens to be xml in the case of MAME, but does Mala need it to be xml?

Well i'm not going to change MaLa from using XML for mame as there is too much work put into it and Mame already builds it upon request...

But if I was to add a similar thing for other EMU's then it DOES NOT need to be in XML.

But does it not make sense to have it in a format that is already supported in the community for other emulators?  Are there such files 'rom info' ?

[Gray_Area]

I mean, is the 'field' generic, and any format can be used, depending upon the emulator?

[loadman]

I mean, is the 'field' generic, and any format can be used, depending upon the emulator?

Well anything is possible but I would prefer to keep the work reduced depending on what data is available out there for other emulators?

[Gray_Area]

I don't know what most other emulators might use. I found out that VPLauncher for example uses a dat file - a database of Visual Pinball tables made by the author of VPLauncher. I would guess that could be used for Mala.

I might guess that most emulators use either xml or dat. But I'll ask in Software, and see what people say.

[Gray_Area]

So this is what Howard_Casto said:

http://forum.arcadecontrols.com/index.php?topic=110616.msg1172593#msg1172593

[loadman]

So this is what Howard_Casto said:
http://forum.arcadecontrols.com/index.php?topic=110616.msg1172593#msg1172593

Yeah, and I value his opinion.

So what file format do you suggest MaLa supoort for MetaData for 'Other Emu's?

[Gray_Area]

I anticipated Howard answering - meaning, so do I. I guess xml, though if it can be more than one, I would include dat.

[loadman]

..well just for now the next version will allow you to open more MaLa's (if you hit return or click OK)

[loadman]

Actually I did better than that.

In the latest beta there is now an option (in Gui-MaLa Start) to allow starting Multilpe MaLa's without any prompt.

Have a try......

[Gray_Area]

I can't tell you what isn't working, but what's happening is that it still says 'mala is already running'. I first used a directory with all the other files copied over, so I thought maybe it was something in the mala ini.

But no, because I deleted that and let it create a new one. I set up a new MAME configuration, noticed it kept my other emu data so obviously that is in a different file though I don't know what, and when I started the nested mala, I got the warning. 'Permit multiple instances of Mala' is checked in the options, though I can't find it in the ini to make sure.

[loadman]

   That does not add up..

Are you sure you have not got and old version of MaLa being called somewhere?

Effectively if the config is set it will behave the way it used to.

FYI: Mala now checks for the follwing setting in Mala.ini on startup

This is set in the config windows but you can do it manually in a text editor instead before MaLa starts.

The following will raise a Warning dialogue if you try and run another MaLa instance

[Starting]
MultiMaLa=0  

If its is set this way you can load lots of Mala's just like the old versions

[Starting]
MultiMaLa=1

Mind you I have only tested launching extra MaLa's from double clicking the shortcut on my desktop on my 2nd screen. Possibly there is different behaviors if launched from MaLa itself?

 
AHH!!

I know what it might be.    Make sure your code is called MaLa.exe  Not MaLa1744.exe

Can you see if it works when you change that please....

If that is what it is I will move the logic order a bit so if you have that config set it does not matter what the .exe is called

    MaLaini := TIniFile.Create(ChangeFileExt(Application.ExeName,'.ini')) ;
    try
    AllowMultipleMalas := (IntToBool(strToInt(MaLaIni.ReadString('Starting' ,'MultiMaLa' ,'0'))));
    finally
    MaLaIni.Free;
    end;
 // AllowMultipleMalas := main.frmMain.FMultiMala;
  sleep(500); // To allow for MaLa restart after a crash
  if (CreateMutex(nil,True,'MaLa.exe')=0) or (GetLastError=ERROR_ALREADY_EXISTS) then
        begin
          if not AllowMultipleMalas then
          Begin
          beep();
          buttonSelected := MessageDlg('MaLa is already running.'+#13+'Start another MaLa anyway?', mtInformation,
          [mbYes,mbNo], 0);
          SetForegroundWindow(FindWindow(PChar(TfrmMain.ClassName+#0),nil));
          if buttonSelected = 7 then Exit;
         End;

        end;

[Gray_Area]

Okay, I got it figured out. Had to remember to change the directory in the main Mala options, as well as replace the mala exe in each sub-folder. Now I'm getting that 'mala is already running....start another mala anyway?' .  If I press 'yes', the nested Mala loads - but is there supposed to be any warning at all now?

[loadman]

No if you have the selected the option detailed in my previous post.

Do you have multiple mala.ini's in different directories?

[Gray_Area]

There's a mala ini for each mala exe, of course.

[loadman]

There's a mala ini for each mala exe, of course.

Well I guess you have to make sure in the [Starting] section of all of them that MultiMaLa=1

Maybee I can add it so that when you get the first  prompt about if you want to Launcher another MaLa that you can choose then and there to set MultiMaLa=1 on each instance of MaLa

[Gray_Area]

I did have the second Mala set for multi. And whether I start a Mala within another one; or start one, go to the desktop and start another one; I get the message.

So it does allow multiple Malas.

I would think that

a) having 'multi' unchecked wouldn't allow another instance, and give the warning.

b) having 'multi' checked would allow another instance, but without the warning message.

[loadman]

I would think that
a) having 'multi' unchecked wouldn't allow another instance, and give the warning.
b) having 'multi' checked would allow another instance, but without the warning message.

Yes how you describe is what I am experiencing.

Is it possible you have missed updating a MaLa.exe or a mala.ini ?

[Gray_Area]

Okay....I started *totally* frm scratch. Downloaded a fresh 1.74 . Downloaded a fresh 1.744, and added that exe to the 1.74 folder.

I did not copy any files over from older directories

Started 1.744 and created all completely new files. Created new config settings, and a new 'other mame emu'. 'Multi' is enabled for both.

If I have the 'parent' Mala running, and start the 'nested' Mala, I get the 'Mala already running....' message. If I start the parent and then go to the nested Mala folder and start that one, I get the message again.

If I start the nested Mala by itself, and then go to the parent folder and start that Mala, I don't get the message.

I thought maybe the default debugging was getting in the way, but turning that off (and turning of 'show tips', just for good measure) in both, didn't help.

I moved the nested Mala outside of the parent folder, and changed the rom path for the nested one in the parent Mala. I get an error about path, syntax, etc.

I moved the folder back into the parent, changed the path data back, and I got that same error. I deleted the emu data, and re-created it. Still the error; it just won't load now.

I don't know. This is a bit wonky. It worked before you made it prohibited. It can't be my system, because I've re-installed the OS a couple times in the last six months, and 1.05 still allows extra malas as usual.

[loadman]

Okay....I started *totally* frm scratch. Downloaded a fresh 1.74 . Downloaded a fresh 1.744, and added that exe to the 1.74 folder.

I did not copy any files over from older directories

Started 1.744 and created all completely new files. Created new config settings, and a new 'other mame emu'. 'Multi' is enabled for both.

If I have the 'parent' Mala running, and start the 'nested' Mala, I get the 'Mala already running....' message. If I start the parent and then go to the nested Mala folder and start that one, I get the message again.

If I start the nested Mala by itself, and then go to the parent folder and start that Mala, I don't get the message.

I know I've asked you before but can you check again...

Can you make sure you have every copy of MaLa you have in your system:
1) Named MaLa.exe  (eg not MaLa174.exe or Mala.exe etc)
2) Every version of MaLa.ini has
[Starting]
MultiMaLa=1

Faling that:
1) I will ask you please to test the latest version of MaLa Beta (releasing later today) this will show what version is running in the 'Another MaLa is running' dialogue.
2) I will make a special version for you with that code completely removed as a test and if that does not work it means you have something inconsistent in your setup. But please check that above first

[Gray_Area]

Okay. I did forget to rename/make sure each Mala was 'Mala'. So, using 1.744, I did that and now it works.

However, this means I have to start with a default configuration, and re-set up the whole thing.

Thanks.

[loadman]

However, this means I have to start with a default configuration, and re-set up the whole thing.

   Really, Why?

[Gray_Area]

Because there seems to be a difference in how 1.73 and 1.74 create and handle inis.

[loadman]

Because there seems to be a difference in how 1.73 and 1.74 create and handle inis.

Still Confused.

Ini files are simple..  You can move the order of sections and items within the section around and it does not matter as MaLa will read it the same way....

Perhaps you mean the other MaLa files for emulator details?

In any case sorry you had to set up again 

MaLa file extensions:

• mlg
MAME game list files
• mlb
MAME bios list
• mll
Layout files
• mle
Non MAME emulator settings
• mlt
Tree files
• ml0, ml1, ml2, ..., mln
Non MAME emultor game list files
• mls
Controller setup
• mld
LCD screens
• mlc
LED config, LED attract mode
• mlj
Jukebox list
• mlf
Filter sets
• mln
Game name files
• mlp
Pattern for the text displays (MaLaLayout)
• pnl
Control panel (MaLaAttractMode)
• led
LED file (MaLa Hardware)
• mplugin
MaLa plugin

[Gray_Area]

No worries.

I tried this again as follows:

- extracted Mala 1.745 to 'Mala1745'; copied all files from 'Mala137', except Mala.exe, to 'Mala1745'.

- copied Mala.exe (1.745) to nested folders; started each one independently and checked 'multi'.

- started Mala.exe in main directory and checked 'multi'.

Exited options, selected nested MAME, pressed start, and got 'mala is already running'.

Now, if let Mala in the main directory create a new ini, and I re-do the options, nested Malas load with no dialogue box. So I have to at least do that. (No idea why they don't all need fresh inis...)

And, there is another issue. The ambience audio is sounding low and 'over-driven' again.

[loadman]

And, there is another issue. The ambience audio is sounding low and 'over-driven' again.

I would check all your volume levels in windows and on the MaLa volume level page.

You may have got in a tangle with all your changes

[Gray_Area]

And, there is another issue. The ambience audio is sounding low and 'over-driven' again.

I would check all your volume levels in windows and on the MaLa volume level page.

You may have got in a tangle with all your changes

I did all that. Nothing apparently out of whack there.

[loadman]

And, there is another issue. The ambience audio is sounding low and 'over-driven' again.

I would check all your volume levels in windows and on the MaLa volume level page.

You may have got in a tangle with all your changes

I did all that. Nothing apparently out of whack there.

Dunno then.

The cause of that was the old Video driver had a bug that altered that main audio level.

That is not happening anymore so I don't know what the issue is you have. It is not happening to me.

Perhaps you could describe the steps you go through to trigger it.