Shareaza

I'm not sure if anyone else had the same problem. When first installing shareaza 2.5.0.0 it converts current torrent downloads to a new format. Trouble is it hangs each time it tries to convert them. At least for me it did. These were large torrents (the debian installation ISOs) 4gig plus. Anyone else have the same problem?

I just know you should wait a long time. Although it may seem not responding it is still converting and you should wait.

Is there any window showing this process? Like in case of hushing?

I see. I waited 15 min but perhapse I should have waited longer for them to convert. Anyway I deleted the partial files and have restarted the torrents from scratch and 2.5 seems to run smoother than 2.4 so all's good.

its not hang, its just very slow process..way to slow..

Agree. The installer should mention that the conversion might take a very long time. Some indicator that the process is working would also be nice, but not sure if it is worth coding for a one time event.

progress indicator and make the converting as background process is very good idea, so people don't have to wait while the process are being done

Is this like some additional option to the normal download of a torrent that in previous versions the file was then automatically converted to the target file type. in the other versions it did not took all that long as I recall if that is what is being talked about...

But this process takes place only once. So it isn't wise to spend more time and code on it.

Indeed, adding some text to the installer or an informative pop-up to warn about the time it might require is practical though. Otherwise the user might give up before that one time is over. And if you put up a pop-up adding a files converted counter to it would be pretty easy and show the user something is happening. Fortunately, not that many people probably use Shareaza for BitTorrent, but I am still bit worried about how many users might give up without even coming to the forum.

Not sure what you mean with introducing Bittorrent, so not really sure why you think most Shareaza users use Bittorrent. Not that it really matters, since having more people than I thought using Bittorrent would actually make my suggestion more relevant. So not like I have any reason to argue about it. Just mark it up to wishful thinking on my part (not that many people affected) and forget about it.

If proces is not worth coding then I think warning message/window and any progress indicator (mostly to show it has not hanged, the hashing progress indicator could be used, and it is coded already I think) seem to me a solution. Also please consider: some user could prefer to start proces later and to know how long it could take, and upon this to make a decision. Perhaps window could have info "it will take about X minutes/hours [OK start] [I will start it next time when start Shareaza]" This would allow users to control this process, but not process to control user.

Don't want to argue.

I really miss the DOS days when just seeing the HD light blink was enough to tell you the program was working. Not that I want to give up multi-tasking or anything. Just wondering aloud how we can have so much better UIs and still end up having less control of what is happening.