You need a 64bit OS to test this. I suspect that it has something to do with the name of the ini: 64bit commandline version uses mame.ini.
I will see what i can do.
Well I may not have a 64 bit OS set up to test this but I can tell you what the MaLa code is trying to do so you can test this manually.
I think the problem is that MaLa is not failing to find the mame.ini but that the mame.ini is not being created ?But what I have done (for the next version) is show an error if this happens. It helps a bit
- When you hit the Config button it checks to see if a mame.ini (or whatever the name of the mame is .ini)
- If it does not exist then it asks you if you wish to create one
- If you choose yes then it fires a command (using the code below) to mame to create one. I assume this is the part that is failing for you for some reason? I guess I need you to confirm what command to mame makes this work on your OS and mame version?
ie at a command prompt (found in start- accessories) type something like 'mame - createconfig'. As that is effectiveley what MaLa is doing. If that does not work you need to do some home work with the mame folk on what command is required to create a mame.ini file with your OS? XP64? and mame64?
Anyway let me know how you go
// create a standard ini file
dir := ExtractFilePath(AMameExecutable);
exe := ExtractFileName(AMameExecutable);
param := '-createconfig';
SetCurrentDir(dir);
case Win32Platform of
0,1: RunProcess('command.com /c ' + exe + ' ' + param, True, frmMain.FMameWindowState); //Win9x
2: RunProcess('cmd.exe /c ' + SystemStr + exe + ' ' + param + SystemStr, True, frmMain.FMameWindowState); // Win2000 and WinXP
end;
SetCurrentDir(ExtractFilePath(ParamStr(0)));