Date |
Driver
Revision |
Operating System |
Draft/Changes |
11.3.00 |
6.03.009 |
Microsoft* Windows*
98/
Second Edition*/
Millennium Edition*
|
Installer:
- Changes to allow for proper CAT file installation under Windows*
Millennium Edition* |
9.29.00 |
6.03.008 |
Microsoft* Windows*
98/
Second Edition*/
Millennium Edition*
|
Microsoft
Logo Certification:
- CAT files received for Windows* 98/Second Edition*/Millennium
Edition* |
9.13.00 |
6.03.007 |
Microsoft*
Windows* 98 Millennium Edition
Microsoft* Windows* 98 |
Windows
Me Miniport and Windows 98 Drivers:
- Changed power management code
Installer:
- Increased uninstall
performance |
8.30.00 |
6.03.006 |
N/A
|
Installer:
- Modified Windows* 98
INF to resolve secondary channel failures |
8.29.00 |
6.03.005 |
N/A
|
Installer:
- Modified Windows*
Me INF to resolve secondary channel failures
|
8.28.00 |
6.03.004 |
N/A
|
Installer:
- File attributes
modified during installs fixed.
- Installer scans corrected
Companion:
- Several fixes implemented,
including more reliable cable detection methods and improved algorithms
for print detection.
|
8.25.00 |
6.03.003 |
Microsoft*
Windows* 98 Millennium Edition
Microsoft* Windows* 98 |
Windows
Me Miniport and Windows 98 Drivers:
- Reverted back to earlier drivers due to better fix methods
Installer:
- (-Back) command line removed from SetupCfg.sys
|
8.2.00 |
6.03.002 |
Microsoft*
Windows* 98 |
Windows
98 Driver:
- Further corrections for Audio CD fix
Installer:
- Fixed Win95 to Win98 upgrade issue.
- Added Microsoft Codename Whistler OS detection.
- Further corrections to Win98 have disk install. |
7.24.00 |
6.03.001 |
Microsoft*
Windows* 98 |
Windows
98 Driver:
- Fixed issue when playing audio CD caused BSOD. |
Production
Version V6.03.009 Release Notes |
|
|
1.
System Requirement and Installation instructions |
For
system requirements and basic installation instructions, please refer to
the readme.txt or the Intel® Ultra ATA Storage driver Application guide.
|
2. Known
Limitations and Compatibility Issues |
General |
- As a general rule,
if the Intel® Driver Installer is not installing the Intel® Ultra
ATA Storage Driver, the Intel® Chipset Software Installation Utility
should always be installed prior to loading the Intel Ultra ATA Storage
Driver; however, installing the Intel Chipset Software Installation
Utility after installing this storage driver package will cause the
user to be prompted for the location of the INTELATA.CAT file, which
can be found in the Windows* directory, under the subdirectories \SYSTEM\IOSUBSYS.
|
- ATAPI CD changers are
not explicitly supported in this release of the Intel® Ultra ATA Storage
Driver.
|
- Due to the Microsoft*
SCSI table reporting properties, the device manager for Microsoft*
operating systems may report an IDE drive as 'SCSI.' Note: This does
not impair the functionality of the HDD.
|
- ATAPI CD/DVD drives
that are running in PIO mode will not correctly recognize inserted
media. This is caused by mishandling of ATAPI commands when in PIO
mode. |
Windows* 98, Windows
98 Second Edition, and Windows 98 Millennium Edition-Specific: |
- Using McAffee VirusScan
*4.0.0 with Scan Engine* 3.2.0, the HDD may not spin down when manually
set using the ControlPanel power applet. This problem does not show
with McAffee VirusScan 4.0.3 with ScanEngine 4.0.35.
|
- Due to compatibility
issues supporting early 1x CD-ROMs under ACPI S3 resume, only CD-ROM
devices that support DMA transfer modes can be connected to the system
when using this driver.
|
- Uninstalling under
Windows* 98 does not restore the previous DMA checkbox settings for
either ATA channel.
|
-
If the Intel® Ultra ATA Storage Driver is being installed by the Intel®
Driver Installer, the Win98 CAT file will not be copied over if the
user installed the OS from the Win98 CD. If the "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\
CurrentVersion\Setup\SourcePath" value points to a read-only device,
the CAT file will not be copied to the users HDD. This is only an
issue if the system re-enumerates the HDD controller.
|
- Earlier versions of
the IOMEGA* toolset causes an incompatibility with media soft eject
function. This has been corrected with the latest version of their
toolset, found at the IOMEGA website.
|
- Under Windows* Millennium,
WebTV* causes a failure to resume from system standby. This is a known
Microsoft* issue for Windows Millennium and is not Storage Driver
dependent.
|
-In the case when a CD-ROM
device is removed after installing the operating system and before
installing the driver or if the CD-ROM device is running in multi-word,
a blue screen (BSOD) may occur.
|
- ATAPI Zip250 drives
from Iomega* with code 38.S and in the Primary Slave configuration
running in UDMA2, may cause the system to hang during a resume from
system standby mode (S3). Recommended workaround is to limit the
transfer mode to DMA multi-word 1 (MW).
|
- ATAPI 12x4x32 CD-RW
drive model ZIPCD1536int from Iomega* running in DMA mode and in
the Primary Slave configuration, may cause the system to hang. Recommended
workaround is to limit the transfer mode to the fastest PIO mode
supported on that channel. Contact Iomega for additional information.
|
-After
the Intel(R) Ultra ATA Storage Driver is installed, the DMA checkbox
appears to be available to the end-user when it should have been
removed during installation. This presence of the checkbox should
not exist when the Intel Ultra ATA Storage Driver is installed.
Having the box checked or unchecked will not have any effect on
the functionality of the system.
|
Windows* NT4.0-Specific: |
- Installing via SETUP
under Windows NT4.0 causes "IDE CD-ROM (ATAPI 2.1) DUAL-CHANNEL IDE
CONTROLLER [not started]" to show in the SCSI Adapters applet. Instead,
the text should read, "Intel Ultra ATA Controller [started]". A workaround
is to run the SETUP program with the -A setup flag, and manually install
the Windows NT4.0 driver using the SCSI Adapters applet in Control
Panel.
|
- NOTE: Though not explicitly
stated in the accompanying README.TXT file, installation on Windows
NT 4.0 requires the user be logged on with Administrator rights. |
|
Windows* 2000-Specific: |
- Windows 2000 requires
two reboots for correct installation of devices (Primary ATA channel
and Secondary ATA channel).
|
- "Super-Disk" LS-120
drives have specific considerations: |
LS-120
drives may appear as "D, "E," or later drive letters. |
LS-120
drives will report as removable storage. |
In
the "Format" Dialog box for 1.44MB FDDs: While NTFS and FAT32 are
displayed as options in the drop down list box, only FAT is supported.
|
- Note that these considerations
on LS-120 drives will not impair their functionality. |
|
3.
OEM Customization Using the SETUPCFG.SYS File |
|
Overview
This section
describes a mechanism to allow OEMs to customize the Intel® Ultra
ATA Storage Driver package via creating a text file named SETUPCFG.SYS
which must exist in the same directory as the storage driver 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 Intel® Ultra
ATA Storage Driver 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®
Ultra ATA Storage Driver package with pre-set defaults (the SETUPCFG.SYS
doesn't exist with the package; the OEM has the option to create and
modify it) |
- To "customize" the
driver 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
(e.g., limit the Secondary Master device's transfer mode limit to
PIO4 upon driver install, etc.) |
- OEMs now 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 storage
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 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 of 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 2 above, 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 storage 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 appear a maximum of once (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 |
CompanionInstall |
Yes, No, CopyOnly,
StartMenu, ControlPanel |
StartMenu |
UseUdmaOnlyOn80PinCable |
Yes,No |
No |
UseIntelLicense |
Yes, No |
Yes |
CuiInstall |
Yes, No, CopyOnly |
No |
HddTargetFolder |
Any valid string |
\Program Files\Intel\Ultra
ATA Storage Driver |
StartMenuTargetFolder |
Any valid start
menu program folder |
Intel Ultra ATA
Storage Driver |
BackgroundDisplay |
Yes, No |
No |
DiskTimeoutValue |
10-30 |
10 |
CdromTimeoutValue |
10-30 |
10 |
CdaudioTimeoutValue |
10-30 |
10 |
|
4.
Intel® Ultra ATA Companion |
|
Overview
By default, running the SETUP program creates a Start Menu Program Folder
named, "Intel Ultra ATA Storage," which contains shortcuts to the Intel
Ultra ATA Companion Application, the Companion's Help file, and the driver
package README.TXT file.
The Intel Ultra ATA Companion is a Win32* application that works in tandem
with the Intel® Ultra ATA Storage Driver to provide detailed, useful information
about the storage subsystem. The Companion queries the Intel Ultra ATA Storage
Driver via its IOCTL interface to obtain detailed Ultra ATA Controller and
device information, which is displayed on the screen and can be dumped to
a log file. The Companion can also be used to set a particular ATA or ATAPI
device's transfer mode limit (described in detail below). |
|
Displaying
Controller and/or Device Information
When started, the Intel Ultra ATA Companion's left window (the "Devices"
window) contains entries for the Intel Ultra ATA controller and all connected
ATA/ATAPI devices. Selecting a particular controller or device in the Devices
windows causes the application to display the corresponding configuration
parameters in the Companion's right window (the "Parameters" window). Parameters
shown with an oscilloscope icon are read-only; parameters shown with a wrench
icon are read-write. The various parameters are described below: |
|
Controller
Parameters |
|
Name |
Description |
IDE
Controller |
Controller
product name |
Driver Build |
Device driver
product name |
Driver Version |
Device driver
version |
Vxd Build (1) |
VSD device driver
product name |
Vxd Version (1) |
VSD device driver
version |
IDE Controller
Tri-State |
Reports if controller
is tri-stated |
PIO Mode Support |
PIO modes supported
by controller |
DMA SW Mode Support |
Single-word DMA
modes supported by controller |
DMA MW Mode Support
|
Multi-word DMA
modes supported by controller |
UDMA Mode Support |
Ultra DMA modes
supported by controller |
Flush Enable
(2) |
Reports if run-time
disk cache write flush is enabled |
Storage Kit Build(s) |
Reports what
kit is installed |
Storage Report
tab |
Reports basic
information |
Cable detection
tab (4) |
Verifies cable
detection methodology for ICH0, ICH, and ICH2 |
Disk TimeOut
Value |
Override the
defaults for Disk TimeOut |
CDROM TimeOut
Value |
Override the
defaults for CDROM TimeOut |
CD Audio TimeOut
Value |
Override the
defaults for Audio CD TimeOut |
|
|
Device
Parameters |
|
Name |
Description |
Model |
Device model
name |
Firmware |
Device firmware
revision |
Serial # |
Device serial
number |
Device Type |
Reports type
of device (ATA -fixed, ATAPI - removable, etc.) |
PIO Mode Support |
PIO modes supported
by device |
DMA SW Mode Support |
Single-word DMA
modes supported by device |
DMA MW Mode Support
|
Multi-word DMA
modes supported by device |
UDMA Mode Support
|
Ultra DMA modes
supported by device |
LBA (3) |
Logical Block
Address information |
CHS (3) |
Cylinder Head
Sector information |
CHS sectors (3 |
Number of CHS
sectors |
Disk Size (3) |
Total size of
disk |
Default Transfer
Mode |
Device's power-up
default transfer mode |
Current Transfer
Mode |
Device's current,
configured transfer mode |
Transfer Mode
Limit |
Used to limit
Current Transfer Mode, applies to any device connected to that cable
position |
Cable Type (Host) |
Reports if system
BIOS recognizes the device is connected via a 40- or 80-conductor
ATA cable |
|
|
Notes:
(1) Only displayed on Windows* 98
(2) Only displayed on Windows* NT4.0
(3) Only displayed for ATA fixed disk drive devices
(4) Only for OEMs |
|
|
|
How to
Change a Device's Maximum ATA Transfer Mode
NOTE: The Intel® Ultra ATA Storage Driver automatically configures
devices for their optimal transfer modes; changing the default "No
Limit" setting may cause adverse system effects.
At system boot, the Intel® Ultra ATA Storage Driver configures each
ATA/ATAPI device to transfer data at particular transfer modes. These
transfer modes are defined by ATA standards, and are either Programmed
I/O (PIO) or Direct Memory Access (DMA or UltraDMA) type transfers.
The Intel Ultra ATA Storage Driver usually configures devices for
their fastest capable transfer modes; however, there may be times
when a different (perhaps slower) transfer mode is appropriate for
a particular device or system configuration. To change a particular
device's maximum configurable transfer mode, the device's Transfer
Mode Limit parameter can be set to a value other than "No Limit."
To change the value of this parameter, first select the target device
in the Devices window. Next, double-click the parameter name "Transfer
Mode Limit" in the Parameters window - this causes the "Edit Parameter"
dialog box to appear. Next, choose a value in the "Parameter Data"
pulldown and select "OK" to change the value. This change will cause
the Transfer Mode Limit parameter wrench icon to flash, indicating
that its value has been changed. The parameter value change does not
take effect, however, until the "File/Commit Changes Now" is selected,
or the application is shut down (at which point, the application will
prompt the user to "Commit Changes Now"). Whenever a device's transfer
mode limit is changed, the change will not take effect until the system
is restarted. |
|
|
The File/View
Report Feature
Select "File/View Report" to view a text report of the storage subsystem.
The text report contains a variety of detailed info pertaining to
the storage subsystem, including: operating system information; system
registry information; platform information; driver information; controller
information including a hex dump of PCI configuration register values;
channel information; and device information including a hex dump of
each device's IdentifyDrive/IdentifyPacketDevice data. |
|
|
User and OEM Control
Modes
The Companion application 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 Companion 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.)
We ask that you do not publish this special key sequence - again,
this mode was implemented for OEM use only.
When the application is in OEM Mode, the following additional parameters
are viewable/configurable:
|
Parameter |
Type |
Viewable? |
Configurable? |
Storage
Driver Kit Build(s) |
Controller |
Yes |
No |
UseUDMAOnlyOn80PinCable(1)
|
Controller |
Yes |
Yes |
FlushEnable(1)
|
Controller |
Yes |
Yes |
Ping
Pong Enable |
Controller |
Yes |
No |
Cable
Type (Device) |
Device
|
Yes |
No |
PIO
PPE |
Device
|
Yes |
No |
UDMA
Control Register |
Device
|
Yes |
No |
UDMA
Timing Register |
Device
|
Yes |
No |
BaseClock |
Device
|
Yes |
No |
DiskTimeoutValue(2) |
Controller |
Yes |
Yes |
CdromTimeoutValue(2) |
Controller |
Yes |
Yes |
CdaudioTimeoutValue(2) |
Controller |
Yes |
Yes |
|
|
|
|
1
Applicable for Windows* NT* 4.0 only
2 Applicable for Windows* NT* 4.0 and Windows* 2000* only |
|
|
|
|
Storage
Driver Kit Build(s)
- Displays kit version information
|
UseUDMAOnlyOn80PinCable:
- Displays whether UDMA0-2 transfers are limited to 80-conductor
cables only (also see SETUPCFG.SYS parameter table above)
|
Flush
Enable:
- Displays whether run-time hard disk write cache flushing is
enabled/disabled
|
Cable
Type (Device):
Displays device's Identify_Drive field, which indicates presence
of 40- or 80-conductor cable (NOTE: this field may not coincide
with the BIOS-obtained information reported via "Cable Type
(Host)" parameter.)
|
PIO
PPE, UDMA Control Register, UDMA Timing Register, BaseClock:
- Displays ICH register values (see ICH EDS documentation for
further information)
|
DiskTimeoutValue
- Override the defaults for Disk TimeOut
|
CdromTimeoutValue
- Override the defaults for CDROM TimeOut
|
CdaudioTimeoutValue
- Override the defaults for Audio CD TimeOut
|
|
|
5.
Issues Resolved |
|
a. |
In
version 6.03.009 |
|
Issues
Resolved |
ID |
Title/Issue |
Component |
Operating
System |
631912 |
Storage
Kit 6.03.008 does not install CAT files under Windows* ME** |
Installer |
Microsoft*
Windows* 98 Me** |
544806 |
Conflict
with incompatible third party .vxd files |
Storage |
Microsoft* Windows*
98 SE**
Microsoft*
Windows* 98 Me**
|
550332
564440 |
Secondary
channel failures |
Installer |
Microsoft*
Windows* 98 SE**
Microsoft* Windows* 98 Me** |
550331 |
Windows*
95 to Windows 98 upgrade |
Installer |
Microsoft*
Windows* 98 Me** |
532354 |
Have
disk install method |
Storage |
Microsoft*
Windows* 98 SE** |
N/A |
System
hang when playing a music CD-ROM with USB Speakers |
Storage |
Microsoft*
Windows* 98 Me** |
532355 |
Current
Zip 250 and new UDMA Zip 250 forced into PIO Mode 0 |
Storage |
Microsoft*
Windows* 98 Me** |
532131
532132 |
Atapi
drives writing in PIO mode |
Storage |
Microsoft*
Windows* 98 Me** |
532133 |
File
naming convention (8.3) |
Storage |
Microsoft*
Windows* 98 Me** |
480501
503218
503219
528253 |
Storage
driver forces system to lock when UDF reader is installed / or general
PIO data transfer size reduction occurs |
Storage |
Microsoft*
Windows* 98 SE** |
468669 |
System
will not boot with Tape drive attached |
Storage |
Microsoft*
Windows* 98 SE** |
448168
448167 |
DVDTEST.exe
failure |
Storage |
Microsoft*
Windows* 98 SE** |
494207 |
Timna/Win98+ME/UltraATA
driver/System can't resume from S3 |
Storage |
Microsoft*
Windows* 98 SE** |
437001 |
Win98
Storage driver exhibit registry corruption error |
Storage |
Microsoft*
Windows* 98 SE**
|
440029 |
Storage
- Incorrect parameters listed in various modes (NT4.0) |
Storage |
Microsoft*
Windows* NT
|
448563 |
Mission
version information |
Storage |
Microsoft*
Windows* 98 SE**
Microsoft*
Windows* NT |
448565 |
Install-Storage-Helpfile
not installed with CUI property page |
Storage |
Microsoft*
Windows* 2000 |
468669 |
Win 98
SE on the Easton ICH2 platform , when you attach a tape backup device
as Primary Slave the system will not boot up correctly. |
Storage |
Microsoft*
Windows* 98 SE** |
|