XLitePro Version 1.3 - XServer for windows
Date: 12 July 2004
Labtam is pleased to present a new software update for XLitePro now Version 1.3. This is the second major release for 2004.
Integrating the Microsoft Windows and X-Window System environments XLitePro is an inexpensive but powerful and effective way to transform a standard PC into a fully functional X-terminal.
Included in the package are the X-Window System, TCP/IP, TFTP and TELNET.
New Features on this release include
The following enhancements have been made
- implemented the "-auto2" option for "setup.exe". This is the same as "-auto" option with the only difference: the Finish dialog message is suppressed.
- implemented the "Enable TCP/IP KeppAlive mode" setting
- implemented the "Enable Logotype" setting
- implemented the randomized RLOGIN initial portnumber to avoid possible rejection of connection
- implemented the "Auto" mode of the "DisplayNumber" setting. Free Display Number will be auto-generated
- implemented the "Auto-reject unauthorized X-Clients" setting to "silently" reject unauthorized X-Clients
- implemented the "Keyboard Mapping for Linux" setting to provide "close-to-Linux" keyboard mapping. This would be useful for some applications of KDE 3.x package (say, "kwrite" editor) that do not recognize correctly some keys (e.g. "Shift"+arrows conbinations)
- improved the XDMCP usage from PC that has more than one IP address
- improved the output of the "Trace Fonts Requests" setting to show the real fontnames used
- now output log files for different Display Numbers have different names
- added starting of xfontsel in the XServer's "Run" menu
- implemented the "PrStat()" keyboard Macros to output useful additional information at any time
The following bugs have been fixed
- the "Xwpwsock.dll" incorrectly provided the "writev()" action in rare cases
- incorrect using of the multimonitor configuration when Monitor#2 set to left from Monitor#1
- implemented more accurate processing of the LocalRefresh after XStoreColors operations
- implemented the "Auto-start XwpPeg Package Watcher" setting to provide the corresponding control of the XwpPeg facility.
- to input any text into the command line before its executing, the "$(INPUTLIP)" macros can be used. E.g., if the "Command" field contains the following line:
"xterm -display $(INPUTLIP):0" then you will be prompted to input a text string (an IP address is assumed). If you enter "22.214.171.124", then the resulting command line will be:
xterm -display 126.96.36.199:0 .
- the "DontUse_MOTIF_WM_HINTS=1" line can be inserted into the "[XSERVERdeb]" section of the xwp.ini file to prevent the "_MOTIF_WM_HINTS" windows property from processing;
- the "DontCheckWM_SIZE_HINTSinc=1" line can be inserted into the "[XSERVERdeb]" section of the xwp.ini file to prevent the "WM_SIZE_HINTS" windows property from processing;
- the "ILikeLINUX=1" line can be inserted into the "[XSETUP]" section of the xwp.ini file to set up the LINUX's console keyboard mapping;
- the "MyIP=?" line can be inserted into the "[network]" section of the xwp.ini file to allow the manual input of a local IP address when the XServer is started.
- the uninstallation procedure does not remove components which were installed in additional (non-first) installation sessions. Such additional components should be removed manually.
- drawing partial arcs can be very slow;
- the CDE/XDMCP of the HP-UX host can provide infinite waiting for connection. To avoid this, the new "HP" fonts alias directory should be included into the XServer FontPath;
- the "Forced Backing Store" setting can provide wrong screen re-displaying in some cases (e.g., Netscape scrolling).
Single User licenses are at $65.00 USD. Please visit the Software Pricing page for pricing on Multiple Licenses.
If at anytime you require any information or assistance please do not hesitate to e-mail us at: sales@Labtam-inc.com
Download and try XLitePro software for FREE. (Demo version runs 60 minutes at a time.)
The programs associated in this package may send and/or receive broadcast IP requests. Since such packets cannot cross the nearest firewall/gateway/router, please be sure that these IP requests are invisible from outside your network. We assume that such behavior cannot be considered as "Hacking" or "Trojan horse's action".