confusion about latest release of MQ2

thenatureboy · Post by **thenatureboy** » Mon Feb 16, 2004 12:28 pm

allright, I'm sure I'm going to get some flames for this but I can't seem to troubleshoot this myself. I compiled the latest source zip file (I ASSUME was created after the GoD patch) and did everything I was supposed to. After I execute MQ2 and then start up EQ I get a pop-up that says "incorrect client version". Did I somehow download the pre-GoD version of MQ2?

Thanks.

MacroFiend · Post by **MacroFiend** » Mon Feb 16, 2004 1:12 pm

It sounds more like your INI files are old/incorrect. Was this a clean install of MQ2 or did you just copy your newly compiled DLLs in to a pre-existing folder?

If this was not a new install, copy all .DLL, .EXE files as well as EQGame.ini in to your other folder from the release folder.

Another possibility is that you aren't on an english server. Non-english servers do not always update at the same time the english servers do. If you are sure you have everything right, the other thing you can try is to change "ClientOverride" in eqgame.ini to 1. That will force MQ to insert itself no matter what ... but if anything I mentioned above is true, you will likely crash to desktop.

yoda · Post by **yoda** » Wed Feb 18, 2004 3:28 pm

I am having the incorrect client version issue also, my eqclient.ini in my release folder has a date of 2/12 on it. Should I be grabbing the one from EQ folders and putting in there when I compile, or am I doing something else wrong?

Edit: Well, thats no help, I did a fresh download, deleted everything I had in compile folder, copied my mq2auth0.h file into the MQ2Main folder, compiled (normal and also tried copying the eqclient.ini file from EQ folders, and neither of them work, both say incorrect client version....can anyone tell me what i am doing wrong?

Lane · Post by **Lane** » Wed Feb 18, 2004 5:18 pm

EQ patched today. MQ will not work as it sits. Wait until there is a new .zip file/message saying things are "ok" again.

I swear, every time they patch this gets posted.... To the first guy that posted... You might be hosed as you had a problem before the patch, but don't worry about it until things are fixed again and you can test on a good system.

Usually, the best thing to do is make a new directory with the .zip file download and compile in that new dir tree. This fixes like 90% of the problems people seem to have.

-Lane

yoda · Post by **yoda** » Wed Feb 18, 2004 5:41 pm

ok, thank you very much.

arnott · Post by **arnott** » Wed Feb 18, 2004 7:55 pm

thenatureboy,

pre GoD i encountered the same problem. Although it appears to be quite common I could not find it mentioned in the RTFM. There is a soulution however. If you use the search function and look for "incorrect client version" you will find a simple work-around.

thenatureboy · Post by **thenatureboy** » Sat Feb 21, 2004 2:49 pm

thanks for the input people. I just re-downloaded the zip file and recompiled everything and made damn sure to put dates on the folder name to avoid confusion. I got everthing to work. But not surprisingly there's a new EQ patch so I have to do it all over again. I almost feel naked playing without Macroquest.

beatnik007 · Post by **beatnik007** » Sun Feb 22, 2004 6:51 am

the other thing you can try is to change "ClientOverride" in eqgame.ini to 1. That will force MQ to insert itself no matter what ... but if anything I mentioned above is true, you will likely crash to desktop.

Downloaded fresh zip 5 mins ago. Compiled and ran from fresh directory. Got invalid client error. Set ClientOverride=1. eqgame.exe crashed as suspected.

Does this mean the current release is invalid?

Pheph · Post by **Pheph** » Sun Feb 22, 2004 8:20 am

Same version I'm running, and it's working fine.

Make sure you don't somehow have the file cached in your browser, and are still using the old zip.

beatnik007 · Post by **beatnik007** » Mon Feb 23, 2004 6:36 am

Just cleared the cache and downloaded again now. It's still not working for me.

I know this is going to be my own stupid error somehow, but I just can't see it. Is the client version "Wed Feb 18 03:17:xx 2004" the up-to-date one?

Is this somehow a timezone issue? (I'm GMT +11).

Mckorr · Post by **Mckorr** » Mon Feb 23, 2004 7:41 am

Sigh...

Okay, one more time. The time and date in your eqgame.ini folder has to match the time and date of eqgame.exe in your EQ folder.

Latest patch was Feb 18th. Patched version of MQ was released on the 19th.

The only thing you should be saving from build to build of MQ are the ini files, all except eqgame.ini which needs to be updated every patch.

beatnik007 · Post by **beatnik007** » Tue Feb 24, 2004 5:35 am

Thanks Mckorr

ClientVersion=Wed Feb 18 03:17:xx 2004

eqgame.exe timestamp is Wed Feb 18 04:17:xx 2004

I guess the build doesn't account for daylight savings when generating the ini

Beatnik

Mckorr · Post by **Mckorr** » Tue Feb 24, 2004 8:37 am

Daylight Savings Time is the biggest cause of this error. Many, many posts on this if you do a search for "incorrect client version".

Pheph · Post by **Pheph** » Tue Feb 24, 2004 11:15 am

How about adding an MD5-hash of eqgame.exe to the ini-file and just check this one instead?
Keep the ClientVersion-field for readability, but don't actually use it.

Mckorr · Post by **Mckorr** » Tue Feb 24, 2004 11:21 am

Client version in eqgame.ini is sort of a checks-and-balances thing. It keeps you from using the wrong version of MQ... which also keeps you from setting off flags on the server when the memory protection offsets are incorrect.

Yeah, it could be built in. The entire eqgame.ini file could be built in, and probably will be someday. It's a legacy from MQ1 that we just never got around to doing away with.

Since we now need to find a gazillion offsets for eqdata.h anyway moving the ini file in there might be a reasonable thing to do, and we could then implement a straight out read of the date from eqgame.exe to make sure we are using the right version of MQ.

I'm already working on doing away with locations.txt, another legacy file from the 2nd gen mouse code. It's all a matter of finding time to do these things. Kinda busy at work atm, trying to get everything in order in my shop before I retire in April.