haw...you found a good one ;)
It's a behaviour of the CreateProcess runtime function which is used to run mame.exe. I usually change to the exe's folder and call CreateProcess from there...now I reread the docs for CreateProcess ...and found out why it reacts weird:


If the file name does not contain a directory path, the system searches for the executable file in the following sequence:

The directory from which the application loaded.
The current directory for the parent process.


So it indeed grabbed mame.exe from the cmpro path....
I "fix" that in the next version..


Some notes though:
- Who the hell keeps a mame binary in the cmpro folder ;)
- you don't need xml2info. CMPro got a buildin xml parser.

Roman Scherzer
ClrMamePro