XVision Desktop on Windows NT 3.51


[Home] Home > Blog >
XVision Desktop on Windows NT 3.51

Playing around with XVision Desktop.

1. XVision Desktop

I have spent a bit of time playing around with Visionware's XVision now, but so far I have held off doing anything serious with XVision Desktop. I think now is a good time to rectify that.

1.1. What is it?

At first I thought it was something similar to IXI's XDesktop, but it seems I was wrong. It does feel inspired by XDesktop (and by OS/2's desktop system), it's more of a way to manage multiple connections and applications across multiple hosts. There are some bad points, but for the most part it is pretty useful.

1.2. How it works

It seems that everything is stored inside a database (which feels very similar to NetInfo), with XVision Desktop providing links to XVision components that use this database and command-line arguments to spawn the right module (e.g. VT320) or connect to the relevant system via telnet, or rlogin, or whatnot. It saves one the effort of using XDMCP, logging into a host, then using telnet/rlogin/rexec manually.

There are some caveats to this, but we'll reach those later on.

2. Initial launch

When first launched, you will be presented with a view that looks not entirely dissimilar to this:

XVision Desktop

Depending on how you set things up, you might only have some pre-defined icons, or you might have a lot. More on this later, as this is one of the major flaws with XVision Desktop.

You can see here that I have a few hosts set up. Solaris, DEC Ultrix, DEC OSF/1, SCO ODT (OpenDesktop), and UnixWare.

The Solaris, OSF/1, ODT, and Ultrix groups were set up by the installer, and I built the UnixWare group by hand. This is hinting at the major flaw. More on this later. No, really.

2.1. Hosts group

This is probably your most important group, as it lists all hosts that have been defined for use and allows you to configure their transport, remote execution, and login options. It would generally be best if each host with which you interact had its own host as this saves you time in the long run.

To see how to add a host, check out my post on Visionware XVision's VT320 emulator.

2.2. Local Applications

XVision Desktop is capable of replacing Program Manager, so it sets up some common-used Windows applications in this group for you. There doesn't seem to be any way to import groups from Program Manager, but there is a way to export to Program Manager. This is useful if you only use the desktop app to configure remote sessions, as doing this is pretty hard with Program Manager–although there is a tool that you can use for this.

Local Applications

2.2.1. Adding applications directly to Program Manager

When exporting X applications to Program Manager, the shortcuts are set up to execute \xvision\xps.exe. If we launch XPS directly, we get a tool that allows us to create links directly in Program Manager.

Program Starter

As a test I filled in the details for /usr/dt/bin/dtpad, saved it as c:\xvision\test.xps and then selected Copy to Program Manager from the File menu.

This created a dtpad icon in the Visionware group in Program Manager which would cause dtpad to launch, so mission successful there. However it appears to be for X apps only. VT320 applications launch via \xvision\deskrun.exe and seem to use an arbitrary identifier–probably linking to an entry in XVision's database.

It appears that you can also create new program group entries with commands similar to:

c:\apps\xvision\xps.exe /c /usr/local/bin/lemacs /h yamato /d /n

and it will launch the respective command.

2.3. XVision Utilities

This is an interesting one, and shows one of the features that I think was inspired by either IXI XDesktop or OS/2 or both. This group allows you to start the X server, access the file transfer, print manger, fonts, etc.

XVision Utilities

The XVision Server icon has unique menu that allows you to access the relevant section in the X server control panel.

X server settings

3. The Big Problem

You are given the option to add hosts during installation of the "communications" component. Then you can then set the type of each host (Solaris, SCO Unix, OSF/1 et al) which will populate an XVision Desktop group with a set of defaults for that specific host type.

And here is the problem.

This only occurs during installation. You cannot add a new host and select, say, SCO Unix and have a group automatically created for that host with preset applications once XVision is installed. You'd have to re-run the installer.

Although, I am probably making this seem like a bigger deal than it actually is–most of the default groups are for pretty old versions, e.g. UnixWare is for USL UnixWare 2.x, Solaris is for systems older than Solaris 2.6, and so on.

4. Solution to the Big Problem: Ignore It.

Unless you happen to be running Solaris 2.5, UnixWare 2.1, OSF/1 4.0, you'll probably want meaningful apps to be set up anyway (e.g. CDE's dtterm on Solaris 9 instead of OPENLOOK's cmdtool/shelltool), so let's simply ignore the fact that we have to set up our groups on a host-by-host basis, by hand, one application at a time :)

4.1. Adding an X application

I feel the urge to set up XEmacs in my OSF/1 group. Let's do it.

First, let's right-click somewhere in the group to get the context menu and select New Item and then X Application,,,

New X Application

Then we fill out the host and the command. In this case, korolev is the name of my OSF/1 host, and XEmacs is available at /usr/local/bin/xemacs.

XEmacs details

Now we can spend hours struggling to find an icon worthy of Emacs.

XEmacs presentation settings

I never really did find one. Perhaps I need my own icon library. However, there should now be a perfectly-usable link to XEmacs in the group that we can execute.

Double-clicking on it yields

Mission Success

Naturally I am now creating this blog post in XEmacs running on Digital UNIX 4.0. But you already guessed that the second you saw me mention Emacs, right?

5. Other icon types

5.1. VT320 Applications

Icons of this type allow you to run text applications via the inbuilt VT320 emulator, i.e. vi, ksh, and so on.

Setting one up is pretty simple. First, right-click for that context menu, then select New Item and then VT320 Application…

New VT320 Application

Then, fill out the host and the command you wish to execute.

Host and command deets

And then you should be able to launch your text app!

Host and command deets

You can also use this to set up a telnet connection to a remote host as documented in Visionware XVision's VT320 emulator.

5.2. X Server

This isn't what I thought it was. When I saw this, I assumed it would allow me to configure an X server instance for a particualar host. "Aha," I thought, "multiple X sessions!" Multiple window locally managed X server for day-to-day use, and an X server running an XDMCP direct query to a remote host. Kinda like how one could use Xephyr or Xnest.

No, I was wrong. This is simply a link to a global X server. Creating an X server for a host (single-window, XDMCP) will result in XVision's settings being set to whatever you set. I find this a crying shame, especially given that XVision Eclipse solves this by allowing multiple X server profiles.

5.3. Document

This allows you to add a group item linking to a local document. It does not seem to support remote documents without the aid of, say, PATHWORKS, VisionFS, PC-NFS, Samba etc.

5.4. Connection

This allows you to add a non-TCP/IP connection to a remote host. If you utilise Visionware's PC-Connect, or NCD's XRemote, you can set up connections here.

As I have neither of those (yet), I have no idea how they work or how they're set up. I do know that XRemote requires a second license if installed with XVision.

5.5. Application Advertizer

Now this is a complete mystery to me. This appears to be something provided by UnixWare 2 (both USL and SCO).

I did have a poke around various UnixWare 2 media (including UnixWare 2.1 Application Server, which I think was the target for this feature), and I found the paths it refers to (/usr/X/lib/app-defaults/.exportApps), but it was an unexpected thing.

At first, I assumed that it might be something akin to NFS exportfs (i.e. /etd/dfs/sharetab, /etc/exports et al) in that you could specify an app and its local path, but upon inspection of the directory layout in UnixWare 2, it's full of binaries.

Technically speaking I could probably run these binaries on UnixWare 7, but it probably requires a more complicated setup than just plonking some files in a directory and hoping for the best.

I would like to set up UnixWare 2 either on a real machine or in a virtualised environment at some point, so I will ensure that should that happen then this feature gets tested.

6. Final Thoughts

I do like XVision. I would love to speak with the people behind this creation, to find out its history, and if it's inspired by IXI's XDesktop or OS/2.

I can't help but feel that I'm missing out on more functionality by not having TermVision installed with XVision 6, but that can be solved once I figure out how the licensing for TermVision works.

It must be said, though… I'm perfectly happy running XVision alongside Kea! on Windows NT, and XVision alongside Reflection and Procomm Plus on Windows 3.x.

Return to top


Made with weblorg
Copyright © 2010-2024 Paul Ward.