|
Search the Community
Showing results for tags 'UAC Administrator'.
Found 1 result
-
Windows 7 64 bit user, trying to update from MAME 149 to 160. Getting some strange behavior that's driving me nuts. First of all, the previous 64bit verson of MAME 149 worked beautifully with Gameex. Installed in a directory named "MAME" in the Program Files directory. When I click on MAME64.exe in this directory, it just works. No UAC prompt, it just starts. When I tried installing MAME 160 into a directory named "MAME160" in the Program Files directory, I get different behavior. Let's forget about Gameex for a second, which only gives me a black screen now. The problem is in permissions or administrator rights or some damn thing. When I click on MAME64.exe in this directory, The UAC (User Account Control) screen comes up. Why does this new installation of MAME 64 require UAC when the old one did not? I think this UAC screen is what is stopping Gameex. Right clicking MAME64.exe and running as administrator still brings up the UAC screen. In fact, right clicking properties of MAME64.exe and checking the compatibility tab, the checkbox is in fact "run this program as an administrator". So why does the UAC screen come up? Strangely, the V149 installation which is the same /program files directory, does not have "run this program as an administrator" checked, but yet runs fine without a UAC screen. Any suggestions? I'm pretty baffled. I can install 160 in a directory on my desktop and avoid the UAC nonsense, but normally I would install a program where the rest of my 64 bit programs go, which is in c:program files. How did I get V149 installed in that directory before? Thanks for any advice.
