MacroQuest64

Hey guys :) It looks like MQ2Auth does not run on Win7 64 bit. The bottom line is I get the not authorized to run on this machine. Please use MQ2Auth to correct the problem. Here's what Ive done over the last few days to try to correct it:

Tried using both Visual Studio 2005 and 2008 according to the wiki compile instructions found here: http://www.macroquest2.com/wiki/index.p ... _and_xp.2A. Tried changing all exe's to XP, XP SP3, Vista, and Vista SP2 compatiblity mode, as administrator. Made sure all associated folders were not write only, and admin priveledges were applied. I ran MQ2Auth both before and after compiling, and tried re-compiling in each version of VS.

Any ideas? If I missed something please feel free to /smack me and publicly make an example of me

I have edited the wiki: http://www.macroquest2.com/wiki/index.p ... uth0.h[url][/url]

edit: It worked fine under Vista 64 bit. I installed Win7 last week.

It works. Follow the instructions for Vista64.

I'm running Win7 64 bit release candidate.

Hmm. Im pretty software savvy. I guess I'll keep trying.

Using W7 64bit RC myself without a problem. Here is what I do:

1. Run MQ2Auth
2. Compile

When new ZIP is available:

1. Download
2. Unzip only changed files
3. Compile

Runs without a hitch and I don't redo the MQ2Auth before each compile.

I have this issue every time I reboot or do a Windows update, I have to recompile MQ because MQ2Auth gives me a different identity code every time for some reason.

With Windows 7 64 bit, never had an issue like this with XP or Vista.

Run both MQ2Auth and MQ2 as administrator and with XP compabitiliy and you won't have this problem.

The easiest way to do that for mq2auth is to start up a CMD shell in administrator + XP mode and run mq2auth from there.

Strangely I did have this same problem even using "run as administrator", when it was located in a folder off of c:\ (which I had all permissions to), so I moved the MQ2Auth.exe onto my Desktop and it worked fine there.

i can run MqAuth fine and edit it adding my 2nd machine in. I then compile and it will run fine the first time. When I shutdown and boot back up the next day, i get the "This system is not auth" message and to run Mqauth to fix it. I have to recompile again and it will work until I shutdown MQ and then end up back in the same boat. I am use Visual Studio 2010 and am not getting any errors. Very much a pain on Win 7 with 64bit.
Sorry forgot to mention that my 2nd system is running Vista ( yea I know) and it works find without any auth errors.

tled wrote:i can run MqAuth fine and edit it adding my 2nd machine in. I then compile and it will run fine the first time. When I shutdown and boot back up the next day, i get the "This system is not auth" message and to run Mqauth to fix it. I have to recompile again and it will work until I shutdown MQ and then end up back in the same boat. I am use Visual Studio 2010 and am not getting any errors. Very much a pain on Win 7 with 64bit.
Sorry forgot to mention that my 2nd system is running Vista ( yea I know) and it works find without any auth errors.

You shouldn't have any issue if you run mq2auth.exe & macroquest.exe with the same compatibility settings. Run as admin, and you can set compat mode os to like xp sp3. Just make sure you run them both with the same settings.

That's assuming something isn't changing certain values on your system which would cause it - which would be very unusual, and of no use that I can see.

I'd really think it's just that macroquest.exe is not getting ran with the same compat settings as you run mq2auth.exe with.

htw

Yea, I ran them both in compat Xp mode as admin. What I had to do to fix this was run it mqauth in cmd window and the it worked for some reason. No idea why, but hey it worked. ^) The drawback now is that mobs are not showing up on map on the Vista machine. Think i will just move compiler over to vista and do the it over there. Too many quirks with Win 7 in 64bit mode that I have run into. Like it much better than Vista, but some things still need tweeking to get them going correctly. Thanks for the info though.