KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q130140: FIX: SourceSafe Might Not Get Long Filenames on Windows NT

Article: Q130140
Product(s): Microsoft SourceSafe
Version(s): 3.10
Operating System(s): 
Keyword(s): kbSSafe400fix kbSSafe300bugkbbuglist
Last Modified: 22-MAY-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft SourceSafe for Windows NT, version 3.1 
-------------------------------------------------------------------------------

SYMPTOMS
========

SourceSafe might not retrieve long filenames correctly on a computer running
Windows NT even if the long filenames option is checked from the GUI and the
LONG_FILENAMES variable is added to one of the .INI files.

CAUSE
=====

SourceSafe for Windows NT supports long filenames only if the drive is a mounted
NTFS drive. Even though Windows NT FAT drives support long filenames, SourceSafe
for Windows NT writes the file as an 8.3 filename.

STATUS
======

Microsoft has confirmed this to be a bug in the Microsoft products listed at the
beginning of this article.
This bug was corrected in Visual SourceSafe version 4.0.

Additional query words:

======================================================================
Keywords          : kbSSafe400fix kbSSafe300bug kbbuglist
Technology        : kbSSafeSearch kbAudDeveloper kbZNotKeyword2 kbZNotKeyword3 kbSSafe310NT
Version           : 3.10
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

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.