Sujet : Re: simh and xdmcp
De : JKB (at) *nospam* hilbert.invalid (JKB)
Groupes : comp.os.vmsDate : 01. Jun 2025, 17:34:26
Autres entêtes
Organisation : NUO - News.Usenet.Ovh
Message-ID : <slrn103p08i.v83.JKB@hilbert.systella.fr>
References : 1 2 3 4 5 6 7 8
User-Agent : slrn/1.0.3 (Linux)
Le 27-05-2025, jayjwa <
jayjwa@atr2.ath.cx.invalid> a écrit :
JKB <JKB@hilbert.invalid> writes:
>
I don't understand difference between BSD export DISPLAY && xterm
and VMS set/display followed by mcr. There is no firewall on LAN.
There's not one. Those are the correct commands. From 192.168.20.1 to
192.168.20.3. I left the xkeyboard and font errors in for completeness.
>
≻ Xephyr :1 -ac -listen tcp -screen 1024x768 -from atr2.lan &
≻ The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Could not resolve keysym XF86RefreshRateToggle
Warning: Could not resolve keysym XF86Accessibility
Warning: Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
r rlogin lunast
[TNDRIVER: Proxy login for user "jayjwa" in progress ...]
>
$ set display /create /node=192.168.20.1 /transport=tcpip /server=1
$ show display
>
Device: WSA19: [super]
Node: 192.168.20.1
Transport: TCPIP
Server: 1
Screen: 0
>
$ mcr decw$clock
X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
X Toolkit Warning: Cannot convert string
"-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
I have tried without success:
hilbert:[~] > Xephyr :1 -ac -listen tcp -screen 1024x768 -from fermat.systella.fr
$ set display /create /node=192.168.10.103/transport=tcpip /server=1
$ show display
Device: WSA1: [super]
Node: 192.168.10.103
Transport: TCPIP
Server: 1
Screen: 0
$ mcr decw$clock
X Toolkit Error: Can't Open display
%DWT-F-NOMSG, Message number 03AB8204
Same error.
(decwclock shows). You may have to consider your install/software kit is
faulty if you are otherwise able to make TCP connections to/from the node.
No firewall, all ports opened in both directions.
Host that runs simh (Rpi 3B running Linux Devuan) is able to open X
applications on Xephyr.
My version of simh was built from source (
https://github.com/simh).
$ @DECW$VERSIONS.COM
DECwindows ident is DW T1.2-6010221
DECwindows server ident is DW V7.1-010215
DECwindows transport ident is DW V7.3-010215
DECwindows xlib ident is DW T1.2-6010221
DECwindows OSF/Motif Toolkit ident is DW T1.2-6010221
DECwindows apps ident is DW V1.2-6010221
DECwindows programming ident is DW T1.2-6010221
Here:
$ @SYS$UPDATE:DECW$VERSIONS
DECwindows ident is DW T1.2-6010221
DECwindows server ident is DW V7.1-010215
DECwindows transport ident is DECWINDOWS V5.4
=> not yours : DW V7.3-010215
DECwindows xlib ident is DW T1.2-6010221
DECwindows OSF/Motif Toolkit ident is DW T1.2-6010221
DECwindows apps ident is DW V1.2-6010221
DECwindows programming ident is DW T1.2-6010221
$ product show product tcpip
----------------------------------- ----------- ------------
PRODUCT KIT TYPE STATE
----------------------------------- ----------- ------------
DEC VAXVMS TCPIP V5.1-15 Full LP Installed
----------------------------------- ----------- ------------
>
1 item found
$ product show product tcpip
----------------------------------- ----------- ------------
PRODUCT KIT TYPE STATE
----------------------------------- ----------- ------------
DEC VAXVMS TCPIP V5.3-18 Full LP Installed
----------------------------------- ----------- ------------
I suppose there are some differences between DECWINDOWS V5.4
transport and DW V7.3-010215. If I remeber, I have installed X from
official OpenVMS 7.3 CD... Where can I find DW V7.3-010215 ?
Best regards,
JB
-- Si votre demande me parvient en code 29, je vous titiouillerai volontiersune réponse.