Hello, I took a break from EQ about 3 months ago and have probably logged on 3 times since then. I am now starting to get back into playing EverQuest and I have come to realize that my Wineq 1 or 2 will not open EverQuest AT ALL nor has it been able to for quite some time now. When I first realized this, it wasn’t a big deal to me because, well, I didn’t play. Now that I’m back, id like some help figuring this out! Ok, now that the story is over, here is my problem. When I load up the newest version of Wineq 2.07 pro or any version of Wineq for that matter, I get ‘Eqgame.exe has encountered a problem and needs to close. We are sorry for the inconvenience’ blah blah blah. I don’t have any log file or sysinfo.txt in my WinEQ folder but here are my computer specs!
System:
Microsoft Windows XP
Professional
Version 2002
Service Pack 1
Computer:
AMD Athlon XP 2500+
1.84 GHz
1.50 GB of RAM
Won't Work...
Moderators: Lavish Software Team, Moderators
Hi there. Unfortunately without the sysinfo.txt there's not much I can guess at, as far as your crash goes. However, it can safely be assumed that some program installed on your computer with or without your consent is preventing WinEQ from launching EQ. The best thing for you to do is to close down all running programs, just to make sure that's not what the problem is. Then if it doesnt work, scan for spyware and viruses with well-known software. Microsoft recently put out some free apps that can be used to scan for spyware and viruses (the virus scan is not intended to replace normal antivirus software and doesn't provide real-time protection, etc). Here's the link to their spyware removal software: http://www.microsoft.com/athome/securit ... fault.mspx
If that doesn't solve the problem, consider reinstalling Windows cleanly. This isn't something I normally suggest because nobody likes to do that, but everyone with similar problems that has reinstalled Windows has reported that this solved their problems.
If that doesn't solve the problem, consider reinstalling Windows cleanly. This isn't something I normally suggest because nobody likes to do that, but everyone with similar problems that has reinstalled Windows has reported that this solved their problems.