Shareaza file download progress bar is coloured red






















Disk Full Shareaza has paused this download automatically because the hard disk appears to be full, or the download file cannot be written to. Searching No Sources There are no known sources for this download, so Shareaza is searching all connected P2P networks for new sources.

Once sources are found, the download will start automatically. Shareaza searches for sources automatically, however you can speed up the process using the Find More Sources command. Unfortunately in many cases there may be no users online who have the file you are looking for.

The only course of action here is to wait for someone to come online, or cancel it and try to find a similar file which is more widely available. Paused You have paused this download. If you want it to resume downloading, you can click the Resume Download command. Read more about optimizing your downloads to avoid this. Tracker Down The BitTorrent trackers for this download appear to be down or malfunctioning. Shareaza is unable to contact them to receive a list of sources.

Verifying This download has finished, and Shareaza is now checking it to ensure that it is exactly the same as the original file. If any damaged parts are found, Shareaza will repair them automatically.

Queued This download is locally queued because too many other downloads are currently active. You can adjust the values of maximum concurrently active downloads files :.

You can also force a locally queued download to start by right-clicking it and choosing Resume. File:Src state downloading1. Requesting Shareaza has connected to a source and is now requesting a part of the file you're downloading from the source client.

Q X of Y You are in the waiting line of the remote client. X represents your queue position, Y the total queue length. TigerTree Shareaza is downloading a Tiger Tree hashset to verify integrity of the downloading file.

Busy The remote client has no upload slots available and its appropriate waitig line queue is full. Uninterested The remote BitTorrent client does not have any parts of the file you're downloading.

Shareaza will retry to connect to them when the timer runs out to attempt getting in queue. Alternatively, a timer can also mean that you're waiting for a firewalled source marked with push to connect to you. To force Shareaza to contact the source, right click it and choose Connect.

Fixed "buffer overrun" error when dragging files from explorer over Shareaza in Windowed mode Set max G1 TTL to 4 to comply with "dynamic querying" Added "Vendor-Message" header to advertise existing VM support Tweaked a few minor Gnutella1 settings to improve support Shareaza 1. Changed ed2k "request callbacks to go via UDP Shareaza now sends ed2k extended request info even if the eMule peer is using a different extended request version.

Changed Maximum Gnutella Ultrapeers to 2 Shareaza 1. New Upload Grouping to uploads view. Optimized keyboard focus handling throughout Shareaza Optimized piece picker for BitTorrent Optimized BitTorrent "Show interest" algorithm Optimized eD2k fragment selector Optimized verification selector Implemented "extended requests" for eDonkey download sources.

Fixed a crash when exporting a collection based on a virtual folder with no metadata Shareaza 1. Added Host Cache detection of gnutella hosts in G2 cache and removal Start up progress bar is now red Fixed moving files crash Fixed escape twice crash Added "assume complete and reverify" feature to the download advanced edit Changed SD files to.

Connection rate limiting applied to host connections. Failed host connections now removed from cache rather than moved to end. SaveInterval and Settings. Added download connection rate limiter Settings. ConnectThrottle, defaulting to ms 10 per second. Shareaza 1. Fixed bug where a new download group would not sort downloads Skipped network selection page for slow connections or '9x due to ed2k issues Changed character classification code to try to be more non-English friendly.

Fixed BitTorrent seeding by doing explicit verification check during the build, so the file starts off completely verified rather than verifying while uploading starts. Fixed views with splits in them being zeroed on '9x Fixed the 16 bit byte-order mark on new shareaza.

Fixed memory leak handling URIs. Added media state anchors and parts to remote window. Of course. Shareaza makes sure that the download is good before finishing and automatically re-downloads bad chunks. Kazaa, and similar software, do not do this, resulting in numerous corrupt downloads. However, Shareaza can't use this method to repair files that are already corrupt; it only prevents more corruption to happen.

The x-ray filter from the shareaza security centre is outdated and is no longer available. This section needs to be updated.

It's possible that Shareaza downloads the same corrupt parts from the same source again and again. If this is the case, you might want to try to identify the bad source by watching which part is downloaded from which source by looking at the colors. This may be a bit difficult to see, but if you happen to identify a source giving away bad data, then right click it and select Forget.

Also you might want to add a ban for the offending IP in the security window type F7. There are collections of security rules, which ban several type of bad hosts, including hosts known to upload bad data all the time. It is recommended for every user to install this.



0コメント

  • 1000 / 1000