Interesting observation. It wouldn't hurt to see if all the failures go through a number from "4600". I don't think it is a line number but it is a number that may indicate that the server or client is in a different state.

I will have to watch for this.

**added**
Interesting, but unfortunately those numbers change from system to system and from various runs. But I a sure that a developer could run it through the debugger

well i tried focusing on using eqw 2.2 but still get the same error CreateSurface(Primary)failed(88760091" i tried what the one thread said about this problem but that did not work =(

[QUOTE]Originally posted by Vipermmx
Planeguy is your desktop set to 16bit? When mine was 32bit I got the crash right after I selected server with EQW2.2. When I set it to 16bit it stopped crashing.
[QUOTE]

Damn you for pointing out the obvious. I beleive that's in th readme even, but I forgot all about it! :P I still don't get in the game, but I have made a character if that means anything. :)

So the new status is:

eqgame patchme
Same as my last post on page one.

eqw
Dump to server select screen after choosing a character and trying to enter game.
world.exe says:
Sending list of guilds
31002 unknown opcode:13601 size:2056
31999 unknown opode:14625 size:2056
etc.
These unknown opcodes don't seem to bother world.exe too much.
The zone server tries to boot a zone and says it can't find it (Map: Maps\arena.map not found), drops the client (that's me) and finally shuts down the server. Zone.exe hasn't crashed, however. It just goes back to sleep.

Maybe all that's wrong is the zone the character is in. I think I'll rummage around the database and see about changing it to something I recognize, like freeport west or something.

Hope this helps! :)

Addendum
Hey... I don't have Maps/ directory... should I? The commercial EQ doesn't seem have one. Why's zone.exe looking for it, and where should it be? Heck, there isn't even anything with a .map extension in any of the EQ or EQEmu directories... this begs the question: How hooped am I? Hopefully this is just more useful information! :)

No need to worry about the Maps directory and the .map files.
that is not the cause of any problem that you may have.

Planeguy:
I got the same thing with zone.exe going to automatic server shutdown when trying to enter the zone -- i found that making changes to the database with the Admin tool fixed it. The first time you try to make a change you'll get an error "db not in insert or edit mode" then hit Commit changes again and it saved. Once I did that, the zone server would allow me to get in. However, now zone.exe causes an illegal operation every time i try to zone in (different problem i suspect).
Hope this helps!

good news -- sort of
 

well this is sort of goods news-- I have one system that still can't get a char into the game. After the char select, the client gets disconnected.

On my other machine I have no problem.

On the problem machine, I did a "world clean" and used eqw 2.2 -- so I could see messages (since its a one box setup). I did notice that I lost my miniloginserver connection while I was going through the character loading part.

The minilogin said that it was removing the ghost IP from 127.0.0.1. Strange given that it was using the same loginserver.ini that I had used for my two-machine set up.

anyway, the good news part, is that at least I have a system where I can try to duplicate problems.

No dice. I'd previously changed my character's current zone to see it that'd get it all working, so I got the whole "db not in insert or edit mode" thing before. It still didn't work :P

It doesn't seem to crash when it gets unknon opcodes (world.exe just goes about its business), but there aren't any other error messages. Something client-side, perhaps? I unzipped eqw and changed eqhosts.txt, but that's the extent of my modifications.

Anyway, more food for thought :)

PG

For those in camp #1, eqw only,

try running this from the command line.

eqgame.exe patchme rather than eqgame patchme

This resolved my problem. Seems to be an issue with the way args are passed in XP/2000.

planeguy -- if you are changing in the admin tool hit commit again to force the db into edit mode.

trump--interesting on eqgame versus eqgame.exe. anyone try this yet? i'm very interested in seeing results of that from the camp one crew.

I am officially out of Camp1 and into Camp 3 thanks to Trumpcard's findings.

using "eqgame.exe patchme" instead of "eqgame patchme" on a win2k machine does the trick!

It is nice to see EQEmu in all of its Full screen Glory LOL :)

this is definitely goofy and a candidate for the FAQ.