> haw...you found a good one ;)

You're welcome.

> It's a behaviour of the CreateProcess runtime function

I figured it was the case of a FileOpen command that had overloaded methods (or a forgotten CD) that either took just a filename or filename and path and the wrong one had been coded against, therefore it assumed current directory, then %PATH%.



> - Who the hell keeps a mame binary in the cmpro folder ;)

I don't know why I had it there, but this aggravated me for about 1/2 an hour as I was doing a Mame 87 to 96 upgrade last night.. I tried everthing from manually deleting allthe cache and dats and restarting...then I saw the exe sitting there that had gotten there last November for some strange reason. But obviously, with the call, if I had Mame in my Windows folder it probably would have done the same thing... so more apt to have been found.


> - you don't need xml2info. CMPro got a buildin xml parser.

I realized that after I posted... IIRC we needed this around mame 84 for a couple releases, right? Just wanted to be thorough.

Thanks for confirming the bug and for fixing it to prevent someone else from pulling their hair out.

But thanks again for the great program.