Crashing at login screen?
 

I have discovered that if you make your eqhosts.txt read only, it will crash when you try to log in. I made mine read only then when i logged in, it crashed, turned off read only, and it worked. Might work read only for some people, but if your crashing at login screen try makeing it non read only.

I just make it read only when i am patching =)

It shouldn't be crashing just by making it read only unless you are doing something else wrong also. The client will always try to change your eqhost.txt back to Sony's servers every time you log in, so if you make it non read only it will need to be changed every time.

When I made my read only it worked fine.

I dono, im not patching, im doing the eqgame.exe shortcut thing.

And when it isnt read only, it doesnt change, and i can login fine, but when it is read only, i cant login, and it still doesnt change.

Just thot this might help those who are crashing at Login.

Why is anyone helping this jackass is this not hte same guy who was flaming at the Devs?

Yes its the same person, but he posted for help before saying he was the one who posted about the Devs.

:roll:

I need help too.. same is happening to me.

Crashing
 

I am having the same problem. When I try to login EQ crashes to the desktop. I've tried setting the eqhost file to readonly and writable but I get the same results either way. Any ideas?

Read the other posts and delete all the extra spaces at the ends of each line.

im having a troulbe too.

it crashes to desktop.

I'm crashing too and I did everything you guys said.

I'm crashing to the desktop as well.

Download http://www.eqemulator.net/eqhost.txt and set it to read only.

Problem
 

I'm kinda having the same problem as the others, but i'm not crashing. I get toi the login screen and select my server and click PLAY EVERQUEST. Now here is problem... after clicking PLAY EVERQUEST my screen flashes like normal goes black then this demonic message comes up saying EQGame has performed an illegal and and we shall now cut off you arms (not really just says made illegal action and then closes). But i would VERy much like if i could figure this stupid thing out.




Thnks,

Kujor Dark Cloud IV

Like the several people above me, I crash when trying to login.I've read every other post regarding this issue an nothing has worked so far. Even the respones in my thread aren't working. =(

I had the login problem, i removed the spaces from my eqhost file and then it worked fine, but then i cant get into a server and get booted to login screen, tried multiple times, maybe i need to download GoD files? i am trying that as we speak but if it doesn't work what could be the problem?

lucky sob, wish that worked for me. Would be nice to get past login. >.<

EQgame crashes at login screen to desktop.
 

Since its been ages since I have played anything at all, and you have gone from 5.2DR3 to 5.7DR6 I went ahead and updated everquest to live as of 6/20/2004.

I have followed many posts directions to get to where I am now.

I am using minilogin.
Minlogin loads perfectly
world (5.7dr6) loads perfectly
zones loads perfectly, although they say they are in sleep mode, I think that is new from when I used to do this with the 5.2dr3 version.

I then start the game and when I put my name and password into the respective places and hit enter the screen goes black for half a second and then crashes to desktop.

My EQ host then chages to the following.
if anyone can help with this, I would be most happy.

My login was working earlier, then i d/led the new patch and now when i run it (read all these posts and did what they said) it works, but hangs after i click on login, doesnt crash, just says "Loggin into the server, please wait...."

Somebody help us :O lol

Aye I'm getting the same problem as the previous poster...

I managed to stop getting booted to desktop after logging in by just removing the spaces in the Eqhost.txt.

But now when I log on, the client says:

" Logging in to the server. Please wait... "

But nothing happens... so I can't get past it.

The latest patch is incompatible with the Emu and causes this to happen. There is no fix for it. You need to wait until the Emu gets updated.