Quote:
Originally posted by Unregistered
2. The problem about never counting up the retries is more puzzling... I have seen it myself, and believe this may be a bug: The system tries to connect to the different sources, but times out before it is through the list. Then, when the system tries to connect again, it starts from the beginning... Bug? I don't know. |
Bug? Maybe. But it might be a screen artifact. When I tick "pending" off and then on again, the numbers change... sometimes. Most of the time, it remains the same.
Another issue - "Undetermined at 0.00kb" message.
I've noticed that during startup, some files get connected immediately, but they give a "Undetermined at 0.00kb" message. The whole system freezes as gnucleus tries to get the download started. In about 10 seconds, the system returns to normal. However, the download does NOT start. I've seen this same behaviour for the last 8-9 times I started up gnucleus.
The system freeze is definitely a bug.
But what about the file not resuming? Is that a bug? Or has something corrupted the file so that resuming is destroyed? Or is the source a RIAA fake?
Quote:
Originally posted by Unregistered
To make it even more complicated, dynamic IPs may confuse the system even more. I usually do a Re-Search on seemingly dead files, but even that only rarely gives results. This is the nature of downloading from a changing network. Sometimes you don't get what you want... Be happy about what you DO get. |
I've done re-search many times too. And like you say, it does not seem to make any difference to the download. I have a fixed IP, so I can vouch for my side of the equation.
Another thing I do is to re-start gnucleus occasionally, if there are no uploads or downloads going on. If I understand correctly, re-starts get me connected to different parts of the network, which may have the content I want.
Re: shareaza. I know it's on the same network. I'm hoping that shareaza does not suffer from the bug? of not resuming after 90%.