Microsoft KB Archive/110305

= Windows NT reads environment variables from AUTOEXEC.BAT at boot time =

Article ID: 110305

Article Last Modified on 4/29/2005

-

APPLIES TO


 * Microsoft Visual C++ 1.0 Professional Edition
 * Microsoft Visual C++ 1.5 Professional Edition
 * Microsoft Visual C++ 2.0 Professional Edition
 * Microsoft Visual C++ 4.0 Standard Edition
 * Microsoft Visual C++ 5.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 5.0 Professional Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition
 * Microsoft Macro Assembler 6.11 Standard Edition
 * Microsoft FORTRAN PowerStation 32

-



This article was previously published under Q110305



SUMMARY
At boot time, Windows NT reads the AUTOEXEC.BAT file and sets any environment variables that do not conflict with Windows NT settings. These environment variables may affect the way some programs work.



MORE INFORMATION
Environment variables may be used to set compiler, assembler, and linker options. Settings made in this way will override settings made in the Visual Workbench and in makefiles. For example, the following setting will cause the compiler to pack structures on 1-byte boundaries, and this can cause problems when creating applications for Windows NT using Visual C++ 32-bit edition:   SET CL=-Zp1 The following environment variables may affect development tools:   CL       : C/C++ compilers ML      : MASM FL32, FL : FORTRAN compilers LINK    : Link Environment variables set in AUTOEXEC.BAT can only be seen in a console session. To see the current environment variable settings, run a console session and enter the following command at a prompt:

set

The resulting list may include variable settings that do not show up when checking the system settings in the Control Panel. These variables are probably being set in the AUTOEXEC.BAT file.

To prevent problems related to setting of unwanted environment variables in Windows NT, but to still allow them to be set when booting MS-DOS on a dual- boot machine, use a secondary batch file. For example, place all of the SET commands in the AUTOEXEC.BAT file in a file called DOSVARS.BAT. Save this file in the root directory of your boot drive (the same directory as AUTOEXEC.BAT). Add a line to execute this batch file to the end of AUTOEXEC.BAT (add it as the last line): DOSVARS This will execute the batch file to set the variables and not return to the AUTOEXEC.BAT processing. You can also use the following CALL DOSVARS at any point in the AUTOEXEC.BAT file so that processing of AUTOEXEC.BAT continues after the settings are made. Because Windows NT does not process nested batch files when reading AUTOEXEC.BAT, the variables will be set for DOS but not for Windows NT.

Additional query words: MASM FORTRAN

Keywords: kbhowto KB110305

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.