ISX Crashing since patch

[Jazcat]

I assumed ISXEQ2 hadn't been fixed for the latest eq2 forced patch but it seems it has, yet straight after I log in the game still crashes. If I delete the extension the game runs fine.

 

[Algamer]

Are you sure youre using the right version of the Eq2.exe? There was a small patch today and the exe got updated. My isxeq2 didnt want to update while I had the new version, so maybe thats your problem. It never crashed on me though...

 

[Jazcat]

You mean everquest2.exe? eq2.exe is just the launcher.

It depends on what version ISXEQ2 is meant to be running with, was it updated twice?

 

[Amadeus]

Are you sure youre using the right version of the Eq2.exe? There was a small patch today and the exe got updated. My isxeq2 didnt want to update while I had the new version, so maybe thats your problem.

You should NEVER run the patcher unless it is a forced patch.

Run EverQuest2.exe ....then, if the game tells you that the client doesn't match the server ...THEN you patch. Running the patcher any other time is a waste of bandwidth.

 

[Jazcat]

Amadeus can you please verify that ISXEQ2 is meant to be running with EverQuest2.exe SOEVersionString 2007/10/16 16:35:51.

That is the exe im using, the first after the forced patch. As for the crashing problem can you suggest anything?

 

[Amadeus]

Hmm..the time stamp that I check says 16:38:32 ...but, I'm not sure how that compares with whatever methodology you're using.

You can attach windbg to EverQuest2.exe ....then load isxeq2 and send me a crash report as explained in the bug reports forum here ..then I might be able to see what's going on.

However, I'm using the executable that patched on 10.17 myself ...and everything seems to work just fine. Perhaps try redownloading http://www.isxgames.com/isxeq2/ISXEQ2.exe ..and reinstalling too.

 

[Mortedamour]

Same issues here as well. I wasn't able to patch till later in the day.

Grabbed 10-17 exe from twonk and all is good. Same timestamp as Ama's

 

[Jazcat]

Amadeus as a suggestion I think it would be better to start working with the soe version date/time stamp string in the properties of the everquest2.exe and not the date it they push it to the patch server. Using the latter method of identifying the file can cause confusion. For example they patched an exe with the version string of the 16th on the 17th and now the most recent exe has a date stamp string of the 17th. You can see where the potential for problems are here...

Also the day that the file is patched can only be determined from when the player actually patches the file, they possibly may patch the exe the day after now thinking the file is date is a day later. Not to mention players from different time zones that are one day ahead or behind, im sure i could think of more reasons if i tried

Each exe i work with i just copy and paste the version string and use that as my folder name for that everquest2.exe archive.

 

[Amadeus]

Amadeus as a suggestion I think it would be better to start working with the soe version date/time stamp string in the properties of the everquest2.exe

I've been at this a LONG time....

If you open up the CORRECT EverQuest2.exe (the last forced everquest2.exe that came through on the American servers) with IDA you will discover that within the client executable is the date/time stamp of when it was compiled. THATS what I use. It would be stupid for me to code up a bunch of shit to get version info from the executable file when I already have this unique information available to me in memory.

I'll even give you the offsets:

.rdata:00CEA720 aEq2applicationclass db 'EQ2ApplicationClass',0 ; DATA XREF: sub_CBD860o
.rdata:00CEA734 ; char aOct162007[]
.rdata:00CEA734 aOct162007      db 'Oct 16 2007',0      
.rdata:00CEA740 ; char a163832[]
.rdata:00CEA740 a163832         db '16:38:32',0

Those are unique for each and every build of EverQuest2.exe and those are the ones I use to make sure that you're using the proper build. Clearly the last patch of EQ2 was odd with some servers getting odd things and the European servers not getting the patch at all.