The information in this article applies to:
Under Windows NT, .INI file variables are mapped into the Registry as defined in the \HKEY_LOCAL_MACHINE \Software\Microsoft\WindowsNT\CurrentVersion\IniFileMapping mapping key. The Win32 Profile application programming interface (API) functions look for a mapping by looking up the filename extension portion of the profile file. If a match is found, then the search continues under that node for the specified application name. If a match is found, then the search continues for the variable name. If the variable name is not found, the value of the (NULL) variable name is a string that points to a node in the Registry, whose value keys are the variable names. If a specific mapping is found for the variable name, then its value points to the Registry value that contains the variable value. The Profile API calls go to the Windows server to look for an actual .INI file, and read and write its contents, only if no mapping for either the application name or filename is found. If there is a mapping for the filename but not the application name, and there is a (NULL) application name, the value of the (NULL) variable will be used as the location in the Registry of the variable, after appending the application name to it. In the string that points to a Registry node, there are several prefixes that change the behavior of the .INI file mapping:
Additional query words: prodnt inifilemapping
Keywords : kbenv ntfilesys ntregistry |
Last Reviewed: January 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |