WinEQ 2.0 Problems

Welcome, Guest. Please login or register.
Did you miss your activation email?

November 26, 2024, 12:28:55 pm


Login with username, password and session length

User

Welcome, Guest. Please login or register.
Did you miss your activation email?

November 26, 2024, 12:28:55 pm

EZ Server > Forum > General Category > General Discussion > WinEQ 2.0 Problems

Pages: [1]

« previous next »

Author

Topic: WinEQ 2.0 Problems (Read 4632 times)

Kenshou

Jr. Member

Posts: 84

WinEQ 2.0 Problems

« on: October 10, 2012, 09:18:15 am »

Has anyone run into problems using WINEQ and MQ2 not loading. Yesterday lavish patched, new security prompt appears with windows 7 64. I load just fine, however MQ never loads with it. I Tried new MQ2 from mqemulators, and attempted to run version 2.14

From Win EQ
Changelog

2.15 - 10/7/2012
- All Games
* WinEQ 2 now requests Administrator permissions, and a useful message replaces the old "-20" error
- EverQuest 1
* Fixed breakage issues with the current EQ1 Test server build, in which SOE has decided to compile
with different options.
* The Patch option is disabled for this game, WinEQ 2 will launch the game directly


« Last Edit: October 10, 2012, 10:53:03 am by Kenshou »	Logged

Blurring

Full Member

Posts: 168

Re: WinEQ 2.0 Problems

« Reply #1 on: October 10, 2012, 02:14:56 pm »

I ran into some problems loading up recently as well. I was able to get things running again after these steps:

Closed everything down.
Deleted eqclient.ini from Everquest directory (this is a pain without backups but ~ Sad

)

Set permissions and compatibility modes to the following:
eqgame.exe - Run as administrator, run in compatibility mode (Windows XP Service Pack 3)
MQ2 - Doesn't run as admin, no compatibility mode
WinEQ2 - Run as admin, compatibility mode XP S.P.3
EQBCS - Doesn't run as admin, no compatibility mode
I apply those settings to all corresponding shortcuts as well, not sure that makes any difference.

Ran OptionsEditor.exe
Restarted a couple times, and it ran just like normal.

I'm not sure how User Account Control (UAC) settings might affect things. I keep UAC at the lowest possible setting though, never notify.