/face wall ; call sub "Beat head against wall"

homburg · Post by **homburg** » Wed Apr 07, 2004 10:07 am

Okay, let's get a few things out of the way...

1) I am new to MQ.
2) I am essentially clueless on coding.
3) I am happy when I can get my home network to work, let alone doing anything complex with my machines.
4) I've read the manual, readme's, docs, and searched this forum (though not extensively, I'll admit)

That said, I did download, compile, and am using MQ2 on my primary box. Love it. Even though I'm still screwing around with macros to get them to work like I want, I'm wildly impressed with this program, enjoying it immensely, and completely understand why so many of my MQ-using friends HATE to play right after a patch.

The problem is box #2. It is subpar, waaaaay subpar. It runs EQ, sure, but performance is stinky. I tried to get my copy of .NET to load on the machine and it choked, spit it back, and laughed darkly when I tried a second time. So, bright boy that I am, I figure I'll just MQ2Auth.exe on the subpar box and compile it on the good machine. Tried it, no go. Keeps saying "This copy of MQ2 is not authorized for use on this machine" etc.

I searched and found a thread where this precise question was asked, and then the bloke asking posted and said it was AOL causing the problem somehow. I don't have a handy AOL to blame for my troubles here, so I figure I'll just ask those what know on this forum.

If anyone has ideas/tips on what I might do in this case, please post. I'm dying to run my DruidBot script (modified from an existing macro in the Depot, props to the folks there, namely some-eq-player in this case). Save me a lot of (probably comical) running across the house when I two-box with the wife's toons.

As an aside, I did contemplate trying the cool Free Trial method above, but I figure that is, at best, a short term fix. I don't want to have to do that each time I need to recompile. I'd rather just fix the current problem and be able to do it using the compiler I have when the next patch hits.

And no, I can't afford to upgrade the crappy 2nd machine. Thanks in advance!

Mckorr · Post by **Mckorr** » Wed Apr 07, 2004 10:23 am

1) Run MQ2Auth.exe on the machine with the compiler. Create MQ2Auth0.h.

2) Copy MQ2Auth.exe and MQ2Auth0.h over to the second, crappy machine.

3) Run MQ2Auth.exe on the second machine. MQ2Auth0.h gets updated.

4) Copy MQ2Auth0.h from the crappy machine to the MQ2Main subdirectory on the good machine with the compiler.

5) Compile. MQ2 now authorized to run on both machines.

6) Copy MacroQuest.exe, YOUR ini files, and all MQ2 dll files from good machine to crappy machine.

7) Enjoy

This issue has been addressed countless times. You just didn't read far enough.

homburg · Post by **homburg** » Wed Apr 07, 2004 10:49 am

Thank you, McKorr, and mea culpa. Eyes started to bleed after the 6th page of posts =)

magictiger · Post by **magictiger** » Wed Apr 07, 2004 11:27 am

http://macroquest2.com/phpBB2/viewtopic.php?t=4132

Was all explained right there, linked off the stickied "HOWTO: Compiling MQ for use on more than one computer" in the MQ2: Announcements forum, and linked in a post by Lax.

Glad you got it working though.
In my experience, you don't even need to send them your mq2auth0.h file, just have them paste their created one back to you and append it to your .h

Lax · Post by **Lax** » Wed Apr 07, 2004 11:57 am

Oddly enough, you should have found that information from the link you were supposed to have read before downloading...

DO NOT DOWNLOAD WITHOUT READING THE Introduction to MQ2. IF YOU DO NOT READ, YOU FORFEIT YOUR PRIVELEDGE OF FREE SUPPORT. YOUR FIRST QUESTIONS ARE ANSWERED WITHIN.
... brings you to http://macroquest2.com/phpBB2/viewtopic.php?t=5371

BEFORE COMPILING WITH ANY METHOD - Run MQ2Auth.exe (NOTE: IF YOU ARE COMPILING FOR SOMEONE ELSE, THEY NEED TO RUN MQ2AUTH.EXE. THE FILES MQ2AUTH GENERATES ALLOWS MQ2 TO RUN ON THE COMPUTER IT IS GENERATED FROM. THE GENERATED FILES CAN ALLOW MULTIPLE PEOPLE TO RUN THE SAME COPY, SEE THE COMPILING FOR FRIENDS TOPICS)
... see the compiling for friends topics... ok, back out to announcements

Sticky: HOWTO: Compile MQ2 for use on more than 1 comp (MQ2Auth.exe)
... 4-5 different ways of explaining the same thing since people dont get it

homburg · Post by **homburg** » Wed Apr 07, 2004 1:22 pm

I read the initial linked topic before I compiled the original, and, frankly, it confused the heck outta me. I also didn't read it that heavily as I thought, incorrectly, that my crapppy box would still be able to compile the program. As I said, I'm not that hot with the Evil Box. That said, I followed the links around a bit more and will try both the method presented here (and failing that, the floppy method.

Insofar as I understand it, it appears that my best bet is to recompile it for both machines, after keying both using the same MQ2Auth.exe, right?

Nevermind, I'll beat on it a bit. Just goes to show that there exists a gulf between reading and comprehension still on this subject. Not terribly surprising given my strident lack of clue on the subject. Thanks again.

dweomer · Post by **dweomer** » Wed Apr 07, 2004 2:27 pm

when the mq2auth thing was implemented, first thing i did was move the mq2 code onto a shared drive where all my machines that use mq have access to it. then on each machine i ran that mq2auth.exe (yes the one on the shared drive) and it in turn updated mq2auth0.h (yes originally it was mq2auth1.h and mq2auth2.h but those have since been deprecated) for each machine in that one spot, no copying. then on my compile box, you guessed it, i compiled. then i copy the executables and readme and the bmpwad (and any other release files not generated by the compile except macroquest.ini) into each machine's mq2 "install" folder. boom, done. it really isn't difficult, be for some reason many many people just don't "get it." /shrug

so a recap to be clear:
-- you only need to compile this shit once per code release (that's the zip file), no matter how many machines you have
-- set up a shared drive that all machines you want running mq2 have access to (example: code exists on your compile box but you share the drive/folder so other machines can map/access it)
-- on each machine you want to run mq2, map that drive/folder that you just shared from your compile box (or wherever)
-- run mq2auth.exe (on the mapped drive, remember?) once from each machine. once you've done this right, you never have to again for these machines. if you get a new machine on your network and want it to use mq2 you will need to run mq2auth.exe from that new machine only and then recompile.
-- copy from the Release folder *.exe, *.dll, readme.html, bmpwad8.s3d, changes.txt, locations.txt, gpl.txt, itemdb.txt, and possibly the Macros directory/folder (i don't anymore as ive found most of the shit in there is way outdated) to an "install" folder/directory set aside on or for each machine.
-- run mq2 on each machine from it's "install" folder, and be happy.
-- the end

magictiger · Post by **magictiger** » Wed Apr 07, 2004 2:30 pm

Don't feel too bad. This was what hung me up when I first tried to get it working.(I had to use the free .net 2003 trial though... heh) Eventually it'll click and you'll understand why it's so hard until you get it.

And you'll appreciate it.

Look at it like you would a puzzle game. When you get stuck, you think it over for a while, then take a break, maybe get a nap or a good night's rest, and the next day you get another idea to try. :)

At least you have your own compiler and aren't limited to 3 hours to try, find the problem, solve the problem, and try again. :) Yes, I've learned the error of my ways and have my own compiler now.

homburg · Post by **homburg** » Thu Apr 08, 2004 12:05 am

Working, wooT! Thanks to diligence, and the great advice I've recieved here, MQ2 is chugging away both on my good box and my gimp one. Thanks for all the help!

/face wall ; call sub "Beat head against wall"

/face wall ; call sub "Beat head against wall"

a simple solution