**************************************************
SourceSafe 3.1 PC Platform Pack: Installation Disk
**************************************************

This file describes:
- How to Install SourceSafe
- How to contact Microsoft for Support
- Notes on using the Microsoft Delta to SourceSafe utility
- Notes on using the Intersolv PVCS to SourceSafe utility
- Release Notes

*********************
Installing SourceSafe
*********************

This disk set contains a complete installation/upgrade kit for
SourceSafe, the project-oriented version control system.  This disk
represents the SourceSafe "PC Platform Pack", that is, the DOS, Windows,
and Windows/NT versions of the program are all included.

SourceSafe installation has changed from previous releases of
SourceSafe.  For Windows and Windows/NT users, SourceSafe is installed
using the SETUP.EXE program found on the disk labeled "Disk 1 -
Setup".  To install SourceSafe for the first time or to upgrade your
already existing SourceSafe installation, perform the following steps:

1. If Windows is not already running, type WIN at the MS-DOS prompt.
   Or, if Windows is running, close any open applications.

2. Insert the Setup disk into drive A: or B:

3. From the File Menu in the Program Manager, choose Run.

4. In the Command Line box, type A:\setup  or  B:\setup (depending on
   which drive the Setup disk is in).

5. Press the OK button or the ENTER key.  The Setup program
   begins by asking your name and company.

6. Setup will ask you the directory to install SourceSafe in.  If you
   are upgrading an already-existing installation, be sure to
   specify your current SourceSafe installation's directory path when
   asked where to install SourceSafe.

7. The Setup program asks you several other questions and then
   begins the installation.  The process should take less than five
   minutes.

The Windows Setup program installs the Windows, Windows/NT,
and MS-DOS versions of SourceSafe.  After it concludes, you have
completed installing SourceSafe or upgrading your present
installation.

During the installation process, SourceSafe creates a new program
group for the SourceSafe program items.  Normally, Setup creates the
SourceSafe program group.  However, you can pick another program group
during Setup.  Five program items will be added to the program group:

--SourceSafe Interface for Windows
--SourceSafe Administrator for Windows
--SourceSafe Interface for Windows/NT
--SourceSafe Administrator for Windows/NT
--SourceSafe Release Notes (this file)

If you are upgrading a previous installation, all users can return to
using SourceSafe as before.  If you have created a new installation,
don't forget to run the SourceSafe Administrator program to add users.

****************************
Microsoft SourceSafe Support
****************************

Microsoft has modified the SourceSafe support policies and support
hours to be consistent with Microsoft standard support policies.  The
Help files have been updated to contain Microsoft standard support
policies, contact phone numbers, and support hours.  You can display
the support information by typing SS Help Support from the command
line.

In the United States, no-charge support from Microsoft support
engineers is available via a toll call between 6:00 A.M.  and 6:00
P.M.  Pacific time, Monday through Friday, excluding holidays.  This
support is available for 90 days after you make your first call.

   For technical support for SourceSafe, call (206) 635-7014.

In Canada, support engineers are available via a toll call between
8:00 A.M.  and 8:00 P.M.  Eastern time, Monday through Friday,
excluding holidays.  Call (905) 568-3503.  This support is available
for 90 days after you make your first call.

When you call, you should be at your computer and have the appropriate
product documentation at hand.  Be prepared to give the following
information:

      - The version number of SourceSafe that you are using
      - The type of hardware that you are using
      - The exact wording of any messages that appeared on your
        screen
      - A description of what happened and what you were doing
        when the problem occurred
      - A description of how you tried to solve the problem

For additional support information, choose Contents Search from the
Help Menu.  Type "support" into the Search Help edit box and press the
"Show Topics" button.  Select "Microsoft Support Services" and press
the "Go To" button.

*************************************
Microsoft Delta to SourceSafe utility
*************************************

SourceSafe 3.1 includes the utility DELTA_SS.EXE.  DELTA_SS.EXE
enables Microsoft Delta 1.0 users to convert Delta project databases
to Microsoft SourceSafe projects.  Appendix D of the Microsoft
SourceSafe User Guide describes how to use the DELTA_SS.EXE conversion
utility.

DELTA_SS.EXE is a DOS command line program.  If you are running
Windows 3.1 or Windows for WorkGroups 3.11, then exit Windows before
running DELTA_SS.EXE.  On Windows/NT, you can run DELTA_SS.EXE from an
MS-DOS window.

When you run DELTA_SS.EXE, you supply the location of the Delta master
project directory and the SourceSafe project name you want the Delta
project tree to be inserted into.  Note, you must supply the
SourceSafe Administrator password to the DELTA_SS.EXE program.

Before you execute the DELTA_SS.EXE program, you should set the Time
Zone environment variable (TZ) to the correct setting.  The DELTA_SS
program uses the TZ variable to compute the file modification time
for the latest version of each file converted from the Delta project
to the SourceSafe project.   If you do not set the TZ variable,
the DELTA_SS program will attempt to set TZ to Pacific Standard Time
("PST8PDT").  This may not be correct for your area.  The following
are example TZ settings:
      - SET TZ="EST5EDT"
      - SET TZ="CST6CDT"
      - SET TZ="MST7MDT"

If you run DELTA_SS.EXE from a MS-DOS window in Windows, the DELTA_SS
program cannot set the TZ variable for you.  If this happens, then
the DELTA_SS program will output --
   Please set the TZ environment variable, (e.g. SET TZ=PST8PDT)
To correct this problem, set the TZ environment variable to the
appropriate value for your location and re-run the DELTA_SS program.

For each file in the Delta \SRC directory, DELTA_SS.EXE scans the
Delta log to retrieve the version history information for the file.
DELTA_SS.EXE creates the file in SourceSafe with versioning
information retrieved from Delta, e.g.  filename, username, date, time
and comment.  The process is repeated for each version of each file in
the Delta \SRC directory.  The username from Delta is inserted into
SourceSafe by DELTA_SS.  The username does not have to be a valid
SourceSafe username.

When DELTA_SS.EXE executes, it creates two files in the top-level
SourceSafe directory (the same place SRCSAFE.INI is stored).  The
first file, DELTA_SS.LOG, contains the log of all file actions.  The
second file, DELTA_SS.ERR, lists all of the messages output by the
Delta RETRV.EXE to stderr.  Typically DELTA_SS.ERR contains the Delta
copyright notice, but there are some error messages may appear which
require the Adminstrator's attention.  Consult your Delta
documentation for how to resolve the errors reported by RETRV.EXE.
Also if you call for product support, the Microsoft Support Engineer
may ask you to read the messages which appear in the DELTA_SS.ERR or
DELTA_SS.LOG file.

The DELTA_SS.EXE file can encounter errors when processing a file.
Depending on the error, the DELTA_SS.EXE may abandon processing the
file where the error occurred and continue with the next file.  In all
cases, the DELTA_SS.EXE utility attempts to copy all versions of all
files from the Delta project to the SourceSafe project.

The following list identifies common error cases:

   -- If you have invoked the Delta prjadmin commands or the
      repair command, then the Delta_SS converter tries
      to continue even if an error (such as a bad "log.mvm" file)
      is found.

   -- If a file has been deleted from the Delta project using the
      delfile or the prjadmin exfile commands, the files are not
      actually deleted from the \SRC directory in some cases.
      Therefore there may be occasional error messages saying that
      a file was not found in the Delta log.

   -- Delta generally only stores the latest version of binary files.
      The DELTA_SS.EXE program examines files in the \SRC for binary
      characters.  If found, then DELTA_SS.EXE ignores the
      text/binary designation found in the Delta log and inserts the
      latest version of the file from the \SRC directory into
      SourceSafe.  However, prior versions of the file may be stored
      in Delta because Delta mistakenly attempted to store the file
      as a text file.

   -- There is a problem with hitting control-C during execution.  When
      fetching prior versions from Delta, the DELTA_SS.EXE program
      invokes the Delta RETRV.EXE program.  The RETRV.EXE program
      catches the control-C with its own handler.  RETRV.EXE will print
      a prompt asking if it should continue.   The solution is to press
      "Y" to RETRV.EXE, wait a few seconds, press control-C.  You may
      have to repeat the process again in case RETRV.EXE is still
      executing or is onto the next file.

************************************
Intersolv PVCS to SourceSafe utility
************************************

SourceSafe 3.1 includes the utility PVCS_SS.EXE.  PVCS_SS.EXE enables
Intersolv PVCS users to convert PVCS log files to Microsoft SourceSafe
projects.  PVCS_SS.EXE program is similar to the DELTA_SS.EXE utility.
PVCS_SS.EXE is a DOS command line program.  It runs on MS-DOS, in a
Windows MS-DOS box, and on Windows/NT.  Appendix D of the Microsoft
SourceSafe User Guide describes how to use the PVCS_SS.EXE conversion
utility.

PVCS_SS.EXE creates a file, PVCS_SS.LOG, containing the log of all
file actions.  Some of the errors reported in the log may be returned
from the PVCS GET program.  Consult your PVCS documentation for how to
resolve the errors reported by the PVCS GET command.  Also if you call
for product support, the Microsoft Support Engineer may ask you to
read the messages which appear in the PVCS_SS.LOG file.

********************************
Release Notes for SourceSafe 3.1
********************************

Changes affecting all versions of SourceSafe include:

--The help files have been significantly improved.

--Utilities to convert from PVCS and DELTA installations were added.

--A bug that inserted the wrong keyword characters when a file was
  separated was fixed.

Changes affecting the NT versions of SourceSafe only include:

--When executing with the long file names feature turned off, the
  Rename command would not detect a new file name exceeding the 8.3
  maximum length.  This would cause SourceSafe to corrupt the
  renamed file.  This bug has been fixed.

*********************************
Release Notes for SourceSafe 3.04
*********************************

Changes affecting SourceSafe menued interfaces only include:

--A bug operating on inherited labels in the history dialog box was
  fixed.

*********************************
Release Notes for SourceSafe 3.03
*********************************

Changes affecting all versions of SourceSafe include:

--Bugs were fixed concerning the SetTime variable in SS.INI ("Mod" and
  "Update" values had problems) and the Password in the -Y parameter,

--When executing on systems with low or zero disk space, SourceSafe
  would display several "Not enough disk space" messages when
  performing operations on multiple files.  Under SourceSafe 3.03,
  SourceSafe will display "Not enough disk space" message only once
  and terminate.

Changes affecting SourceSafe menued interfaces only include:

--The View and Difference commands now have Search ability.

--The History dialog will no longer show Labels that were applied before
  the item was created.

--Bugs were fixed concerning: Reporting from the History/View dialog,
  file operations immediately after renaming a project, and using the
  Project Difference command in a root directory.

Changes affecting the Windows and NT versions of SourceSafe only include:

--The Project Difference command would display the an "Out of Memory"
  error on Projects of 100 files or more.  This bug has been fixed.
  SourceSafe Project Difference completes successfully on projects of
  100 files or more.

--When the SourceSafe main screen is sorted by filename, you can type a
  filename to jump to the appropriate file.  For instance, if you type
  SOU, selection will jump to the first filename that starts with these
  three letters.

--It is now possible to customize the colors used by the Visual
  Difference display.

Changes affecting the NT version of SourceSafe only include:

--A bug was fixed concerning multiple selection in the Add dialog.

Changes affecting SourceSafe command line only include:

--A bug was fixed concerning the -B and -D flags on the History
  command.

Changes affecting the SSADMIN program include:

--Bugs were fixed concerning the security system (giving more than 16
  rights to a project below $/), saving INI variables that are set
  while running the program.


********************************
Release Notes for SourceSafe 3.0
********************************

The full list of new features in SourceSafe 3.0 is too exhaustive to
be listed in the form of release notes.  However, some of the most
notable changes are listed below.

Changes affecting all versions of SourceSafe include:

--A "three-way merge" enables SourceSafe to automate the process of
  rejoining different versions of a file after separate changes have
  been made.  The merge can be used after a branch (Separate) is
  created, or after one file is checked out by more than one user.

--An advanced security system, controlled from the SourceSafe
  Administrator's program, enables you to set project-by-project
  rights for users.

--The Difference command can now be customized, including a visual
  display that shows both files being compared, side by side, with
  changes highlighted.

--A project-level Share command completely automates the process of
  creating branches.

--All variables in SS.INI now propagate down the project tree.  This
  enables you to use one line to set, for instance, shadow directories
  for an entire tree of projects, instead of having to set a directory
  for each project individually.

Changes affecting the SourceSafe menued interface only include:

--All SourceSafe informational dialog boxes now have a Report" button
  that enables you to export the information to a text file, printer,
  or (in SourceSafe for Windows) to the Windows clipboard.

--Most SourceSafe commands are now optionally preceded by a command
  dialog offering many power-user options that were previously
  available only on the SourceSafe command line.

Changes affecting the graphical (non-DOS) SourceSafe interfaces only
include:

--The icon bar is now customizable by the user.

