Shareaza

I've uninstalled and reinstalled 5 or 6 times now. The connection tests run from the HELP menu runs perfectly and everything shows OPEN and working (GREEN).

No matter what I do, in the NEIGHBORS windows my eDonkey connections always show a LowID.

This is on a 100MB fiber connection to AT&T. The router is a Cisco RV320 that works perfectly.

The OS is Windows Server Essentials 2012 R2 with 2 x Intel E5-2470 v2 chips with 10 cores per chip (total of 20 cores and 40 threads across 2 CPUs) each running at 3.2Ghz. Total memory is 96GB.

Storage consists of 6 x 4TB Hot Swap SAS Disks running in RAID 10 on a LSI Logic 9270CV-8i with LSI CasheCade SSD Virtual cashing enabled using 2 x 800GB HOT SWAP SSD Drives paired in a RAID 0 configuration for the virtual caching repository.

This is a Lenovo TD340 Server with 8 hot swap 3.5" drive slots (all filled with the above listed drives) and dual power supplies.

No matter what I do, I can't get the NEIGHBORS window to show anything but LowID no matter eDonkey Server I click on. I am trying eMule Security Servers 1 -4 as my usual targets but have tried others as well. No way to get a high ID. Is this a known bug or is there a way to get this working correctly? I have Shareaza set to use 6346 but just to test I've used other random ports and nothing works. In every case I get all green on the connection test with everything passing.

I am running 2.7.8.0 x64.

No idea what to do next...

Any idea?

Keith

Maybe this is a 64-bit issue.
Did you try with 32-bit, too ?
Did you ever get a highID, maybe in previous version or older computer ~8/16 GigRam ?

Seems like I fixed it. I removed all the incomplete files and it now gives me a HIGH ID. I put them back and then a LOW ID. Odd behavior. About 10,000 files in the queue to I guess I will now have to dispose of all that. Everything worked before 2.7.8.0 so this seems to have been timed with 2.7.8.0. In any case, I think I fixed the issue for now but what a huge loss just to fix this bug having to dispose of all those partials just to get a HIGH ID.

I tried my theory about 4 times moving files in and out of the incomplete directory and that made it switch from LOWID to HIGHID each time. So, that was the culprit... but a forklift fix for a small bug it seems.

Typical ED2K server describes why it granted a LowID to you, check System log please.

Can he do that ? Is the System Log not created new, every time Shareaza restarts ?

BTW, where is .log-file stored on win8 ?

Just copy text from System window.