Date

Driver Revision

Build Number

Draft/Changes

Features Added in 2.0

Reference No: 

Description

 Release Name

ID: 973925

ID: 972812

Known Issues in 2.0 Production Version - Build 2100

Reference No: 

Description

 Affected OSs

ID:  960913

 Issues Resolved in 2.0 Production Version - Build 2100

 Issues Resolved in 2.0 Production Candidate 1.0 - Build 2093

 Issues Resolved in 2.0 Beta Candidate 3.0 - Build 2083

 Issues Resolved in 2.0 Beta Candidate 2.0 - Build 2069

 Issues Resolved in 2.0 Beta Candidate 1.0 - Build 2059

Reference No: 

Description

 Affected OSs

 Issues Resolved in 2.0 Alpha Candidate 1.0 - Build 2049

Reference No: 

Description

 Affected OSs

Components Contained in 2.0 Production Version - Build 2100

Component 

Filename

Version

Windows* 2000/XP Driver

IdeChnDr.SYS

2.0.0.2093

Windows* 98/SE/Me Driver

IntelATA.MPD

2.0.0.2093

Windows* 98/SE/Me SMART VSD Driver

IntelVSD.VXD

2.0.0.2093

Windows* NT* 4.0 Driver

IntelATA.SYS

2.0.0.2093

Intel® Application Accelerator

IntelATA.EXE

2.0.0.2093

Under a Desktop Environment:

Microsoft* Windows* 98

Microsoft* Windows* 98

Microsoft* Windows* 98 Second Edition

Microsoft* Windows* 98 Second Edition

Microsoft* Windows* Millennium Edition

Microsoft* Windows* Millennium Edition

Microsoft* Windows* NT* 4.0 (Service Pack 3.0+)

Microsoft* Windows* 2000 Professional

Microsoft* Windows* 2000 Professional

Microsoft* Windows* XP

Microsoft* Windows* XP

This section describes a mechanism to allow OEMs to customize the Intel® Application Accelerator package via creating a text file named SETUPCFG.SYS which must exist in the same directory as the driver component InstallShield* files (the .SYS extension is intentional, to cause the file not to appear under the default Explorer* file view settings).

Background: OEMs also require a flexible way to "customize" software packages for their specific business needs. In the past, OEMs could simply modify the driver INF file to set up registry key values based on their specific needs. However, with the advent of Microsoft* WHQL* digital signing of all drivers for Windows 98 and Windows 2000, this is no longer a viable solution, as modifying the INF file for a WHQL-signed driver invalidates the driver digital signature file (*.CAT). This inability of the OEM to modify driver INF files severely limits the driver package's flexibility.

As one example, an OEM's needs may require a custom version of a vendor-supplied driver SETUP program which does not install an accompanying applet by default. With a non-flexible SETUP program, the options would be: (1) have the vendor supply a custom version of the software which does not install the applet by default, or (2) require the use of a SETUP flag (e.g., > SETUP -flag1). The problem with solution (1) is that support for multiple software driver packages would be required, which entails multiple localization passes, multiple documentation development, etc. The problem with (2) is that OEMs have requested the ability to provide a package to their customers without having to instruct them to supply a SETUP flag for a particular install feature - OEMs want to offer a "customized" SETUP package requiring no flags.

Solution: The SETUP script will parse an external text file named SETUPCFG.SYS, which OEMs may create to build their own "custom" driver package. The mechanism is as follows:

• OEMs receive the Intel® Application Accelerator package with pre-set defaults (the SETUPCFG.SYS does not exist with the package; the OEM has the option to create and modify it)

• To "customize" the package for their customers, OEMs may modify the SETUPCFG.SYS file by adding one or more preset parameters and their values

• Once the SETUPCFG.SYS has been modified, invoking SETUP causes the InstallShield script to parse the contents of SETUPCFG.SYS and perform specific actions

• OEMs repackage the contents of the original .ZIP file, including the newly-modified SETUPCFG.SYS file

OEMs now ship this "customized" package to their customers with SETUPCFG.SYS presets already in place to support their functional and business requirements.

Modifying the SETUPCFG.SYS File to Customize the Driver Package

By default, the driver package contains no SETUPCFG.SYS file, and the internal driver and SETUP program defaults for all parameters (see table and descriptions below) are used. This is how the driver will appear on Intel's external driver website. OEMs may choose to re-bundle the package with a modified SETUPCFG.SYS file, which must be located in the same directory as the package's other files. If the SETUPCFG.SYS file does not exist, no action will be performed. The SETUPCFG.SYS file is only accessed when the SETUP program is run; changes to the SETUPCFG.SYS file after installing the driver will have no effect until the user runs the SETUP program again.

OEMs may choose to modify the file to meet their business needs, as described above. Syntactical requirements and editing guidelines are listed below:

All SETUPCFG.SYS file editing should be done using an ASCII editor such as DOS* Edit - non-ASCII editing can result in incorrect parsing which may cause the SETUP program to bypass one or more lines of the file due to "syntactical" errors

- Parameter names and values are not case-sensitive

- Comment lines may be added to file as long as the first character of the line is a semicolon (";")

- Any number of white-space lines may be inserted into the file, at any location.

- Valid parameter lines must be of the form PARAMETER=VALUE, where PARAMETER is one of the parameters listed in the table below, and VALUE is within the valid value range (also listed in the same table)

- If the file includes duplicate PARAMETER=VALUE lines, all instances but the first will be ignored

Any syntactical errors will cause the SETUP program to ignore all information contained on that line of the SETUPCFG.SYS file. Note that when the SETUP program encounters syntactical errors, the SETUP program will not abort, but instead, will continue processing the remaining SETUP script code.

It is strongly encouraged that the OEM test any customizations made to the SETUPCFG.SYS file, as this release of the driver package has not been exhaustively tested for all possible configurations of SETUPCFG.SYS parameters and their values.

The final step in creating the customized driver package is to repackage the custom SETUPCFG.SYS file and all other files into a new package (e.g., self-extracting .ZIP file, standard .ZIP file, packaged-for-the-web .exe, etc.). The new "custom" features will be invoked when the SETUP script successfully parses the modified SETUPCFG.SYS.

Parameters

The InstallShield SETUP script parses the SETUPCFG.SYS file (if it exists) via an exhaustive search for reserved words and corresponding preset values in the following format: "PARAMETER=VALUE". For each line of the SETUPCFG.SYS file successfully parsed by the SETUP script, one or more registry keys are set, which the driver reads upon the next driver initialization (or system reboot).

SETUPCFG.SYS lines containing these parameters and their values may appear in any order within the file, however, they must be syntactically correct (see below) and each line must only appear one (1) time (no duplicate entries). Note that by default, the driver has internal presets for each of these parameters; however, parameters and corresponding values set by the OEM in the SETUPCFG.SYS file override the internal driver defaults. All possible SETUPCFG.SYS parameters and their corresponding values are shown in the table below, and below the table, each parameter is described in further detail.

Parameter

Value Range

Default

TransferModeLimit.PM

piox, swdmax, mwdmax, udmax

Auto (no limit)

TransferModeLimit.PS

piox, swdmax, mwdmax, udmax

Auto (no limit)

TransferModeLimit.SM

piox, swdmax, mwdmax, udmax

Auto (no limit)

TransferModeLimit.SS

piox, swdmax, mwdmax, udmax

Auto (no limit)

ExtendedControl.PM

On, Off

On

ExtendedControl.PS

On, Off

Off

ExtendedControl.SM

On, Off

Off

ExtendedControl.SS

On, Off

Off

WinNT4DriverInstall

Yes, CopyOnly

Yes

UseUdmaOnlyOn80PinCable

Yes,No

No

UseIntelLicense

Yes, No

Yes

HddTargetFolder

Any valid string

\Program Files\Intel\Intel® Application Accelerator

StartMenuTargetFolder

Any valid start menu program folder

Intel® Application Accelerator

BackgroundDisplay

Yes, No

No

User and OEM Control Modes

The  Intel® Application Accelerator has two control modes: User Mode and OEM Mode.

User Mode is the default control mode. In this mode, the only configurable parameter is "Transfer Mode Limit," which sets a maximum amount for a particular device's transfer mode. This is also documented in the help text. To return to User Mode from OEM Mode, press the key sequence <Alt>U.

Pressing the key sequence <ALT>OEM changes the control mode from User Mode to OEM Mode, which is intended for use by OEM personnel only. (To return to User Mode from OEM Mode, press the key sequence <ALT>U.) 

Do not publish this special key sequence - again, this mode was implemented for OEM internal use only.

When the application is in OEM Mode, the following additional parameters are viewable/configurable: