WinEQ 2.0 + Win 7 64bit Home = 0x04b1e086 Error

Carnivac · Post by **Carnivac** » Tue May 04, 2010 3:42 pm

Hey Lax hope you can see this and hopefully comment.

Recently upgraded to the AMD X6 1095T 6core CPU + 890FX AMD Chipset, but very much doubt this is the problem.

Just to note this is the exact same problem as in this topic: http://www.lavishsoft.com/forum/viewtopic.php?t=4561 posted on 15th Feb 2010.

I previously used Win XP 32bit & Vista 64bit with WinEQ 2 with no problems.

Now I'm on Windows 7 64bit Home Edition, exact same error notification when passed the patcher.

If I delete the eqclient.ini I can get into EverQuest but if I change the resolution to my native 1920x1200 it's works BUT next time I play EverQuest the error comes up & I have to delete my eqclient once more & change the resolution in EverQuest back to 1920x1200.

Post by **Lax** » Tue May 04, 2010 4:02 pm

The error that shows up as 0x00000044 comes up because EQ failed to initialize the Direct3D device, and doesn't check for an error condition. This would seem to imply that some video-related setting in your eqclient.ini file is not compatible with your windows desktop configuration. I'm not sure what it would be specifically

You could also try updating your video driver

Carnivac · Post by **Carnivac** » Tue May 04, 2010 4:11 pm

Thanks for the info, it gets even more mysterious!

I just tried Inner Space & had the exact same error.

I then ran the developer patch for Inner Space and now I'm running EverQuest.

I wonder what is bugged with WinEQ 2 running EverQuest in Windows 7 h'mmm?

Carnivac · Post by **Carnivac** » Wed May 05, 2010 2:46 am

Seem to have fixed this, not sure what the exact solution was but....

1) Removed the eqclient.ini file so it repatches.

2) Removed UI_Charactername_antonius so it repatches of last character logged in on the account.

3) Turned off UAC in Windows 7.

From their WinEQ 2 worked fine, I then decided to switch UAC back on, rebooted & WinEQ 2 still worked.