EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Specialt1212 on 26 January 2012, 14:38

Title: Mame Dat help
Post by: Specialt1212 on 26 January 2012, 14:38
Maybe I'm doing something wrong but I'm getting an "error while saving settings" error message when I try to load the mame64.exe into clrmamepro.

Just to make sure I'm not doing anything wrong,

1. Click on Create in the Profiler
2. Navigate to the mame64.exe file
3. Type MAME in teh description field
4. Select MAME as the emulator
5. Click Create Profile

I don't know why I'm getting the error but can someone post the latest mame dat file because I can't seem to get it to work  :-/
Title: Re: Mame Dat help
Post by: Roman on 26 January 2012, 15:18
Sounds weird...are you running Windows7/Vista and installed cmpro in an UAC protected folder (like c:\program files), if so, select a different place. However the mentioned setup should work flawlessly anyway....
I try to reproduce this at home. Please let me know where you installed cmpro to.
Title: Re: Mame Dat help
Post by: Specialt1212 on 26 January 2012, 15:21
I have clrmamepro installed at

C:\Users\Special-T\clrmamepro

I'm running Windows 7 64 bit version.
Title: Re: Mame Dat help
Post by: Roman on 26 January 2012, 18:19
Works fine here in c:\users\(username)\clrmamepro

Try again with a different (non-UAC controlled) folder or check if other programs (like virusscanners) are interfearing.

Title: Re: Mame Dat help
Post by: Specialt1212 on 26 January 2012, 18:38
well after moving the clrmamepro to the desktop it worked although I also decided to try creating the mame date in the default [Profiles] folder instead of a sub folder... I don't know if that had anything to due with it?

Well it's off to work now but I'll scan my set later tonight just to make sure it's working properly.
Title: Re: Mame Dat help
Post by: Roman on 26 January 2012, 18:43
I also tested a profile subfolder...worked ;)
No idea...maybe a temporary windows access right hickup...
Title: Re: Mame Dat help
Post by: Specialt1212 on 27 January 2012, 18:39
Just wanted to follow up, I don't know what the problem was but it seems to be fixed now.

Thank you for the help!