Re: simh and xdmcp

Le 24-05-2025, jayjwa <jayjwa@atr2.ath.cx.invalid> a écrit :

JKB <JKB@hilbert.invalid> writes:
>

I'm trying to configure XDMCP on OpenVMS 7.3/VAX (running on simh)
and I'm unable to obtain a running configuration.
>
X server is Xephyr running on hilbert (192.168.10.103). In a first
time, I have configured xdmcp on a foreign NetBSD server
(legendre, 192.168.10.128).

>
Which TCP stack are you using? The Compaq one that comes with 7.3 is so
old that only older things like PathWorks v7.4 under Windows or the
Microvax2000 booted as a VXT off an Infoserver can catch the
display. Something must have changed between then and now. The Multinet
one you can catch with modern setups. At least this has been my finding
after wrestling with it.

$ product show product tcpip
----------------------------------- ----------- ------------
PRODUCT                             KIT TYPE    STATE
----------------------------------- ----------- ------------
DEC VAXVMS TCPIP V5.3-18            Full LP     Installed
----------------------------------- ----------- ------------

Under X11, I could use either Xephyr or Xnest. Now under Wayland only
Xnest "works", with some issues (windows don't move/resize properly). I
have no experience with BSD to VMS: only Linux, Windows, and Solaris.

I use X11.

Xephyr :1 -ac -listen tcp -screen 1200x800 -from atr2.lan -retro -query
kirin.lan
>
Xnest :1 -ac -listen tcp  -from atr2.lan -retro -query kirin.lan
>
"-ac" turns off access control; you don't have to use xhost.
>
$ show display
>
    Device:    WSA2:    [user]
    Node:      192.168.20.1
    Transport: TCPIP
    Server:    1
    Screen:    0
   
$ spawn /nowait mcr sys$system:decw$clock

I have tried with Xnest with the same result:

$ set display/create/node=192.168.10.103/transport=tcpip/server=1
$ show display
 
    Device:    WSA17:  [super]
    Node:      192.168.10.103
    Transport: TCPIP
    Server:    1
    Screen:    0
 
$ mcr sys$system:decw$clock
X Toolkit Error: Can't Open display
%DWT-F-NOMSG, Message number 03AB8204

This is with Slackware Linux Current/Wayland. In other words, you may
have to play around with it to get it working. If you want to use the
microvax2000 off the infoserver100 (SIMH), here's the config for it
(assuming you have a bridge and the infoserver100 on it with VXT
installed). The software for the infoserver100/150 is in the file
infoserver.zip that you see floating around online. Then you'll really
be retro with a monochrome VXT.
>
; MicroVAX 2000 (KA410)
; This is set up as a diskless Virtual X Terminal
; to be booted off an Infoserver that serves VXT.
>
; Max memory this model will support is 16M.
set cpu 16M
set cpu idle
set cpu conhalt
>
; Enable monocrome graphics display, "VC". "VA" is
; for color GPX, but will not boot off the infoserver
; (hangs).
;set va capture
;set va enable
;set cpu model=VAXstationGPX
set vc capture
set vc ena
>
; Non-volitile memory file goes here
att nvr nvr.bin
>
; Keep a log for debugging purposes
;set console log=console.log
>
; Disable disk drives since this is set up as
; a virtual X terminal thin client
set rd0 dis
set rd1 dis
set rd2 dis
>
; MAC address is set on NAR, this would be 1.16.
; Enable Lance ethernet controller and attach to tuntap
set nar mac=AA:00:04:00:10:04
set xs ena
att xs tap:tap7
>
; Start simulator
boot cpu
>
; Commands to boot VXT off the Infoserver:
; >>> b/101                                                                    
;  Bootfile: vxtldr                                                            
;  VXTLDR> VXT.SYS
;
; Patience - it can take a while to load!
; Terminal group "XTERMINALS" password: VXT
; Manager password for group configuration: VXT
;
; EOF
>
That one will work for Compaq XDM, but not Multinet XDM. Xnest/Xephyr
work for Multinet, but not Compaq. Pathworks does both. YMMV.

I will try xdm /after/ I'm able to display clock on Xnest/Xephyr. I
don't understand why VMS answers "can't open display"...

Best regards,

JB

--
Si votre demande me parvient en code 29, je vous titiouillerai volontiers
une réponse.