Config File Windows 7
By Overview IIS 7 introduces a brand-new configuration system, at the core of all the new administration-related features. The configuration system is based on distributed, clear-text, XML files that hold the configuration settings for the entire web server platform, including IIS, ASP.NET and other components, such as FTP 7.5; they may optionally be set at the content directories together with the web content if unlocked for that level. Notice that FTP 6.0 configuration settings are stored in the MetaBase. Different levels of the configuration hierarchy may be delegated by the machine administrator to other users, such as the site owner or the application developer. Secure defaults and out-of-the-box lock down limit write-access to configuration settings to the machine administrator only (the exceptions are a few site specific settings such as DefaultDocument); however, sophisticated and granular locking features enable safe unlocking and delegation of management of specific configuration settings to more users, for their scope of the web namespace.
The system is backward compatible at the API level with previous versions of IIS (after the MetaBase compatibility layer is installed). At the root (or global) level, there are two separate files:. system32 inetsrv config applicationHost.config: Holds the global defaults for web server (IIS) settings.
IIS7 Settings File Locations. Windows System32 inetsrv config. Yes, it's an XML file, and yes, editing the file by hand will affect the IIS config after a restart. The fastest and easiest way to open your CONFIG file is to double-click it. This allows the intelligence of Windows to decide the correct software application to open.
Windows Microsoft.NET Framework v4.0.30319 Config machine.config: Holds the global defaults for the.NET framework settings, including some of the ASP.NET ones (the rest of the settings are in the web.config at the same folder, which is sometimes called the root web.config). The reason there are still two separate files is because the two technologies version differently (schedule-wise and product-wise). IIS is part of Windows and the.NET framework may version independently. In the web content directories, there may be optional web.config files that control the behavior for their level of the hierarchy and downward. They could be local or remote (if the content directory is on a UNC share, for example). They may contain IIS, ASP.NET or any other.NET framework configuration settings that can be specified at their level. By default there are no web.config files.
Hierarchy In terms of inheritance hierarchy, the root file is machine.config, then web.config at the same directory (referred to as root web.config), then applicationHost.config, then the optional web.config files along the namespace as illustrated in the following diagram. Sections Within a configuration file, the settings are organized in a structured manner, based on a unit called 'section'.
Configuration section is a group of logically-related settings that can be deployed as a whole, or unregister from the system as a whole, and are typically consumed by one server module. In other words, almost every runtime module that runs in the worker process has a corresponding configuration section for it. Configuration section is also the unit of extensibility: adding new settings to the configuration schema is done by extending an existing section or by adding one or more sections to it. The sections are further grouped into logically-related collections, called 'section groups'.
Section groups are not the unit of deployment, or registration, or any other substantial operation (e.g. Locking, encryption). They do not have settings in them. Their purpose is to further structure the organization of settings, and avoid a long flat list of configuration sections.
They are used to build hierarchy of settings, so they do have relationships between them (parent/child). In other words, section groups can be nested. A given section always belongs to one section group only, and cannot contain other section (or section groups).
A given section group may belong to a parent section group, and may contain zero or more child section groups. It typically contains more than one section; otherwise there is not a good reason to have it in the first place (however, customers can extend the schema by creating their own section groups that have one section only, for whatever reason). Here is an example that demonstrates sections and section groups:
Configuration for a given level inherits down to child levels, unless specifically overridden by a child level. A simple way to achieve per-URL configuration is by using web.config files, in the physical file-system folders that are mapped to the virtual paths. Note There is no high-level programmatic interface to get and set schema files, short of traditional file access API and XML parsing/editing. It is always recommended to backup sensitive state like the schema folder, before making any changes to it. Three files make up the unified schema of the web server platform:.
Windows 7 System Config
IISschema.xml: covers the Windows Activation System and IIS web server settings and section groups. ASPNETschema.xml: covers the ASP.NET settings in the section group. FXschema.xml: covers other.NET framework settings in various section groups. You will also find FTPschema.xml if you have IIS 7 FTP feature installed.
That sounds like you have an old DOS program or other 16 bit program. Those will not run under windows 7 64 bit, but will run under windows 7 32 bit.
Customizing autoexec.nt and config.nt You can choose to further configure the MS-DOS and Windows 3.x environment by modifying Windows 7's equivalent of the old CONFIG.SYS and AUTOEXEC.BAT files. These files are called config.nt and autoexec.nt and are used to configure each DOS VDM when it starts up. Just remember: The files CONFIG.SYS and AUTOEXEC.BAT in your hard drive's root folder are completely ignored by Windows 7.
If they're there at all, it's only to fool really old applications that won't run unless they see that these files exist. The files config.nt and autoexec.nt in windowssystem32 are used, but only when Windows needs to start up an MS-DOS or Windows 3.x application.
Any change to these files will take effect the next time you start the application - you don't need to restart Windows. That sounds like you have an old DOS program or other 16 bit program. Those will not run under windows 7 64 bit, but will run under windows 7 32 bit. Customizing autoexec.nt and config.nt You can choose to further configure the MS-DOS and Windows 3.x environment by modifying Windows 7's equivalent of the old CONFIG.SYS and AUTOEXEC.BAT files. These files are called config.nt and autoexec.nt and are used to configure each DOS VDM when it starts up. Just remember: The files CONFIG.SYS and AUTOEXEC.BAT in your hard drive's root folder are completely ignored by Windows 7. If they're there at all, it's only to fool really old applications that won't run unless they see that these files exist.
Microsoft Windows 7 Free Download
The files config.nt and autoexec.nt in windowssystem32 are used, but only when Windows needs to start up an MS-DOS or Windows 3.x application. Any change to these files will take effect the next time you start the application - you don't need to restart Windows. To me there are only 1 thing to do and that is to bye a computer like windows xp and never yous windows 7 or higher.