Blog

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Reference one or more INF-writer-defined sections in the INF that each specifies a list of files to be copied from the source media to the destination. A CopyFiles directive can be specified within any of the sections shown in the formal syntax statement. This directive can also be specified within any of the following INF sections:.

Interfaces section. Each named section referenced by a CopyFiles directive has one or more entries of the following form:. An INF-writer-defined file-list-section can have any number of entries, each on a separate line. Each file-list-section can have an optional, associated file-list-section.

If no source-file-name is given, this specification is also the name of the source file. If the source and destination file names for the file copy operation are the same, source-file-name can be omitted. One or more ORed values for the following system-defined flags can be specified. However, some of these flags are mutually exclusive:. This flag and the next are mutually exclusive, and both are irrelevant to INF files that are digitally signed.

This flag is implied if the driver package is signed. This flag and the next two are mutually exclusive. This flag is irrelevant to digitally signed INF files. Instead, copy the given source file with a temporary name so that it can be renamed and used when the next restart occurs.

This flag cannot be combined with any other flags. For more info, see Version Information. If the target file is not an executable or resource image, or the file does not contain file version information, then device install assumes that the target file is older.

The system will prompt the user to restart the system. For example, Windows might determine that the file copy operation is not necessary because the file already exists. However, the writer of the INF knows that the operation is required and directs Windows to override its optimization and perform the file operation. If the destination file cannot be renamed, complete the copy operation during the next system restart.

If the renamed destination file cannot be deleted, delete the renamed destination file during the next system restart. For information about security descriptor strings, see Security Descriptor Definition Language Windows. If an file-list-section. For more information about how to specify security descriptors, see Creating Secure Device Installations. Windows only copies a driver package to its destination location as part of a driver installation if the file has an INF CopyFiles directive.

When it copies files, the operating system automatically generates temporary file names, when necessary, and renames the copied source files the next time that the operating system is started. This section controls the destination for all file-copy operations, as follows:. If a named section referenced by a CopyFiles directive has a corresponding entry in the DestinationDirs section of the same INF, that entry explicitly specifies the target destination directory into which all files that are listed in the named section are copied.

File names that are specified in either the filename or file-list-section entries must be the exact name of a file on the source media. The CopyFiles directive does not support decorating a file-list-section name with a system-defined platform extension. When a driver package is staged in the driver store , a file is only copied from the driver package source to the driver store if the file has a corresponding INF CopyFiles directive.

As part of a Windows upgrade, Windows only copies a driver package file to the driver store as part of a driver migration if the file has an INF CopyFiles directive.

Skip to main content. This browser is no longer supported. Table of contents Exit focus mode. Table of contents. Submit and view feedback for This product This page. View all page feedback. Additional resources In this article.

$winnt$.inf driver download

 
If it is not highlighted, select it.

$winnt$.inf driver download

Note: If this screen is not displayed as the first user input, then the F6 key press was not seen by the setup program. Reboot the system and try again. The system prompts for the manufacturer-supplied hardware support disk.

Current Windows NT 4. Note: If more than one SDMS driver needs to be installed, they can be installed one after the other using steps 4 through 6. Installation order is not important. This driver supports controllers that are listed in the description section above.

If the bundled driver will support the LSI Logic chip which is being used, please skip to step 3. Press Enter when the Welcome to Setup screen appears. Press S to skip automatic detection and do manual selection. A screen displays the message : Setup has recognized the following mass storage devices in your computer Note: If more than one SDMS driver needs to be installed, they can be installed one after the other using steps 7 through Existing System Installation.

Note: Windows NT 4. Click on the Start button. Click the Drivers tab. SYS drivers are listed, select the driver s and choose Remove before adding the new driver. SYS is listed, remove it before adding the new driver. Do you want to use the currently installed driver s or install new one s?

Note: Selecting Current uses the driver already on the system, and selecting New uses the driver on the diskette. Unless you want to use the older version already on the system, choose New. If you choose Current , go to step You must restart your computer before the new settings take effect.

Do you want to restart your computer now? Performance Tuning for Windows NT 4. In Windows NT 4. This file will set a Kbytes maximum, but it can be edited to set other desired maximum transfer sizes.

REG data file before editing it. REG data file supplied with the driver files using Windows Explorer and double click on the file.

Both methods insert an entry into the registry to enable Kbytes block size support. The formula to calculate the proper value for MaximumSGList is:. The system must be rebooted for the new registry setting to be effective. REG as the data file. This can have a huge impact on performance benchmarking between different driver versions or adapter vendors. This can affect systems with high performance storage subsystems, such as disk arrays.

REG file can be edited. High values for this setting can degrade system performance. Auto Request Sense. The SDMS 4. All of the disk drives on all host adapters will be recognized through the INT13h function call. Because of this implementation, disk mirroring under Windows NT needs to be done. This must be done so that you can boot from the mirrored partition in case the primary partition fails. INI to this diskette. Temporarily remove the read-only attribute of the BOOT.

The length of the class-name string must be 32 characters or less. This entry is irrelevant to an INF that installs neither a new device driver under a predefined device setup class nor a new device setup class. This entry is required for device drivers that are installed through the Plug and Play PnP manager. The GUID value is formatted as shown here, where each n is a hexadecimal digit.

This class-specific GUID value also identifies the device class installer for the type of device and class-specific property page provider, if any. Also see Device Setup Classes. The GUID value is formatted as shown here, where each x is a hexadecimal digit. However, when updating an existing extension INF, the ExtensionId must remain the same so that multiple related versions of the extension INF are versioned against each other instead of being treated as independent extension INFs that may be simultaneously installed on the same device instance.

When a driver package is submitted to Microsoft for digital signing, WHQL provides a catalog file for the driver package after WHQL has tested and assigned digital signatures to the package.

Windows assumes that the catalog file is in the same location as the INF file. Specifies another INF-writer-determined, unique file name, with the. If any decorated CatalogFile. For more information about how to use the system-defined. Because the same. However, you must use this entry if you want to create platform-specific.

Starting with Windows , this entry is required. SourceDisksNames Section. This section includes one entry for each disk within the distribution set.

The entry takes the form. Typically, disks are numbered starting at 1. The disk-description tag is a human-readable text string that can be used to prompt the user for the proper disk as needed. The tagfile value assumes a dual role.

To ensure that the user supplies the correct disk during the installation process, the tagfile value is verified as existing on the inserted media before the install process continues.

If the tagfile file is missing, the user is reprompted to insert the correct disk. If the tagfile value contains a. CAB extension, the file is further assumed to be a collection of compressed files for the source of driver files on the disk. The path value is a root-relative disk path value for the source of driver files on the disk.

Like the tagfile value, path is optional. If omitted, the root directory is assumed to be the source of the files. SourceDisksFiles Section.

This section lists the filenames used during installation of the driver. Each file corresponds to one entry within the section and takes the form. Naturally, the diskid value specifies a disk within the [SourceDisksNames] section where the filename is to be found. The optional subdir value specifies a path on the disk for the file.

The optional size value specifies the uncompressed size of the file in bytes. An installation process can use the size to determine if the source file fits on the target system prior to attempting the copy. DestinationDirs Section. This required section in an INF file specifies the target directory for source files.

Without knowledge of this section, an installation program or process would have no target directory in which to copy files. The entries in the [DestinationDirs] section take the form. It specifies that all the files copied by a directive install into the specified directory. For the entry DefaultDestDir , the specification applies to all [CopyFiles] directives that do not otherwise associate with a file-list-section within the DestinationDirs section. The dirid value specifies an enumerated value for a destination directory according to Table If the value subdir is supplied, it specifies a relative path beneath the directory called out by dirid.

Services Section. In order to actually have the copied file s act as a driver on the target system, the Service Control Manager SCM must be notified. A ServiceType value of 1 signifies a kernel-mode device driver. StartType designates at what point in the boot process the driver loads 3 denotes on-demand or manual start. The ErrorControl value determines what happens during the driver load if an error is encountered.

ServiceBinary value points to the location of the driver file. DestinationDirs dirid Definition. Root directory of the boot drive. Boot directory for Windows Directory of this INF file. INF file directory.

Fonts directory. Spool directory. Spool drivers directory. Print processors directory. Color ICM. Absolute path. Viewers directory. User Profile directory. Applications directory. Shared directory. Help directory. Program Files. The entries of the DDInstall.

Services section include an entry of the form. SYS extension. The flags value is described in Table AddService flags Definition. AddService flags. Driver is an FDO function driver , not a. Do not overwrite friendly name. Do not overwrite description. Do not overwrite start type.

Do not overwrite error control. The service-install-section and optional eventlog-install-section values call out additional INF section names that control service value entries such as ServiceType and StartType. ServiceInstall Section. Services sections, controls the installation of a driver into the Service Control Manager. The allowed entries within the [ServiceInstall] section are listed in Table ServiceInstall Section Entries. Friendly name of driver, displayed in Device Manager.

Short description of purpose of driver or service, displayed by Device Manager. Type of driver:. Specifies when driver loads:. Disposition of errors during driver load:. Full path name of driver, which may include dirid values see Table INF Example. If the preceding explanation of INF files appears overly complex, a simple example may clarify.

In the following example, a two-file driver is controlled by the INF file. The driver binary, Launcher. SYS, is copied into the system’s driver directory e. A separate help file, Launcher. HLP, is copied into the help directory of the system e.

Services] ; DDInstall. Services sec. Validating INF Syntax. While the tool is not without merit, it reports numerous errors when checking standard Microsoft INF files. The output from the tool is in the form of an HTML file.

The tool must also be classified as rudimentary but may assist first-time authors. Manual Installation. Right-clicking the file offers the option to Install process the file.

In a true Plug and Play environment, the insertion or removal of a device triggers the installation, load, and unload of an appropriate driver.

Therefore, the use of manual installation is reserved for initial testing and debugging of a driver. Automatic Installation.

When a PnP device is inserted into a system, several subsystems interact to force the loading of a new driver, if necessary. The steps are outlined below. When the device is inserted, the hardware, using auto-detection and notification, alerts the bus driver that the device is present.

Depending on the bus hardware, this might involve notifying the bus driver that a change has occurred that warrants a new enumeration of bus devices.

Regardless, at the end of this step, the bus driver is aware that the new device is present and that it has a specific device ID. The INF directory of the system e. If a suitable INF file cannot be located, the system delays further action until a privileged user logs on. Then the user is presented with a dialog-driven New Hardware wizard.

The user supplies the location of the drivers CD, diskette, Web location, etc. The driver files and Registry entries are installed and modified. This step is primarily carried out by the kernel-mode PnP Manager. Based on the directives of the INF file, the kernel-mode PnP Manager loads any lower filter drivers, then the functional driver, and finally any upper filter drivers for the device. As just explained, the user must sometimes interact with even an automated installation.

The prime interface for this interaction is the New Hardware wizard.