Forced Patch 5/30?
- Thread starter davebob35
- Start date
eddie43302
Senior Member
Nope no forced patch.. maybe tommorow...
Kannkor
Ogre
Follow the directions EXACTLY in that big blue screen that pops up.
Thanks for the input so far. This morning I followed the information on the blue screen, getting the EverQuest2.exe the link provided, and deleted the one there and replaced it with that one. No luck. Thinking I might update the isxeq2.dll file, manual patch I think it is called. Read that on a couple of posts that has helped. Also went back and checked the install guide. The .exe that I am using is EQ2.exe not EverQuest2.exe. I tried changing the .exe, using the EverQuest2.exe, but then get the 999 FPS lock up. I checked to make sure that the compatibility box is not checked in the InnerSpace properties. FYI I am running Windows 7 and it had been working fine until Wednesday morning. Again I appreciate any advice.
eddie43302
Senior Member
not even a forced patch today.. so the problem is on your end.
Kevinshp
Well-Known Member
Yes absolutely each switch changes th EXEI too have been getting the 'patch day' blue box.
Guess I need to look into the problem at my end too
Edit: could something have messed up at my end by switching from the Euro to US client?
appleuser
Well-Known Member
Thank you Kevin, that makes a lot of sense. The console tells me to use the exe dated 24 May, but when I go to http://www.isxgames.com/isxeq2/exe/ the file I download says it was modified on 23 May... is that right? If it's not right could someone point me to the correct exe please?
Kannkor
Ogre
You HAVE to use everquest2.exe
Using EQ2.exe will not work.
If you're still getting the 999 FPS lock up, restart, then check compatibility mode again. If it still is locking up do this..
Turn compatibility mode ON.
Restart your computer.
Turn compatibility mode OFF.
Restart your computer.
Try again.
No, it does not. The console says to download the file that was patched on whatever day. When the exe is dated is arbitrary. Thankfully, Amadeus has simplified this process and, instead of having to choose which file to download from a list of hundreds, there is now only one to download and it is always correct. Perhaps the error message in the console could be changed since the download process was changed.