Frequently Asked Questions About X-Win32 vs FastX
I have X-Win32 under maintenance. Do I have to pay for FastX?
FastX is available to X-Win32 customers at a discount.
FastX is great when connecting from home, but at work I prefer to use an XDMCP connection. Do I need both FastX and X-Win32 to do this?
If you need both X-Win32 and FastX, we offer a combination in which both products are discounted.
What is the difference between FastX and X-Win32 LIVE connections?
LIVE connections are based on the NX protocol, which uses X11 and can be slow over the Internet. FastX uses an RDP process our engineers ported to Linux. FastX has shown to be considerably faster than LIVE.
How are FastX connections different from Exceed OnDemand, VNC or NX connections?
FastX uses the RDP-based protocol. EoD uses a VNC-like protocol and NX is X11 based. All 3 have shown to be slower than FastX in basic tests we have performed with 2D and 3D applications.
Why doesn't the FastX Server support Solaris, HP/UX or AIX?
The Unix operating systems cannot support the RDP protocol on which FastX was designed.
How can I use FastX to connect to applications on a Solaris, HP/UX or AIX server?
You can set up a Linux server with the FastX server installed. Then you can set up what we call a "FastX-Indirect" connection. Once set up, your sessions will automatically connect first to the LIVE server and then onto the application on the Unix host.
I can no longer see my Gnome desktop when connecting with X-Win32. Our SuSE server uses Gnome3.
Linux desktops like Gnome3 are based on the latest OpenGL code that uses the "Direct Rendering Interface" (DRI) where the graphics are processed on the server hardware. Regular X servers cannot see this. Your best option is to switch to FastX which performs great with Gnome3 thanks in part to the RDP protocol, which is not hindered by DRI.
Why is it faster to connect to OpenGL applications on a server on our LAN with FastX and X-Win32 than standard LIVE connections?
The NX protocol on which LIVE sessions are based, cannot use the graphics acceleration from the PC graphics chips. Rendering is done on the remote host in software with only a slight bit of improvement when also using VirtualGL. On the other hand, X-Win32's SSH and XDMCP connections accelerate the 3D graphics on the local machine using the PC's graphics processor. FastX is able to use a different protocol that offers near LAN performance even if the application is running on a server thousands of miles away.
What are some of the key differences between FastX and X-Win32?
- X-Win32 is a traditional X11 based, client only PC X server. FastX is based on the RDP protocol and uses a client-server model.
- X-Win32 connections like XDMCP, REXEC, SSH will cause the remote application to crash if the PC gets disconnected from the network. FastX sessions, under control of the FastX server, keep running on the remote server and users simply reconnect to their sessions.
- X-Win32 has many configuration options due to the complex nature of X Windows. FastX simply displays the server’s graphics output and thus does not require any configurations such as turning on pseudo color support, backing store, etc.