EverQuest support for WinEQ 2.0 was unable to initialize at this time (final stage). Please try again later. OR I will get a message that says something like "EQplaynice was unable to initialize) OR it will plain crash and I'll get the windows error message stating that the program could not be started or something and it gives me the option to "SEND" the crash to windows. Anyway, those are the 3 most common problems I have trying to use WinEQ 2.0 for Everquest 1. I usually have to start it 3 or 4 times before I can finally get in.
Thanks for your time.
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.070227-2254
System Physical RAM: 1499/2045MB
Page File: 4551/4892MB
Virtual Memory: 1993/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 2992MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 2992MHz
CPU Affinity Mask: 3
Video 1: \\.\DISPLAY1/NVIDIA GeForce 6800
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.15
Loaded Modules:
-----------------------------------
Module 0: C:\Program Files\EverQuest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Program Files\EverQuest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: C:\WINDOWS\system32\d3dx9_30.dll
Module 15: C:\Program Files\EverQuest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\WININET.dll
Module 19: C:\WINDOWS\system32\CRYPT32.dll
Module 20: C:\WINDOWS\system32\MSASN1.dll
Module 21: C:\WINDOWS\system32\OLEAUT32.dll
Module 22: C:\WINDOWS\system32\SHLWAPI.dll
Module 23: C:\Program Files\EverQuest\xul.dll
Module 24: C:\Program Files\EverQuest\js3250.dll
Module 25: C:\Program Files\EverQuest\nspr4.dll
Module 26: C:\Program Files\EverQuest\MSVCR71.dll
Module 27: C:\Program Files\EverQuest\plc4.dll
Module 28: C:\Program Files\EverQuest\plds4.dll
Module 29: C:\WINDOWS\system32\SHELL32.dll
Module 30: C:\WINDOWS\system32\WINSPOOL.DRV
Module 31: C:\WINDOWS\system32\comdlg32.dll
Module 32: C:\WINDOWS\system32\COMCTL32.dll
Module 33: C:\WINDOWS\system32\IMM32.dll
Module 34: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
Module 35: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 36: C:\Program Files\WinEQ2\Lavish.dll
Module 37: C:\WINDOWS\system32\iphlpapi.dll
Module 38: C:\WINDOWS\system32\MSCTF.dll
Module 39: C:\Program Files\WinEQ2\WinEQ2.dll
Module 40: C:\WINDOWS\system32\PSAPI.DLL
Module 41: C:\WINDOWS\system32\imon.dll
Module 42: C:\WINDOWS\system32\mswsock.dll
Module 43: C:\WINDOWS\system32\hnetcfg.dll
Module 44: C:\WINDOWS\System32\wshtcpip.dll
Module 45: C:\WINDOWS\system32\DNSAPI.dll
Module 46: C:\WINDOWS\System32\winrnr.dll
Module 47: C:\WINDOWS\system32\WLDAP32.dll
Module 48: C:\WINDOWS\system32\rasadhlp.dll
Module 49: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 50: C:\WINDOWS\system32\MSIMG32.dll
Module 51: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 52: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 53: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Direct3D9:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN (Windowed)
Current Adapter: 0
Available Texture Memory: (not currently available)
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------
EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Jul 10 2007 19:38:34
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30
WinEQ 2.0 unable to initialize....
Moderators: Lavish Software Team, Moderators
I'll add my 2 cents to this. I am experiencing the same problem on three different boxes. Each of them has a different hardware configuration. When I get to them this evening I will post my sysinfo.txt from them to see if I can help us figure this problem out.
At first I thought this could be related to my specific setup, but after reloading my laptop two nights ago and having this happen to three different setups, I'm thinking it's code related.
Anyhow, happening here too. Not just to you.
At first I thought this could be related to my specific setup, but after reloading my laptop two nights ago and having this happen to three different setups, I'm thinking it's code related.
Anyhow, happening here too. Not just to you.
It is most likely network related. If you lose connection to our server during startup, then it will fail. However, without knowing the exact messages given (slyone...) I can't offer detailed assistance, or if it was code related (note: there would literally be hundreds more posts...), I couldn't locate the problem.
If you are connecting to your home network over a wireless connection, make sure the connection is good quality. It can also be caused by temporary routing problems from your ISP and throughout the internet. The signal strength in your cable modem can also be a factor, as poor signal could cause packet loss, which could result in the same behavior.
If you are connecting to your home network over a wireless connection, make sure the connection is good quality. It can also be caused by temporary routing problems from your ISP and throughout the internet. The signal strength in your cable modem can also be a factor, as poor signal could cause packet loss, which could result in the same behavior.