Giving up on finding Arq in cache stream ???

[BinaryConfusion]

Anyone out there willing to take the time to explain what this error means and if it is causing spawns to come up as unknown on my map.

I am running the latest verson from Zap's tarball and am having no problems with the install and all skittles are appearing upon zone in. Thru the course of playing in one zone for an amount of time I start to get unknowns and these errors. Just wondering if its something I am doing or my hardware somewhere along the way.

SEQ: Giving up on finding arq 3ec4 in cache stream 3, skipping!
SEQ: Giving up on finding arq 3ec5 in cache stream 3, skipping!
SEQ: Giving up on finding arq 3ec7 in cache stream 3, skipping!
SEQ: Giving up on finding arq 3ec8 in cache stream 3, skipping!
SEQ: Giving up on finding arq 3f2e in cache stream 3, skipping!
INVALID PACKET: Bad CRC32 [211.161.172.37:4852 -> 192.168.1.3:1028] seq 2800 len 604 crc32 (434f4d00 != 68d76452)

[LordCrush]

What do you have under Network->Advanced->Arq Seq Give Up ?

Try a higer number (mine is set to 512)

[BinaryConfusion]

set to 512 that seems to get rid of the msg but not the problem .

[fester]

Originally posted by BinaryConfusion
SEQ: Giving up on finding arq 3ec4 in cache stream 3, skipping!
INVALID PACKET: Bad CRC32 [211.161.172.37:4852 -> 192.168.1.3:1028] seq 2800 len 604 crc32 (434f4d00 != 68d76452)

"Giving up on finding arq" = I know I am missing a packet that the PC and SOE sent, but I was never given the packet by pcap.

This can be cause by any of the following:
1) ShowEQ system seriously overload (CPU/RAM.)
2) ShowEQ system has a network card with bad ram.
3) ShowEQ system's network card is unable to keep up with packet rate.
4) The cable to the ShowEQ system is damaged.
5) The network is so busy that the hub managed to send the packet to the PC, but failed to do so to the ShowEQ system.

Bad CRC32 means the packet was corrupt. It arrived on your computer with bits modified. It was not the packet that SoE sent to your PC, it had been altered. This also leads to some of the same conclusions as above.

Check your CPU/RAM, then swap your network card (try a 3c905), then swap your cable and last your hub. If none of that fixes the problem, change ISP's.