-
The FTP protocol allows direct server-to-server transfers, but in reality, such transfers are often impossible due to firewalls.
BitKinex is able to transfer files from one server to another even if these servers run different transfer protocols and/or if there are firewalls protecting the participating networks.
How is this possible ?
When transferring files between two servers BitKinex uses the local computer as a temporary storage for the transferred files. There is no direct connection between the two servers. BitKinex downloads a file to a temporary folder on the local machine and then uploads it to the destination server. All these steps are performed automatically and the user does not need to take any action at any time during the completion of this entire process.
-
After the program is launched, BitKinex connects to a remote server even if there is no request registered. Why ?
This happens due to the auto-update functionality which automatically searches for new versions of the application. BitKinex periodically connects to the Barad-Dur server to obtain the information about the updates available for download. There is no data sent back to the server. The auto-update option can be turned off in the main options dialog.
-
In the Control window I selected a data source I would like to remove but the "Delete" menu item stays disabled. Why ?
There are two possibilities why an item cannot be removed from the data source pane:
- The item represents a folder or data source which is defined as "read-only" ( e.g. "FTP", "HTTP" ). Such definitions are necessary for the basic program functionality and cannot be removed.
- There are some instances of the data source opened. You have to close all browse windows displaying this data source and remove all request using this data source from the request pane.
-
I would like to install BitKinex on another computer. Can I copy my settings and data source definitions to the other machine ?
Yes, all your definitions are stored in the "bitkinex.ds" configuration file which is stored in your profile directory ( e.g. "C:\Documents And Settings\MyName\Application Data\BitKinex\bitkinex.ds" ). Simply copy this file to the same location on the other computer and all your data sources will appear on the other machine exactly the same.
-
Why does BitKinex transfer and overwrite files already existing at the destination location ?
When copying files from one data source to another BitKinex does not have any information about the content of the source and destination file(s) and can therefore not decide if a particular file can be skipped or not. The default procedure (which simply transfers all selected files) guarantees the equality of the source and destination file(s) after a successful copy operation. The user can change this behavior by instructing BitKinex to skip files identical in the name and length ( via the extended version of the copy request ).
-
I don't like the way file update times are displayed in browse windows and there is also no predefined format I would like to use.
Can I define my own date/time format which would be used by BitKinex ?
Yes, the way that BitKinex displays the date/time values can be adjusted by editing the "bitkinex.ds" configuration file. This file is typically located in the user's private profile directory (e.g. "C:\Documents And Settings\MyName\Application Data\BitKinex" ). The custom format specification is stored in the TM_DISP_FORM attribute of the main node. As soon as this variable is set a new item ("Custom format") appears in the list of available date/time formats.
Example:
### Node definition: BitKinex ###
NODE: TYPE = GROUP|DS NAME = BitKinex
SET COMMENT Main group.|Includes all data sources available.
.
.
.
SET TM_DISP_FORM %m/%d/%Y
.
.
.Such setting causes BitKinex to display the time information ( e.g. in the file list pane ) in the form "month/day of month/year" ( e.g. "10/12/2003" ).
The user can specify any combination of the following format identifiers:
%a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %c Date and time representation appropriate for locale %d Day of month as decimal number (01 - 31) %H Hour in 24-hour format (00 - 23) %I Hour in 12-hour format (01 - 12) %j Day of year as decimal number (001 - 366) %m Month as decimal number (01 - 12) %M Minute as decimal number (00 - 59) %p The A.M./P.M. indicator for 12-hour clock %S Second as decimal number (00 - 59) %U Week of year as decimal number, with Sunday as first day of week (00 - 53) %w Weekday as decimal number (0 - 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 - 53) %x Date representation for current locale %X Time representation for current locale %y Year without century, as decimal number (00 - 99) %Y Year with century, as decimal number %z, %Z Time-zone name or abbreviation; no characters if time zone is unknown %% Percent sign The # flag may prefix any formatting code. In that case, the meaning of the format code is changed as follows:
%#a, %#A, %#b, %#B, %#p, %#X, %#z, %#Z, %#% # flag is ignored %#c Long date and time representation, appropriate for current locale. For example: "Tuesday, March 14, 1995, 12:41:29". %#x Long date representation, appropriate to current locale. For example: "Tuesday, March 14, 1995". %#d, %#H, %#I, %#j, %#m, %#M, %#S, %#U, %#w, %#W, %#y, %#Y Remove leading zeros (if any).