|
Release Notes
WITE 1.8
Introduction
This document contains the release notes for WITE revision 1.8 from Guzik Technical Enterprises. The highlights of revision 1.8 include:
- Support of RWA2550++ model
- Support for new head amplifier and head stacks
- Bug fixes
All discussion of features and bugs in this document uses WITE version 1.71 as a baseline for comparison. For information about features and modifications prior to 1.71, please refer to the WITE user’s manual and to the release notes for previous revisions of WITE.
New Features in WITE 1.8
Support for the 2550++
WITE 1.8 supports the RWA2550++, with the following functionality:
- PRML chip integration with data rates 800 Mbits/sec.
- Fast PRML channel optimization
- 800Mflux/s programmable Pattern Generator
- Bit precompensation with 20ps resolution
- 400MHz bandwidth Spectrum Analyzer
- Bit shift analysis 250 MFlux/s (333Mbit/s with 1-7 code) Optional
- All industry-standard parametric tests
Support for new head amplifiers and head stacks
The following head amplifiers were supported in WITE 1.8:
- VM61868
- VM620212
- KATANA
- 623206_3654CPOL
- REGTDA5360GR
- RRVM620212E2
- 623206_3654MRRM
Bugs fixed in WITE 1.8
If the "skip failed head" runtime grading option was enabled, a failed head still was graded as "passed". WITE 1.8 marks this situation "failed."
Previous versions of WITE did not allow Guzik Spinstands’ RPM to be set below 500. WITE 1.8 allows lower rotational speeds to be selected.
In WITE 1.71, the Alternative Spectral Elimination test reported incorrect result names, making them non-gradable. WITE 1.8 allows the results to be graded.
In the scanning retry threshold list, the last threshold was always reported when an error was detected during retry. WITE 1.8 stops retrying whenever a threshed setting gives some errors and reports that threshold.
Known bugs in WITE 1.8
Some bugs were found too late to be fixed for the 1.8 release and will be fixed in a later release. This section contains all known bugs that you are likely to encounter. A bug’s presence here means that we are aware of the problem and actively working to solve it. If you encounter a problem not on this list, please report it to Guzik customer support.
After changing the product alignment parameters in WDCP (track pitch, number of tracks, etc.) WITE won’t use the updated parameter values until the current product is reloaded.
Scanning can cause system errors when too many errors are reported into the result flow.
Some DOS applications interfere with communication with Guzik hardware and can result in unstable test results. Please exit all DOS applications before running WITE.
| 
