Search found 5 matches
- Thu Nov 04, 2004 10:17 am
- Forum: GamingTools Members::WinEQ 2.0 Pro
- Topic: WinEQ was unable to initialize at this time (-12)
- Replies: 6
- Views: 6655
Thanks again Lax. I searched my hard-drive for the Lavish.dll file and found two others aside from the one in the winEQ 2.0 directory. One was in Windows, the other was in My Documents. I deleted both of them, ran WinEQ 2.0 and it went through just fine. I'm very anxious to play around with v2.0 now...
- Thu Nov 04, 2004 12:06 am
- Forum: GamingTools Members::WinEQ 2.0 Pro
- Topic: WinEQ was unable to initialize at this time (-12)
- Replies: 6
- Views: 6655
I tried two things. 1) uninstalled WinEQ 2.0, rebooted, reinstalled, ran WinEQ 2.0 and watched it patch, changed the eqgame.exe path in the preferences, ran the default profile... and got the same error 2) Deleted the old lavish.dll then copied the lavish.dll from the WinEQ 2.0 folder to my windows ...
- Wed Nov 03, 2004 3:03 pm
- Forum: GamingTools Members::WinEQ 2.0 Pro
- Topic: WinEQ was unable to initialize at this time (-12)
- Replies: 6
- Views: 6655
not sure if this is needed but it seems to be pretty standard when posting problems: WinEQ 2 System Information System: ----------------------------------- Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158 System Physical RAM: 819/1023MB Page File: 2344/2465MB Virtua...
- Wed Nov 03, 2004 2:56 pm
- Forum: GamingTools Members::WinEQ 2.0 Pro
- Topic: WinEQ was unable to initialize at this time (-12)
- Replies: 6
- Views: 6655
- Wed Nov 03, 2004 2:55 pm
- Forum: GamingTools Members::WinEQ 2.0 Pro
- Topic: WinEQ was unable to initialize at this time (-12)
- Replies: 6
- Views: 6655
WinEQ was unable to initialize at this time (-12)
I downloaded and ran the install tool for WinEQ 2.0. The patch program ran. I completed the Lavish login. I changed to eqgame directory to my install path. Launch Everquest --> wineq 2.0 default profile yields this error mesasge "WinEQ was unable to initialize at this time (-12). Please try again la...