On this page: |
 |
|
1. What are possible values for the Status column?
Here's the list of possible values:
- Current: local file is in sync with the remote one
- Modified: local file is newer than the remote one
- Out of date: local file is older than the remote one
- Missing: local file is missing
- Not in project: remote file's stub does not exist
- Local-only: remote file does not exist
- Unknown: CRC of the remote file is not recorded in its stub
Back to Top
|
2. How is status determined?
- If the remote file does not exist, the status is Local-only.
- Otherwise, figure out local file name by attaching the remote file name to a local directory name.
- If the file's stub does not exist, the status is Not in project.
- Otherwise, if the local file does not exist, the status is Missing.
- Otherwise, get the remote file's CRC stored in the stub. If no stub does not contain CRC,
the status is Unknown.
- Calculate the local file's CRC. If it is the same as the remote CRC, the status is Current.
- Otherwise, if the file is checked out by the current user, the status is Modified.
- Otherwise, the status is Out of date.
Back to Top
|
3. What do stub names introduced in version 2.1 mean?
New stub names contain extra information about the file controlled by the stub and the
last version control action performed on the file:
- CRC of the file
- Latest action code (1 - add, 2 - check out, 3 - check in)
- Name of the user (escaped) who performed the latest action
- Date and time (escaped) of the latest action
- Check-out directory (escaped) -- if the latest action was check-out
Back to Top
|
4. Are 2.1 stubs backward compatible with 2.0 stubs?
When 2.1+ encounters 2.0 stubs, it asks whether the user wishes to convert stubs to
the more efficient 2.1 format. If some client versions are still 2.0 (have not yet upgraded to
2.1), nothing bad will happen but 2.0 will not find stub files, and will create new ones with
.stub suffix. So 2.0 will not know check-out history, and will have its own (parallel to 2.1)
history but a shorter one.
Back to Top
|
5. When I try to connect, I get error 12163. Why?
Error 12163 (ERROR_INTERNET_DISCONNECTED) is the result of
the Internet Explorer being in "Work Offline" mode. FtpVC
uses WinInet Windows library for its FTP functionality.
If you switch to Work Offline mode in IE, it will effect
all programs on your computer that use WinInet. Uncheck Work Offline
in IE and connect with FtpVC again.
Back to Top
|
6. Why do I need to set up ASCII extensions?
If a binary file is received as ASCII, it will be corrupt -
because during the FTP transfer, e.g. from UNIX to MS Windows, '\n'
will be replaced with '\r\n'. Whereas if you transfer any file as binary,
it is guarantied that both files will be identical in byte-to-byte
comparison. That's why we wanted to have the users make an explicit
inclusion of their ASCII file extensions.
Back to Top
|
7. Why are some of the features disabled even after I register the software?
When the 30-day evaluation period ends, certain advanced features of FtpVC
become disabled, and for some of these feature it is done by resetting the program options. After the
registration these options do not become automatically enabled (after all, they
may be disabled by a user for any reason). This is why, if you want to get all
of the advanced features restored after the registration, you need to go to
FtpVC Settings and Project Options and enable the following:
- Use encryption (Project Options | Advanced)
- Use compression (Project Options | Advanced)
- Use recursive subdirectories (Project Options | Options)
- Use multiple check-outs (Project Options | Options)
- Load options and settings upon connecting (Project Options | Startup)
- Define double-click action (Settings | Double-click)
Back to Top
|
8. Why do I get error 12003 ("Could not rename stub file...") when I try to check out or check in a file?
There may be a couple of reasons why a file cannot be renamed. Depending on the FTP server, the destination file name may be too long. Or the FTP server does not accept some characters in the destination name. Both reasons can be tested by attempting to manually create the destination file using your favorite FTP client.
In the first case you could reorganize your directory structure to make the path shorter, or use the Windows subst command to map a long directory name to a drive name. In the second, use Project Options | Advanced | Escape Characters For Stub File Names to replace offending characters.
Back to Top
|
9. Why do I get "The directory is not empty" message when I try to delete a directory?
The problem arises because FtpVC uses ".ftpvc" by default as the directory name where stub files and previous file versions are stored. Some servers hide all items whose names start with "." and as a result, FtpVC (which uses WinInet.dll, provided by Windows), is incapable of viewing these directories, and so doesn't know which files/directories to delete.
To solve this problem, simply change the FtpVC directory from ".ftpvc" to "ftpvc" in the Project Options | Startup dialog.
Back to Top
|
Features
