consistent
Actually your log looks cleaner than mine. I get 13601 too, and a couple of extra before it.
The next unknowns should be: 14625 and 0x9221
then the autoboot
So the problem is not that you are getting unknown op codes, but you are not getting enough of them.
After you start minlogin (which you are not doing), world, and boot5zones.bat , you world screen should have this:
Newzone server #5
Zoneserver
then when your client logs nothing interesting happens until you select a server then you get the logged in message and sending guild list.
I then get 4 known opcodes, then the 13601.
I also get by the time I am at the char select two more unknown op codes:
14626 & 0x9221.
So you are getting disconnect from the server select to before all the char load stuff and the char select.
All this matches what you have said. So now its a matter for someone to duplicate that.
but here is my point, you screen looked fine up to and including 13601
But I also get 4 additional known op codes before 13601.
You are hanging/crashing on the client side. The connectivity message is correct-- when you crash the world server you can go on. EQ for some reason puts out their cryptic message but all it means is that you have crashed.
|