Howdy, I'm having a wee bit of difficulty getting the latest release to work. The last release I had to putz around with it for a while and finally I did get it to work. But with the latest release I've tried and tried and tried, everything I tried with the last one. I get it to compile with Visual C++ 2005 Express all patched and everything (as I said, it worked eventual on last the last release). I have 2 issues actually, one is the MQ2auth.exe, I run that, but then I'll still get the error from running MacroQuest2.exe saying I am not authorized to run it. ((And when I do get it to work, I get the MQ2 tray icon, and I launch Everquest, and it doesn't show up in game, at either the character select or the ingame, and no commands will work either, I get the "This command doesn't exist blah blah blah" bit. ))I messed up that part, never got it to launch right.
The best wiki page I could find was http://www.macroquest2.com/wiki/index.p ... king_in_EQ And I tried the suggestions in there already, but I can not think of anything what so ever that would even remotely work. I know I didn't edit the wiki, because the advice in there was all I could some up with myself, and it seems logical enough.
Thank you in advance for your help.
[EDIT] I forgot a few details. I run everything as admin, I leave UAC off, and I have tried compatability mode also to no avail.
MQ2 running but not working in Vista x64
Moderator: MacroQuest Developers
MQ2 running but not working in Vista x64
Last edited by saren on Thu Jun 11, 2009 12:33 pm, edited 1 time in total.
Your post is poorly written and quite vague, so I'm not sure if I understand it correctly, but I'll attempt to answer what I think are your two questions:
1. You have compiled MQ2, but when you run it, it says not authorised.
Did you run the MQ2Auth.exe after you compiled or before. It needs to be run before you compile, and if you run it afterwards, you will need to clean and then re-compile in order for it to recognise the new codes.
If in doubt, delete everything and start again from scratch with the instructions in the wiki page [[MacroQuest2:Compiling]]. The instructions for VC++ 2005 on vista64 work 100%, I used the exact steps to get it running on my PC.
2. You have launched MQ2, have the tray icon, but it does not show up in game.
Does this mean you managed to get it compiled and authorised? (it's not clear from your question whether this is true)
The only time I've seen this is when you run MacroQuest2.exe and eqgame.exe using different accounts with different permissions. I use vista64 myself and I have UAC disabled. My account is an administrator on the PC and I start MacroQuest2.exe as my normal account, and then I start EverQuest, and everything works fine. Make sure you start MQ2 before EQ, since there can be issues starting it afterwards.
1. You have compiled MQ2, but when you run it, it says not authorised.
Did you run the MQ2Auth.exe after you compiled or before. It needs to be run before you compile, and if you run it afterwards, you will need to clean and then re-compile in order for it to recognise the new codes.
If in doubt, delete everything and start again from scratch with the instructions in the wiki page [[MacroQuest2:Compiling]]. The instructions for VC++ 2005 on vista64 work 100%, I used the exact steps to get it running on my PC.
2. You have launched MQ2, have the tray icon, but it does not show up in game.
Does this mean you managed to get it compiled and authorised? (it's not clear from your question whether this is true)
The only time I've seen this is when you run MacroQuest2.exe and eqgame.exe using different accounts with different permissions. I use vista64 myself and I have UAC disabled. My account is an administrator on the PC and I start MacroQuest2.exe as my normal account, and then I start EverQuest, and everything works fine. Make sure you start MQ2 before EQ, since there can be issues starting it afterwards.
Ok, I guess I need to clarify. I realized a mistake I was makeing, I never did get MQ2 to run without it erroring me saying it wasn't authorized, I just didn't realize it didn't not open when you got that message. So, I never did get a proper try. And what you've been saying for #1, is what I've been doing the whole time, I run it before I compile.