WinEQ2 and the Everquest Expansion, SoF
Moderators: Lavish Software Team, Moderators
-
- GamingTools Subscriber
- Posts: 14
- Joined: Fri Nov 19, 2004 10:45 am
I havent been a long time user.. but have seen 3 patches and its normally updated pretty fast.
I love it as i run a box on a laptop with a 32meg video card... being able to clip down EQ is awesome and saved me a grad on a new laptop.
It is to be expected after an expansion for it to take a tad longer than just a normal patch.
Keep up the good work guys.
I love it as i run a box on a laptop with a 32meg video card... being able to clip down EQ is awesome and saved me a grad on a new laptop.
It is to be expected after an expansion for it to take a tad longer than just a normal patch.
Keep up the good work guys.
The initial WinEQ 2 update today was making the incorrect assumption that the login process from within the game was still not working. After eolewis notified me that they had fixed that functionality, the option to skip the LaunchPad was patched back into WinEQ 2. You can close and restart WinEQ 2 to regain full functionality.Well it just started working after I enabled patching witin wineq and now it's not working ahain and the patch option is no longer there.
I'm still having problems with loading multiple instances. One two of my computers I can load multiple EQ1 sessions (up to three) while on my best computer I try to load a second window and I get this error:
Windows-Bad Image
Exception Processing Message c000007b Paramters 75b6bf9c 75b6bf9c 75b6bf9c 75b6bf9c 75b6bf9c
Then eq crashes. I get my first window up no problem and the first instance doesn't crash at all.
I get the same error if I run the patcher or not.
I'm can post all the system information up if that would help, but I"m guessing I'm just missing something since the SoF launch. I didn't have this problem before SoF.
Thanks,
Ottsca
Windows-Bad Image
Exception Processing Message c000007b Paramters 75b6bf9c 75b6bf9c 75b6bf9c 75b6bf9c 75b6bf9c
Then eq crashes. I get my first window up no problem and the first instance doesn't crash at all.
I get the same error if I run the patcher or not.
I'm can post all the system information up if that would help, but I"m guessing I'm just missing something since the SoF launch. I didn't have this problem before SoF.
Thanks,
Ottsca