Microsoft KB Archive/259915

Knowledge Base

FIX: Analyze.exe Corrupts MBCS File Names When First 8 Bytes Are Same Text

Article ID: 259915

Article Last Modified on 8/7/2007

---

APPLIES TO

• Microsoft Visual Studio 6.0 Service Pack 1
• Microsoft Visual SourceSafe 6.0 Standard Edition

---

This article was previously published under Q259915

SYMPTOMS

The command "analyze.exe -f" in Visual Source Safe 6.0 causes an inconsistencies error if the Visual SourceSafe database has 10 Multibyte Character Set (MBCS) files in which the first 8 bytes of the file name are the same text.

Also, if there is a long file name whose file name's first 8 bytes are the same as the first 8 bytes of text for the other files in the database, the long file name is changed when you run "analyze.exe -f".

CAUSE

This is caused by a bug in the "analyze.exe -f" command.

RESOLUTION

Install the latest service pack for Visual Studio 6.0.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0.

For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed

To download the latest Visual Studio service pack, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/vstudio/Aa718353.aspx

MORE INFORMATION

Steps to Reproduce Behavior

1. Create the following files:

   NOTE: The following file names are MBCS.
   
   TEST0.txt
   TEST1.txt
   TEST2.txt
   TEST3.txt
   TEST4.txt
   TEST5.txt
   TEST6.txt
   TEST7.txt
   TEST8.txt
   TEST9.txt
   TESTABCDEFGHIJKLMN.txt
   

2. Start the Visual SourceSafe Administrator, and create a new database on C:\VSS.
3. Start the Visual SourceSafe Explorer and open the database that you just created.
4. Add all of the files that you just saved to the database.
5. Close the database.
6. Open a DOS command prompt, and then type analyze -f C:\VSS\Data, and run the command.
   
   Result 1: The Analyze Results dialog box appears, and it says serious errors or inconsistencies occurred:

   Analyze Visual SourceSafe Version 6.0 (Build 8383)
   Database analysis in progress @ 99/03/17;16:27.
   Creating a new nameset, or long filename information, for the file <TESTABCDEFGHIJKL>
   Creating a new nameset, or long filename information, for the file <TEST9>.txt.
   Analysis complete @ 99/03/17;16:27
   Potentially serious errors or inconsistencies were found.

7. In the Visual SourceSafe Explore, open the database again and verify the file name that you added in step 4.
   
   Result 2:

   "TESTABCDEFGHIJKLMN.txt" is modified to read "TESTABCDEFGHIJKL".

REFERENCES

Additional query words: sp4 VSSP4, MBCS

Keywords: kbbug kbfix kbssafe600fix kbvs600fix kbvs600sp4fix kbvs600sp5fix KB259915

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.