Starting second session issues

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
Krizzik
GamingTools Subscriber
Posts: 9
Joined: Wed Jun 29, 2005 7:25 pm

Starting second session issues

Post by Krizzik » Wed Oct 26, 2005 12:04 pm

Ok, here is what I do and what happens ...

click icon on desktop, get updates, go to tray, right click the icon, go to Everquest, then to my session 1 profile, get box to enter username and pw, enter it, session 1 starts.

for session2: go to tray, right click the icon, go to Everquest, then to my session 2 profile, now this is where it gets weird. EQ1 patcher comes up, c hecks for files, then I get the login box for WinEQ, thing is, when I type in my user name, the first letter is always dropped off, go back and insert it, hit enter, then a I get a SECOND WinEQ login box, this time with my previously dropped off first letter of login already in the box, fill out the login and PW, hit enter, nothing for a few seconds, then the message, eqgame.exe has experienced trouble bleh bleh, is shutting down, then the send or don't send report box, THEN I go dow to try again and repeat process, except it works this time.

This procedure happens every single time, in that order/manner everytime I fire up the second session. It doesn't *break* anything, is just annoying to have to do this over and over when I want to do a second session ....

suggestions for *fixes*, settings changes? and do we have to *login* everytime we start a session or is there a way to just login once for the first and then fire up additional without doing all that?

Thanks =)

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Oct 26, 2005 12:14 pm

When you log in through any of our software, it stores session information for a period of 15 minutes. As long as it is able to successfully contact the server in less than 7 tries or so, you wont see the login box again unless you launch a session after 15 minutes has expired.

The first time it pops up in a single session it would be WinEQ, and the second time would be EQPlayNice, which has a delay before it grabs its info from our server so that ideally, you do not see multiple login boxes.

As to why you are seeing this problem, I can't even guess. I can tell you that it's extremely rare for this to happen. Probably even more rare since most people use the auto-login feature. Can you post your sysinfo.txt? You can get to it in the WinEQ 2 folder or by selecting Generate System Info from the game window right-click menu (shift+right click in game, or release the mouse and right click on the window's title bar)

Krizzik
GamingTools Subscriber
Posts: 9
Joined: Wed Jun 29, 2005 7:25 pm

Post by Krizzik » Wed Oct 26, 2005 12:45 pm

I don't generally use the auto-log feature on anything as I frequently change my passwords for personal security, so auto log makes it a hassle for me, however ... here is my info as requested:

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 571/1023MB
Page File: 2648/3926MB
Virtual Memory: 1370/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 2500+ @ 1833MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce FX 5600 Ultra
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: SB Live! Wave Device
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.12

Loaded Modules:
-----------------------------------
Module 0: C:\EverQuest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\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\IMM32.dll
Module 15: C:\EverQuest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: C:\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: C:\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: C:\WinEQ2\WinEQ2-D3D9.dll
Module 28: C:\WinEQ2\WinEQ2-D3D8.dll
Module 29: C:\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: C:\WinEQ2\EQPlayNice.dll
Module 38: C:\WINDOWS\system32\NTMARTA.DLL
Module 39: C:\WINDOWS\system32\SAMLIB.dll
Module 40: C:\EverQuest\EQGraphicsDX9.DLL
Module 41: C:\WINDOWS\system32\d3d9.dll
Module 42: C:\WINDOWS\system32\d3d8thk.dll
Module 43: C:\EverQuest\dpvs.dll
Module 44: C:\WINDOWS\system32\usp10.dll
Module 45: C:\WINDOWS\system32\HID.DLL
Module 46: C:\WINDOWS\system32\SETUPAPI.DLL
Module 47: C:\WINDOWS\system32\WINTRUST.dll
Module 48: C:\WINDOWS\system32\CRYPT32.dll
Module 49: C:\WINDOWS\system32\MSASN1.dll
Module 50: C:\WINDOWS\system32\IMAGEHLP.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce FX 5600 Ultra/nv4_disp.dll/6/14/10/7189
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1175x950 D3DFMT_X8R8G8B8
Current Adapter: 0
Available Texture Memory: 146MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 2: 2
EQ Path: C:\EverQuest
EQClient.ini: .\eqclient.ini
Patch: ON Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: LOW (+0 min RAM)
Sky: COMPLEX (+10 min RAM)
Calculated minimum RAM: 442MB (BASE+159MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=0
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=1

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Oct 10 2005 17:02:52
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Oct 26, 2005 1:02 pm

I don't generally use the auto-log feature on anything as I frequently change my passwords for personal security
Absolutely, which is why it's available both ways :)

Unfortunately, your sysinfo.txt looks normal. The only suggestion I have is to grab the latest NVIDIA drivers, version 81.85 I believe, to replace your version 71.89.

The only other thing I can think of is if some firewall software or something running on your computer is stopping WinEQ from either a) contacting the server or b) properly accessing the shared memory in Lavish.dll that stores the session information. If you havent scanned for spyware/etc recently, I would definitely recommend scanning with Adaware, Spybot - Search & Destroy, or Microsoft AntiSpyware. On a similar note, it is also possible that part of your Windows installation is corrupt, or that there is a minor hardware issue.

I'm not going to tell you that it's definitely not a bug in our software, but I will say that I tried it just now and didn't have a problem, and it wouldnt hurt to try a few things such as mentioned above on your end to see if that helps. I'll try again in a little while after my session with the server closes out, and maybe I can turn up the crash you're having. If you can get me any debugging information from your crash (it should give you an address of the crash if you click "more info", for example), that might help too.

Krizzik
GamingTools Subscriber
Posts: 9
Joined: Wed Jun 29, 2005 7:25 pm

Post by Krizzik » Wed Oct 26, 2005 1:11 pm

I would update the drivers, but it seems that EQ isn't too favorable on the new drivers so I always wind up rolling back tot he ones they claim to support *rolls eyes* ... firewall? no, not an issue ... spyware? no, check it every other day, ran it this morning before I began playing eq .. windows installation corrupt or minor hardware issue? hihgly doubtful since I have had the same everything for some time now and this only happens with winEQ ... I'll give the drivers update a try, but if it pooches my eq I'll have to simply rollback ... will try the autolog feature as well and see if it helps ... I just really dislike autologging on anything .... thanks for looking into it ..

Post Reply