Release Notes
WITE32TM
Version 2.21
05/12/99
The 2.21 release introduces new
features and fixes
bugs found in the WITE32 2.20 release. (This document
uses the WITE32 2.20 revision as a base line for comparison.)
New Features
A New Spin Stand Parameter
A new parameter "Manual Unclamp" is introduced in the Guzik
spin stand control program.
By default, the parameter is set to off.
When the parameter is set to on (enabled), the chuck of the
spin stand is clamped unconditionally. When a spin stand is started
for the first time (after powering on or after pressing the red button),
the disk is unclamped, the spin stand waits for 3 seconds, and then
clamps the disk. This is done for safety, to prevent the start of the
spin stand with an unclamped disk put on the clamped chuck by mistake.
You can disable this feature. If the "Manual Unclamp"
option is off, then the spin stand Clamp/Unclamp operations are
the same as in WITE32 2.14.
WITE32 Results Processor Engine
Since the new Result Processors keeps the data in the memory, you need
to ensure that the Windows swap-file has enough size to handle virtual
memory properly.
GTE recommends that you change the Windows Settings
| Control Panel | System | Performance | Virtual Memory to a minimum
of 128Mb.
Fixed Bugs
The following bugs have been fixed:
- NLTS tests can not go higher than 415Mflux (2.4 bit period) on RWA2550.
- WITE cannot distinguish between parameters that are disabled for normalization, which results in the error message "Missing normalization coefficients".
- After running a Standard production test and a Gold production test WITE displays the error message "Qualified Gold records cannot be found"
- The M16 PRML channel causes very long delay (up to 1min) while switching between zones.
Known Bugs
GTE is actively working to solve known bugs. If you encounter a problem not on this list, please report it to Guzik customer support.
- Control | ScopePoint Scope Point 4 is not displayed in Edit Mode.
- While running Production Standard test the error message "No current record" shows up if "Grading" or "Normalization" was turned on. The workaround is to disable temporarily the Normalization and the Grading.
- If a user deletes the last and the second from the last Normalization record, then WITE enters into a long loop of meaningless error messages like "Object ~~ Method ~~ has failed". The workaround is to delete the records beginning from the top.
- If a Production test is canceled then the subsequent runs of any test will never display the "Raw data". The workaround is to restart WITE after Production test is canceled.
|
