vwemirror/firestorm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
1fd489d9a64736b8d154bd0fe4f699143a4a91fe
firestorm/build-env/VisualStudio6/READMESS.HTM
T
Cyd 2b8ca921cb Initial full mirror of c:\VWE (source + assets + toolchain + outputs) via Git LFS 
Complete disaster-recovery snapshot: engine/game source, game data assets,
VC6 toolchain + DX SDKs, build outputs, deployed game, and _UNUSED archive.
Large binaries in Git LFS; text preserved byte-for-byte (core.autocrlf=false,
no eol attributes). See RECOVERY.md for the one-clone rebuild procedure.
2026-06-24 21:28:16 -05:00

2194 lines
90 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html public "-//W3C//DTD HTML 4.0 Draft//EN">
<html>
<!----------------------------------------------------------------------------->
<!-- BEGIN HTML HEAD -->
<!-- -->
<!-- ToDo: - <title>Visual SourceSafe 6.0a Readme</title> -->
<!-- - content ="ReadmeSS" -->
<!-- -->
<!-- -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1251">
<title>Visual SourceSafe 6.0a Readme</title>
<meta name="MS-HAID" content="readmess">
<body bgcolor=#ffffff text=#000000 link="#0000FF" vlink="#0000FF" onclick="checkExpand( )">
<font face="Verdana" size=2>
</head>
<!-- -->
<!-- END HEADER -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN JSCRIPT -->
<!-- -->
<!-- THIS IS STUFF IS STATIC - DO NOT ALTER -->
<!-- -->
<!-- -->
<script language="JSCRIPT">
function checkExpand( )
{
if ("" != event.srcElement.id)
{
var ch = event.srcElement.id + "Child";
var el = document.all[ch];
if (null != el)
{
el.style.display = "none" == el.style.display ? "" : "none";
if (el.style.display != "none")
event.returnValue=false;
}
}
}
</script>
<!-- -->
<!-- END JSCRIPT -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN README INTRO -->
<!-- -->
<!-- -->
<!-- ToDo: - <h2>Visual SourceSafe 6.0 Readme</h2> -->
<!-- - <i>Visual SourceSafe</i> -->
<!-- -->
<!-- -->
<h2>Microsoft<sup>&reg</sup> Visual SourceSafe<sup>&trade;</sup> 6.0a</h2>
<p>&copy; 2000 Microsoft Corporation. All rights reserved. </p>
<p>Other product and company names herein may be the trademarks of their respective owners. </p>
<p> <i>Visual SourceSafe Readme</i> includes updated information for the documentation provided with Microsoft<font face="Symbol"><span style="font-family:Symbol">&#226;</span></font> Visual Studio&reg; -- Development System for Windows&reg; and the Internet. The information in this document is more up-to-date than the information in the Help system.</p>
<!-- -->
<!-- -->
<!-- END README INTRODUCTION -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN TOC -->
<!-- -->
<!-- ToDo: -->
<!-- - For each <h5><a>nchor TITLE attribute, enter a helpful tooltip. -->
<!-- - For each <h5><a> ID attribute, enter a unique, descriptive id. -->
<!-- - For each <h5><a>, replace "Section X.0" with a unique section name.-->
<!-- -->
<!-- -->
<!-- - For each <div> ID attribute, add the <h5> ID string, appending -->
<!-- the word "Child" to the end. -->
<!-- - For each <a>nchor element, replace href="Template.htm#Topic_XX" -->
<!-- with the name of the readme file, followed by a unique Topic -->
<!-- shortcut. ex. href="ReadmeVJ#SetupWreaksHavoc" -->
<!-- - For each <a>nchor element, replace "Topic X.X" with a Topic String.-->
<!-- -->
<!-- Notes: -->
<!-- - Following line is only needed to highlight new product features: -->
<!--<font color="#FF0000" size="1" face="Arial,Helvetica"><strong>NEW</strong></font>-->
<!-- -->
<!-- - Do not extract the pound sign (#) from the <a>nchor element. -->
<!-- -->
<!-- -->
<!-- -->
<!-- -->
<h3><p>Contents <font color="#000000" size="2" face="Verdana,Arial,Helvetica">- Click any of the items below</font></p></h3>
<!------------------------------------------------------------------->
<!-- SECTION 1.0 -->
<!-- -->
<h5><a href="ReadmeSS.htm#Topic_10">Release Description</a></h5>
<!------------------------------------------------------------------->
<! SECTION 2.0 -->
<! -->
<h5><a class=ex href="#" title="Click to expand or collapse." id="KnownProblems">Known Problems</a></h5>
<div id="KnownProblemsChild" style="display:none">
<blockquote>
<a href="ReadmeSS.htm#Topic_20">Installing on a Novell Network Server</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_21">Corrected Documentation Text</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_22">MBCS/DBCS Users</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_23">Bug Fixes</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_24">Unicode Files</a>
</blockquote>
</div>
<!------------------------------------------------------------------->
<!-- SECTION 3.0 -->
<!-- -->
<h5><a class=ex href="#" title="Click to expand or collapse." id="GettingStarted">Getting Started</a></h5>
<div id="GettingStartedChild" style="display:none">
<blockquote>
<a href="ReadmeSS.htm#Topic_30">Before You Run Setup</a>
</blockquote>
</div>
<!------------------------------------------------------------------->
<!-- SECTION 4.0 -->
<!-- -->
<h5><a class=ex href="#" title="Click to expand or collapse." id="Installation">Installation</a></h5>
<div id="InstallationChild" style="display:none">
<blockquote>
<a href="ReadmeSS.htm#Topic_40">Visual SourceSafe 6.0a Setup</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_41">Installing Visual SourceSafe 6.0a over Visual SourceSafe 6.0 SP4 or Earlier</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_42">Installation Options</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_43">Installing Visual SourceSafe Standalone Version</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_44">Installing Multiple Versions of Visual Studio 6.0 Products "Side-by-Side" on the Same Computer</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_45">(Individual Users) Using Netsetup to Create a Personal Installation</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_46">Upgrading a Database After Installing</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_47">Deleting VSS</a>
</blockquote>
</div>
<!------------------------------------------------------------------->
<!-- SECTION 5.0 -->
<!-- -->
<h5><a class=ex href="#" title="Click to expand or collapse." id="GeneralNotesandTips">General Notes and Tips</a></h5>
<div id="GeneralNotesandTipsChild" style="display:none">
<blockquote>
<a href="ReadmeSS.htm#Topic_50">New Features in VSS 6.0</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_51">Maintaining Your VSS Database</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_52">Loss of Network Connection Produces Numerical Error Message</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_53">System Date/Time</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_54">Using the Command Line After Running a Client Setup</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_55">Details on Defining a Shadow Folder in Visual SourceSafe</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_56">Running Netsetup from a Windows NT Server Computer Using Windows 95</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_57">VSS Home Page</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_58">Microsoft Knowledge Base</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_59">VSS Newsgroup</a>
</blockquote>
</div>
<!------------------------------------------------------------------->
<!-- SECTION 6.0 -->
<!-- -->
<h5><a class=ex href="#" title="Click to expand or collapse." id="BestPractices">Best Practices</a></h5>
<div id="BestPracticesChild" style="display:none">
<blockquote>
<a href="ReadmeSS.htm#Topic_60">Introduction</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_61">General Database Recommendations</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_62">How Visual SourceSafe Tracks Files</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_63">Finding and Repairing Data Corruption</a>
</blockquote>
<blockquote>
<a href="ReadmeSS.htm#Topic_64">Backup and Restore</a>
</blockquote>
</div>
<p>&nbsp;</p>
<!-- -->
<!-- END CONTENTS TOC -->
<!----------------------------------------------------------------------------->
<!----------------------------------------------------------------------------->
<!-- BEGIN CONTENTS -->
<!-- -->
<!-- Structure Outline -->
<!-- ----------------- -->
<!-- H3 - Section Name -->
<!-- H4 - Topic Title -->
<!-- H5 - Sub Topic -->
<!-- -->
<!-- -->
<!-- -->
<!------------------------------------------------------------------->
<!-- SECTION 1.0 -->
<!-- -->
<h3><a name="Topic_10"></a>Visual SourceSafe 6.0a Release Description</h3>
<p>
Visual SourceSafe version 6.0a is a re-release.
It contains a modified installation program and updated VSS files containing all
bug fixes made since VSS 6.0 released.
This version is intended to upgrade the VSS release included in Microsoft Office
Developer version 9.0.
</p>
<p>
The installation program for VSS 6.0a has been modified to ensure an upgrade of your
existing VSS 6.0 installations.
Read the Installation section in this document for the latest install directions.
For a list of the fixes included in this release, see <a href="ReadmeSS.htm#Topic_23">VSS 6.0a
Bug Fixes.</a>
</p>
<br>
<!------------------------------------------------------------------->
<!-- SECTION 2.0 -->
<!-- -->
<h3>Known Problems</h3>
<br>
<!------------------------------------------------------>
<!-- TOPIC 2.0 -->
<!-- -->
<h4><a name="Topic_20"></a>Installing on a Novell Network Server</h4>
<p>
Novell NetWare servers
can be configured to handle either long file names or file names in the 8.3
file name format. If the Novell NetWare server can handle only file names in
the 8.3 format, the regular Visual Studio installation process cannot install
on the Novell NetWare server. To install VSS on a Novell NetWare server that
can handle only file names in the 8.3 format, use the following steps.
</p>
<p><b>To install from the Visual Studio CDs:</b></p>
<ol>
<li>Insert Disk 2.</li>
<li>Switch to the VSS_SS\ folder.</li>
<li>Run the following command: setup.exe /F</li>
<li>Click <b>Server Applications</b>.</li>
<li>When prompted for the installation location, change it to the Novell NetWare Server.</li>
</ol>
<br>
<p><b>To install from the Visual SourceSafe standalone compact discs:</b></p>
<ol>
<li>Insert the Visual SourceSafe compact disc.</li>
<li>Run the following command: setup.exe /F</li>
</ol>
<br>
<!------------------------------------------------------>
<!-- TOPIC 2.1 -->
<!-- -->
<h4><a name="Topic_21"></a>Corrected Documentation Text</h4>
<p>
Difference for File
Dialog Box topic — In the Dialogs section of the Visual SourceSafe
documentation, the first paragraph in the Remarks section is incorrect.
</p>
<br>
<blockquote>
Current
text: This dialog box is used only when you have not selected the visual
difference comparison. (For visual differences, make sure you select the Visual
option from the Difference Options dialog box.) By default, VSS uses the Visual
Difference dialog box.
</blockquote>
<br>
<blockquote>
Correct
text: This dialog box is used only when you have not selected the visual
difference comparison. (For visual differences, make sure you select the Visual
option from the Difference Options dialog box.) By default, the Visual option
is selected, and VSS uses the Differences for &lt;filename&gt; dialog box with
options specific to visual differences.
</blockquote>
<br>
<p>
In the File History
Options Dialog Box topic of the Visual SourceSafe Documentation, the first sentence
of the Labels section is incorrect.
</p>
<br>
<blockquote>
Current
text: Includes only labels in project history if you have selected the Include
file checkins option.
</blockquote>
<br>
<blockquote>
Correct
text: Includes only labels in project history if you have selected the Include
file histories option.
</blockquote>
<br>
<p>
In the Advanced Check Out
Options Dialog Box topic of the Visual SourceSafe Documentation, the Replace
option is incorrect.
</p>
<br>
<blockquote>
Current
text: Replace — Replaces the file with a read-only version.
</blockquote>
<br>
<blockquote>
Correct
text: Replace — Replaces the file with a writable version.
</blockquote>
<br>
<p>
In the Advanced Check Out
Options Dialog Box topic of the Visual SourceSafe Documentation, the End of
Line option has been removed.
</p>
<br>
<p>
In the Advanced Get
Options Dialog Box topic of the Visual SourceSafe Documentation, the End of
Line option has been removed.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 2.2 -->
<!-- -->
<h4><a name="Topic_22"></a>MBCS/DBCS Users</h4>
<p>
VSS 6.<i>x</i> handles
MBCS (multibyte character sets) and DBCS (double-byte character sets)
differently from earlier versions of VSS. If you are upgrading an existing
installation of VSS that has a file called SSUD.dll, rename it so that VSS 6.<i>x</i>
does not recognize it. For example, rename the file to SSUD.bak. If you do not
rename it, you may have trouble in the IME with font association (FA) turned
off or it may generate GPFs when dialog boxes that are new to VSS 6.<i>x</i>
are displayed.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 2.3 -->
<!-- -->
<h4><a name="Topic_23"></a>Bug Fixes</h4>
<p>
VSS 6.0a contains the
following bug fixes. References to articles in the Microsoft Knowledge Base are
included where appropriate.
</p>
<br>
<ul>
<!-- SP5 Fixes -- >
<!-- [64603 | 22 August 2000] -->
<li>Q238242: OLE Automation loads incorrect TypeLibrary in late binding.</li>
<!-- [64604 | 22 August 2000] -->
<li>Q238345: OLE Automation: Opening a SourceSafe database fails with "Out of Memory" on WIndows 2000.</li>
<!-- [66172 | 23 August 2000] -->
<li>Calling QueryInterface on a IVSSVersion returns E_NOINTERFACE.</li>
<!-- [66081 | 22 August 2000] -->
<li>DATA LOSS: Enabling Make Writable on file get dialog causes Replace Writable options to be ignored.</li>
<!-- [66082 | 22 August 2000] -->
<li>Running analyze -f overwrites analyze.log file when backup folder is not empty.</li>
<!-- [66083 | 22 August 2000] -->
<li>OLE Automation created with VSS 5.0 not working on a 6.0 computer.</li>
<!-- [66084 | 22 August 2000] -->
<li>Setting multiple checkouts on a per project basis disables the Checkout option after a file has been checked to one user.</li>
<!-- [66086 | 22 August 2000] -->
<li>CDCR: Destroying a project does not show that it is still working.</li>
<!-- [66088 | 22 August 2000] -->
<li>Analyze fails to repair or remove orphaned files in a VSS database.</li>
<!-- [66089 | 22 August 2000] -->
<li>Names.dat corruption not repaired by Analyze.</li>
<!-- SP4 Fixes -->
<!-- 161 -->
<li>Project Difference shows file changed, then says files are identical.</li>
<!-- 2207 -->
<li>Q244960: When running DDUPD.exe on a Visual SourceSafe database, you may receive
an error &quot;Out of memory.&quot; This typically occurs when you have many files
that are labeled</li>
<!-- 2213 -->
<li>Q230702: Delete and Destroy or Rename Project gives &quot;File or project not found&quot;
and &quot;1E string load failure #%d&quot; errors.</li>
<!-- 2217 -->
<li>Restoring archived files generates an error message "Too many file handles open" and the
files are not restored.</li>
<!-- Missing bug number -->
<li>Running analyze –f incorrectly truncates long file names resulting in database corruption.</li>
<!-- 2250; same as 2264 -->
<li>Q228927: Performance problem with the integration between Visual C++ and VSS.</li>
<!-- 2271 -->
<li>Q237184: Branching from a label gives &quot;File or project not found&quot; and &quot;You
do not have access rights to $/&lt;deleted project&gt;&quot; and the branch operation
does not successfully complete.</li>
<!-- 2281 -->
<li>Running analyze.exe –f on a database after archiving and restoring can result
in project data file corruption</li>
<!-- 2306 -->
<li>Q248760: Sharing a file, then deleting it, and branching the file to the same project
causes analyze to report the &quot;Project log '&lt;physical filename&gt;' has a
share (from another project) record for item '&lt;filename&gt;', but that item
wasn't found in the current project.&quot; Running analyze –f does not fix the
error/warning message.</li>
<!-- 2353 -->
<li>Regular Users cannot open the VSS database on a W2k machine.</LI>
<!-- 2378 -->
<li>OLE Automation: Memory leak in VSSItem::Get.</li>
<!-- SP3 Fixes -->
<!-- 2160 -->
<li>Q196599: VSS 6.0 hangs when issuing a Get on a Label from the History dialog box.</li>
<!-- 2083 -->
<li>Q197050: &quot;Get&quot; by Label of subproject of labeled $/ by a VSS 6.0 client
on a VSS 5.0 format database results in &quot;Version not found,&quot; and nothing is
retrieved.</li>
<!-- 2189 -->
<li>VSS 6.0 Analyze utility crashes with access violation.</li>
<!-- 2190 -->
<li>VSS 6.0 Show Difference window is giving errors. In the VSS 6.0 Show Difference
window, several operational bugs were reported that resulted in erroneous information
being displayed and valid operations not being performed. Many of these reported
display problems with the Show Difference window have been fixed in this release.</li>
<!-- 2206 -->
<li>Q196599: Doing a recursive Get from the command line on a root ($/) project label
fails with &quot;Unable to finish writing file.&quot;</li>
</ul>
<br>
<!------------------------------------------------------>
<!-- TOPIC 2.4 -->
<!-- -->
<h4><a name="Topic_24"></a>Unicode Files</h4>
<!-- 66455 -->
<p>Visual SourceSafe cannot handle Unicode files. When a file is first added to SourceSafe, SourceSafe auto-detects whether the file is in text or binary format. If Unicode files are added as text format files, SourceSafe can corrupt them.</p>
<p>To work around this issue, add all Unicode files to SourceSafe as binary format files. You can override the file type auto-detect feature by clicking the Advanced button on the File Add dialog when you are adding a file. If the Unicode file has already been added, you can access the properties of the file in SourceSafe and change the file type to Binary.</p>
<!------------------------------------------------------------------->
<!-- SECTION 3.0 -->
<!-- -->
<h3>Getting Started</h3>
<br>
<!------------------------------------------------------>
<!-- TOPIC 3.0 -->
<!-- -->
<h4><a name="Topic_30"></a>Before You Run Setup</h4>
<p>
<UL>
<LI>Review the Hardware and Software Requirements. </LI>
</ul>
</p>
<br>
<!------------------------------------------------------------------->
<!-- SECTION 4.0 -->
<!-- -->
<h3>Installation</h3>
<!------------------------------------------------------>
<!-- TOPIC 4.0 -->
<!-- -->
<h4><a name="Topic_40"></a>Visual SourceSafe 6.0a Setup</h4>
<p>
<ul>
<li>Visual SourceSafe 6.0 requires Internet Explorer version 4.01 SP1 or later
to enable the Help system. The Setup program for VSS 6.0a does not include a
distribution of Internet Explorer, so you must install it before you install
VSS 6.0a. You can find the latest version of Internet Explorer at
<a href="http://www.microsoft.com/windows/ie/">http://www.microsoft.com/windows/ie/</a>.
The VSS 6.0a Setup program checks for the minimum required version of Internet
Explorer and displays a message if it does not detect it. You can continue the
installation, but it is strongly recommended that you quit the VSS 6.0a Setup
program and install Internet Explorer version 4.01 SP1 or later before resuming Setup.</li>
<li>If you already have VSS 6.0 installed on your system, the VSS 6.0a Setup
program upgrades your current installation to version 6.0a. Answer Yes when you
are asked to upgrade and select the same installation you currently have on your system.</li>
<li>VSS 6.0a is a minor release to the VSS 6.0 product and cannot run side by
side with another installation of VSS 6.0. Either upgrade your existing VSS
6.0 installation to 6.0a or do not install VSS 6.0a on the same system.</li>
<li>If you upgrade your existing server share installation to VSS 6.0a, your
clients can upgrade to VSS 6.0a by re-running the Netsetup program and choosing
to upgrade their existing installation.</li>
</ul>
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.1 -->
<!-- -->
<h4><a name="Topic_41"></a>Installing VSS 6.0a Over VSS 6.0 SP4 or Earlier</h4>
<p>
When you run the VSS 6.0a
Setup program on a computer that has VSS 6.0 with SP1, SP2, SP3, or SP4 installed,
the Setup program displays the following warning message:
</p>
<blockquote>
The Installation Wizard has detected a potentially
conflicting version of a Visual Studio 6.0 product on your machine. One or both
of these products may not work after installing this product. The Readme topic
&quot;Side by Side Product Installations&quot; describes the supported
combinations.
</blockquote>
<br>
<blockquote>
Do you wish to continue?
</blockquote>
<br>
<p>
This warning is valid
because installing VSS 6.0a side by side with VSS 6.0 is not supported. Answer
Yes to this message and to a subsequent message asking you if you are certain
you want to continue.
</p>
<p>
When Setup continues, it
states that you have an older version of the product already installed and asks
whether you would like to upgrade it. Click Next to accept the selected folder
location. When prompted for the specific installation type, select the type
already installed on your system.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.2 -->
<!-- -->
<h4><a name="Topic_42"></a>Installation Options</h4>
<h5>General Notes</h5>
<p>
The source code control database maintained by VSS must be on a drive that is
accessible to all users working on projects controlled by VSS. The most
versatile method of working with VSS is to perform a server installation to a
network drive, and a netsetup installation on each workstation.
</P>
<br>
<h5>Upgrading an Older Version of SourceSafe to Version 6</h5>
<p>
You will be prompted to replace an existing installation if found. This is
recommended, but you can choose an alternate path and then maintain two
different databases, one in the old format and one in the new format, on the same computer.
</p>
<br>
<p>
<b>Note</b>&nbsp;&nbsp;&nbsp;Make sure you back up the database before you upgrade.
</p>
<br>
<p>
You will be prompted to convert your database to the new format for faster performance.
You should do this only if:
</p>
<br>
<ul>
<li>You are the administrator for your database.</li>
<li>No people are logged onto the database.</li>
<li>All users of the database can be upgraded to client software compatible with the version 6 format.</li>
</ul>
<br>
<h5>VSS Database Administrators Note About Netsetup</h5>
<p>
Be aware that a full VSS license is required for each user of Visual SourceSafe.
For example, if you have 100 people using your VSS database, you must purchase
100 Visual SourceSafe licenses to avoid violating copyright law.
</p>
<br>
<p>
The version 6.0a Netsetup program requires a CD-Key before it can install the
Visual SourceSafe client software to a client computer. To make sure your
clients can run Netsetup successfully, give a CD-Key from one of your licensed
boxes to each user you recommend Netsetup to. It is acceptable to reuse the same
CD-Key for everyone running Netsetup, but you are still required to have an
individual license on hand for every user.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.3 -->
<!-- -->
<h4><a name="Topic_43"></a>Installing Visual SourceSafe Standalone Version</h4>
<br>
<h5>To install Visual SourceSafe standalone version as the Administrator (Admin)</h5>
<ol>
<li>Install Visual SourceSafe on the shared server.</li>
<li>Use the Admin tool to create user accounts in the shared database.</li>
<li>Set up security as appropriate for the users of the database.</li>
<li>Tell your users where to find Netsetup (if those users are licensed).</li>
</ol>
<br>
<h5>To install Visual SourceSafe standalone version as a Client</h5>
<ul>
<li>Run Netsetup from the server location for client-only installation.</li>
</ul>
<br>
<blockquote>
<b>Note</b>&nbsp;&nbsp;&nbsp;A full Visual SourceSafe license is required to use Netsetup by each client.
</blockquote>
<br>
<p>
- or -
</p>
<br>
<ul>
<li>Install the standalone Visual SourceSafe from the compact disc (by choosing Standalone).
This creates a local database. To use a shared database, click Open SourceSafe Database on the File menu from
the Visual SourceSafe Explorer.</li>
</ul>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.4 -->
<!-- -->
<h4><a name="Topic_44"></a>Installing Multiple Versions of Visual Studio 6.0 Products "Side-by-Side" on the Same Computer</h4>
<p>
Visual Studio products with the same version and in the same language&mdash;Visual
C++ and Visual Basic version 6.0 in English, for example&mdash;can be
installed separately on the same workstation. Such installations are supported by
Microsoft. The Visual Studio 6.0 Installation Wizard detects if other versions
of the 6.0 product line have been installed on a workstation.
</p>
<br>
<p>
Mixing different language
versions, point releases, or product tiers on the same workstation are
generally not supported. This means that the installation can fail, one or more
of Visual Studio 6.0 products may not work even if the installation succeeds,
or in the worst case you may not be able to remove any of the products
completely.
</p>
<br>
<p>
If the wizard generates a
warning during installation, the safest course of action is to uninstall the Visual
Studio 6.0 product before proceeding. The detection scheme checks for the
following scenarios:
</p>
<br>
<ul>
<li>Users <b>installing different language versions</b> of the same product.
For example, Japanese Visual Basic and English Visual Basic.
Installation of certain combinations is supported.</li>
</ul>
<br>
<table border=1 cellpadding=0 cols=2 frame=below rules=rows>
<tr>
<td>
<font size=2>
<p><b>Product</b></p>
</font>
</td>
<td>
<font size=2>
<p><b>Supported Installation</b></p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual Basic</p>
</font>
</td>
<td>
<font size=2>
<p>Install in two different locations</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual C++</p>
</font>
</td>
<td>
<font size=2>
<p>No side-by-side installation is supported.</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual FoxPro</p>
</font>
</td>
<td>
<font size=2>
<p>Install in two different locations</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual InterDev</p>
</font>
</td>
<td>
<font size=2>
<p>Install in the same location. You must reinstall after removing one version.</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual J++</p>
</font>
</td>
<td>
<font size=2>
<p>Install in the same location. You must reinstall after removing one version.</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>Visual SourceSafe</p>
</font>
</td>
<td>
<font size=2>
<p>Install in the same location. You must reinstall after removing one version.</p>
<p><b>Note</b>&nbsp;&nbsp;&nbsp;The UI
language chosen when you run Visual SourceSafe is based on the system's
language settings. If that language is not installed for Visual SourceSafe,
it uses English instead.</p>
</font>
</td>
</tr>
<tr>
<td>
<font size=2>
<p>MSDN</p>
</font>
</td>
<td>
<font size=2>
<p>Install in default directory.</p>
</font>
</td>
</tr>
</table>
<ul>
<li>Users <b>installing different tiers of
Visual Studio 6.0 products</b>. For example, Visual J++ Standard Edition and
Visual InterDev Professional Edition. Installing different tiers of the same
product on the same workstation is not supported.</li>
<li>Users <b>installing point releases</b>.
Upgrading a later point release of Visual Studio over an earlier point release
is supported. However, installing earlier versions over later versions is not
supported.</li>
<li>Users <b>installing stand-alone versions of
Visual Studio 6.0 products over the versions installed from Visual Studio 6.0
Professional or Enterprise</b>. For example, Visual FoxPro 6.0 over Visual
Studio Professional 6.0. Installing a stand-alone version of the same language
versions (English) of Visual Studio 6.0 products is supported. It is safe to
install Visual FoxPro 6.0 (English) from the stand-alone version on a
workstation that already has Visual Basic 6.0 installed from Visual Studio
Professional Edition.</li>
</ul>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.5 -->
<!-- -->
<h4><a name="Topic_45"></a>(Individual Users) Using NetSetup to Create a Personal Installation</h4>
<P>
After an administrator has created a VSS installation on the server, users can run NetSetup to copy the VSS executables to their hard disk.
</P>
<br>
<p><b>To install using NetSetup:</b></p>
<OL>
<LI>In Windows Explorer, navigate to the main folder containing the VSS Server installation.</LI>
<LI>Double-click <b>netsetup.exe</b>.</LI>
<LI>Follow the instructions in the Installation Wizard, using <b>[Change Folder]</b> to change
the default installation path</LI>.
</ol>
<br>
<blockquote>
<b>Warning to Administrators</b>&nbsp;&nbsp;&nbsp;All users, including
anyone running Netsetup, must possess an individual VSS license to install
and/or use the product. Netsetup is provided as a convenience, but the
administrator should make sure to obtain individual licenses for each person
that installs and uses the product.
</blockquote>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.6 -->
<!-- -->
<h4><a name="Topic_46"></a>Upgrading a Database After Installing</h4>
<p>
If you were prompted to
upgrade your database to the new 6.<i>x</i> format and you indicated Yes, you
now have a 6.<i>x</i> database and can take advantage of label promotion and
enjoy performance enhancements. If you weren't prompted or you indicated No to
the prompt and you now want to upgrade your database, run the DDUPD.exe
command-line utility, which exists in the \win32 directory of your VSS 6.<i>x</i>
server installation. (You can either go to that directory and run it or add
that directory to your path and run it.) We recommend you run DDUPD only when
everyone has quit VSS. The syntax is:</p>
<br>
<blockquote>
DDUPD &lt;path to data folder&gt; [-undo] [-redo]
</blockquote>
<br>
<p>
To upgrade a 5.0 database, for example, you would run:
</p>
<br>
<blockquote>
DDUPD \\server\share\vss\data
</blockquote>
<br>
<p>
To undo an upgrade,
return to the version 5.0 format and stop taking advantage of the performance
enhancements and label promotions:
</p>
<br>
<blockquote>
DDUPD \\server\share\vss\data -UNDO
</blockquote>
<br>
<p>
To redo the upgrade
process on a database that is already in the new format, run:
</p>
<br>
<blockquote>
DDUPD \\server\share\vss\data -REDO
</blockquote>
<br>
<!------------------------------------------------------>
<!-- TOPIC 4.7 -->
<!-- -->
<h4><a name="Topic_47"></a>Deleting VSS</h4>
<P>
If you delete a VSS
installation (including the database) and then attempt to run Setup, Setup may
try to install VSS in the Recycle bin (if the old database is found here). This
happens only if the Recycle bin hasn't recently been emptied. To remedy the
problem:</P>
<OL>
<LI>Empty the Recycle bin.</LI>
<LI>Run Setup again, and verify that the default directory for VSS is no longer the Recycle bin.</LI>
</OL>
<br>
<!------------------------------------------------------------------->
<!-- SECTION 5.0 -->
<!-- -->
<h3>General Notes and Tips</h3>
<!------------------------------------------------------>
<!-- TOPIC 5.0 -->
<!-- -->
<h4><a name="Topic_50"></a>New Features in VSS 6.0</h4>
<P>Microsoft VSS 6.0 adds many new features. Some of the highlights include:</P>
<UL>
<li><b>Create database</b> – Available in the Visual SourceSafe Admin application.
With it, you can create a new VSS database in any location. To use this
command, on the Tools menu, click Create Database.
<LI> <b>Archive and Restore </b> - Now available in the Visual SourceSafe Admin
application in addition to the command line. </LI>
<LI><b>Label promotion</b> - You can promote, or add, a file to an existing label. </LI>
<LI><b>Move files</b> - When you move a file, VSS automatically shares the file
to a new project and then deletes it from the original project. In the new
project, the file appears as shared. </LI>
<LI><b>Compare differences in multiple projects</b> - You can compare differences in a project against
another project, compare in two different local folders, or compare a project
against any directory, not just its working directory.</LI>
<LI><b>Deploy individual files from the GUI</b> - In VSS 6.0, using the VSS
Explorer, you can now deploy a file as well as an individual folder. </LI>
<LI><b>Filter history information</b> - You can now view history of files and projects
without including labels. </LI>
<LI><b>Clean temp directory option</b> - A quick, easy way to delete all files from the
temp directory used by VSS, provided the files are not open. </LI>
<LI><b>Check External Hyperlinks</b> - In VSS 6.0, Check Hyperlinks now works on
external hyperlinks, or jumps outside the project, as well as internal
hyperlinks, or jumps within the project. </LI>
<LI><b>Create desktop shortcuts to VSS databases (from VSS Explorer)</b> - You
can create a shortcut on your desktop that opens a specified VSS database in
the specified project. </LI>
<LI><b>HTML Help</b> - This version uses HTML Help rather than WinHelp.</LI>
</UL>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.1 -->
<!-- -->
<h4><a name="Topic_51"></a>Maintaining Your VSS Database</h4>
<p>
It is still advisable to
back up the drive where your VSS database resides regularly. It is important to
use full backups, not incremental or differential backups, to avoid problems.
</p>
<br>
<p>
In addition, you should
run the ANALYZE program periodically to maintain database integrity. If a
corruption is found, the ANALYZE program can usually repair the problem.
Updates to the ANALYZE tool are posted periodically on the VSS Web site, <a
href="http://msdn.microsoft.com/ssafe/">http://www.msdn.microsoft.com/ssafe</a>.
You can check that site to see if there is a version of ANALYZE more recent
than the one shipped with this product.</p>
<br>
<p><b>To run ANALYZE:</b></p>
<OL>
<LI>Click the Start menu.
<LI>Point to Programs.
<LI>Click Microsoft Visual SourceSafe (if you installed VSS with Microsoft Visual Studio,
click Microsoft Visual Studio, then click Visual SourceSafe).
<LI>Click either Analyze VSS DB or Analyze & Fix VSS DB.
</OL>
<br>
<blockquote>
<b>Note</b>&nbsp;&nbsp;&nbsp;It is always advisable to run ANALYZE and back up
older databases before upgrading them to the 6.<i>x</i> format.
</blockquote>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.2 -->
<!-- -->
<h4><a name="Topic_52"></a>Loss of Network Connection Produces Numerical Error Message</h4>
<p>
If you are using VSS on a remote database and you lose your connection to the server, the following error
will occur:
</p>
<blockquote>
&quot;unknown error - 20038,&quot; (or similar)
</blockquote>
<br>
<p>
If you see this error,
you have lost your network connection.</p>
<p>
<b>To correct the situation</b>
</p>
<ol>
<li>Restore your network connection.</li>
<li>Restart VSS to continue your work.</li>
</ol>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.3 -->
<!-- -->
<h4><a name="Topic_53"></a>System Date/Time</h4>
<p>
VSS uses the date and
time that your local computer stores. If your computer is not synchronized with
other computers, unpredictable results can occur. For instance, you check in a
file after someone else, but VSS thinks your checkin happened first because
your system clock was off!
</p>
<p>
The best solution for
this problem is to synchronize your local date and time with the network on a
regular basis. With Windows NT this can be done with a Domain Time Source
Server. Check the <a href="http://www.novell.com/">http://www.novell.com/</a>
site for information on time synchronization with Novell NetWare servers.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.4 -->
<!-- -->
<h4><a name="Topic_54"></a>Using the Command Line after Running a Client Setup</h4>
<p>
If you are working from
the command line and receive a message stating &quot;No VSS database
(SRCSAFE.INI) found. Use the SSDIR environment variable or run netsetup.&quot;,
set the SSDIR variable. This tells VSS where to find the Srcsafe.ini file for
the VSS server installation to which you want to connect. You can do this by
typing the following at the Command prompt:
</p>
<br>
<blockquote>
set ssdir=\\server\share\vss
</blockquote>
<br>
<p>
Where \\server\share\vss
is the folder where the Srcsafe.ini file is located.
</p>
<br>
<p>
<b>Note</b>&nbsp;&nbsp;&nbsp;There should not
be a space between the equal sign and the location of the VSS server
installation. For example, the following will not work:
</p>
<br>
<blockquote>
set ssdir= \\server\share\vss.
</blockquote>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.5 -->
<!-- -->
<h4><a name="Topic_55"></a>Details on Defining a Shadow Folder in Visual SourceSafe</h4>
<p>
A shadow folder is a live
mirror (on the file system) of the projects in the Visual SourceSafe (VSS)
database.
</p>
<p>For a shared database,
you must set up the shadow folder with a Universal Naming Convention (UNC)
path, such as \\Server\Share\Shadow, to avoid failure when changes are made
from a computer other than the one used to set up the shadow. Make sure the UNC
contains no long names, just eight-character short names for the
\\Server\Share\Root portion.
</p>
<p>For example, instead of
defining the shadow folder as D:\VSSShadow, you can define the shadow
folder as: \\server\D\Shadow.
</p>
<p>Confirm that all the
Visual SourceSafe users have read/write access to the UNC directory.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.6 -->
<!-- -->
<h4><a name="Topic_56"></a>Running Netsetup from a Windows NT Server Computer Using Windows 95</h4>
<p>
Due to a problem Windows
95 has accessing some programs on Windows NT Server computers through a UNC
that contains long names, you should create a network share on the Windows NT
Server computer that points directly to the VSS location on the server's disk
drive, and avoid long names for the server and share names as well.
</p>
<p>
For instance, if VSS is
installed to:
</p>
<br>
<blockquote>
D:\Program Files\Microsoft Visual Studio\Common\VSS
</blockquote>
<br>
<p>
You can provide users
access to it by setting:
</p>
<br>
<blockquote>
D:\
<br>
<i>shared as</i>
<br>
\\Long Server Name\Long Share Name
</blockquote>
<br>
<p>
And they would then
access it with:
</p>
<br>
<blockquote>
\\Long Server Name\Long Share Name\Program Files\Microsoft
Visual Studio\Common\Vss\Netsetup.exe
</blockquote>
<br>
<p>
The long names cause
computers running Windows 95 to fail when the server is a computer running
Windows NT.
</p>
<br>
<p>
Instead, set it up with:
</p>
<br>
<blockquote>
D:\Program Files\Microsoft Visual Studio\Common\VSS
<br>
<i>shared as</i>
<br>
\\Server\VSSShare
</blockquote>
<br>
<p>
In this way, users can
access Netsetup.exe with the following short UNC:
</p>
<br>
<blockquote>
\\Server\VSSShare\Netsetup.exe
</blockquote>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.7 -->
<!-- -->
<h4><a name="Topic_57"></a>VSS Home Page</h4>
<P>
Microsoft VSS has a home
page on the Internet. This home page features a variety of information
including articles on VSS, a self-running demo that you can download, a
collection of helpful VSS utilities, and much more. The URL for the home page
is: <a href="http://www.msdn.microsoft.com/ssafe/">http://www.msdn.microsoft.com/ssafe.</a>
</P>
<br>
<P>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.8 -->
<!-- -->
<h4><a name="Topic_58"></a>Microsoft Knowledge Base</h4>
<p>
If you encounter problems
or have questions not addressed here or in the online documentation, you can
search the Microsoft Knowledge Base at <a
href="http://support.microsoft.com/support/">http://support.microsoft.com/support</a>.
The Knowledge Base is also available on the <i>MSDN Library Visual Studio 6.0</i>,
included on the CD-ROM with Visual SourceSafe.
</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 5.9 -->
<!-- -->
<h4><a name="Topic_59"></a>VSS Newsgroup</h4>
<p>
You can exchange
information with other VSS users by visiting the
microsoft.public.visual.sourcesafe newsgroup on the Internet. This newsgroup is
on the msnews.microsoft.com server.
</p>
<p>
<b>Note</b>&nbsp;&nbsp;&nbsp;Microsoft does not provide support for messages
posted to the newsgroup.
</p>
<br>
<!------------------------------------------------------------------->
<!-- SECTION 6.0 -->
<!-- -->
<h3>Best Practices</h3>
<p>The most up-to-date SourceSafe Best Practices Guide can be found at: <a href=http://msdn.microsoft.com/library/default.asp?URL=/library/techart/vssbest.htm>http://msdn.microsoft.com/library/default.asp?URL=/library/techart/vssbest.htm</a>.
This guide is in English only.</p>
<!------------------------------------------------------>
<!-- TOPIC 6.0 -->
<!-- -->
<h4><a name="Topic_60"></a>Introduction</h4>
<p>Under normal operation in a stable environment, Visual SourceSafe
provides excellent storage and security for your current source data and past
revisions. However, as with any database product, data corruption can occur.
This section outlines recommended practices to help avoid corruption problems.
Although all the practices can help minimize the impact of corruption, one of
the most valuable is using a data repair utility called Analyze. The Analyze
tool ships with Visual SourceSafe. It checks for and repairs many common data
write errors. Run Analyze on your Visual SourceSafe database with your regular
tape backup schedule to ensure the stability and security of your source data.</p>
<p><b>Important</b>&nbsp;&nbsp;&nbsp;When using Visual SourceSafe, make sure
that you are running the latest version of the applications.
Microsoft periodically releases service packs for our applications that correct known
issues.
We recommend that you install the service packs as soon as possible.</p>
<p>Customers who want to upgrade their Visual SourceSafe client to the latest Visual Studio Service Pack releases should use the Service Pack installations instead of running netsetup.exe again.</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 6.1 -->
<!-- -->
<h4><a name="Topic_61"></a>General Database Recommendations</h4>
<h5>Database Size</h5>
<p>Under normal use, your Visual SourceSafe database should not
exceed 3 to 5 GB.
To determine an appropriate size, consider the amount of free
space on the server, the relationship among the projects being stored, the
amount of file history you need to access quickly, and user tolerance for
reduced performance.
Although Visual SourceSafe does not have a size
limitation, on very large databases it takes longer to perform normal
operations and maintenance tasks, such as running Analyze.
Visual SourceSafe
does not limit the number of databases you can put on a server.</p>
<p>To reduce potential file size, keep projects that are not
interrelated in separate databases.
You can use the Archive and Restore utilities
included in Visual SourceSafe version 5.0 and later to move projects to another
database or to remove outdated history from a project.</p>
<h5>Location</h5>
<p>Although you can store Visual SourceSafe databases on any
Microsoft Windows®-compatible file server (Windows NT, Novell, Banyan, and so
on), database performance is best on Windows NT.
Network operations are generally faster.
In addition, in the server-based Windows environment you can
run Analyze and other highly intensive file I/O operations directly on the
server, often dramatically decreasing execution time.</p>
<h5>Analyze Frequency</h5>
<p>Use the Analyze tool shipped with Visual SourceSafe to detect and
repair problems in the database structure. When you run Analyze regularly,
especially in high-use situations, you can discover small problems and fix them
before they become worse. Run Analyze weekly or, at minimum, monthly as part of
regular maintenance.</p>
<p>While running Analyze directly on your production database, you
must lock out users. To minimize the impact, restore your regular backup to
another location and run Analyze on that copy. Another way that you can create
a duplicate on-line copy of your VSS database is to use the ROBOCOPY utility
from the Windows NT Resource Kit. This
utility copies all the files in a folder and subfolders; however, if a file is
in use, it will retry the copy instead of just failing.
You can use this method to create a backup
of your database on another server as well. If you detect problems in the backup that need to be resolved, you can
then lock out users from the production database while making any necessary
fixes. If Analyze returns no errors, you do not need to interrupt user
connections. This method also checks the validity of the backup strategy.</p>
<p>Each time you run the Analyze utility, create a list of all items
in the database. This list is useful in determining which logical file name is
related to an error based on the file name (for example, Abcaaaaa.a) for which
the error is reported.</p>
<p><b>To create the physical list</b></p>
<ul>
<li>At the command prompt, type:</li>
<blockquote>
SS PHYSICAL $/ -R–O@PHYSICAL.TXT
</blockquote>
</ul>
<p>For more detailed information on Analyze, see <a href="ReadmeSS.htm#Topic_63">Finding and
Repairing Data Corruption</a> later in this document.</p>
<h5>Free Disk Space</h5>
<p><b>Caution</b>&nbsp;&nbsp;&nbsp;Do
not allow Visual SourceSafe or the Analyze tool to run out of disk space while
running. Running out of disk space in the middle of a complex operation can
create serious database corruption.</p>
<p>Visual SourceSafe does check for disk space. However, due to
performance concerns, it does not check for space on every disk write
operation. To avoid possible database corruption, make sure there is enough
free space on the server so that a complete copy of the database can be created
during normal Analyze operations.</p>
<h5>Sharing and Branching</h5>
<p>Use the Sharing and Branching features of Visual SourceSafe with
discretion. Avoid Sharing or Branching across top-level projects because it
complicates the process of archiving a project and restoring it into another
database. Moreover, when you branch files and then delete them, the space is
not recovered until all copies of the branched file in the database are
destroyed.</p>
<h5>Number of Users</h5>
<p>The acceptable number of users varies depending on the
performance of the server and the network. When you control the size of the
database, performance improves, and more users can access the database with
reasonable performance. The number of full-access users you have determines the
number of licenses that you need for Visual SourceSafe.</p>
<h5>Server Rights</h5>
<p>All users must have create, modify, change/edit, and delete
permissions for files in the Data folder and its subfolders in the directory
tree. These permissions must also be
applied to the share permissions. If a user
receives the message “Unable to create user login file,” that user does not have the proper
permissions to the VSS database location.</p>
<p>Each database has its own User and Rights management systems. You
cannot interrelate these files.</p>
<h5>Ss.ini and SSAdmin.ini Files</h5>
<p>Users' Ss.ini files are limited to 64 KB and a maximum of 10
different computer-specific settings. Each time a user logs on from a different
computer, the Ss.ini saves the window positions and other computer-specific
information. If you are experiencing unusual user-specific problems, try
deleting unnecessary entries in the user's Ss.ini file.</p>
<h5>Working Folders</h5>
<p>To maintain file integrity, make sure that all users have their
own working folders for all projects. When multiple users share a working
folder, a file checked out by one user can be modified by anyone with access to
that folder. Maintaining separate working folders ensures that users modify
only files they have checked out themselves.</p>
<h5>System Clocks</h5>
<p>Synchronize the dates and system clocks for all Visual SourceSafe
client computers with the Visual SourceSafe server. This prevents check-in and
check-out operations from appearing to happen out of sequence and affects any
labels that are applied. Synchronizing dates and system clocks is particularly
important when users from different time zones access the same database.</p>
<p>You can set up a computer running Windows NT Server to act as a
Domain Time Source server for users to synchronize their local date and time
with the network. For additional information, see the Knowledge Base article
&quot;How to Set Up and Synchronize with Domain Time Source Servers (search on
article ID Q131715).</p>
<h5>New Databases</h5>
<p>Avoid creating a new database by copying an existing one. Doing
so can potentially cause problems because the globally unique identifier (GUID)
in the Um.dat will be the same for both databases. For details on how to create
a new database, see Knowledge Base article Q123467, &quot;How to Create a New
Database in SourceSafe.&quot;</p>
<h5>Moving Databases or Visual SourceSafe Installations</h5>
<p>To move a Visual SourceSafe installation, copy the entire VSS
folder and all of its subfolders to the new location. However, do not use XCOPY
to do this because it does not copy some zero-byte files. Instead, use Windows
Explorer to copy the folder(s). After you have copied the installation, Visual
SourceSafe clients must change the <b>#include</b> statement
in their local Srcsafe.ini file to reflect the new location. No other
modifications are necessary. To move just the database itself, perform the same
operation on the Data folder and then modify the DATA_PATH line of the server Srcsafe.ini
instead of the client Srcsafe.ini. When specifying the DATA_PATH, use the UNC
method (\\SERVER\SHARE). For details, see Knowledge Base article Q176909,
&quot;HOWTO: Move a VSS Database or Project to New Location.&quot;</p>
<p><b>Tip</b>&nbsp;&nbsp;&nbsp;After
you have moved the VSS location, you can create a Srcsafe.ini file in the old
location with a <b>#include</b> statement pointing to the new
SrcSafe.ini location. This provides time for users to change their links.</p>
<h5>Integrated Environments</h5>
<p>When using Visual SourceSafe through the integration in the
development environments (Microsoft Visual Basic®, Microsoft Visual C++®,
Microsoft Access, Microsoft FrontPage®, and so on) use the integrated component
to perform Visual SourceSafe operations that can be done within that
environment. For example, do not check out and check in files from both the
Visual SourceSafe Explorer and integrated environments. This is very important because Visual
SourceSafe does not understand the links between the source files the way the
integrated development environment does. For instance, in Visual Basic a form can be made up of a FRM and a FRX
file. Visual Basic knows to check out
both files at the same time, but SourceSafe does not. Checking only one file out in the Visual SourceSafe Explorer
causes the files to get out of sync in Visual Basic and hence corrupted.</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 6.2 -->
<!-- -->
<h4><a name="Topic_62"></a>How Visual SourceSafe Tracks Files</h4>
<p>Visual SourceSafe is a file-based version control system that is
designed for use on multiple, industry-standard network servers. No special
program needs to be run on the server during normal use. The core of a Visual
SourceSafe database is the Data directory; it has a unique structure that is
designed for maximum flexibility. A Visual SourceSafe database consists of the
following files and folders.</p>
<table border=1 cellspacing=0 cellpadding=0 style='margin-left:4.0pt;
border-collapse:collapse;border:none;mso-border-alt:solid silver .5pt;
mso-padding-alt:0pt 4.0pt 0pt 4.0pt'>
<tr>
<td valign=top style='border:solid silver .5pt;background:#E2E2E2;mso-shading:
windowtext;mso-pattern:gray-50 silver;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>File/folder</b></p>
</td>
<td valign=top style='border:solid silver .5pt;border-left:none;mso-border-left-alt:
solid silver .5pt;background:#E2E2E2;mso-shading:windowtext;mso-pattern:gray-50 silver;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>Description<b></p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>SrcSafe.ini</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Visual SourceSafe database global settings and configuration
information for all users.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Users.txt</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>List of all users of the Visual SourceSafe database.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Aaaaaaaa.cnt</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Physical name of last file added to the database.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Crcs.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>CRC information used to speed up the get and check-out
processes (Visual SourceSafe 6.0 format databases only).</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Names.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Long file name information.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Rights.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>User and project security information.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Status.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Visual SourceSafe Explorer cache file (used to speed up the
display of the Visual SourceSafe Explorer).</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Um.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>User management information (names and passwords) and the
database identifier (GUID).</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Version.dat</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Visual SourceSafe database version.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\A…Z (folders)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Folders containing log files and data files.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Backup (folder)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Contains analyze log file (analyze.log), list of bad files
(analyze.bad), and backups of files changed by Analyze.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Labels (folder)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Label cache information used for label promotion (Visual
SourceSafe 6.0 format databases only).</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Locks (folder)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Used if Visual SourceSafe locking is enabled.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Data\Loggedin (folder)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Contains user logon files and an Admin.lck file if the database
is locked.</p>
</td>
</tr>
<tr>
<td valign=top style='border:solid silver .5pt;border-top:none;mso-border-top-alt:
solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Users (folder)</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p class=Text>Contains Template.ini, which stores default values for the
Ss.ini file for new users. The Users folder also contains a subfolder for
each user. This subfolder contains an Ss.ini file defining user-specific
settings. The Admin folder also contains Ssadmin.ini, which defines
administrator settings.</p>
</td>
</tr>
</table>
<p>Visual SourceSafe creates two files in the Data directory for every
file and project that you add to Visual SourceSafe (with one exception
described later in this section). These file pairs are distributed evenly
across the A through Z subdirectories in the Data directory. The file without
an extension (such as QRBAAAAA) is the log file for the file type being stored.
The log file contains internal information for Visual SourceSafe, such as who
added the file, where it exists, and all the differences between the versions
of the file. The file with an .a or .b extension (such as QRBAAAAA.A) is the
most recent version of the actual file, stored under a Visual SourceSafe
physical name. Each time a file is checked in, the extension it is saved with
alternates between .a and .b.</p>
<p>When a user checks in a file, it is copied from their working
directory to the Data directory and renamed with the physical name and either
an .a or .b extension, whichever is not currently there. Visual SourceSafe then
calculates the differences between the .a and .b files and stores it in the log
file (the file without an extension). After the log file is updated, the old
copy of the data file is deleted. Under normal circumstances you should never
have both .a and .b extensions for one physical file name.</p>
<p><b>Caution</b>&nbsp;&nbsp;&nbsp;Never
rename an .a or .b file in the DATA folder. Although doing so appears to correct the immediate problem that you are
experiencing (such as: The file QRBAAAAA.A not found.), it will make the previous
versions of the file unrecoverable. If
you receive this error, restore the file pair from a recent backup.</p>
<p>When you share a file from another project, no new file pair is
created in the Visual SourceSafe database. Instead, Visual SourceSafe creates a
reference in the original file's log, noting that the file also exists in
another project.</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 6.3 -->
<!-- -->
<h4><a name="Topic_63"></a>Finding and Repairing Data Corruption</h4>
<p>Use the Analyze tool, located in the Microsoft Win32<sup>&reg</sup> directory,
to check for and correct corruption problems. You should run it as frequently
as is practical—once a week is recommended, or at a minimum, once a month.
Analyze checks all the files in the Visual SourceSafe Data directory for
corruption or disconnected links and often repairs these with proper switch
settings. Because Analyze is so thorough, it can be slow to run. The amount of time that Analyze takes to run
depends on the contents and structure of the database, such as the amount of
sharing and branching and the total number of files.</p>
<p>For best performance, all users should log off Visual SourceSafe
before you run Analyze.exe. If you use the -F switch to repair problems, users
must log off. However, if you want to run Analyze.exe without requiring users
to log off, you can use the -X switch.</p>
<p><b>Note</b>&nbsp;&nbsp;&nbsp;Due
to the amount of file I/O required, you can dramatically improve performance by
running Analyze locally (that is, on the server) rather than across the
network.</p>
<p>Analyze has several switches you can use to tell it what to do
when running. Do not try to use every switch at once. The more Analyze is
required to do, the longer it takes to run. </p>
<p>When you run Analyze, it executes in the following four passes.</p>
<ol>
<li>Analyze checks every file in the Data directory to make sure
that it is valid and is not corrupt.</li>
<li>Analyze checks the relationships between parents (projects)
and children (files and projects).</li>
<li>Analyze checks the relationships between shared and branched
files.</li>
<li>Analyze checks the files Um.dat, Rights.dat, and Names.dat and
performs cleanup operations.</li>
</ol>
<p>Analyze supports the following switches.</p>
<table border=1 cellspacing=0 cellpadding=0 width=604 style='width:453.25pt;
margin-left:4.0pt;border-collapse:collapse;border:none;mso-border-alt:solid silver .5pt;
mso-padding-alt:0pt 4.0pt 0pt 4.0pt'>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
background:#E2E2E2;mso-shading:windowtext;mso-pattern:gray-50 silver;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>Switch</b></p>
</td>
<td valign=top style='border:solid silver .5pt;border-left:none;mso-border-left-alt:
solid silver .5pt;background:#E2E2E2;mso-shading:windowtext;mso-pattern:gray-50 silver;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>Description</b></p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-B<i>&lt;folder&gt;</i></p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Specifies the folder to use for backup.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-C</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Compresses unused space. (This simply removes blank space and
does not compress the log files.) This pass can generate a large number of files in the backup folder
and should be used only when there is plenty of disk space available.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-D</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Deletes unused files.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-DB</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Deletes the Backup folder.</p>
<p><b>Caution</b>&nbsp;&nbsp;&nbsp;If
you find corruption, create backup copies of logs before running Analyze with
the -DB switch.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-F</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Automatically fixes corrupted files. (Requires users to log off
database.)</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-I-</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>When the analysis is complete, the program quits. (Useful if
running in a batch script.)</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-V1</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Displays only critical errors. (This is the default setting, if
no -V switch is used.)</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-V2</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Displays only significant errors.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-V3</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Displays all errors and inconsistencies.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-V4</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Displays errors, inconsistencies, and informational notes.</p>
</td>
</tr>
<tr>
<td width=72 valign=top style='width:54.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>-X</p>
</td>
<td valign=top style='border-top:none;border-left:none;border-bottom:solid silver .5pt;
border-right:solid silver .5pt;mso-border-top-alt:solid silver .5pt;
mso-border-left-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Does not attempt to lock the database when analyzing. (Recommended
only when users must remain logged on while Analyze.exe runs; -X cannot be
used with -F. If Analyze tries to
access a file that is in use while in this mode, it will quit and you will
need to re-run it at a later time.)</p>
</td>
</tr>
</table>
<p>Running Analyze in the following order provides good coverage.</p>
<table border=1 cellspacing=0 cellpadding=0 style='margin-left:4.0pt;
border-collapse:collapse;border:none;mso-border-alt:solid silver .5pt;
mso-padding-alt:0pt 4.0pt 0pt 4.0pt'>
<tr>
<td width=297 valign=top style='width:223.0pt;border:solid silver .5pt;
background:#E2E2E2;mso-shading:windowtext;mso-pattern:gray-50 silver;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>Command line</b></p>
</td>
<td width=297 valign=top style='width:223.0pt;border:solid silver .5pt;
border-left:none;mso-border-left-alt:solid silver .5pt;background:#E2E2E2;
mso-shading:windowtext;mso-pattern:gray-50 silver;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p><b>Description</b></p>
</td>
</tr>
<tr>
<td width=297 valign=top style='width:223.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Analyze –V4 <i>&lt;database path&gt;</i></p>
</td>
<td width=297 valign=top style='width:223.0pt;border-top:none;border-left:
none;border-bottom:solid silver .5pt;border-right:solid silver .5pt;
mso-border-top-alt:solid silver .5pt;mso-border-left-alt:solid silver .5pt;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>The first pass should always locate problems before trying to
fix them.</p>
</td>
</tr>
<tr>
<td width=297 valign=top style='width:223.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Analyze -F –V4 <i>&lt;database path&gt;</i></p>
</td>
<td width=297 valign=top style='width:223.0pt;border-top:none;border-left:
none;border-bottom:solid silver .5pt;border-right:solid silver .5pt;
mso-border-top-alt:solid silver .5pt;mso-border-left-alt:solid silver .5pt;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>If errors are reported in the first pass, run Analyze again in
fix mode to correct them.</p>
</td>
</tr>
<tr>
<td width=297 valign=top style='width:223.0pt;border:solid silver .5pt;
border-top:none;mso-border-top-alt:solid silver .5pt;padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Analyze -F -C –V4 <i>&lt;database path&gt;</i></p>
</td>
<td width=297 valign=top style='width:223.0pt;border-top:none;border-left:
none;border-bottom:solid silver .5pt;border-right:solid silver .5pt;
mso-border-top-alt:solid silver .5pt;mso-border-left-alt:solid silver .5pt;
padding:0pt 4.0pt 0pt 4.0pt'>
<font size=2>
<p>Run this pass when you have “Found a DIFF” and “Found a
COMMENT” errors that you want removed.</p>
<p><b>Caution</b>&nbsp;&nbsp;&nbsp;Since
the DIFF and COMMENT messages can occur in a large number of files, it is
extremely important that you have enough disk space available when running a
Compress pass on your database.</p>
</td>
</tr>
</table>
<p>Each time Analyze runs, it places an Analyze.log file in the Backup
folder along with a file called Analyze.bad. The Analyze.bad file contains a
list of all files in which Analyze found problems. When Analyze fixes a file,
it first creates a copy of the file in the Backup folder so that the repair can
be undone if necessary. Each time Analyze runs, it requires that the Backup
folder is either empty or does not exist. If there is sufficient disk space, it
is a good practice to rename the Backup folders instead of deleting them. This
history can prove very useful in troubleshooting corruption issues. The errors
and messages reported by Analyze are discussed at length in Knowledge Base
article Q152807, &quot;INFO: Error Messages from Analyze Tool of Visual
SourceSafe.&quot;</p>
<p>Analyze can also re-create the Status.dat, Names.dat, and
Rights.dat files. To do this, rename or delete the files you want rebuilt, and
run Analyze -F. Analyze re-creates the Names.dat file with the spaces in long
file names appearing as underscores. You then need to rename the file using
Visual SourceSafe Explorer. The Rights.dat file is re-created, but as an empty
structure; you need to add permissions for each user again.</p>
<p>Microsoft occasionally updates the Analyze tool to include more
checking or to improve performance. For the latest version of Analyze, visit
the Microsoft Visual SourceSafe Web site located at
<a href="http://msdn.microsoft.com/ssafe/default.asp">http://msdn.microsoft.com/ssafe/default.asp</a>.</p>
<br>
<!------------------------------------------------------>
<!-- TOPIC 6.4 -->
<!-- -->
<h4><a name="Topic_64"></a>Backup and Restore</h4>
<p>Backups should be performed regularly as part of the daily or
weekly file maintenance and security process. When backing up your Visual SourceSafe
database, make sure you are getting a full backup of the database. Although you
can use incremental backups, you should avoid them because some of the files
from the database may not be able to be restored. If users are logged on to
Visual SourceSafe and actively using the product, the files they have open will
not be backed up by most standard backup utilities. There are several backup
and copy utilities that can back up open files. However, if you use these
utilities and someone is actively updating a file in Visual SourceSafe when the
file is backed up, the backup may be corrupted.</p>
<p><b>Note</b>&nbsp;&nbsp;&nbsp;Do
not schedule Analyze to run at the same time as a backup of the database! If
the backup program has files open that Analyze is trying to open, Analyze will
shut down unexpectedly. </p>
<p>Visual SourceSafe automatically closes any files opened by Visual
SourceSafe or an integrated application after 15 minutes of inactivity. (This
requires Service Pack 3 of Visual SourceSafe 5.0 or later.) The user still
appears to be logged on to Visual SourceSafe and the files will be reopened
when they start working again. However, the Rights.dat and Status.dat files
remain open any time users are logged on and will not be backed up. You can
rebuild these if needed using the Analyze utility. Each time the administrator
modifies the rights by project information for a Visual SourceSafe database,
Visual SourceSafe copies the Rights.dat file to a Rights.bak file. If
necessary, you can rename the Rights.bak file during a restore process.</p>
<p><b>Caution</b>&nbsp;&nbsp;&nbsp;Never
restore a complete backup of a database over an existing database. Visual
SourceSafe maintains very complex links between files. Restoring a whole
database backup over an existing database may confuse the links between files
and cause incorrect versions of the files to be displayed in the database.</p>
<h5>Prevent Power Loss</h5>
<p>A disaster-recovery study by Contingency Planning Research found
that power loss caused 27 percent of data-center disasters in which there was
actual data loss in addition to loss of service. This figure includes power
outages due to environmental disasters such as snowstorms, tornadoes, and
hurricanes. To minimize these disasters, invest in an uninterruptible power
supply (UPS). Windows NT Server includes built-in support for UPS.</p>
<h5>Install Fault-Tolerant Storage</h5>
<p>RAID technology minimizes data loss due to problems accessing a
hard disk. RAID is a fault-tolerant disk configuration in which part of the
physical storage capacity contains redundant information about the data stored
on the disks. You can regenerate the data using this redundant information if
one of the disks or the access path to it fails or if a sector on the disk
cannot be read.</p>
<ul>
<li>Install RAID Level 1 for the operating system and LOGs.</li>
<li>Install RAID Level 5 or RAID 0+1 for DATA.</li>
</ul>
<p>For information about how to make your server more reliable, see
the following resources:</p>
<p><a
href="http://www.microsoft.com/backofficeserver/prodinfo/BOS_Checklst.doc">http://www.microsoft.com/backofficeserver/prodinfo/BOS_Checklst.doc</a></p>
<p><a
href="http://www.microsoft.com/Windows2000/library/howitworks/management/relavail.asp">http://www.microsoft.com/Windows2000/library/howitworks/management/relavail.asp</a></p>
<p><a
href="http://www.microsoft.com/NTServer/nts/deployment/planguide/HighAvail.asp">http://www.microsoft.com/NTServer/nts/deployment/planguide/HighAvail.asp</a></p>
<p><a
href="http://www.microsoft.com/NTServer/fileprint/exec/overview/reliability.asp">http://www.microsoft.com/NTServer/fileprint/exec/overview/reliability.asp</a></p>
<br>
<p>&nbsp;</p>
<br>
<!-- -->
<!-- END CONTENTS -->
<!----------------------------------------------------------------------------->
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink