Huge zone times and frequent disconnects.

[Dr Zauis]

There is no bug..It should work 99% of the time..Try defragging your clients HD.

[EQEmu102]

Thanks for the suggestion.. thats not it. Client is fresh install on a fresh install of XP pro.

Very glad to hear it's just me though. I'll keep looking for the source of my problems.. Could be my routers.. I changed my system yesterday when I got this all working. I migrated my client machine off the Servers subnet.

So:

Client = 192.168.1.x connected through routerA with no port forwarding etc to internet on public IP 207.xx.xx.152

Server = 192.168.0.x connected through routerB with port forwarding for 5990-6000 and 7800-7900 and 9000 to the servers LAN ip on external IP 24.xx.xx.64

I'll have another go at it tonight and maybe do some packet sniffing to see what the hell is going on. I suspect my client at this point if this isnt a common problem.

Thanks all

[EQEmu102]

Just to confirm a suspicion I have could someone please consider PMing me a their OPCodes or really better yet a link to an opcodes file that is working 100%? I am still getting wierd unkown opcodes when I zone and thats most likely part of the issue.

I am using 6.2DR1 server with Mickey's fixed world.exe and zone.exe. I would LOVE a copy of the fixed zoneperl.exe if anyone has it it seems from the threads I've read work stopped at the end of september on that and not much more has been said.

[Belfedia]

Rahh search in WIKI !!!
http://www.eqemulator.net/wiki/wikka.php?wakka=HomePage
you find all you want : EQEMU 0.6.2 DR1 PERL by JimmOthy

[EQEmu102]

I have the zoneperl from jimothy but I thought it wasnt 100% stable. just thought there might be a newer one =) thanks

As to my opcode problem.. I'd really lvoe to get an opcode file from someone running a stable 6.2 server. I inserted the 0 opcodes to stop alot of the spam but I still get:

Minilogin.exe console:

654156 New client from ip:XX.xx.xx.xx port: xxx
Unkown packet: .4233692 [92.153.64.0:15-> 0.0.0.0:0]
[OpCode 0x0003 <Op_Unkown> size=11]
00000: 00 06 00 00 00 00 00 00 - 00 00 00

However I can usually log in so thats not a huge concern..
Next is the World exe console when a user logs in:
Logged in: xxxxxxxxxxxxx
Recieved unkown OpCode: 0x0107 size: 0 bytes

However it still allows me to go to char selection usually.

Now when I try to login to a slected char I get world.exe console showing this:

... standard zone setup stuff here.....
then.
Zone Port=8784
Client disconnected
Removing client from ipx.xx.xx.xx port: xx
Zoneserver Setzone xx.xx.xx.xx:portx

This part concerns me as it looks like world.exe may actually be dorpping my client? Or is it dropping my client because it is now passed the client to zoneperl.exe?

Now when I do sometimes get zoned in I get zoneperl doing this:

[error] Unhandled incoming OpCode: Op_AnoyingZoneUnkown (@299, eq=0x0000) size:8, client: (clientnamehere)
0: 79 00 00 00 40 00 00 00
Dropping client: process: false, IP= xx.xx.xx.xx port: xxxx
[status] zone shutdown


Thanks for any insite folks.

[EQEmu102]

As per my earlier post Sdabbs its not the PC

My server is a P4 2.4 with 512 Ram and I'm only triyng to run 1 zone at a time =) I'm usinag a grand total of 300 MBs of memory with O/S overhead included.

My client PC is a P4 2.6 Gig with 1gig Ram and a 256 MB ATI 9600 Pro..

Not my PCs

Thanks for the info on your probs though. maybe its memory handling... I'm running the server on XPPro O/S is that bad?

[Belfedia]

Dohhh we need one more compil from last CVS source !!!
Have you try Cavedude version from dark rogue production pack 2.0 ?

[Damilis]

Originally Posted by EQEmu102

As per my earlier post Sdabbs its not the PC

My server is a P4 2.4 with 512 Ram and I'm only triyng to run 1 zone at a time =) I'm usinag a grand total of 300 MBs of memory with O/S overhead included.

Only 1 Zone.exe? I have always had really good luck running >=2 zone.exes.

Reasoning: Zone.exe A has you in ecommons and you want to zone to freportw

With 1 Zone.exe running:
1) you are removed form zone.exe A
2) Zone.exe A shuts down ecommons
3) Zone.exe A boots up freportw
4) Then you are inserted into freportw

aka the process is all happening in series.


With 2 Zone.exe's running:
1) Zone.exe B boots up freportw while you are still in ecommons
2) You are transferred to freportw once its done booting
3) Once you are out of ecommons, Zone.exe A shuts down while you are already in freportw

aka the process is happening mostly in parallel and the only waiting you have is for 1) Zone.exe B to boot up freportw and 2) your client load time.