

                               SOURCE MINDER

			    Version Control System

                                Version 1.0

			      Reference Manual

                    Copyright (c) 1992 G.N.E. SOFTWARE LTD.


This is a shareware copy of Source Minder, which you may use to evaluate its 
suitability for your needs. If you decide that Source Minder is of use
to you, then you must register to continue using it.

Registration provides the following benefits:

o	Latest version of Source Minder.
o	Printed version of the full manual.
o	Technical support.

See the file REGISTER.TXT for details on how to register.


G.N.E. SOFTWARE LTD. accept no responsiblity or liability for any loss or 
damage arising from the use or misuse of this software.

All Company names and product names are registered trademarks or trademarks
of their respective companies.

                         Source Minder Reference Manual


           About this manual

           This reference manual provides full details on each of the Source
           Minder commands.  It is assumed that the reader has already read
           the user manual and is thus familiar with the basic operation of
           the commands.

           For installation instructions or for a tutorial, refer to the
           user manual.

           Terminology

           This chapter provides the definition for some terms that are used
           within this manual.

           Binary file     If a file does not contain lines of text, then it
                           is considered to be a binary file.

           Branch          Normally there is a main development sequence
                           where each version is a modification of the last
                           version.  This results in a single branch.  But
                           often during a project, the same version of a
                           file is modified to produce two different
                           versions. (eg. The file may be modified ready for
                           a future release, but in the meantime some bugs
                           have been spotted in the current release, which
                           cannot wait for the future release before being
                           fixed.)  This would produce two branches, the
                           main development sequence and a new offshoot.

           List file       A list file, is a file containing a list of the
                           filenames that Source Minder is to process as a
                           single entity.

           Multi-user      When a file is marked as being 'multi-user',
                           Source Minder performs extra administration to
                           ensure that the same version of a file is not
                           modified by two different people at the same
                           time.

           Revision        Each version of a file is given a unique revision
                           number whenever it is put under version control.
                           The numbers are assigned by Source Minder, and
                           start at 1 for the first version that is put, and
                           they increment by 1 for each new version that is
                           put.

           Single-user     When a file is marked as being 'single-user',
                           Source Minder does not perform any checking to
                           ensure that the same version of a file is not
                           modified by two different people at the same
                           time.

           Source file     This may be a file containing source code in any
                           programming language.  Alternatively it could be
                           a file containing resources (eg. fonts or bitmaps



                                       -1-

				       

                         Source Minder Reference Manual


                           etc.), or a word processor document, or even an
                           executable program.

           Source Minder file    This is where the Source Minder keeps all
                           of the different versions of a particular source
                           file.  The file is a binary file and it should
                           only be modified by using the Source Minder
                           commands.

           Version         When version is used alone, it refers to the
                           version of the file as it existed at some point
                           in time.

           Version control A file is considered to be under version control
                           if there exists a corresponding Source Minder
                           file for it.  A version is considered to be under
                           version control if the Source Minder file
                           contains the details to re-create that version of
                           the file.

           Version label   A version label is a user supplied mnemonic used
                           to identify a particular version.





































                                       -2-

				       

                         Source Minder Reference Manual


           Common features

           This chapter describes features that are common to most of the
           Source Minder commands.

           Version specification

           With most of the commands it is necessary to specify an existing
           version.  There are four different ways in which a version may be
           specified:

           o       By specifying the revision number.  A revision number can
                   be specified using the /R switch.  For example, /R5 would
                   specify the version that has revision number 5.

           o       By specifying a version label.  A version label can be
                   specified using the /V switch.  For example, /V1.0 would
                   specify the version that has the version label "1.0".

           o       If a branch name is specified using the /B switch, then
                   this would specify the last version in the given branch.
                   For example, /BTest would specify the last version on the
                   branch "Test".

           o       If none of the above are specified, then this would
                   specify the last version that was put.

           List files

           A list file contains a list of file names that the Source Minder
           can operate on in one go.  The file names should be separated by
           white space.  To mark a file as being a binary file, it should be
           immediately preceded by a '^'.  Any characters from a '#' to the
           end of the line are considered to be part of a comment.

           Configuration file

           The configuration file SMVCS.CFG can contain default switches for
           the Source Minder commands.  If a line starts with the name of a
           command followed by a ':', then the switches on the rest of the
           line will be used for the specified command only.  If the line
           doesn't start with a command name, then the switches on the line
           will be used with all Source Minder commands.  Any characters
           from a '#' to the end of the line are considered to be part of a
           comment.














                                       -3-

				       

                         Source Minder Reference Manual


           Restrictions and limitations

           The following list of restrictions and limitations should be kept
           in mind when using Source Minder.

           o       The maximum number of lines in a non-binary source file
                   is 65,535.

           o       The maximum size of a source file is 16 Megabytes.

           o       The maximum size of a Source Minder file is 16 Megabytes.

           o       A Source Minder file can contain up to 65,535 versions.

           o       The maximum revision number is 65,535.

           o       The maximum number of version labels is 65,535.

           o       A version label may be up to 16 characters long.  Longer
                   names will be truncated.

           o       A branch name may be up to 16 characters long.  Longer
                   names will be truncated.

           o       A user name may be up to 16 characters long.  Longer
                   names will be truncated.

           o       A version description may be up to 1024 characters long.































                                       -4-

				       

                         Source Minder Reference Manual


           Command reference

           Syntax for all of the commands is similar.  It takes the form:

                   command [switches] [files...] [@listfiles...]

           The order of  switches, files and listfiles is not significant.
           All switches, version label names, branch names and user names
           are case insensitive.  The command will have an exit code of zero
           on success, and a non-zero exit code on failure.

           List files must be preceded by a '@' character, otherwise the
           command will operate on the file itself, rather than the
           filenames contained within it.

           All commands support the switch /?, which gives brief online help
           regarding the usage of the command.

           Switches normally start with the character '/', but '-' may be
           used as an alternative.  If the switch has a parameter, then the
           parameter must follow immediately after the switch with no
           intervening spaces.  If any of the parameters contain spaces,
           then the parameter must be enclosed within double quotes.  For
           example, /N"Joe Bloggs".

           In the description of each command that follows, the switches are
           split into up to three sections.  These cover the switches unique
           to that command, the version specification switches and the
           switches which are common to most of the commands.






























                                       -5-

				       

                         Source Minder Reference Manual


           ADMIN - Administrative functions

           The ADMIN command performs various administrative functions.  You
           would not normally want to use the ADMIN command, but it may be
           useful  in the following circumstances:

           o       When you want to change single-user files to multi-user
                   files.  This could be done using the /M switch with the
                   PUT command, but PUT would also put back a new version.
                   ADMIN will not put back a new version.

           o       When you want to change multi-user files to single-user
                   files.

           o       When you have locked a version by accident, but decide
                   that you do not want to modify the version after all,
                   ADMIN can be used to unlock the version.

           o       When you wish to lock a version, but don't want to
                   actually get the version, then ADMIN may be used.

           Basic switches

           These switches control the operation of the command.  Only one of
           them may be used at a time.

           /L              Locks the specified version.

           /M              Makes the file multi-user.

           /S              Makes the file single-user.

           /U              Unlocks the specified version

           Version specification switches

           When using ADMIN to lock, or unlock a version, it is necessary to
           specify a version.  The following switches allow a version to be
           specified.  Only one of the following switches should be
           specified.  If none of them are specified, then the last version
           that was put will be locked or unlocked.

           /B<Branch>      The last revision in the given branch is
           locked/unlocked.

           /R<Revision>    Revision number to lock/unlock.

           /V<Version label>Version label to lock/unlock.











                                       -6-



                         Source Minder Reference Manual


           General switches

           The following switches provide extra information for the basic
           switches:

           /D<Directory>   Directory containing the Source Minder files.

           /N<User name>   Name of person locking the file.  This is only
                           needed when the /L switch is used.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to process every file listed within the
           specified version of the list file SMVCS.LST.

           Examples

           To make TEST.C a multi-user file:

                   ADMIN /M TEST.C

           To unlock the version with version label "2.7B" from all files in
           the list file SMVCS.LST:

                   ADMIN /V2.7B /U @SMVCS.LST

           Alternatively, as the default is to use "@SMVCS.LST" when no
           filenames or list filenames are specified on the command line,
           the following may be used:

                   ADMIN /V2.7B /U



























                                       -7-

				       

                         Source Minder Reference Manual


           GET - Extracts file from version control

           This command is used to extract a previously saved version of the
           source file from version control.  When used with multi-user
           files, the file may be locked to prevent other users from
           modifying the same version.

           Basic switches

           /L              Locks the file out for modification.

           /O              Retains the original modification time of the
                           file as it was when the version was put.  By
                           default the last modification time of the file is
                           set to the current system time.

           Version specification switches

           The following switches are used to specify the version to get.
           Only one of these switches should be specified.  If none of them
           are specified, then the last version that was put will be
           retrieved.

           /B<Branch>      Gets the last version of the file in the given
           branch.

           /R<Revision>    Gets the version with the given revision number.

           /V<Version label>Gets the version with the given version label.

           General switches

           The following switches provide extra information for the basic
           switches:

           /D<Directory>   Directory containing the Source Minder files.

           /N<User name>   Name of person locking the file.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to process every file listed within the
           list file SMVCS.LST.















                                       -8-



                         Source Minder Reference Manual


           Examples

           If the list file SMVCS.LST is being used to contain all filenames
           within the project, then to get the last version of every file,
           use the command:

                   GET

           If the Source Minder files for a project are contained within the
           directory S:\SM\PROJX, then to get the version with version label
           "1.5" from the multi-user file TEST.C, with the intention of
           modifying it to produce a new version with a version label of
           "1.6", use the command:

                   GET /L /V1.5 /DS:\SM\PROJX /NJoeBloggs TEST.C

           By setting the name 'JoeBloggs' in the environment variable
           'SMVCSNAME', and by specifying the location of the Source Minder
           files in the SMVCS.CFG file, using a line containing
           '/DS:\SM\PROJX', the above command can be reduced to:

                   GET /L /V1.5 TEST.C

           When the modification of this file is complete, it can be
           returned to version control using:

                   PUT /A1.6 TEST.C
































                                       -9-

				       

                         Source Minder Reference Manual


           IDENTIFY - Shows versions used to make executable

           This command is used to show all keywords within a file.  The
           file would normally be an executable file, built from source
           files which were under Source Minder version control.
           Alternatively it can be used with a source file to show what
           version it is.  Refer to the user manual for more information on
           how to use keywords.

           This command does not have any switches, or defaults.

           Examples

           To show the source files and their versions used to make the file
           TEST.EXE, use the command:

                   IDENTIFY TEST.EXE










































                                      -10-



                         Source Minder Reference Manual


           LOG - Shows history of versions

           This command is used to show a history of the previously put
           versions of a file.

           Basic switches

           If more than one of the selection switches are used together,
           then the intersection of the versions are displayed.  For example
           if  /B and /L are specified, then only the locked versions on the
           given branch are displayed.

           /B<Branch name> Shows all versions in the given branch.  Note
                           that this is different to the other commands,
                           where /B normally refers to the last version in
                           the given branch.  With LOG, /B refers to all
                           versions in the branch.

           /E              Shows the last version.

           /L              Shows the locked versions.

           /L<User name>   Shows the versions locked by the given user name.

           /S              Gives a one line short description for each
                           version.

           Version specification switches

           The following switches allow information about a particular
           version to be shown.

           /R<Revision>    Shows the version with the given revision number.

           /V<Version label>Shows the version with the given version label.

           General switches

           The following switches provide extra information for the basic
           switches:

           /D<Directory>   Directory containing the Source Minder files.

           Default

           If no filenames or list filenames are specified on the command
           line, then the default is to show the history log of SMVCS.LST.












                                      -11-

				      

                         Source Minder Reference Manual


           Examples

           To show the log of SMVCS.LST, use the command:

                   LOG

           To show all locked versions of the file TEST.C, use the command:

                   LOG /L TEST.C

           To show information on the last version of every file listed
           within SMVCS.LST, use the command:

                   LOG /E @SMVCS.LST

           To show all locked versions of all the files, use the command:

                   LOG /L /S @SMVCS.LST









































                                      -12-



                         Source Minder Reference Manual


           PUT- Puts version of file under version control

           This command is used to save the current version of the file, by
           putting it under Source Minder version control.

           Basic switches

           /A<Version label>Adds the given version label to the version
                           being put under version control.

           /C<description> The given description is saved with the version
                           of the file under version control.  If the /C
                           switch is used without a description then the
                           user will be prompted to enter a description
                           before the file is put.

           /E              Marks the file as being a binary file.  This is
                           only valid on the first put of a file.

           /F              Source Minder will not allow two different
                           versions to have the same version label.  It you
                           try to add a version label using the /A switch
                           that already exists, then PUT will report an
                           error.  Using the /F switch will force the
                           version label to be removed from the version
                           currently using it, and it will be added to the
                           version being put.

           /H<Branch name> The new version being put back is to be put onto
                           a new branch with the given name.  This branch
                           name must not already exist.

           /L              Keeps the file locked after putting it back.

           /M              Marks the file as being a multi-user file.

           Version specification switches

           The following switches are used to specify the parent of the
           version being put.  In single-user mode, if none of the following
           switches are used, then the last version that was put is used as
           the parent.  In multi-user mode, if none of the following
           switches are used, then PUT looks for a version that is locked by
           the user.  If more than one version is locked by the user, then
           an error is reported and it will then be necessary to use one of
           the following switches.

           /B<Branch>      The version at the end of the given branch is
                           used as the parent of the version being put.

           /R<Revision>    Specifies the revision number of the version to
                           be used as the parent.

           /V<Version label>Specifies the version label of the version to be
                           used as the parent.




                                      -13-



                         Source Minder Reference Manual


           General switches

           /D<Directory>   Directory containing the Source Minder files.

           /N<User name>   Name of person putting the file.  This is needed
                           to check that the person putting the file back is
                           the same as the person who locked the file out in
                           the first place.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to put every file listed within the
           list file SMVCS.LST.

           Examples

           To put all the files listed within SMVCS.LST with a version label
           of "3.5", use the command:

                   PUT /A3.5

           Note that the switch /A is used, and not /V.  /V is used to
           specify existing versions, and /A is used to add new version
           labels.

           To put a new version with version label "2.2.1" on a new branch
           called "Rel2Maint" whose parent is the version with version label
           "2.2", use the following command:

                   PUT /A2.2.1 /V2.2 /HRel2Maint




























                                      -14-

				      

                         Source Minder Reference Manual


           SMCHECK- Performs integrity check

           As the Source Minder version control files contain all versions
           of your valuable source, it is very important that they are
           checked every now and again for corruption.  It is recommended
           that you run SMCHECK in the following circumstances:

           o       After a machine crash, especially if the DOS command
                   CHKDSK has reported any corruption of the disk.

           o       After the version control files have been moved from one
                   machine to another, especially via communications links.

           o       Before backing up the files, as there is no point in
                   backing up corrupt files.

           SMCHECK performs two different checks:

           o       The checksums located within the Source Minder files are
                   checked to make sure that they are all correct.

           o       Each version within the Source Minder file is checked to
                   make sure that it can be extracted.

           By default both of these checks are performed.  However if you do
           not have a disk cache, or are accessing the Source Minder files
           across a network, then the second check can take a long time.  In
           this case it is recommended that you use the /Q switch which
           prevents the second check from being run.

           Switches

           /D<Directory>   Directory containing the Source Minder files.

           /Q              Perform a quick check only.  This will just check
                           the checksums, but will not test that all
                           versions are extractable.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to perform an integrity check for every
           file in the last version of the list file SMVCS.LST.

           If the /Q switch is not specified then a full integrity check is
           performed.

           Examples

           To perform a quick check of every file listed in SMVCS.LST, use
           the command:

                   SMCHECK /Q






                                      -15-



                         Source Minder Reference Manual


           SMDEL - Deletes versions

           Using SMDEL it is possible to delete individual versions from the
           Source Minder files. You may want to delete a version in any of
           the following cases:

           o       When a version has been incorrectly put. For example not
                   all of the files have been put, or they are the incorrect
                   files, or they wont compile etc.

           o       To remove intermediate versions between release versions
                   to reduce the amount of clutter in the Source Minder
                   files.

           o       To save disk space for machines which are short on
                   available disk space.

           In order to prevent accidental deletion of versions, SMDEL
           requests confirmation from the user before it starts deleting
           versions.

           Version specification switches

           The following switches are used to specify the version to delete.
           Only one of these switches should be specified.  If none of them
           are specified, then the last version that was put will be
           deleted.

           /B<Branch name> Deletes the last version in the given branch.

           /R<Revision>    Deletes the version with the given revision
           number.

           /V<Version label>Deletes the version with the given version
           label.

           General switches

           /D<Directory>   Directory containing the Source Minder files.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to delete the version from every file
           in the specified version of the list file SMVCS.LST.

           Examples

           To delete revision number 7 of TEST.C, use the command:

                   SMDEL /R7 TEST.C








                                      -16-



                         Source Minder Reference Manual


           SMDIFF - Shows differences between versions

           SMDIFF may be used either to show the differences between two
           versions that have been previously put under Source Minder
           version control, or between the current source files in the
           current directory and a previously put version.

           When the lines that are different between the two versions are
           printed out, they are preceded by either a '<' or a '>' character
           to indicate which version of  the file the lines are from.  When
           two versions are specified on the command line, the '<' refers to
           the first of these versions, and '>' refers to the second of the
           versions.  When comparing between the current source files and a
           previously put version, then '<' refers to the version in the
           current directory, and '>' refers to the previously put version.

           Before each block of changed lines is displayed, a line is
           displayed containing two numbers.  The numbers are the line
           numbers within the two different versions of the file where the
           differences occur.

           Basic switches

           /C              Show changes only.  Do not report files that
                           haven't changed.

           /S              Short listing.  Don't show the differences, just
                           report if the file is different or not.

           Version specification switches

           With SMDIFF it is possible to specify up to two versions.  If two
           versions are specified, then the differences between the first
           version and the second version are shown.  If only one version is
           specified, then the differences between the file in the current
           directory and this version will be shown.  If no versions are
           specified, then the difference between the file in the current
           directory and the last version put will be shown.  This last
           option is useful to see what you have changed since you last put
           the file.

           /B<Branch>      Use the last version on the given branch.

           /R<Revision>    Use the version with the given revision number.

           /V<Version label>Use the version with the given version label.

           General switches

           /D<Directory>   Directory containing the Source Minder files.









                                      -17-

				      

                         Source Minder Reference Manual


           Default

           If no filenames or list filename are specified on the command
           line, then the default is to show the differences for every file
           in the first version specified of the list file SMVCS.LST.

           If no /B, /R or /V switch is specified then SMDIFF will show the
           differences between the source code in the current directory and
           the last version that was put.

           Examples

           To find those files that changed between the versions with labels
           "1.1" and "1.2, use the following command:

                   SMDIFF /V1.2 /V1.1 /C /S

           To show the differences between the files in the current
           directory and the last version that was put, use the command:

                   SMDIFF /C






































                                      -18-

				      

                         Source Minder Reference Manual


           SMLABEL - Changes version labels

           SMLABEL may be used to add, delete or change version labels.

           Note that when a version label is deleted, it's only the label
           that gets deleted.  The version itself is not deleted.

           Basic switches

           /A<Label>       Adds the label to the specified version.

           /C<Label>       Changes the label specified with the /V switch to
                           the one specified with the /C switch.

           /F              If the new label being added already exists, then
                           this normally results in an error being reported.
                           The /F switch forces the original label to be
                           deleted, so that it may be added to the specified
                           version.

           /X              Deletes the label specified with the /V switch.
                           This does not delete the version, it just deletes
                           the version label.

           Version specification switches

           The following switches are used to specify the version we are
           adding the label to.  To change or delete a label, the /V switch
           must be used to specify that label.

           /B<Branch name> When used with the /A switch, specifies that the
                           last version in the branch is having a label
                           added to it.

           /R<Revision>    When used with the /A switch, specifies the
                           version we are adding a label to.

           /V<Version label>Specifies the version we are adding, deleting or
                           changing the label of.

           General switches

           /D<Directory>   Directory containing the Source Minder files.


           Default

           If no filenames or list filename are specified on the command
           line, then the default is to add/delete/change the label in every
           file in the specified version of the list file SMVCS.LST.

           Examples

           To add the label "1.2" to those versions that already have the
           label "1.1" for every file in SMVCS.LST, use the following
           command:



                                      -19-

				      

                         Source Minder Reference Manual



           SMLABEL /A1.2 /V1.1

           If there is a possibility that the label "1.2" already exists in
           some of the files, and you wish to delete its existing
           association, then the switch /F should be specified as well.





















































                                      -20-

				      

                         Source Minder Reference Manual


           VIEW - Looks at a version of a file

           VIEW lets you look at any version of a file without the need to
           get it first.  The contents of the specified version of the file
           are sent to the screen.  Alternatively the output of VIEW may be
           piped into another command.

           Version specification switches

           The following switches are used to specify which version to show.
           Only one of these switches should be specified.  If none of them
           are specified, then the last version that was put will be shown.

           /B<branch>      The last version in the branch is shown.

           /R<Revision>    The version with the given revision number is
                           shown.

           /V<Version label>The version with the given version label is
                           shown.

           General switches

           /D<Directory>   Directory containing the Source Minder files.

           Default

           If no filenames or list filename are specified on the command
           line, then the default is to view the list file SMVCS.LST.

           If no /B, /R or /V switch is specified then VIEW will view the
           last version that was put.

           Examples

           To view version "1.1" of the file TEST.C, use the following
           command:

                   VIEW /V1.1 TEST.C




















                                      -21-

				      

                         Source Minder Reference Manual



           Filenames

           By default Source Minder files are stored in the sub-directory
           SMVCS within the current directory. The Source Minder file will
           have the same name as the original source file, but the third
           character of the extension will be replaced with a 'V'. Leading
           underbar characters will be added to the extension if necessary
           to produce a 3 character extension.

           For example, for a source file TEST.C, the Source Minder file
           would be SMVCS\TEST.C_V.

           To prevent accidental deletion, Source Minder files have the
           read-only file attribute set.  You will need to use the DOS
           command ATTRIB to remove the read-only attribute, if you wish to
           delete a Source Minder file.

           In the same directory as the Source Minder files, a file named
           $SMVCS.TMP may be found.  This is a backup copy of the last
           Source Minder file before it was modified by either the PUT or
           the SMDEL command.  It can be used in an emergency to undo the
           last change to the file by copying it back on top of the Source
           Minder file.  For example, if you had run the command:

                   SMDEL /V2.0 TEST.C

           then the following commands could be used to undo the deletion:

                   CD SMVCS
                   REN TEST.C_V TEST.TMP
                   REN $SMVCS.TMP TEST.C_V

           Note that this can only be used to undo a single change on a
           single file.
























                                      -22-



                         Source Minder Reference Manual


           Appendix A - Error messages

           All error messages are preceded with a 4 digit number for easy
           identification.  In the following list of error messages, a %s
           represents a string and a %d represents a number, the values of
           which relate to the item in error.

   0100    Cannot open file %s

           The given filename which was specified as one of the parameters
           to the command cannot be opened.  Check the spelling of the
           filename, and make sure that it exists.

   0101    Version %s not found for %s

           The given version label does not exist in the Source Minder file.
           Use LOG to see which version labels are valid.

   0102    Switch '%s' invalid

           The specified switch is invalid for this command.  Use /? to get
           a list of all valid switches for the command.

   0104    Version %s already exists for %s

           You tried to add a version label which already exists for the
           given file.  Either use a different version label, or use the /F
           switch to override the current usage of the version label.

   0105    Cannot create source file %s

           It was not possible to create the source file.  Check in case the
           source file already exists and is write protected, or if there is
           insufficient disk space left.

   0106    Cannot open list file %s

           The given list filename which was specified as one of the
           parameters to the command cannot be opened.  Check the spelling
           of the filename, and make sure that it exists.

   0107    Branch %s already exists

           The given branch name already exists.  If you wish to create a
           new branch, you will need to specify a branch name that does not
           already exist.

   0108    Cannot find revision %d

           The given revision number does not exist in the Source Minder
           file.








                                      -23-

				      

                         Source Minder Reference Manual


   0109    Cannot find branch %s

           The given branch name does not exist in the Source Minder file.

   0110    Too many versions have been specified.

           You have specified too many versions using /V, /R or /B switches.

   0111    Only one of /l, /m, /s & /u can be specified

           The ADMIN command requires that one and only of the above
           switches be specified.

   0112    One of /l, /m, /s or /u must be specified

           The ADMIN command requires that one and only of the above
           switches be specified.

   0113    Only one of /a, /c & /x can be specified

           The SMLABEL command requires that one and only of the above
           switches be specified.

   0114    One of /a, /c or /x must be specified

           The SMLABEL command requires that one and only of the above
           switches be specified.

   0115    A user name must be specified.

           When using Source Minder in multi-user mode, some of the commands
           require that a user name is specified.  This may be done either
           using the /N switch, or by setting the environment variable
           SMUSERNAME to the users name.

   0116    A version label must be specified

           A version label must be specified using the /V switch.

   0117    A new branch name must be specified

           The version being put, must be put onto a new branch.  Use the /H
           switch to specify the name of the new branch.

   0118    A version must be specified

           A version must be specified using a /B, /R or /V switch.

   0200    Source file %s is too large

           There was not enough free memory (RAM) to read the given
           filename.  Check to see what else is loaded into memory.

   0201    Version %s from %s is too big





                                      -24-



                         Source Minder Reference Manual


           There was not enough free memory (RAM) to extract a version from
           the Source Minder file.  Check to see what else is loaded into
           memory.

   0202    Out of memory

           There is insufficient free memory (RAM) to complete the
           processing of the command.  Check to see what else is loaded into
           memory.

   0300    Aborted by user

           The program was aborted by pressing either <Ctrl>+C or
           <Ctrl>+<Break>.

   0600    Calculated chain idx is invalid

           Internal program fault.

   0700    Cannot rename %s to %s
   0701    Cannot rename %s to %s

           The program could not rename the given file.

   0702    Cannot write to %s

           A write operation failed when writing to the given file.  Check
           that there is sufficient disk space.

   0703    Cannot write to output

           A write operation failed.  Check that there is sufficient disk
           space.

   0800    Cannot open Source Minder file %s

           Either the source file has not been put under Source Minder
           control yet, or the directory path for the Source Minder file is
           incorrect.  The /D switch is used to specify the directory path
           for Source Minder files.

   0801    %s is not a Source Minder file

           Source Minder doesn't recognise the given filename as being a
           Source Minder file.  Check in case it has been corrupted.

   0802    %s is not compatible with this version

           You are trying to use a Source Minder file produced by a future
           version of Source Minder.  (Note that future versions of Source
           Minder will be able to read files produced by older versions of
           Source Minder, but the reverse will not necessarily be true.)

   0803    %s is corrupt





                                      -25-

				      

                         Source Minder Reference Manual


           Source Minder has detected that the given file has been
           corrupted.  Use SMCHECK to confirm this.  You will need to use a
           backup version of the Source Minder file.

   0804    Read error on %s

           There was a problem reading the Source Minder file. Use SMCHECK
           to confirm this.  You will need to use a backup version of the
           Source Minder file.

   0805    Cannot seek within %s

           There was a problem seeking within the Source Minder file. Use
           SMCHECK to confirm this.  You will need to use a backup version
           of the Source Minder file.

   0807    No versions found in %s

           The given Source Minder file does not contain any versions.  This
           is possible if they have all been deleted with SMDEL.

   0811    Node does not have a parent

           Internal program fault.

   0812    %s is not locked

           The file is not locked.  In multi-user mode it is necessary to
           lock the file before a version can be put back.

   0813    %s is not locked by %s

           The file is not locked by the given user.

   0814    %s is already locked by %s

           The required version is already locked by another user.  Only one
           user may have a version locked.

   0815    You have already locked %s

           You already have the file locked.

   0816    File size is inconsistent

           Source Minder has detected that the size of the Source Minder
           file is incorrect.    You will need to use a backup version of
           the Source Minder file.

   0900    Cannot create version control file %s

           Check that the directory path is correct and that there is
           sufficient disk space.

   0901    Cannot write to version control file %s




                                      -26-



                         Source Minder Reference Manual


           Check that there is sufficient disk space.

   0902    Cannot seek within %s

           Check that there is sufficient disk space.






















































                                      -27-
