FAQ -- Frequently Asked Questions

Wikipedia has a good background article on version control systems. In summary, version Control Systems and QVCS serve a number of purposes. These include:

Automating the tracking of files as they change during the course of a development project.
Controlling access to files so different users don't step on each others' work.
Preventing 'collisions' between multiple developers on the same project by preventing multiple edits to the same file at the same time.
Providing the ability to recover previous revisions of files.
Allowing multiple lines of development to proceed at the same time for a single file.
Auditing the development process so you can keep track of who changes which file, when they make the change, and what changes they make.
Reducing storage requirements.
Labeling a group of file revisions for a product release.
Creating comprehensive reports to show what files have changed between product releases.

This list is not exhaustive, but it gives you a sample of the kinds of things that QVCS can do for you. QVCS lets you make changes to the files of your project with the confidence that you can go back to previous snapshots of those files if you need to.

What is the difference between QVCS-Enterprise, QVCS-Pro and QVCS?

QVCS-Enterprise is a 100% Java client/server application that is designed for use by distributed teams.

QVCS and QVCS-Pro are Windows-only applications. QVCS-Pro includes all the features of QVCS and adds:

Support for IDE integration via the Microsoft SCC API interface. This means that QVCS-Pro can provide version control to any SCC-compliant application. IDEs that support this interface include Microsoft's Visual Studio 2005, Visual Studio.net 2003, Visual C++ 6.0, Visual Basic 6.0, Sybase's PowerBuilder, and others.
Support for simple drag-and-drop actions to the file list pane. If you drop an uncontrolled work file onto the file list pane, QVCS will invoke the Add File dialog. You can also drag a file from the list pane onto a number of applications that accept dropped files. The behavior is similar to Windows Explorer. Drag-and-drop operations are limited to single-file operations.
Support for triggers. This feature allows you to have QVCS associate your own applications with certain QVCS operations. For example, you can have QVCS call a trigger program before performing an operation; if that application exits with a status of 0, then QVCS will perform the operation; otherwise, QVCS will skip the operation. Trigger support allows you to integrate your own processes into QVCS version control operations.
Support for the qrecurse command line utility that makes it easy to apply a QVCS command to an entire directory tree.

For QVCS and QVCS-Pro, during the 60 day evaluation period, the product provides the QVCS-Pro feature set. After purchase, the license file that we send to you determines whether you will get the QVCS-Pro feature set or just the features of QVCS.

How many separate files do you have under QVCS control for managing the QVCS product itself?

For the QVCS and QVCS-Pro 3.10.15 release, there are 1098 files, including source files, project files, help topic files, and web site files.

For the QVCS-Enterprise 2.0.18 release, there are 975 files, including Java source, and other .html files used for documentation.

Is there a version of QVCS available for platform fill-in-the-blank?

QVCS/QVCS-Pro is available only for Windows platforms (NT 4.0, W2K, and WinXP).

QVCS-Enterprise is supported on Windows, Linux, Mac OS X, and Solaris 10 platforms. It should also work on any platform with a suitable Java virtual machine, but we cannot officially support other platforms at this time.

What's the best way to find out more about the capabilities of QVCS/QVCS-Pro?

The help file included with the product has lots of information. Select a topic in the help file and browse through all the topics linked to that topic in a browse sequence -- you'll probably discover something about QVCS that you didn't already know. There is a FAQ topic in the help file that covers several technical topics that aren't covered here. There is also a series of "Understanding..." topics that explain some QVCS details.

How long has QVCS been in development?

Since 1991.

When was QVCS first released?

We published the first Amiga version of QVCS (version 1.0) in 1991. We published the first Windows compatible version of QVCS March 1996. We published the first release of QVCS-Enterprise March 2004.

Does QVCS integrate with any IDE?

QVCS-Pro and QVCS-Enterprise integrate with any IDE that supports Microsoft's SCC API. This includes Visual Studio 2005, VS 2003, PowerBuilder, and others.

What tools do you use to develop QVCS?

The 3.10, 3.9 and 3.8 releases were developed with Microsoft's Visual Studio.net 2003. The 3.7, 3.6, 3.5, 3.4 and 3.3 releases were developed using the Microsoft 6.0 C++ (SP2). The 3.2 release was developed using the Microsoft 5.0 C++ compiler (SP3). The 3.1 and 3.0 releases were developed using VC++ 4.2. Earlier releases were developed using Symantec's 7.21 C++ compiler.

QVCS-Enterprise was developed using Netbeans and Sun's series of JVM's.

All releases were developed using QVCS for source control.

Is there a separate QVCS API library available for embedding version control into a non-QVCS application?

No.

Is the source code for QVCS available?

No.

QVCS-Pro and QVCS Support Questions

I installed the QVCS license file, but QWin still complains that I'm not a licensed user. What gives?

Included with the registration e-mail we send you is a file: QVCSLicense.zip_. (We send it with the .zip_ file extension so that the file attachment has a better chance of getting past the virus filters that block .zip attachments). That zip file contains a single file: QVCS.License. You need to unzip the QVCSLicense.zip file so that the QVCS.License file contained in that .zip file is in the same directory as the QWin3.exe executable.

Note that some flavors of Windows come with a bundled version of an unzip utility. When using that unzip utility, it creates a separate directory that has the same name as the .zip file, and then unzips the zip file's contents into that newly created sub-directory. This causes confusion for some users.

Please use Windows Explorer to make sure that the file named QVCS.License is co-located with QWin3.exe. They must be in the same directory. If QVCS.License is in the QVCS.License.zip sub-directory, move it from there into the same directory as QWin3.exe.

Nothing happens when I click the "Compare Files" button! What am I doing wrong?

Download Examdiff, a very nice freeware visual compare utility. Then go to QWin's Admin→Preferences... menu. On the Utilities tab of the preferences dialog, fill in the Visual Compare Utility Command Line with a string that looks like:

C:\Program Files\ExamDiff Pro\ExamDiff.exe "%s" "%s" /n

where the path should point to the location on your system where you installed examdiff.exe.

The publisher of ExamDiff also makes a shareware version of their product, which is a good value. You can visit their website for more information.

How do I share a project with a team of QVCS or QVCS-Pro users?

Here's a simple approach:

Create a shared directory on a file server. The directory should be visible to all members of the team. Team members will need read/write/update access to that shared directory.
Install QVCS into that shared directory. The simplest way to do this is to unzip qvcs.zip into that shared directory. You also need to copy your QVCS.License file into this shared directory.
Have team members run the copy of QWin3.exe that is located in this shared directory. You may find it convenient to create desktop shortcuts that point to this shared copy of QWin3.exe.
When you create projects using this shared copy of QWin3.exe, make sure to locate your archive files on a network shared directory also. Ideally, you should use a UNC style directory name to identify the location of the archive files. (UNC style directory names look like: \\computername\sharename\directory...) Users also need read/write/udpate access to the shared directories where the archive files are located.
Users should define their workfile locations to be on their local hard drives, or some network location that is theirs alone.

How do I get QVCS or QVCS-Pro to work with a SAMBA file server?

QVCS and QVCS-Pro can be used with a SAMBA file server, provided you configure the SAMBA server properly. SAMBA configuration is a huge topic -- there are whole books on the subject. However, as it relates to use with QVCS and QVCS-Pro, the configuration elements that you need to be concerned with are limited.

Here is a sample smb.conf file that we use here for testing with SAMBA:

[global] workgroup = Quma restrict anonymous = no domain master = no preferred master = no max protocol = NT ldap ssl = No server signing = Auto [qvcsbin] path = /qvcsdata/bin/ guest ok = yes read only = no [qvcsarchives] path = /qvcsdata/archives/ guest ok = yes read only = no delete readonly = yes

The most important settings to get right are the ones that are shown bolded above: read only = no and delete readonly = yes.

I changed the access list of a project but some users still can't access files of the project. What's going on?

When you change the access list of a project using the Project→Edit Settings... dialog, unless you enable the 'Change all children' check box, you only change the access list that QVCS will use when it creates a new QVCS archive. Existing archives are unaffected by this change, since QVCS access lists are stored within the archive files themselves - not at the project level.

In order to change the access list of existing archives, you must enable the 'Change all children' check box, or use the Project→Modify Archive→Access List menu selection. This will display the "Maintain Access List" dialog which allows you to change the access list contained within the archive files of the selected project or sub-project.

How do I get rid of unwanted branches?

If you lock or check out a non-tip revision (a revision that isn't the newest revision on the TRUNK or on a branch), when you check that revision back in, QVCS will automatically create another branch for you. Sometimes this may not be what you want, and you're left with a new branch that you don't want. How do you get rid of it?

To use QWin to delete the unwanted branch, follow these steps:

Select the file.
Execute the File→Delete Revisions... menu command.
On the Delete Revisions dialog, select the revisions on the branch that you want to delete, and click the OK button.
Repeat this process as needed until all the unwanted branches are trimmed from the QVCS archive.

You can also accomplish the same result using the qdelrev command line utility. The command line format for qdelrev is very simple:

qdelrev -r revision filename

So for example, if you wanted to delete revision 1.2.1.5 from the QVCS archive for foo.c, you'd type the command line:

qdelrev -r 1.2.1.5 foo.c

To prune an entire branch from an archive, you can use a wildcard character in place of the final minor revision number. For example, to delete the entire 1.2.1 branch, you'd use the following command:

qdelrev -r 1.2.1.* foo.c

What files should I backup?

The simplest approach for QVCS-Pro and QVCS is to backup the QVCS/QVCS-Pro installation directory, and all directories beneath that directory. You'll also want to backup the archive directory trees, i.e. the directory trees that contain your QVCS archive files.

If you are using QVCS in a team environment (where your QVCS executables are located in a network shared directory), you should make sure to backup the contents of that network shared directory. Make especially sure to create backup copies of all the .ini files located in the directory where the QVCS executable files are located.

Backups should be performed on a regular basis.

How do I upgrade from an earlier QVCS or QVCS-Pro release?

If your license is older than one year, you may need to purchase a license update ($20/user). After confirming that you have a license that will work with the latest release, follow these steps:

Here's the simplest approach:

Make sure all users have exited QWin3.exe, and that all users have closed all IDE's that make use of QVCS-Pro's IDE integration support.
Make a backup copy of your existing QVCS or QVCS-Pro installation directory, including all subdirectories.
Download the qvcs.zip file for the latest release from here.
Unzip that qvcs.zip file so that its contents overwrite the contents of your existing QVCS or QVCS-Pro installation directory.

You should also make a point of reading the upgrade.txt file that's contained in the qvcs.zip file for any additional information about the upgrade.

Updates are 'free' for up to 1 year after your initial purchase.

How do I get QVCS-Pro to integrate with an IDE?

Follow these steps to get QVCS-Pro to work with an IDE that supports Microsoft's SCC API:

Start QWin, and after defining at least one QVCS user, define a project that identifies where you want QVCS to store the archives associated with the files that you maintain within the IDE. The goal should be to make it so you can version control the files from within QWin.
From the Admin→IDE Integration menu, select the kind of IDE behavior you need from QVCS. Some IDE's require QVCS to be the 'default' version control tool (e.g. Microsoft's VC++); others will work so long as QVCS is installed as a version control supplier.
Within your IDE, you may need to set up QVCS as the version control tool. This varies from tool to tool.

How do I get QVCS-Pro to integrate with Visual Basic?

If you have the professional version of VB 6.0, you can get QVCS to work with it by following these steps after installing QVCS and setting up QWin to be 'aware' of the VB project (i.e. setting the project location, etc.).

Find the vbaddin.ini file in your windows system directory. If the file doesn't exist, create it.
Add the following line to that file in the [Add-Ins32] section:
vbscc=1
Start VB and go to the Add-Ins menu and with the Add-in manager, enable Source Code Control to be loaded, and to load on startup. Click OK.

How do I get QVCS-Pro to integrate with Visual Studio 2005?

QVCS-Pro 3.9.25 and later releases support integration with Visual Studio 2005. To get QVCS-Pro to work with Visual Studio 2005, follow these steps:

You must install QVCS-Pro on your local hard drive. This is a requirement of Visual Studio 2005. If you work with a team of developers, QVCS-Pro provides a way for you to share project definitions with other team members, even when your copy of QVCS-Pro is installed locally.
If you work alone, skip this step. If you work with other team members, you need to create a shared location accessible to team members where you will store the QVCS archive files. Typically this shared directory is the root directory for all your projects' archives. It might have a name like:
\\QumaServer\qvcsArchives\
This location is then used when defining the "Location of archive files" when creating new projects with QWin, or when defining the location of a QVCS project's archive files via the Admin/Project Settings... menu.

For a project named "Test Project", you might define that project's "Location of archive files" as:

\\QumaServer\qvcsArchives\Test Project
If you work alone, skip this step. If you work with other team members, you need to create a shared directory that will contain your qwin.ini and user .ini files. (qwin.ini and user .ini files are created automatically by QVCS as you define users and projects). This directory should be different than the directory used to store your archive files described in the previous step. Typically, this shared directory is located on a network server in a network shared directory. It might have a name like:
\\QumaServer\qvcsbin
If you work alone, skip this step. In the QVCS-Pro installation directory on your local drive, use notepad (or some other editor) to create a file called qvcs.ini and save this file in the QVCS-Pro executable directory located on your local hard drive. Edit the contents of qvcs.ini so that it contains the following:
[Initialization] LicenseLocation=shared directory that contains qwin.ini -- blank line --

For example, the contents of the qvcs.ini file that we use here looks like:

[Initialization] LicenseLocation=\\QumaServer\qvcsbin\ -- blank line --

By creating the qvcs.ini file in your local QVCS-Pro executable directory, and defining the LicenseLocation property, you are telling QVCS-Pro to use the .ini files located in the LicenseLocation directory instead of using the .ini files located on your local drive. You are also telling QVCS-Pro that your QVCS.License file will be found in the LicenseLocation directory.
Launch Visual Studio 2005. Select or create the project that you want to have under version control. Exit Visual Studio 2005.
Execute the copy of QWin3.exe located on your local hard drive.
In QWin, make sure that the project files that you use within Visual Studio 2005 are under version control. In QWin, this means that you should be able to navigate to that VS 2005 project, and see that the files that you use within VS 2005 are under version control. Visual Studio 2005 generally expects that you place the .sln file under version control, and that you also version control your source files and the *proj files the define the projects that compose your solution.
In QWin, select the Admin→IDE Integration→Make QVCS the default Version Control tool menu item.
Launch Visual Studio 2005 again.
In the simplest case, Visual Studio 2005 will detect that files in your project are now under version control. Alternately, you may need to 'bind' your project files to version control. To do this, right click in the toolbar area in VS 2005, and make sure to enable the 'Version Control' toolbar. On the 'Version control' toolbar, click on the 'Change source control' button. On the resulting 'Change source control' dialog, select each row, and click on the 'Bind' button.

How do I get QVCS-Pro to integrate with PowerBuilder?

QVCS-Pro works with PowerBuilder 8 and later releases. It should work with PB7 too but has not been fully tested with it. Because of known problems with some PB-EBF's we recommend that you use the latest version of QVCS-Pro. QVCS-Pro supports a Sybase specific SCC API extension first used in PB 9 (SccQueryInfoEx()) which makes it much faster to open PBL's that are under source-control.

To get QVCS-Pro to work with PowerBuilder, follow these steps:

Install QVCS-Pro on a central network drive or on a local drive as described in the Visual Studio 2005 FAQ.
Choose a local root-directory for your PB project and distribute all PBL's into subdirectories beneath that directory. One PBL per directory is a good rule of thumb.
If neccessary, create your target and workspace for the project.
In QWin create your QVCS project and point its working directory to the root-directory of your PB-project. With QWin, create sub-projects for every sub-directory that contains a PBL. Do not auto-populate the sub-projects, just create them! If more PBL's will be added to the project in the future, you must always create the corresponding sub-project in QWin before before attempting any version control operations on the PBL.
Open the properties of your PB workspace:
- Choose "Quma Version Control System" as Source-Control-System. If QVCS doesn't show up here you probably forgot to register QVCS as a source-control provider (QWin:Admin→IDE Integration)
- Enter your QVCS-user-id into the "User ID" field
- Click on the button right next to "Project": "QVCS Projects" will show up in the project field.
- Choose the local root directory for your workspace
- Enable "Delete Powerbuilder generated object files"
- Enable "Supress prompts to overwrite read-only files"
- All other options can be used as needed by the team.
Register all PBLs one by one by right-clicking on it and choosing "Add to Source Control". PBG-Files will be created (and added to Source Control) by PB automatically.
Add the target file to QVCS.
NEVER put any PBL files under source control thru QWin!
All source control operations (except "Remove from Source-Control") can be done in PB-IDE.
If an object has to be removed from source control:
- Delete the archive in QWin.
- Refresh the status of the object in PB.
- Delete the object from the PBL

Does QVCS/QVCS-Pro work on Windows Vista?

Yes... though there are some caveats:

You should install QVCS/QVCS-Pro in C:\qvcsbin instead of C:\Program Files. Vista doesn't like applications to write to the C:\Program Files area. QVCS-Pro stores and updates its config files in the same directory as the executable files, so Vista isn't happy if you install it in C:\Program Files...
QVCS/QVCS-Pro still uses Windows help for its help system. If you launch QVCS/QVCS-Pro help, Vista will tell you that you need to download something from Microsoft in order to be able to use Windows help files. If you install the Microsoft supplied 'utility', you'll be able to use the QVCS-Pro help files.

QVCS-Enterprise Support Questions

How do I run the QVCS-Enterprise server as a Windows Service?

There are two important details that must be observed in order to get things to work:

On the server, you need to install the JVM, not the JRE. The JVM includes the 'server' flavor of the virtual machine. The scripts included in the QVCS-Enterprise installation assume that the 'server' flavor of the virtual machine is available. If the server virtual machine is not present, then the installation scripts will not work.
Make sure that your server's JVM is installed so that there are no spaces in the path to its location. This means for Java 5 and Java 6 installations, you cannot use the default install location of C:\Program Files\.... A location that will work would be something like C:\Java\jdk1.6.0. You then need to make sure that the path to the JVM (JAVA_HOME) is defined correctly in the setEnv.cmd command file.
If you installed the JVM to C:\Java\jdk1.6.0, then the line in setEnv.cmd that defines the JAVA_HOME environment variable would look like:

set JAVA_HOME=C:\Java\jdk1.6.0

After making sure you have set things up correctly, follow these steps:

Edit the setEnv.cmd file in the server install directory so that the JAVA_HOME environment variable is correctly defined.
Start a command window.
Change directories to the server install directory (where server_out.jar is located).
Execute the test_enterprise_install.bat batch file located in that directory. This should install the server as a Windows service, provided you have correctly defined the JAVA_HOME environment variable in setEnv.cmd.
Start the service by executing the start_service.bat batch file.

Note that the test_enterprise_install.bat is written to install the service to start automatically. This means that when the machine next boots, the server will automatically be started.

How do I upgrade QVCS-Enterprise to the latest release?

If your license was purchased more than one year before the release date of the latest release, you will need to purchase a license update ($20/user). Your license file is located on your server machine in the same directory as server_out.jar. The license file (QVCSEnterprise.License) is a digitally signed human readable text file that includes the date of purchase for your license. After confirming that you have a license that will work with the latest release, follow these steps:

Download the latest release from the Quma web site.
Stop the server application. If you are using server.bat, just type CTRL-C in that command window; if running the server as a Windows service, use the stop_service.bat batch file to stop the Windows service.
Extract the server_out.jar file from the .zip file that you downloaded in the first step, and replace the existing server_out.jar with the new one.
Restart the server application using server.bat or start_service.bat.
Each client can now login to the server. The client will detect a version mismatch and automatically download the correct gui_out.jar file from the server. You will have to restart the client after it updates the gui_out.jar file. Windows clients will also automatically update the QVCSEnterpriseSCC.dll file so you can connect to the server from within a Microsoft SCC compliant IDE.
You should also run the admin tool (admin.bat or admin.sh) so that the admin tool will get updated.

Where do I find the client log file?

The client log file will generally be located in the same directory as the gui_out.jar file. The log file will have a name like qvcsEnterpriseClient0.log.

You can change the location of this file by manually editing the guiLogging.properties file that's located in the same directory as the gui_out.jar file. That properties file is pretty well commented. Look for the line that looks like:

java.util.logging.FileHandler.pattern = qvcsEnterpriseClient%u.log

You can change the file name to the right of the equal sign to some more suitable name and/or location.

Where do I find the server log file?

The server log file will generally be located in the same directory as the server_out.jar file. The log file will have a name like QVCSEnterpriseServer0.log.

You can change the location of this file by manually editing the serverLogging.properties file that's located in the same directory as the server_out.jar file. That properties file is pretty well commented. Look for the line that looks like:

java.util.logging.FileHandler.pattern = QVCSEnterpriseServer%u.log

You can change the file name to the right of the equal sign to some more suitable name and/or location.

What files should I backup?

On the server:

On the server, you should backup the server installation directory, and all directories beneath that directory. The server installation directory is the one containing the server_out.jar file. If you use the default locations for the archive storage, this backup strategy will include all the QVCS archives for all the projects hosted on that server. You should perform server backups on a regular basis.

On the clients:

On the client, you may want to backup the client install directory (the one containing the gui_out.jar file) and all its sub-directories. Backup on the client is not so critical as server backups, in that data on the client can be regenerated without too much effort.

I'm getting 'out of memory' exceptions on the server. What should I do?

If you are running the server as a Windows service, you will need to:

Stop the service (use the stop_service.bat batch file).
Uninstall the service (use the test_enterprise_uninstall.bat batch file).
Edit the installEnterpriseService.bat batch file, replacing the -Xmx256M found there with -Xmx512M.
Reinstall the service (use the test_enterprise_install.bat batch file).
Restart the server as a Windows service (use the start_service.bat batch file).

If you are running the server from the command line:

Shutdown the server by typing CTRL-C in the command window where the server is running, or by using the admin tool to shutdown the server.
Edit the server.bat (or server.sh) file, adding -Xmx512M before the -jar on the command line used to start the server.
Restart the server.

I'm getting 'out of memory' exceptions on the client. What should I do?

Try this:

Exit the client application.
Edit the gui.bat (or gui.sh) file, adding -Xmx512M before the -jar on the command line used to start the client.
Restart the client.

How do I port archives from QVCS or QVCS-Pro to QVCS-Enterprise?

QVCS-Enterprise supports some features that are not available in QVCS/QVCS-Pro. This means that when you port archive files from QVCS/QVCS-Pro, QVCS-Enterprise needs to perform some 'one-time' operations to create QVCS-Enterprise meta-data. The creation of this meta-data is performed for all projects on the server -- which means that when you import archives from QVCS/QVCS-Pro, any existing project meta data will be lost.

QVCS-Enterprise and QVCS/QVCS-Pro handle deleted files differently. In QVCS/QVCS-Pro, when a user 'deletes' a file, it is marked obsolete, and the archive file continues to reside in the original directory. When QVCS-Enterprise 'deletes' a file, the associated archive file is moved to the project's cemetery, and renamed. This means that while the archive file formats are the same, it will be challenging to migrate QVCS-Enterprise archive files back to QVCS/QVCS-Pro.

To migrate QVCS/QVCS-Pro archives to QVCS-Enterprise:
(You should NEVER use QVCS-Enterprise at the same time as QVCS and/or QVCS-Pro).

1. With the QVCS-Enterprise admin tool create a new project with a name that is meaningful for you. You may want to use the same project name that you have used with QVCS/QVCS-Pro, but it's not required.
2. With the admin tool, make sure to define the user roles for this new project.
3. Shut down the server, and exit the admin application.
4. Using a tool appropriate for your server's platform, delete the qvcs.fileIDStore.dat located in the qvcsMetaData beneath the directory that contains server_out.jar. Deleting this file will force the server application to regenerate the project meta-data described above.
5. With Windows Explorer (if on Windows), locate the existing QVCS/QVCS-Pro archive files and move those archive files into the qvcsProjectsArchiveData\Your new project name directory located beneath the server_out.jar's directory.
6. Restart the server. Before the server will accept connections from a client application, it will generate the project meta-data. For large projects, this can take some time.
7. Start the Enterprise client application. You should be able to 'see' the new project, and all the history that you captured back when you were using QVCS/QVCS-Pro.

What kind of encryption does QVCS-Enterprise use?

Communication between the client application (gui.bat or gui.sh) and the QVCS-Enterprise server application is encrypted using anonymous SSL.

Communication between the admin application (admin.bat or admin.sh) and the QVCS-Enterprise server application is encrypted using anonymous SSL.

Communication between an IDE client (using the IDE integration .dll) and the server is not encrypted.

Anonymous SSL offers good security, but is vulnerable to a 'man-in-the-middle' attack. If you need better security, we recommend that you use a VPN to establish a connection between your client machine(s) and the server, and then connect from the client application to the QVCS-Enterprise server via that VPN connection.

Does QVCS-Enterprise work on Windows Vista?

Yes... though there are some caveats:

You should install QVCS-Enterprise server in C:\qvcseBin instead of C:\Program Files. Vista doesn't like applications to write to the C:\Program Files area. QVCS-Enterprise server stores and updates its config files in the same directory as the executable files, so Vista isn't happy if you install it in C:\Program Files...
You should install QVCS-Enterprise client in C:\qvcseBin instead of C:\Program Files. Vista doesn't like applications to write to the C:\Program Files area. QVCS-Enterprise client stores and updates its config files in the same directory as the executable files, so Vista isn't happy if you install it in C:\Program Files...