Is there some bug is gnucleus? I have 3 movie files which reached upto 95% done - and then stopped.

Gnucleus got upto 60 different sources for one file, but after 3 weeks, it has not finished the file. And even with 60 sources, the file did not increase a single byte!

Sometimes, it gets "stuck" and gives a message "Retrying host 1 of 60" and after 5 minutes, it's still says "Retrying 1 of 50" without advancing to 2 of 50, 3 of 50, etc.

Is this some bug? What is the matter?

I want to transfer the partial files to download in shareaza. How do I do that? Edit the .nfo in gnucleus to a .dat for shareaza?

Anyone done this before? Any help appreciated. Thanks.

Having used Morpheus and recently converted to Gnucleus (recommended), I have noticed the same thing. I don't think this is a Gnucleus bug. There are several other reasons for this:

1. People use their download directory as Share directory... This is good if you have lotsa space and doesn't have to delete stuff, but with movies people tend to burn it to CD-R as soon as possible (or so I believe...) So most of your sources may be downloaded files that are now erased. Lesson to learn: Don't share files you're going to burn and delete.

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.

So what can you do, especially about the 90% download that stopped? Just wait! Some day, it will be online again, and you'll get your last 10%.
The main problem about movies is that they are so long that most people sharing them out may do a reboot before it completes. 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. And btw: Shareaza is also using the gnutella network, so chances of finding your last 10% aren't any better there...

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?
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%.

Another, more selective way of doing this may be to disconnect your worst nodes.

Check your connected nodes on Statistics, especially the Distribution tab. When nothing happens for a while, I browse through my list of connected nodes and removes those with few friends and small libraries. When new nodes have popped up, I try a Re-Search again.

BUT: Usually I just wait. I have seen files starting to download again after a week or two, and I don't expect 3 weeks is a limit either. The problem is when you have 10 files at 80-95%... The partial files start to take up so much space on your hard drive that when another (new) file download kicks in, your HD may be full...