FIX: SSARC & SSRESTOR Do Not Store Macintosh Resource Fork DataLast reviewed: December 1, 1997Article ID: Q172337 |
The information in this article applies to:
SYMPTOMSWhen using SSARC and SSRESTOR to archive and restore files from a database that has Macintosh SourceSafe clients and stores Macintosh files, the file's resource fork is not included as part of the archive. Restoring the archive to another database causes resource fork information to be lost. Attempting to get or checkout these files on a Macintosh client produces the following error message:
File '<path>:<filename>' not found where <filename> has either a .c or a .d extension. CAUSESSARC and SSRESTOR do not make use of the information stored in files with the .c or .d extension in the SourceSafe database. These files contain the resource fork information for Macintosh files.
RESOLUTIONIt is possible to copy the Macintosh resource fork information to the restored database. SSARC & SSRESTOR may re-map the physical filenames when archiving from one database and restoring into another database. The following steps can be used to copy the resource fork information:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 3. For more information, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Packs - What, Where, and Why REFERENCESFor additional information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q131447 TITLE : HOWTO: Use PHYSICAL Command to Find SourceSafe Database File ARTICLE-ID: Q157714 TITLE : How SourceSafe Stores Log Files |
Additional query words: mac
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |