|
Release notes
WITE 1.84
Introduction
This document contains the release notes for WITE revision 1.84 from Guzik Technical Enterprises. WITE 1.84 is a maintenance release which provides bug fixes only.
All discussion of features and bugs in this document uses WITE version 1.83 as a baseline for comparison. For information about features and modifications prior to 1.83, please refer to the WITE user’s manual and to the release notes for previous revisions of WITE.
Bugs fixed in WITE 1.84
In production mode, power could remain on to the preamp for some time after the head was returned to the home position. This could cause damage to GMR heads when they were removed. WITE 1.84 always turns off the power to the preamp before moving the head to home position.
Head stacks were previously limited to a serial data packet length of 16 bits. This limitation has been removed in WITE 1.84, allowing more head stacks to be supported in the future.
The results of PW tests (PW50, PW asymmetry, MR saturation) could be incorrect when context was enabled from WITE 1.8 to WITE 1.83. Incorrect results were only obtained when consecutively tested good heads varied in signal amplitude by more than 4dB. In WITE 1.84, PW measurements are always accurate whether context is enabled or not.
When ASCII output was enabled in production, a failed test could cause subsequent test results to be incorrectly attributed to the failed test. This bug was introduced in WITE 1.71 and has been repaired in WITE 1.84.
Known bugs in WITE 1.84
Some bugs were found too late to be fixed for this 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.
|