TRUSOFT may help you
(TRUE Software Inc.)
Venkat
-----Original Message-----
From: Steve Hall [mailto:srh@CONVOY.COM]
Sent: Thursday, January 28, 1999 1:17 AM
To: Multiple recipients of list SQR-USERS
Subject: Visual SourceSafe - how can I get a cheap copy?
Greetings, my fellow SQRunts.
Uh, I really like Visual SourceSafe and want to add it to my toolkit.
But it is expensive, around 600 bucks.
Does anyone know how I can get a legal, legitimate copy for less?
Is there any competing versioning software that is excellent and cheap?
Tanks in Advance
-S
TRUEchange Release Notes for Release 2.1.0a OVERVIEW TRUEchange 2.1 is designed to support your configuration management needs across a variety of software platforms. This release supports interoperability for UNIX servers with Windows NT, Windows 95, UNIX, and VMS clients. Windows NT servers are supported with any WIN32 (Windows NT and Windows 95) client. New features in TRUEchange 2.1 include consistent file extension handling across platforms, a single license server for multi-platform environments, a pause/resume feature for repository backup, additional reporting facilities and enhancements for the Windows client, as well as configuration support and graphical user interface enhancements for Xadc. File Extension Handling TRUEchange 2.1 offers consistent support for file extensions across all platforms. A consistent set of file extensions is available for Windows NT, UNIX, and VMS repositories. WIN32 file extensions are now handled by the repository server, not by the client. In previous releases, the WIN32 client extensions file defined default file extensions, while UNIX and VMS file extensions were handled by the repository server. Now repositories on all platforms have a consistent set of default file settings managed by the repository server. You must make changes to an entire repository, to ensure consistent file handling within each repository. Single License Server on Three Platforms The TRUEchange license server is available for UNIX, VMS, and Windows NT platforms. With this release, one license server can support users on all platforms. A TRUEchange installation with UNIX and WIN32 clients and Windows NT and UNIX repositories, for example, now needs only one license server; a single license server can run on Windows NT or UNIX, and supports all users. If you are currently using TRUEchange in a mixed environment, and are running two license servers, contact TRUE Software for an updated license key when you install TRUEchange 2.1. The updated license key enables you to move to a single license server environment. Pause/Resume It is now possible to pause a server before backing up the repository. The pause and resume facility allows you to back up repositories with minimal interruption. You can access this new feature from the Command Line interface for UNIX and VMS servers, or from the Windows NT Administration Tool for Windows NT servers. Previously, servers had to be stopped in order to back up the repository. Removing and Restoring Directories The TRUEchange 2.1 release provides you with the ability to remove and restore directories. You can remove a directory, the files contained within the directory as well as any sub-directories and their contents. You can also remove an empty directory or sub-directory. This feature is avail- able from the Windows 95, X Windows, and Command Line interfaces. You can also restore files and directories. Note that you cannot use the adc-rmfile command to remove a directory. Windows Interface Enhancements Update Load The Development Tool Update Load facility now includes support for the Check In of new files through Update Load, and the ability to add file annotations when loading new or existing files in Update Load. In addition, the Update Load facility tracks whether filenames had upper, lower, or mixed case letters when the files were originally loaded. During an Update Load operation, if file names on the file system match file names in the repository except for their case TRUEchange informs you of the conflict, and recommends that you maintain the files as they are in the repository. You can, however, specify the case used for the names of new files when they are loaded. Enhanced Reporting The following reports offer Development Tool users additional information available previously only through the Command Line interface: *File Information Report - Displays information about a selected file. This facility allows you to view detail, changeset, annotation, and other file information from the new File-Information menu item. *Annotation Report - Displays an annotated source listing for a specified file. This report provides information such as file name, file ID, description, revision history by cset and complete line-by-line source revision history. Miscellaneous New Features The following miscellaneous new features are also included in TRUEchange V2.1: *The Development Tool includes a version difference feature that shows change-set as well as file differences. *The Development Tool provides improved handling for file differences with binary files (they are not displayed). *The Administration Tool includes a permanent setting for Task Log on. *TRUEchange prevents files and directories with spaces from being loaded to improve interoperability. *The batch tool no longer requires that a password be echoed when connecting to a repository or session. Command Line Interface Enhancements The TRUEchange 2.1 release includes several new options for existing Command Line interface commands. For example, the adc-getfiles command allows you to get specific files with and without specified change-sets. The adc-updateauth command now includes a -cfgdb option. Finally, an expanded set of file extensions for COBOL and FORTRAN is now available and the scripts that create repositories and configuration databases (create.rep and create.cfg) have been improved. Xadc Enhancements Support for Configurations Xadc now offers support for managing configurations and configuration data- bases. Users with administrative privileges can add and maintain configurations using the GUI (graphical user interface). Non-privileged users can note information about the configuration database and configuration associated with their current work environment. New Icons A new set of icons and a toolbar were added to the GUI to improve ease-of-use. Other Enhancements The dialog boxes and buttons in the GUI are now more consistent with other TRUEchange interfaces. Miscellaneous Enhancements for All Interfaces Checking for Empty Unchanged Files All interfaces now check for empty files at load time. When you Check In or load new files, you are warned if TRUEchange finds empty files and the empty files are not loaded. TRUEchange 2.1 also checks for files that have not changed at Check In time. If you Check In files from the wrong directory, and these files are not the updated ones, your Check In fails and a message informs you that the files are unchanged. Documentation TRUEchange 2.1 includes updated documentation for all interfaces. Consult the Reference Guide for Command Line Interface, the Motif User Interface, the Development Tool User Guide and the Administration Tool User Guide for additional information about the new features included in TRUEchange 2.1. Known Issues Windows Platforms This section describes the known issues associated with the 2.1 release of TRUEchange on the Windows 95 and Windows NT platforms. 1. You must specify a DOS reference path for configurations that you maintain from the Windows Administration tool, even if the reference are you are using is on a UNIX file system only. This is MR 2760. 2. The portmapper service is occasionally unresponsive on systems at or near the minimum required configuration (32mb). When this happens, client transactions time out, even though the repository appears to be running; alternatively, you may see an error indicating that the license server is unresponsive. TRUE Software recommends running TRUEchange on systems that are not at the minimum required configuration. When the portmapper service becomes unresponsive, you must restart Windows NT. This is MR 2758. 3. If source code scanning is enabled (through the Options menu), certain .c files will not be successfully loaded and the following message is displayed: "Failure to make local copy of a file. Please check access privileges or disk space on your local disk. -10003." To solve this problem disable source code scanning and Checkin these files separately. This is MR 2736. 4. If source code scanning is enabled (through the Options menu), Check In with Add New Files produces the error message "Failure to make local copy of a file. Please check access privileges or disk space on your local disk. -10003." To solve this problem disable Source Scanning when using Check In with Add new Files. If you wish the new files to be scanned, then check in the new files separately. This is MR 2668. 5. You can add new files to an existing cset by selecting the New Files button in the Checkin dialog box. All new files checked in using this feature are permanently linked to the cset with which they were checked in. If you migrate a file added with the New Files button without migrating its corresponding cset, the file appears to be empty. The file contents are still part of the cset which you must also migrate to the target branch. If you remove a cset without removing the file added with the New Files button, the file contents are removed with the cset and the file appears to be empty. Files, csets and asets under these circumstances must be managed together. To help you manage files added to a cset using the New Files button, TRUE Software now includes an "added-in" relationship that is viewable from qs and the File Information report. To checkin files that can be migrated or removed independently from a cset, checkin the files when there are no active csets open or select the Checkin New Files option from the Change Set selection list in the Checkin dialog box when there are active csets open. This is MR 2847. 6. If you create a UNIX repository and have a Windows NT license server, you MUST manually register the repository with the Windows NT license server. If you create a Windows NT repository with a UNIX license server, you also need to manually register the repository through the Windows NT Administration Tool (with the license server set to the appropriate machine). If you create a UNIX repository with a UNIX license server, or a Windows NT repository with a Windows NT license server, no manual registration is required. 7. If the local setting "Set read-only on copyout" is enabled, the read-only attribute also applies to files on checkout. This MR 2685. 8. Before running the TRUEchange uninstall utility (unwise.exe), on a TRUEchange NT Server, stop all repository server (adcsvr.exe) and license server (adclmd.exe) processes that are running on the local Windows NT machine. If TRUEchange is uninstalled while these processes are running, the next TRUEchange installation will not complete successfully. If you encounter this type of problem, restart Windows NT and reinstall TRUEchange a second time. 9. The Development Tool Function menu (using the Validate Workspace option) Select Work Directory for Validate dialog is disabled. 10. The Development Tool Function menu (using the Update Load option) Resolve File Case Ambiguity dialog is disabled. 11. The Development Tool Function menu (using the Update Load option) Undefined File Types dialog is disabled. 12. The Admin Tool Repository menu Backup and Recover dialogs are disabled. 13. MS Visual Basic 5.0 and MS Developer Studio 5.0 are not currently supported. TRUEchange 2.1 supports integration with MS Visual Basic 4.x and MS Developer Studio (Visual C++) 4.x. 14. Any time that a repository server is stopped and restarted, you must exit and restart all Development Tool sessions which connect to the repository. 15. Files of zero bytes in length are not supported. 16. Files or directory names containing spaces are not supported. UNIX Platforms This section describes the known issues associated with the 2.1 release of TRUEchange on UNIX platforms: 1. Under certain conditions if the SCCS expansion flag is turned on and you refresh the reference area an error such as the following can occur: ***Error: A procedure left SCCS keyword expansion (option u) on! *** Your local administrator should fix the procedure. This is MR 2825. 2. If you create a project in the xadc environment and update or create a configuration, the project does not appear even if you exit and restart xadc or the repository server. To update the configuration database so that project related information is displayed run the adc- addprojcfg command with the project repository as an argument. This is MR1465. 3. If you create a UNIX repository and have a Windows NT license server, you MUST manually register the repository with the Windows NT license server. If you create a Windows NT repository with a UNIX license server, you also need to manually register the repository through the Windows NT Administration Tool (with the license server set to the appropriate machine). If you create a UNIX repository with a UNIX license server, or a Windows NT repository with a Windows NT license server, no manual registration is required. 4. The adc-movedir command does not prevent you from moving a directory from the project directory. This is MR 2792. Registering a UNIX Repository with an NT License Server If you create a UNIX repository and have a Windows NT license server, you must manually register the UNIX repository with the Windows NT license server. Use the following procedure to manually register the UNIX repository: 1. On the NT License Server machine, use TRUEchange Administration Tool > Options > Set License Server to set the license server host to the local hostname. 2. On the NT License Server machine, use TRUEchange Administration Tool > Repository > Register to register the UNIX repository with the 2.1 NT License Server. The repository path should be in UNIX syntax, as if you were typing it on the UNIX host machine. Do not use the Browse button to enter the repository path. UNIX repository registration example: Repository Name: sunrep1 Host Name: icarus (the UNIX repository server host) Host IP Address: 123.456.78.91 (the UNIX repository server host) Host Platform: UNIX Repository Path: /soft/usr/jlown/ sun/sunrep1 Repository File Name: sunrep1.db License Server Host: denali (the TRUEchange 2.1 NT License Server) 3. To connect a TRUEchange 2.1 Windows client to the UNIX repository, use TRUEchange Dev- elopment Tool > Options > Set License Server to set the icense server host to the NT License Server’s hostname. Then use TRUEchange Development Tool > Options > Network Settings > Add to add connection parameters for the UNIX repository. UNIX Network Settings example: Repository: sunrep1 Login Host: icarus (the UNIX repository server host) Login ID: jlown (a valid UNIX userID, and a valid author in the repository) Password: ******* (a valid password for the UNIX userID) Registering an NT Repository with a UNIX License Server If you create an NT repository and have a UNIX license server, you must manually register the NT repository with the UNIX license server. 1. On the NT Repository Server machine use TRUEchange Administration Tool > Options > Set License Server to set the license server host to the UNIX License Server’s hostname. 2. On the NT Repository Server machine, use TRUEchange Administration Tool > Repository > Register to register the NT repository with the 2.1 UNIX License Server. You can browse the NT filesystem for the repository path, or you can type in the repository path in DOS syntax. The Browse button should only be used if the repository path is on the local NT file system. NT repository registration example: Repository Name: ntrep1 Host Name: rex (the NT repository server host) Host IP Address: 123.456.78.92 (the NT repository server host) Host Platform: NT Repository Path: c:\tcrep\ntrep1 Repository File Name: ntrep1.db License Server Host: icarus (TRUEchange 2.1 UNIX License Server) 3. To connect a TRUEchange 2.1 Windows client to the NT repository, use TRUEchange Development Tool > Options > Set License Server to set the license server host to the UNIX License Server’s hostname. Then use TRUEchange Development Tool > Options > Network Settings > Add to add connection parameters for the NT repository. NT Network Settings example: Repository: ntrep1 Login Host: rex (the NT repository server host) Login ID: jlown (a valid NT userID, and a valid author in the NT repository) Password: ******* (a valid password for the NT userID)