TETware Release Notes v1_1
TETware 1.1 Release Notes
TETware 1.1 is the first customer shipment. Version
1.0 was the customer beta of the GUI only. Our thanks to the TETware
Customers who participated in the beta program.
Version 1.1 adds Wizards to the GUI, the TETware Report
Writer, and an automatic installation mechanism using InstallShield for Java.
The following is a list of release notes for the TETware professional ordered by platform, they outline problems and current issues known at the time of release:
Linux
There are no known issues with the use of the TETware professional
on the Linux platform at the time of release.
UNIX
The following issues are known for Users of the TETware professional
on a Unix based platform:
- It has been noticed that the Solaris Java Virtual Machine has a large footprint for
TETware , generally in the region of 70MB. This can cause problems if the Solaris machine does
not have it's swap space set to the correct size. It is recommended that Solaris Users
configure their swap space file to be at least 200MB. This should provide enough space
for TETware to execute correctly.
Windows
The following issues are known for Users of the TETware professional on a Windows platform:
- There is an outstanding issue with the Hotspot Virtual Machine version 1.0.1. The
following error is displayed and the interpreter exited:
#
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
#
# Error ID: 4F533F57494E13120E435050028D
#
- Abnormal program termination. No explanation of this problem has been found and there is no known work around. The
problem usually manifests itself when loading TETware . It generally occurs more
when TETware has been re-loaded a number of times. If this problem is seen re-loading
TETware generally works.
- The light-weight browser used to display and browse Problem Reports can sometimes trap
and cause an uncatchable exception, this is due to the use of the Java Swing JEditorPane.
The exceptions generated are uncatchable by TETware . However they are only seen if
TETware is started via a DOS-box, if it is started via a shortcut or by double clicking
on the jar file directly then the exceptions are not seen. The exceptions thrown do not
have a detrimental effect on the rendering of the web pages.
|
