Logic Crash

xulok · #1 07-24-2007, 04:01 AM

I haven't found anyone yet that has posted about this particular event chain, but the symptom is that I log in, the server select screen shows up briefly, and the the process abruptly ends with no errors or other feedback.

This is repeatable on my laptop and desktop, and is somewhat intermittent. Both are Vista if that has anything to do with it.

Any ideas?

Regards,
X

EDIT:

I tried setting the processor affinity to just CPU 0 and it loaded. I can't certainly that this fixed it, but it's a good chance. Anyone else seen this?

techguy84 · #2 07-24-2007, 04:12 AM

"Logic Crash" or "Login Crash"

I had a error that booted me without any signs of distress because I was typing in my username wrong, but I couldnt even see the server select screen.

Could assume, but should ask still,

Are you using Fresh Titanium,

Are your links properly setup,

Do you have any Widescreen Highres monitors?

Is your Windows Vista a fresh install, or do you have mounds and mounds of stuff installed on their, that could possible conflict with EQ like Firewalls, Internet Security Suites ect..

xulok · #3 07-24-2007, 05:29 AM

Login, sorry. I tried to edit it but it doesnt seem to reflect on every view.

I have a widescreen high-res on both computers, is there a known issue with that? Fresh titanium install, more or less pristine Vista Ultimate install.

Also wanted to add that the processor affinity doesn't always fix it, but seems to help somewhat.

John Adams · #4 07-24-2007, 11:43 AM

Ahh, nm... you're a "dualy". Might not be the login survey problem.

techguy84 · #5 07-24-2007, 01:00 PM

Delete your eqclient.ini file in your Everquest directory. There is a imcompatiblity with the widescreen resolutions and EQ, like the 1400x900.

xulok · #6 07-25-2007, 01:37 AM

I believe it is indeed the survey issue, but I will wait to confirm. After adding the [MISC] section from another thread, I am 4/4 in successful logins. Odd that I don't exhibit the same crash sequence that the other thread described, but if it's now fixed, so be it. I will post the details of my fix for future reference once I am satisfied that the problem is solved.

Thanks for letting me bounce ideas off of you.