Release Notes
WITE32TM
Version 2.23
05/25/99
The 2.23 release fixes
bugs found in the WITE32 2.22 release. (This document
uses the WITE32 2.22 revision as a base line for comparison.)
New Features
None.
Fixed Bugs
The following bugs have been fixed:
- The statistical test results of a previously aborted test are displayed together with the results of the current successful run.
NOW: When a test is now aborted, the aborted results will not be introduced into the results of your subsequent test.
- Add back the feature to grade all results whether the head passes or fails. This will generate all failing results for all heads.
NOW: The feature has been re-introduced into WITE32.
- When the Bitshift test is executed from the Track Profile test, each call to this test generates a set of configuration parameters. Eventually, the config grid has a lot of columns and will slow down the test result display.
NOW: Only one set of configuration parameters are displayed.
- In Popcorn test’s baseline shift, the length of the clamp signal extends beyond the start of the read gate.
NOW: The clamp signal does not extend beyond the start of the read gate, and has a maximum value of 4 ms.
Known Bugs
Guzik Technical Enterprises is actively working to solve known bugs. If you encounter a problem not on this list, please report it to Guzik customer support at Support@Guzik.com.
- Control | ScopePoint Scope Point 4 is not displayed in Edit Mode. (found in 2.15)
No workaround.
- Importing a product to replace a "Protected reference" product will cause this (originally protected) product to be unprotected.
The workaround is to check the "Protected Reference" checkbox again. (found in 2.21)
- Installing a module twice will disconnect the module completely.
The workaround is to shutdown and restart of WITE32. If it is possible, never install a module twice. (found in 2.22)
- Closing a plot window before the test has completed plotting makes WITE32 hang until the test is aborted. (found in 2.22)
The workaround is to abort the test first and then close the plot window. Do not assume that you can close a plot window while a test is plotting.
- Missing or mixed-up grading results were displayed when two or more heads were used in a production test with multiple setups.
The workaround is to run in single head only mode, or to run with a single setup per zone only. (found in 2.22)
- Selecting one out of two or more grade names results in an error message: "Wgrade>Duplicate Grade name: ‘grade name."
The workaround is to press the OK button on the error message. (found in 2.22)
- Renaming a grade name results in an error message: "Wgrade>Duplicate Grade name: ‘grade name."
The workaround is to press the OK button on the error message. (found in 2.22)
- When many grading-related windows (grading limit, grading definition, grading result, failure result) are left open, and then you run the Production Test, you trigger either one or both of the following error messages:
Ggrid> Automation Error
Ggrid> Invalid procedure call or argument
All the GGrid outputs become slashes. WITE32 crashes. This is intermittent, and the problem cannot be reproduced every time. (found in 2.22)
No workaround, because we don't know the exact cause of this problem, nor do we know the exact conditions that cause the problem.
- After some rare runnings of two tests, incomplete raw test results were displayed or garbled with the following error message:
Wresult> Permission denied.
There is no workaround. Select the "Reset Format" menu item on the result window may help. Try to run the test again. (found in 2.22)
|
