This is being provided for some users that seem to need help transitioning between live and the EQ2Emu version. This program should be rather straight forward and has a setup process that you have to follow. If you have any questions or run into issues you can ask them here.
Edited by John Adams: 5/10/2011
We've switched to supporting this tool as part of our EQ2Emulator Core Utilities. See the details below for how to use this tool properly.

First, unpack the RAR file. You should have 4 files in the folder: Run EQ2EMuPatcher.exe. On first launch, it will ask you where your EQ2 Dir is. If it does not, click the button "Change EQ2 Dir": Browse to your Everquest II folder where the Everquest2.exe file is and select it. Then click Open. Pick which version you wish to patch to. By default, 5122L is selected. If your Everquest2.exe does not match our version, you will be asked if you wish to patch that file. A backup is always made, but you should ALWAYS back up your own files accordingly (specifically, Everquest2.exe in this case)

If patching was successful, you should see a screen like this:
You can also change what LoginServer to connect to for logging in. This will edit your eq2_defaults.ini file for you. By default, "cl_ls_address eq2emulator.net" is set.

You can also use this tool to patch your TSO Box back to 5040L, or your SF Box back to 6120L if you wish.



NOTE: EQ2EMuPatcher.exe auto-updates itself from our files stored on our webserver. Be aware that different patches may become available, or new versions of the patcher for that matter. Keep this in mind if you have firewalls or security software enabled that blocks apps from downloading updates to themselves.



Any questions? Ask below.

Image was kind enough to give us the source code to this tool, and today I've made a few updates to (hopefully) make it useful again.

The scenario I tested was:

• 1. Installed Sentinel's Fate Box set client
  2. Ran EQ2EMuPatcher.exe
  3. Selected version 6118L (the last known good client)
  4. Patched my SF install dir
  5. Logged into Tess just fine.

You might have to locate a TSO-version UI though, because some of the stuff (like Quest Helper) do not work properly.

Hope this helps some of you struggling with finding a client that is compatible.

John Adams wrote:Image was kind enough to give us the source code to this tool, and today I've made a few updates to (hopefully) make it useful again.

Thanks Image!

Giving this a "Sticky" and a bump.

Hmhm keeps saying that I need to re-run patcher and will not let me log in. I chose the 6118L and I have SF disk set. and chose my Dir so I have no clue what's up with it. Although I'm sure it's something i'm doing wrong.

Check the SOE build version on the Everquest2.exe you patched to. Sounds like you're still using the SF exe, and the patch didn't work?

FYI, due to some problems with throughput on the old server this was pointing to, I have moved it to a new server.

Please re-download the package to ensure you are pulling patches from the proper location. The other location has been disabled.

Thanks!

Well I'm re-installing SF Box set and re uploading the patcher on the rite setting hopefully it works. Soon I plan to start playing/testing and helping out as much as I can. Personally SOE eventually ruins every great game that they have created due to arrogance. So I'm glad to seen an EMU for a once great game!!!

Also along with running the patcher there are a few things I did not understand. So can you elaborate on what it is I should check on?

Throatseeker wrote:Also along with running the patcher there are a few things I did not understand. So can you elaborate on what it is I should check on?

Can you elaborate on what it is you don't understand?

Well the only EMU I have actually ever played is EQ EMU. This one is slightly difference on how you login in ect ect. It sais use 6120L but that didn't work and now I went to 6118L and I'm about to try. I suppose really I don't understand the majority of the terminology seeing how this is only the second time I have ever been involved in something like this. Sorry newbie here =/

Unable to deflate and replace file.
The process cannot access the file 'C:\Program Files\Sony Online Entertainment\Installed Games\EverQuest II\EverQuest2.exe' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at EQ2EMuPatcher.frmPatcher.DownloadFiles(String DirectoryToUse)
Unable to delete temporary file.
The process cannot access the file 'C:\Program Files\Sony Online Entertainment\Installed Games\EverQuest II\EverQuest2.exe.6120L.tmp' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at EQ2EMuPatcher.frmPatcher.DownloadFiles(String DirectoryToUse)
Files downloaded and updated.

There's nothing different about it than EQEmu, except our client support covers multiple versions. Think of "6118L" as our "Titanium", because that's where we're going to be for a while.

Install SF.
Install and Run EQ2EmuPatcher.
Select "6118L" and Update.
Follow the player guide on how to configure the cl_ls_address for 'eq2emulator.net' ( had to do that for eqemu, too)
Run Everquest2.exe

Yes, it is that simple.

Throatseeker wrote:Unable to deflate and replace file.
The process cannot access the file 'C:\Program Files\Sony Online Entertainment\Installed Games\EverQuest II\EverQuest2.exe' because it is being used by another process.

Dude, you can't patch Everquest2.exe while it's running haha.

Note, I am glad you are testing it out tho... not many people actually give us feedback here, so thanks for taking the time - even if it may be 'user error' tee hee