SAMPLE: Updated Visual SourceSafe 4.0 Ddconv.exe

 Last reviewed: January 12, 1998
Article ID: Q150647
The information in this article applies to:
  • Microsoft Visual SourceSafe for Macintosh, version 4.0
  • Microsoft Visual SourceSafe for Windows, version 4.0
  • Microsoft Visual SourceSafe for Windows NT, version 4.0
  • Microsoft Visual SourceSafe for Windows 95, version 4.0

SUMMARY

A new version of Ddconv.exe, dated August 14, 1996, is available. You should use this new version of Ddconv.exe if you are:

  • Using Visual SourceSafe for Macintosh version 4.0 and have a Visual SourceSafe database in 3.x format.

- or -
  • Experiencing a General Protection Fault when Ddconv.exe attempts to upgrade your 3.x database.

Ddconv4.exe contains the following files:
  • Ddconv.exe
  • Ssus.dll
  • Ssapi.dll
  • Readme.txt

The following file is available for download from the Microsoft Software Library: 

 ~ Ddconv4.exe (size: 417274 bytes)
For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services

MORE INFORMATION

The following information is also provided in the Readme.txt file included in Ddconv4.exe:

DDCONV is a utility that converts SourceSafe 3.x databases to Visual SourceSafe 4.0 database format. DDCONV is automatically run as part of the setup process, therefore, most users usually never manually run this utility. DDCONV is also one of several steps in the process of creating a new Visual ourceSafe database. DDCONV can also be used with the -S option to rebuild some files in the database.

DDCONV has been posted up here to ensure that the latest version of DDCONV is available to customers. This is a 32-bit executable and must be run from a 32-bit operating system such as Windows 95 or Windows NT. If, during installation, Visual SourceSafe cannot find all of the installed databases, he administrator may have to run this utility manually. Also, if DDCONV produces a General Protection Fault and the last line of the DDCERR.LOG file reads "File <path to file ending in .a or .b> not found," you may need to take additional steps. For additional information, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q156451
   TITLE     : FIX: DDCONV Causes GP Fault During Database Conversion
To install this file, create a directory and copy Ddconv.exe, Ssus.dll, and Ssapi.dll to it. You can also install these files in the root directory for Visual SourceSafe.

NOTE: Do not install these files in the VSS\WIN32 directory because it might disable the use of the 32-bit version of Visual SourceSafe.

Syntax 

   DDCONV [-s] [-mSSpath]|[data path]

Option      Description
--------    -----------

-MSSpath    The path of a SRCSAFE.INI file from which DDCONV can determine
            the data directory.
Datapath    The path to a data directory to convert.
-S          Rebuild the Visual SourceSafe checkout status index file,
            status.dat.
In some cases, the conversion of the SourceSafe 3.1 data to Visual SourceSafe 4.0 format fails with the version of Ddconv that shipped with Visual SourceSafe 4.0. If you receive an error message while your data is converting, reference the steps as outlined in the following article in the Microsoft Knowledge Base: 

  ARTICLE-ID: Q153873
  TITLE     : How To Upgrade from SourceSafe 3.x to Visual SourceSafe 4.0

Additional query words: convert analyze
Keywords : ssdb
Version : Mac:4.0;Win3.x:4.0;Winnt:4.0;Win95:4.0;
Platform : MACINTOSH NT WINDOWS
Issue type : kbfile
Solution Type : kbsample

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.

Last reviewed: January 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.