I re-D/L the new tools. It appears that the file I had was from Jan 2nd. The new D/L from the 4th compiles & executes just fine so far. (Wing Force anyone?)
Thanks for the help everyone. Hope this fixed yours too Zag!
DISREGARD- It's compiling fine where it is. That is not the problem. When I go to execute MAME is when it comes up with that error. It's looking for a .dll that IS in the new tools directories but if you move it to the MAME directory it gives the other error Zag quoted. I could try to register that file (& put it wherever) but it would still give the 2nd error so why bother...also MAME is stand alone so it does not need anything else installed to run.
I am using my source from Github. Even if I update the tools from there it should have no bearing on these new build tools.
I don't have the time to mess with it now. I'll try more when I do have time.
Pessimist: Oh, this can't get any worse!
Optimist: Yes, it can!