Mylex DAC930PL Firmware 2.49 firmware diskette, rev d

To create the Mylex firmware 2.49 upgrade diskette:
   run mlxfw249.exe
then boot to the diskette to use it.
--------
.
. Mylex DAC960PL Firmware 2.49 firmware flash and FUA-bit utility
.
. This diskette Perform each of the following steps:
. -------
. Step 1   to flash the Mylex firmware to version 2.49 
. Step 2   to set the FUA-bit for forced error detection
. Step 3   to set the disk retries to the optimum value (0x0C),
.          this sets the disk mode page values.
. -------

The diskette automatically performs Step 1, then, after rebooting, 
performs Steps 2 and 3.

Step 3 involves setting the mode page values on all disks on the
Mylex array to the desired retry setting.  It also turns of SMART.
Step 3 may need to be performed again later if a new disk is inserted
without the mode page settings.  You can use A:3.bat to do this, or
use the NCR PREPDISK diskette.

Note that Seagate ST19171 9GB drives must have at least FW ver 0024 or
greater before their mode pages can be set.

This diskette with Mylex FW 2.49 resolves a problem with ST19171, ST34371, 
and ST34572 disks shipped prior to 12/02/97, which had retry counts that 
caused the retries to exceed the 2.2 second limit set in firmware 2.39.
The symptom of this problem is that a disk with bad spots would not 
send an error back to the Mylex board before the timeout expired and
cause the Mylex to issue a SCSI bus reset.  The Mylex FW 2.49 has a 4.0 
second timeout, and its FUA-bit forces errors to be read from disk
rather than cache.  Also, this diskette sets the mode pages on each
disk to a retry count of 12 (0x0c), which results in a time-to-expire
of 1 second or less.

The output of the mode sense values goes into dacutil.ms on the diskette.
In the DACUTIL.MS file, you will see that Page 1, Byte 3 shows "52 c c"
and Page 7, Byte 3 shows "52 c c", indicating that the default retry count
was 0x52, but has been changed to 0x0c.

In rev d of this diskette, the default image was switched so that the 
S40-compatible image is loaded via autoexec.bat.  This image is also 
compatible with the other systems.