I run Personal Alpha emulator on a PC, running OpenVMS 7.2 (the Alpha,
not the PC)
VMS TCTIP is 192.168.1.200
PC is 192.168.1.11
Emulator Interface is set to shared.
Everything works fine, thanks to all of you.
But one thing, I do not "remember" how to map my screen to DECwindows.
I started DECwindows
I did a $ set display/create/transport=tcpip/node=192.168.1.11
then when I start say Mozilla, it sez
Starting mozilla-bin...
Gtk-WARNING **: cannot open display: _WSA0:
I do not remember if I should run an X11 program on the PC.
Thanks for your help. I'll write the HOWTO later.
Didier,
You need to run an X11 display server on your PC (Windows doesn't
include one, although something like Ünix Extensions for Windows [?] may
be downloaded from Msoft for some Windows versions). If you have access
to Pathworks xCursion, that's fine. Xming or any other open source X11
server will do as well.
/Wilm
Didier, Wilm,
the toolkit from Microsoft is called Support For Unix (SFU). The most
recent version is V3.5. This version runs on XP and W2k.
I have no idea whether it works with Vista.
A very good alternative is Reflection X, distributed by Attachmate
(used to be WRQ). Excellent product but costs serious money.
Ebay sometimes offers real bargains, might be useful.
The problem Didier encountered is elegantly solved by Reflection X.
You can start the Xserver on the pc, but that does not start an
application on the remote system (the X client in thee awkward,
counter intuitive X terminology). If you run SFU then you need to
login to the Xclient via a standard VT100 terminal emulator. The
telnet command in XP's cmd is sufficient. Next you have to enter (and
remember) the SET DISP/CREATE/TRANSPORT=.../HOST=... and CRE/TER/DET
commands.
The disadvantage is that you've got to know network details of your
own workstation.
ReflectionX supports XCMP broadcasts. This means that once the Xserver
is running it presents you with a list of Xclients available on your
network.
Select one and you get the same logon screen as shown on a VAX or
Alpha console.
There used to be an X server kit in PCSA/Pathworks. I forgot its name
and have never used it. Perhaps it is now part of the VMS Freeware
kit?
Hans
[snip]
> Didier, Wilm,
> the toolkit from Microsoft is called Support For Unix (SFU). The most
> recent version is V3.5. This version runs on XP and W2k.
> I have no idea whether it works with Vista.
It does not. I checked.
[snip]
> ReflectionX supports XCMP broadcasts. This means that once the Xserver
> is running it presents you with a list of Xclients available on your
> network.
> Select one and you get the same logon screen as shown on a VAX or
> Alpha console.
>
> There used to be an X server kit in PCSA/Pathworks. I forgot its name
> and have never used it. Perhaps it is now part of the VMS Freeware
The Pathworks X11 display server is called xCursion. It's not freeware,
at least has never been, but it *may* be covered under the VMS hobbyist
license. I did not check this.
It is on a Windows CD that comes with the Pathworks distribution.
xCursion supports XDMCP. I would never use it in a business setup
(security issues, beaten to dead in forums here and elsewhere), but for
private / hobbyist use it is very convenient like you explained. It
works under Vista, even the x64 variant thereof.
If anyone can convince me that it is indeed covered by the hobbyist
license, I have the media available. Contact me privately if so desired.
/Wilm
> You can start the Xserver on the pc, but that does not start an
> application on the remote system (the X client in thee awkward,
> counter intuitive X terminology).
The way to undertand this quirk: it is the application which makes the
network connection to the terminal.
The client system runs the application.
The server system runs the X terminal software.
Anyone heard about XMING ? http://gears.aset.psu.edu/hpc/guides/xming/
The X-terminal syste issues an RSH command which runs a .COM on the
target system. That .COM defines DECW$DISPLAY (or SET DISP/CREATE) and
then run/proc=xxx sys$system:decw$session.exe
This way, RSH invokes a procedure which will pop the decw$display on the
X terminal.
What I have done is:
at boot time:
$SET DISP/CREATE/EXEC/TRANSPORT=TCPIP/NODE=MyMac
$DEFINE/SYSTEM MAC$DISPLAY F$TRNLNM("DECW$DISPLAY")
And in my RSH:
> $write sys$output "''f$getsyi("SCSNODE")' starting a decterm on the mac"
> $define decw$display 'f$trnlnm("MAC$DISPLAY")
> $create/term/detached/NOLOGGED
Xming as such is fine, stable.
Takes a little effort to do the correct mapping for the various Digital
(TM) fonts. I finally got it right by running a font server on VMS and
pointing Xming to same font server. Somehow, without that the session
manager menu fonts would not display correctly.
/Wilm
BTW, (the latest version of) Xming is officially available from Colin
Harrison, who wrote it, via
http://www.straightrunning.com/XmingNotes/index.php
Donations are gracefully accepted by Colin for this fine piece of SW.
And guess who provided the translation into Dutch. And who cares...
/Wilm
Good god!!! You complain about XDM and security (which, by the way is not
an XDM problem at all but only an XDM as implemented on VMS problem) and
offer a Berkeley R-command as an alternative!!
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill...@cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
Run eXcursion on the PC use PuTTY on the PC to open an SSH session to
VMS and then your done.
--
PL/I for OpenVMS
www.kednos.com
More likely only an XDM as implemented on VMS by UCX problem.
I don't know, does the Multinet version do the login accounting right?
And I don't even know if TCPWare has XDM.