Invalid uptime reported

[ale5000]

[raspopov]

Looks like DWORD with time was wrapped. In many places Shareaza still using DWORD (32-bit) for time measuring and it's start shows wrong values after 49.7 day from Windows start (it can be on servers and never-rebooted notebooks).

[ale5000]

And about reporting repetitively the same GWC 15 times?
It shouldn't re-report the same GWC every time if the previous reporting is failed, it should be random every time.

[raspopov]

Exactly, with wrapped time Shareaza always think "I reported to this GWC too long ago, need update."

[ale5000]

But Shareaza shouldn't just report the one reported earliest in the past, but a random one from the list of reported earlier; this is safer in every case.

[raspopov]

It's just an assumption.