Downloads
This page contains the configuration options for where DC++ will
place complete and incomplete downloads, options that control the
maximum simultaneous downloads, and information on the public hub list
that DC++ will use.
Directories
- Default download directory
- After a download is complete, DC++ tries to move your
just finished file to this directory. It defaults to the
"Downloads\" subdirectory under where the DC++ executable is located. The directory will be automatically created if needed.
Make sure you have enough disk space for your downloads, have write access to the directory and
have an appropriate file system if you download large files (note that maximum possible size for a
file on a FAT32 volume is 4 GiB).
If the target volume runs out of space, DC++ will keep your downloaded files in the Unfinished Downloads Directory
having renamed them to their original filename.
- Unfinished downloads directory
-
All incomplete downloads will be stored in this directory.
If you leave it empty, temporary downloads will be stored in the "Incomplete\" subdirectory under
where the DC++ executable is located. The directory will be automatically created if needed.
Make sure you have enough disk space for your unfinished downloads, have write access to the
directory and have an appropriate file system if you download large files (note that maximum
possible size for a file on a FAT32 volume is 4 GiB).
From version 0.700 on of DC++, the antifragmentation method must always be used for segmented
downloads to work correctly. Hence DC++ tries to reserve the full space needed for the file when
starting the download. In case of an error (eg. when the drive that holds your Unfinished
Downloads runs out of space), you will get an error message going like "Not enough space on the
disk" even if your target drive does have enough free space!
Incomplete file names follow the following rule: <filename>.<ext>.<TTH>.dctmp.
You can use the %[targetdrive] variable in order to have
unfinished download directories in all of your target drives. This way, unfinished download
directories will be distributed amongst all of your drives, resulting in a smaller chance of
runnig out of disk space.
Example: when %[targetdrive]DCUnfinished\ is set
as the unfinished downloads directory, DC++ creates incomplete files in E:\DCUnfinished\ when
you download to any target folder located on drive E: and so on...
The %[targetdrive] variable is also useful if you often download larger files to a drive other
than the one that contains your usual unfinished directory. At the end of a successful download,
moving a large file from the unfinished folder to its target can be very time and resource
consuming, especially when moving files to another partition of the same physical drive.
Limits
These settings are to avoid overloading your internet connection with
a large number of simulatenous downloads. However, for both values listed below, certain conditions can result in the
limits not being obeyed. Specifically, up to 3 files that are set
to the 'highest' priority can be transferred while other downloads are
going. File lists and small files (64 kibibytes or
smaller) are queued with 'highest' as their priority. When either
of the limits are hit, DC++ shows "All download slots taken"
next to each source in the status column of the Connections tab.
- Maximum simultaneous downloads (0 = infinite)
- This limits the number of simultaneous downloads.
A value of 0 means no limit. (default: 3)
- No new downloads if speed exceeds (KiB/s, 0 = disable)
- This is another method of limiting simultaneous downloads,
designed to prevent new downloads if your existing downloads exceed a
specific threshold. It's measured in kibibytes per second, and a
value of zero will disable this limit.
Note; because of changing download speeds, this is not 100% accurate...
Public Hubs list
- Public Hubs list URL
- Configured Public Hub Lists
- HTTP Proxy (for hublist only)
- This HTTP proxy will only be used to request the Public
Hub List specified above. It's not used for uploads,
downloads, or connecting to a hub.