Introduction

The 2.34 release fixes bugs found in the WITE32 2.33 release. (This document uses the WITE32 2.33 release notes as a base line for comparison.)

Fixed Bugs

The following bugs have been fixed:

• The programmable filter board has a EEPROM that keeps information on Boost Factor, Minimum cutoff frequency, and Maximum cutoff frequency, among other parameters. WITE32 does not read these paramters upon startup, and therefore cannot display them correctly. NOW: WITE32 reads these 3 parameters upon startup and display this information properly.
• The Control | Filter menu shows that there is no programmable filter, though it exists physically in the Analog box. NOW: The Control | Filter menu shows correctly whether there is a programmable filter or not.

Modifications:

1. The Offtrack Performance Test is modified in the following ways:
   1. In the configuration menu, the label of the checkbox, Center at Read Offset Position, has been changed to Center MR Head at Read Position
   2. In the configuration menu, Output Data Points checkbox has been added for enabling/disabling the sending of the Comparator Error test results to the result database. The default value is enabled.
   3. In the configuration menu, the label Track Pitch was truncated in some monitors and displayed only Track. NOW: The label is displayed correctly to be Track Pitch.On the graph, the Offset field is added to the grid result box.
2. License requirement has been removed from all PRML chip adapter optimization software.
3. The Initial setup in all PRML chip adapter optimization software is disabled by default. If you want to use the initial setup, you have to enable it manually.

The following modification was made in WITE32 version 2.31, but was not reported in all subsequent release notes,

In the configuration menu of the Head Polarity Test, a new parameter Preamp Polarity has been added for you to specify if the test result should be reversed (the polarity is reversed inside the Preamp).

Known Bugs

All the recurring known bugs are reported on our web site, www.Guzik.com. If you encounter a problem that is not on that list, please report it to Guzik customer support at Support@Guzik.com.

There are no new known bugs in this release.