PRB: PVCS to SourceSafe Conversion Fails

Article ID: Q153494
Creation Date: 10-JUL-1996
Revision Date: 10-JUL-1996

The information in this article applies to:

Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows 95

SYMPTOMS

When you run Pvcs_ss.exe to convert a PVCS database to a SourceSafe database, the conversion does not complete nor does it return an error message.

RESOLUTION

Add the following lines to the Autoexec.bat file:

set libpath = <path to the dll's used by the GET program, i.e. c:\pvcs\dll> set vcsid = <userid> set vcscfg = <path to configuration file> set intrsolvdir = <path to dir where license admin facility is>

NOTE: When you call PVCS_SS *.* to convert *all* of the files, it may appear to hang as it does a lot of initialization in PVCS.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Call the following command:

   PVCS_SS *.* $/<newproject>

Note that on screen and in the conversion log file, the following appears:

   PVCS_SS. Copyright...
   7/25/95 12:42

There may be some other unusable information as well. It was expected that the PVCS data is converted to SourceSafe data.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.