KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q42415: Eliminating Extra QC.INI Files

Article: Q42415
Product(s): See article
Version(s): 2.00
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_c
Last Modified: 2-MAY-1989

Question:

Why does QuickC 2.00 create a new QC.INI file in every directory that
I compile in?  How can I get QuickC to generate only one of these
files and then always use it?

Response:

When QuickC is started, it looks first in the default directory and
then along the PATH environment variable for QC.INI. If it doesn't
find this file, it will start with its default configuration. Making
any changes to QuickC's configuration will cause it to create a QC.INI
file in the default directory.

To keep QuickC from creating multiple QC.INI files, start it from the
directory where QC.EXE is found and make a change to its
configuration. This will create a QC.INI file in that directory. This
.INI file then will be found in the PATH when QuickC is started from
any other directory.

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.

Copyright Microsoft Corporation 1986-2002.