PRB: Files Truncated One Byte When Placed in SourceSafe

 Last reviewed: April 30, 1997
Article ID: Q129187
The information in this article applies to:
  • Microsoft Visual SourceSafe, versions 4.0, 5.0
  • SourceSafe for MS-DOS, versions 3.04, 3.1
  • SourceSafe for Windows, versions 3.04, 3.1
  • SourceSafe for Macintosh, versions 3.04, 3.1
  • SourceSafe for Windows NT, versions 3.04, 3.1

SYMPTOMS

Files are truncated one byte when placed in SourceSafe.

CAUSE

SourceSafe converts the <carriage return> <line feed> combination when adding a text file to SourceSafe. Some programs write files out with the <carriage return> <line feed> <end of file> combination at the end of the file. SourceSafe will truncate the <end of file> character if the file is stored as a text file.

On occasion, text files are interpreted by programs that rely on this <end of file> character. This behavior may cause problems with these programs.

RESOLUTION

Change the file type in SourceSafe from Text to Binary.

  1. Enter the following from the Command Line: 

          ss filetype <filename> -b

  2. in the interface, choose Properties from the Info menu. Change the Type from Text to Binary.

To have SourceSafe read files in as type Binary by default, use the Binary_Masks setting in the SRCSAFE.INI or SS.INI files: 

      Binary_Masks = *.BAS

STATUS

This behavior is by design.

Keywords : kbusage SourceSafe SRCSAFE SS vbwin vss kbprb
Version : 3.04 3.1 4.0 5.0
Platform : MACINTOSH MS-DOS NT WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.