|
|
JET 6530 Documentation > Troubleshooting
General troubleshooting
Solutions to the following common problems are
provided in this page:
Description: JET 6530 does not work correctly running
under Internet Explorer 3.0 or Communicator 4.04.
Cause: JET 6530 does not support these browsers.
Corrective Action: Run JET 6530 under a
supported
environment.
Description: Even though a new version of JET 6530 has been
successfully installed, JET 6530 is
still behaving exactly as it did
for the previous version
Cause:
Browsers store loaded applets in their memory,
and continue to
use this code even if the Reload button is clicked, or the memory
and/or disk cache is cleared.
The most recently installed version of JET 6530 may
have an older version number than the previously installed
version (for example, you previously installed an early
release but recently "fell back" to an older generally
available release). In this case Internet Explorer and the
SmartUpdate scritps provided will not install the older JET
6530 class files.
The "useseslibarary" applet parameter in the web page
you are using does not match the version number of the new
version. Internet Explorer continues to use JET 6530
class files installed previously.
Corrective Action:
Restart your browser, and reload the web page
or page on the local
hard drive that contains the reference to the JET 6530 applet.
Delete all old versions of JET software.
Remove the installed class files, for instructions see
Working with
installed class
files. Then restart your browser and reload the web page
that loads the JET 6530 applet.
Change the "useslibraryversion" applet parameter in all
of your web pages to match the distribution unit version of
the new version of JET 6530. See
Creating a web page
which will load JET 6530 for details.
Description: Microsoft Internet Explorer was unable to load the JET
6530 applet.
Cause:
The browser has been configured to disable its Java support
The browser could not find the JET 6530 applet files on
the web
server or the local hard drive
A network communication error occurred while the browser was
loading the applet files
Corrective Action:
Enable Java support. To do this, from the "View" menu select
"Options...", select the "Security" tab. Click the "Enable Java
Programs" box (in the "Active content" area) so that a tick is placed
there.
Ensure that the <APPLET> tag within the web page that was
loaded correctly refers to
com.platypuspartners.jet6530.JET6530.class and
JET6530.cab. Refer to Configuration for more information.
Ensure that all of the JET 6530 class files are
correctly installed
on the web server or local hard drive
Ensure that there is a stable connection between the browser and
the web server
Description: The JET 6530 applet starts, and displays a screen
containing the text "Connecting...", but does not get any further.
Cause:
The Domain Name Server used by the
browser may be down or unable to
resolve the name of the NonStop Himalaya server.
There may be no TN6530 Server program listening
on the specified port
on the NonStop Himalaya server.
A network Firewall may be preventing access
to the NonStop Himalaya server.
Corrective Action:
Ensure that the Domain Name Server
used by the browser is active and
able to resolve the name of the NonStop Himalaya server.
Ensure that there is a Telnet Server program listening
on the port to
which the JET 6530 applet is trying to connect. The default port
number is 23. The <APPLET> tag that refers to the JET 6530
applet may
override this value by containing a <PARAM NAME="port" ....>
tag. Refer to
Configuration
for more information.
Ensure that there is no firewall preventing the
system on which the
browser is running from reaching the NonStop Himalaya server.
Description: A dialog box with a message like "Could not execute
print command: [Ljava.lang.String;@805202f" appears after clicking
Print on the print dialog box when running JET 6530 under
Communicator on Linux. Clicking OK dismisses the dialog box but
the terminal screen is not printed.
Cause: Communicator for Linux does not support printing from Java
applets properly.
Corrective Action:
Login as root on the Linux machine.
Create a /usr/bin/lp file with the
following contents:
#!/bin/sh
if echo $1 | grep '^-d' > /dev/null
then
modified="`echo $1 | sed s/^-d/-P/`"
shift
set -- "$modified" "$@"
fi
if echo $1 | grep '^-t' > /dev/null
then
modified="`echo $1 | sed s/^-t/-J/`"
shift
set -- "$modified" "$@"
fi
if echo $2 | grep '^-t' > /dev/null
then
original1="$1"
modified="`echo $2 | sed s/^-t/-J/`"
shift; shift
set -- "$original1" "$modified" "$@"
fi
exec /usr/bin/lpr "$@"
Set the file's ownership and permissions with the following commands:
chown root:root /usr/bin/lp
chmod 755 /usr/bin/lp
This workaround does not handle the "Copies" or "Print Command Options"
fields on the print dialog box having values other than their defaults.
Description: Double-clicking an HTML file to start Communicator
and load JET 6530 under Windows results in two JET
6530 applets running.
Cause: The default "open" action performed by Windows when
opening an HTML file when Communicator is the default browser
passes the file both as a command line argument and as a DDE
message. Because of this Communicator loads the HTML page twice,
resulting in two JET 6530 applets.
Corrective Action:
Edit the default open action so that it does not use DDE using
the following instructions. Start Windows Explorer. From the View
menu select Options.
Select the File Types tab. Find Netscape Hypertext Document in the
list of registered file types, select it and click Edit. Select
the open action and click Edit. Remove the tick from the Use DDE
check box. Click OK, Close and Close.
Description: Solid black rectangles are displayed at the top
of the right hand side of the Session Settings and Preferences
windows under Communicator under Linux in an 8-bit colour
mode. The rectangles do not show the title of the current
category.
Cause: With an 8-bit colour mode Communicator does not
allocate different colours to the category title text and
background colours, both are black.
Corrective Action:
Change to a 16-bit or higher colour mode.
Start Communicator specifying the "-install" command
line option. Communicator will install a private colour map
and allocate different colours to the text and background.
However, when Communicator or JET windows are active
colours in other application's windows will be incorrect and
vice versa.
Description: Keys pressed are not processed after the JET
6530 window is resized (for example, as a result of
connecting or changing between
block and conversational modes)
under Communicator under Unix.
Cause: The problem is due to a bug in Communicator. After the
JET 6530 window is resized it loses the keyboard focus.
Corrective Action: Click in the terminal window to restore key
processing whenever the problem occurs.
Description: The Ctrl+Pause key combination is received as Ctrl
by JET 6530 under Communicator under Linux. For example,
when the Add Key Combination dialog box is open typing Ctrl+Pause
(pressing the Pause key while holding the Ctrl key) displays Ctrl
next to Key Combination.
Cause: Under some versions of Linux the
default X keymap does not map the keycode generated
by Ctrl+Pause to a keysym. This means Communicator cannot
identify Ctrl+Pause properly to pass it to JET 6530.
Corrective Action: Change the X keymap so that the Ctrl+Pause
keycode is mapped to the Pause keysym. Under Red Hat 6.0 the keycode
is 114. The following command changes the keymap:
xmodmap -e "keycode 114 = Pause"
To make this change permanent place the command or the string
in quotes in the appropriate X init file. For a default Red Hat 6.0
installation put the string in quotes in .Xmodmap in your home
directory.
|
