WITE32™
Version 2.32
8/11/99
The 2.32 release introduces new features,
and fixes bugs found, in the WITE32
2.31 release. (This document uses the WITE32 2.31 release notes
as a base line for comparison.)
New Features
- PRML chip adapter software now supports 2 types of write data formats: NRZ data, and narrow pulses on every edge of NRZ. Previously only narrow pulses on every edge of NRZ was supported.
If you use the new style chip adapter, e.g. M16+, and select its chip related patterns, then the divider in the universal interface, or Guzik universal interface, will be turned off, and data will be represented in NRZ format. If you use the old style chip adapter, e.g. Venom, and select Guzik pattern generator related patterns, e.g. HF, then the divider(s) will be turned on, and write data will be represented as edges of the NRZ data format. In order to take advantage of this feature, you have to order from us the "Guzik Head Amplifier without flip-flop" (Guzik MR Head Amplifier #4 family).
WITE32 selects NRZ data format whenever it is possible, because it allows hardware to work with higher data rate
- A new option called "TstDone" is added to the "Write Pattern" operation, which is selectable within a production test sequence. This option allows you to choose from a combo box between Restore Original Pattern, or Keep Test Pattern after a pattern has been written.
Fixed Bugs
The following bugs have been fixed:
- Final grading may assign a wrong grade, when multiple grades are defined and enabled, and that each grade is configured to grade on a different test results.
NOW: Final grading is performed correctly on multiple grades.
Known Bugs
If you encounter a problem that is not on this list, please report it to Guzik customer support at Support@Guzik.com.
- 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 (found in 2.22).
The workaround is to shutdown and restart WITE32. If it is possible, never install a module twice. In particular, never install WNorm.exe, WGrade.exe, WResult.exe, and WControl.exe—these modules are installed automatically by WITE32.
- When user specifies an output file name with a different extension other than WEX, the common dialog box will append WEX as the file extension to it.
The workaround is to choose "All (*.*)" to be the filter ("Save as type").
- Creating a product using multiple words for product directory name, e.g. "C:\WITE32\Product One", causes the following error when running "Run Alignment Program" under "Configure | Device" (found in 2.25),
WDCP: Path not found
Workaround: Use underscore "_" to replace any blanks between words, e.g. "C:\WITE32\Product_One".
- Intermittent problem arises when creating new zone. The following error message may pop up (found in 2.25),
WITE: Couldn’t save; currently locked by user ‘username’ on machine ‘machine name’. Abort/Retry/Ignore.
Workaround: Press Ignore, exit WITE32, and try again.
- If a second WITE32 is started shortly after the first WITE32 is completely closed, the following error message may pop up (found in 2.25),
…duplicate instance: Invalid procedure call or argument. Abort/Retry/Ignore.
Workaround: Press Abort. Wait approximately 15 seconds between two WITE32 sessions.
|
