Microsoft KB Archive/106748

From BetaArchive Wiki

BUG: Read-Only Attribute Causes Error C1063

PSS ID Number: Q106748 Article last modified on 10-12-1995

1.00 2.00


The information in this article applies to:
- The Microsoft C/C++ Compiler (CL.EXE), included with: - Microsoft Visual C++ 32-bit Edition, versions 1.0 and 2.0


The compiler generates the following error:

fatal error C1063: compiler limit : compiler stack overflow.


If the project directory has the read-only attribute set, the compiler generates one of the following errors:

fatal error C1063: compiler limit : compiler stack overflow


fatal error C1063:

The read-only attribute of the project directory can be set as the result of copying a sample from the CD-ROM. This results in all files and directories copied to the hard disk being marked with the read-only attribute.


To workaround this problem, reset the read-only attribute of the project directory. This can be done in one of two ways:

  • Use File Manager to change the read-only attribute. Select the project directory name. From the File menu, choose Properties, or press ALT+ENTER, and clear the check box labeled Read Only.


  • Use the Command window ATTRIB command to change the read-only attribute. In a Command window, change to the parent directory of the project directory and type ATTRIB -R <directory name> where <directory name> is the name of the directory that has the read-only attribute set.


Microsoft has confirmed this to be a bug in the products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Generally, if the compiler fails to write to a project directory or file because the read-only attribute is set, it will issue compiler error C1083, “Cannot open filetype file: ‘file’: message.” When the failure occurs, the project makefile is sometimes erased from the hard drive.

This appears to be a problem only when the directory is on a FAT drive or partition. Also, the problem is related to the generation of the precompiled header file, such that not generating a precompiled header file does not generate the error.

Additional reference words: 1.00 2.00 8.00 9.00 KBCategory: kbtool kbbuglist KBSubcategory: CLIss ============================================================================= Copyright Microsoft Corporation 1995.