[ Disclaimer, --- , ]
EverQuest in Linux Guide
This guide, which is based on countless hours of research from numerous valiant contributors in the main forum, will walk you through the process of getting Project 1999 EverQuest working under Linux. The original version of it was compiled by forum user mgellan, and all Linux users should be grateful for his effort.
Distribution Note: Debian Based System Recommended
While EverQuest can be run under any major Linux distribution, a Debian-based distribution is recommended for this guide. Previous contributors to this guide strongly recommended Linux Mint. This was simply because many existing Linux EQ users used Linux Mint when writing their instructions, and the commands to install new packages are Debian specific (ie. they involve the
If you are using a Red Hat based distribution instead please see the EQ under wine (Fedora LINUX 14+ 32 or 64bit) guide.
Use the general Project 1999 Guidebook as a supplement to this linux guide https://www.project1999.com/forums/showthread.php?t=2651
(Last version to work without problems is 4.21)
WINE (Wine Is Not an Emulator) is a program which allows you to run Windows applications from within Linux. However WINE does not normally come installed with Linux distributions, so you need to install it with the following command:
sudo apt-get install wine
If you are installing on a 64-bit machine you will need wine, wine64, and all of their dependencies. You may want to consider installing using Synaptic Package Manager.
Note: On newer systems, you might need the
Optional: Configure WINE
While this shouldn't be necessary, if you wish to customize your WINE configuration you can do so with the following command:
Install Mesa libGLU?
Not sure if this is required for all users, but I had to install this:
sudo apt install libglu1-mesa:i386.
This step can be performed two different ways depending on whether you have an installed EverQuest copy or just the installation media.
Using an Existing Installation
If you have access to a copy of an EverQuest installation (eg. from a previous Windows installation) you can simply copy those files to somewhere on your computer. You can either put them in a generic location:
or you can copy them into WINE's pseudo-Windows file structure:
/home/*yourname*/.wine/drive_c/Program Files/Sony/Everquest/)directory will be hidden by default, but you can reveal it with
- NOTE: The <code>.wine
CTRL + H
After that you're done.
Using the Installation Discs
Install from CDs (or ISO images of those CDs) should work fine:
- insert the first Titanium installation CD into the drive (or mount the equivalent ISO file) and it will pop up as a CD icon on the desktop
- Double-click that CD to open it
- Double-click on setup.exe to run setup (it should be run using WINE automatically).
- Proceed through the setup (see the Everquest Titanium Installation Guide) using the first CD as normal
- When you are finished with the first CD you will need to run the following command from a terminal window (
CTRL + ALT +Tto open one) to eject the disc:
wine eject d:
- The above command is needed because LINUX tends to want to mount CDs as filesystems, and resists unmounting them if they're in use to avoid various problems. Wine eject gets around this.
After the installation if you have trouble with the default
eqclient.ini file that is generated, and also are unable to change your options via the in-game options menu, you may wish to replace your
eqclient.ini with the Linux Reference eqclient.ini File, which has been reported to work for other users. If you cannot get past the character selection screens, or you do but Norrath is jacked up, use this file but adjust the following settings to fit your machine . If you do not and try to change them in game the screen may go black.
Patching in the Project 1999 Files
At this point you will need to patch your installation with the files provided by Project 1999, the same way you would on Windows. Download the latest patch file from , un-zip it, and copy/paste the files into your EverQuest installation folders. Do not copy/paste them all at once. Use the folder paths to know where to paste the individual files. If you paste entire folders you will replace entire folders, not merge them. This will cause "Error in your GUI XML files" and similar errors later when you try to play the game.
Linux file names are case sensitive, Windows file names are not. The following Project 1999 file names (V46), released 2/10/19, do not match the EverQuest Titanium installation files exactly so they must be renamed so that they will replace the installation files when you paste.
Project 1999 Files (V46) /Resources/loadscreen.jpg vs installation file /Resources/loadscreen.JPG
Project 1999 Files (V46) /dsetup.dll vs installation file /DSETUP.dll
If you log into a Project 1999 server and get an error about spell files at the character selection screen these files haven't been properly copied. Often the installation DSETUP.dll file hasn't been replaced by the Project 1999 dsetup.dll file.
Just as in Windows you can't run the Everquest executable directly: you need add the
patchme argument first. The Project 1999 team provided a batch file which does this for you when you patched:
However, you may need to add additional environmental variables and wrappers, in which case you will want to create a shortcut to your
eqgame.exe and then right-click on it, choose properties, and then change the "Command:" to include that extra stuff. For instance:
env WINEPREFIX="/home/*yourname*/.wine" taskset -c 0 padsp wine C:\\Program\ Files\\Sony\\EverQuest\\eqgame patchme
(NOTE: The above command assumes you installed EverQuest inside the WINE directory structure; if you installed it elsewhere you will need to change the path in the above command to match.)
Launcher Alternative: Custom Bash Script File
Cramming commands in to the shortcut can only take you so far, and they can be difficult to read later on, so instead you may want to create a bash shell script. You can then run that script in place of the Launcher or shortcut. mgellan explained that this "also lets you do other things that I don't mention here but I do on my own system, like playing with Soundfonts and so on."
To create a bash script start a new text file, open it in gedit (or your editor of choice), and then cut and paste the following into it:
# if you don't have the script's cwd set, you get XML errors
cd ~/.wine/drive_c/Program\ Files/Sony/EverQuest
# Bind to one core of the processor and launch.
# The client will spew a lot of errors, especially every time
# you target a mob, hence the stdout/stderr redirect.
# You probably want to leave off the 2>/dev/null until you're satisfied
# everything is working.
taskset -c 0 padsp wine eqgame.exe patchme 2>/dev/null
Props to Zallarenya for the above script!
Once you have the script working (it's always a good idea to try it via command line until you work out all the issues) you can create a shortcut to it, and then you should be all set.
If you are able to start EverQuest but the server list is blank/empty reference https://github.com/Zaela/p99-login-middlemand. Download and unzip the file. From within the unziped folder run the command $ make. Many errors are caused by missing libraries and can be corrected with the command $ sudo apt-get install build-essential.
Getting MIDI Music to Play
- Install fluidsynth, a soundfont for it, and qsynth:
sudo apt install fluidsynth fluid-soundfont-gm qsynth
- Run qsynth
- Go to Setup > Audio tab and select alsa
- Go to Soundfonts tab and open the soundfont file FluidR3_GM.sf2
- qsynth has to stay open to continue playing MIDI music
Note: Might need to set sound to ALSA in wine, via
winetricks sound=alsa and select proper ALSA driver under
winecfg > Audio > output device.
Project 1999 Linux Install Script
For an all-in-one Project 1999 Linux installation on Debian based systems (mint, ubuntu, etc.) checkout https://gitlab.com/FTN806/P99-Linux-Installer
The script should work on most distributions regardless of the systems package manager, but it won't install the prerequired packages unless the distribution is using the apt package manager.
Please read the README.md before running the script.
This guide was originally based on the following forum thread:
The following threads may also be helpful: