Unable to get WinEQ 2.0 Pro to run on new Windows 8.1 system

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
aborianus
GamingTools Subscriber
Posts: 15
Joined: Wed Dec 15, 2004 5:17 pm

Unable to get WinEQ 2.0 Pro to run on new Windows 8.1 system

Post by aborianus » Wed May 27, 2015 3:15 pm

Hello,

Long time user and member of this site, using WinEQ since 2007.

I use it for EverQuest (1) only.

I have never had any issues with getting WinEQ 2.0 to run on my older WinXP or Win 7 systems... worked right out of the box (directly after install).

The issue I am having is that I am using Win 8.1 OS (64bit) on my laptop, fresh/clean install... and having issues with WinEQ.

WinEQ loads... I select my profile from under the EQ account profiles i setup.. it loads the eqgame.exe client... lets me login to my EQ account.. and gets me to the character selection screen. BUT... once i select a character and attempt to enter game.. WinEQ just hangs indefinately.... tested it a million different ways,... enabling eqplaynice... testing.. disabling eqplaynice... testing... and a million other single change then test scenarios... same deal...

Windoes OS task Manager shows as eqgame.exe "not responding" and continues to hang indefinately until i terminate the process id.

I'm thinking maybe i don't have a specific Microsoft Visual C++ package installed that may be required that i am unaware of ???????

Currently have installed:
MS Visual C++ 2005 redistributable (64bit) version 8.0.61000
MS Visual C++ 2010 redistributable (64bit) version 10.0.40219
MS Visual C++ 2010 redistributable (32bit) version 10.0.40219
MS Visual C++ 2012 redistributable (64bit) version 11.0.50727.1
MS Visual C++ 2013 redistributable (32bit) version 12.0.21005.1

If anyone can help me figure out why the heck it is only doing this on the win 8.1 os 64bit system... i would be VERY appreciative.


Thanks in advance.

aborianus
GamingTools Subscriber
Posts: 15
Joined: Wed Dec 15, 2004 5:17 pm

fixed

Post by aborianus » Wed May 27, 2015 3:49 pm

ok.. after spending a few minutes trolling the forums.. found 2 possible reasons why it was doing this... TeamViewer 9.0 and 10.0 both cause this issue...

Unloaded teamviewer... works perfect like it always did now...

Post Reply