WebTerm X Frequently Asked Questions
Why does my display look incorrect when using WebTerm X?
If your display does not appear correct when using WebTerm X, but does look correct at the Host computer's console, the problem is typically due to the Host or X Client making assumptions about the display mode or capabilities of WebTerm X with out checking. To be compliant with the X11 standard, the data should be sent to the X display server, in this case WebTerm X, in Server Natural Format. This means the host OS or X client needs to check what the display mode of WebTerm X is and then send the data in that mode. If this does not occur, the display will not appear correctly.
This lack of conformity by the Host's OS or X Client is more apparent with the newer WebTerm X 2.0 or greater, than with older X display servers. This is because WebTerm X now uses Microsoft's Direct X to enhance graphics performance. This dramatically increases the speed and quality of the display. However, since Direct X does not evaluate or convert the data, it depends upon the host to send the data in the correct format. On a Unix host, you can run the xdpyinfo utility (which is typically located in your X11 directory) to verify that WebTerm X is reporting its display mode correctly to the host.
Introduced with the older version 2.0.2 and also in 3.0: A special option to convert 24-bit images to 32-bit images during XDM sessions has been added as a work around for those hosts that do not recognize X servers such as WebTerm X that can run into 24-bit color depth. This option is available on the Session Tab when configuring an XDM session in the WebTerm X Administrator. If this workaround does not resolve your display problem, please contact your host OS or X Client vendor and notify them of the discrepancy with the X client not sending it's display in server natural format.
Some examples of display discrepancies caused by the Host not sending the display data in Server Natural Format include:
Symptom: The icons or images are the wrong size and or distorted.
The problem is caused by the images being sent to the X server in an incorrect color depth or resolution. In xdpyinfo, the correct color depth and resolution are listed for the screen in question.
Known example: CDE 1.2 toolbox icons on Sun Solaris 2.6 when the Windows computer is in 24 bit color mode.
A possible work around is selecting the configuration option in the WebTerm X administrator to convert 24-bit images during XDM sessions under the Session Tab or changing the color depth of you Windows display to the one that is assumed by the X client.
Symptom: The image is vertically rippled, chopped, or striped.
Data is being sent using the Most significant Bit format (MSBFirst) instead of the reported Least Significant Bit format (LSBFirst), so that the value of a data byte is 12345678 instead of 87654321. this means that every 8 bits of image on the display will be inverted. In xdpyinfo, this is reported as "image byte order".
Known example: Sun Solaris 2.6 CDE 1.2 opening splash screen.
Symptom: The image is missing colors or displays the wrong colors.
The X client may be trying to use pseudo color to assign specific values to one of 256 possible colors even though WebTerm X is reporting that it is not in 256 color mode. To use pseudo color or cell based colors, the Windows computer must be in 256 color mode, and the value assigned can not be to the protected colors of black or white. In xdpyinfo these protected colors are reported as "pre-allocated pixels".
Please note: If you are using WebTerm X version 3.0 you can change the color setting within WebTerm X now. View the following FAQ: How do I change the color setting for WebTerm X version 3.0.
Should you have any questions or issues please use our Support Request Form.
NOTE: For discontinued products or products no longer in development, contact Sales at 603.880.9118 or via e-mail at: sales@powerlan-usa.com.
|
