[Info-vax] XWindows Client

[Wilm Boerhout]

Jerry Alan Braga mentioned  on 21-1-2010 20:40:
> Thanks for the note, however I do not understand why I need a vms
> session to launch the Xwindows clients. With eXcusrsion everything is
> launched from the client. According to what you say I have to telnet
> into the box first to launch it. that does not make sense. If telnet
> into the box I get and try to run the clock I get this
>
>
> $set disp/cre/node=10.73.10.201/trans=tcpip
> j$mc decw$clock
> X Toolkit Warning: Cannot convert string
> "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
> X connection to _WSA139: broken (explicit kill or server shutdown).
> %XLIB-F-IOERROR, xlib io error
>
> does the above mean I need a font server somewhere and if so how do I
> know if my vms box is setup correctly
>
>
>
> "Wilm Boerhout" <wboerhout.no at spam.gmail.com> wrote in message
> news:4b589810$0$14130$703f8584 at textnews.kpn.nl...
>> Jerry Alan Braga mentioned on 21-1-2010 18:21:
>>> ok I get something now. If I replace the netbck with my server I can
>>> keep the icon in the system tray but it is not responsive. This is what
>>> is in the %tmp%\Xmin.log file
>>>
>>> Welcome to the Xming X Server
>>> Vendor: Colin Harrison
>>> Release: 6.9.0.31
>>> FreeType2: 2.3.4
>>> Contact: http://sourceforge.net/forum/?group_id=156984
>>>
>>> Xming :0 -multiwindow -clipboard -ac -fp tcp/stimpy:7100
>>> -nodecoration +bs -wm -dpi 100 -multimonitors -xkbmodel pc105
>>>
>>> XdmcpRegisterConnection: newAddress 10.73.10.201
>>> (++) FontPath set to "tcp/stimpy:7100"
>>> winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per
>>> pixel
>>> winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200
>>> depth: 32
>>> winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
>>> bpp 32
>>> glWinInitVisuals:1596: glWinInitVisuals
>>> glWinInitVisualConfigs:1503: glWinInitVisualConfigs
>>> glWinSetVisualConfigs:1581: glWinSetVisualConfigs
>>> init_visuals:1055: init_visuals
>>> null screen fn ReparentWindow
>>> null screen fn RestackWindow
>>> InitQueue - Calling pthread_mutex_init
>>> InitQueue - pthread_mutex_init returned
>>> InitQueue - Calling pthread_cond_init
>>> InitQueue - pthread_cond_init returned
>>> winInitMultiWindowWM - Hello
>>> winInitMultiWindowWM - Calling pthread_mutex_lock ()
>>> winMultiWindowXMsgProc - Hello
>>> winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
>>> glWinScreenProbe:1390: glWinScreenProbe
>>> fixup_visuals:1303: fixup_visuals
>>> init_screen_visuals:1336: init_screen_visuals
>>> (--) 3 mouse buttons found
>>> (--) Setting autorepeat to delay=500, rate=31
>>> (--) winConfigKeyboard - Layout: "00000409" (00000409)
>>> (--) Using preset keyboard for "English (USA)" (409), type "4"
>>> (++) XKB: model: "pc105"
>>>
>>>
>>> "Wilm Boerhout" <wboerhout.no at spam.gmail.com> wrote in message
>>> news:4b588902$0$14129$703f8584 at textnews.kpn.nl...
>>>> Jerry Alan Braga mentioned on 21-1-2010 17:15:
>>>>> this is not work for me, this is what I get in Xming.log
>>>>>
>>>>> Welcome to the Xming X Server
>>>>> Vendor: Colin Harrison
>>>>> Release: 6.9.0.31
>>>>> FreeType2: 2.3.4
>>>>> Contact: http://sourceforge.net/forum/?group_id=156984
>>>>>
>>>>> Xming was started with the following command line...
>>>>> Xming :0 -multiwindow -clipboard -ac -fp tcp/netbck:7100
>>>>> -nodecoration +bs -wm -dpi 100 -multimonitors -xkbmodel pc105
>>>>> -nolisten inet
>>>>>
>>>>> ddxProcessArgument - Initializing default screens
>>>>> winInitializeDefaultScreens - w 1920 h 1200
>>>>> winInitializeDefaultScreens - Returning
>>>>> _XSERVTransTransNoListen: unable to find transport: inet6
>>>>>
>>>>> Fatal server error:
>>>>> Failed to disable listen for inet6 transport
>>>>> winDeinitMultiWindowWM - Noting shutdown in progress
>>>>>
>>>>>
>>>>> "Wilm Boerhout" <wboerhout at gmail.com> wrote in message
>>>>> news:c3f711fa-a0c6-4d8e-a81f-fbaf1cf30865 at j14g2000yqm.googlegroups.com...
>>>>>
>>>>>
>>>>>> On 21 jan, 15:44, "Jerry Alan Braga" <jerry.br... at hotmail.com> wrote:
>>>>>>> that email account is a bogus account, can you post the file here, I
>>>>>>> believe
>>>>>>> that is is just a text file.
>>>>>>>
>>>>>>> "Wilm Boerhout" <wboerhout... at spam.gmail.com> wrote in message
>>>>>>>
>>>>>>> news:4B55DEE6.9010001 at spam.gmail.com...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> > Jerry Alan Braga mentioned on 18-1-2010 14:35:
>>>>>>> >> Do you start a program or not, and if so what is the syntax?
>>>>>>>
>>>>>>> >> "Wilm Boerhout" <wboerhout... at spam.gmail.com> wrote in message
>>>>>>> >>news:4b508f3a$0$14119$703f8584 at textnews.kpn.nl...
>>>>>>> >>> Jerry Alan Braga mentioned on 15-1-2010 15:05:
>>>>>>> >>>> thanks for xMing, I downloaded but do not understand how to get
>>>>>>> it >>>> to
>>>>>>> >>>> work
>>>>>>>
>>>>>>> >>>> "Wilm Boerhout" <wboerhout... at spam.gmail.com> wrote in message
>>>>>>> >>>>news:4b5016b2$0$14119$703f8584 at textnews.kpn.nl...
>>>>>>> >>>>> Jerry Alan Braga mentioned on 14-1-2010 19:53:
>>>>>>> >>>>>> Currently I am using Excursion 7.3.189 to connect my Alpha
>>>>>>> Cluster
>>>>>>> >>>>>> boxes
>>>>>>> >>>>>> using the New Desktop model and everything works fine. We
>>>>>>> have
>>>>>>> >>>>>> added
>>>>>>> >>>>>> some CentOS linux boxes and I would like to connect to
>>>>>>> them as
>>>>>>> >>>>>> well. My
>>>>>>> >>>>>> question is, can I use Excursion to connect to these boxes
>>>>>>> and
>>>>>>> if >>>>>> so
>>>>>>> >>>>>> how, and if I cannot what client (free if around) can work
>>>>>>> with >>>>>> both
>>>>>>> >>>>>> openVMS 8.3 alpha and linux CentOS boxes.
>>>>>>>
>>>>>>> >>>>> Google for xMing. It is a fine, modern X display server that
>>>>>>> also
>>>>>>> >>>>> works with VMS clients.
>>>>>>>
>>>>>>> >>>>> /Wilm
>>>>>>>
>>>>>>> >>> Hmm, "intuitive" should be the word. After installation, you
>>>>>>> run >>> the
>>>>>>> >>> executable image. The dialog helps you to configure your display
>>>>>>> >>> server (for Windows, use the "multiple windows" mode), and
>>>>>>> you >>> can
>>>>>>> >>> save the config to an .xlaunch file, that you can use
>>>>>>> afterwards.
>>>>>>>
>>>>>>> >>> For optimal results, use the remote font server option in
>>>>>>> Xming >>> to
>>>>>>> >>> point to a VMS server with DECwindows Motif installed, and
>>>>>>> enable
>>>>>>> the
>>>>>>> >>> font server on that VMS system. This will ensure that all VMS
>>>>>>> >>> client
>>>>>>> >>> apps use the familiar fonts.
>>>>>>>
>>>>>>> >>> The Help for Xming should explain it all...
>>>>>>>
>>>>>>> > After installing Xming, you can run Xming.exe. This is your
>>>>>>> display
>>>>>>> > server, and now using default settings. It will signal its
>>>>>>> presence
>>>>>>> by > an
>>>>>>> > icon in your system tray. Right clicking the icon will give you
>>>>>>> access > to,
>>>>>>> > among others, the Help area.
>>>>>>>
>>>>>>> > If the default settings do not please you (and for VMS clients,
>>>>>>> they > most
>>>>>>> > likely won't), you can start the Xlaunch wizard. At completion of
>>>>>>> the
>>>>>>> > wizard, you save the settings as an *.Xlaunch file. The Xlaunch >
>>>>>>> extension
>>>>>>> > is associated with Xming.exe, so clicking the saved file will
>>>>>>> start a
>>>>>>> > display server with the saved settings.
>>>>>>>
>>>>>>> > I'll send you my VMS.xlaunch file by separate mail.
>>>>>>>
>>>>>>> > /Wilm- Tekst uit oorspronkelijk bericht niet weergeven -
>>>>>>>
>>>>>>> - Tekst uit oorspronkelijk bericht weergeven -
>>>>>>
>>>>>> Indeed, save the following as text, rename to *.xlaunch, and Robert's
>>>>>> your father's brother.
>>>>>>
>>>>>> <?xml version="1.0" encoding="utf-8"?>
>>>>>> <XLaunch
>>>>>> xmlns="http://www.straightrunning.com/XmingNotes"
>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>>> xsi:schemaLocation="http://www.straightrunning.com/XmingNotes
>>>>>> XLaunch.xsd"
>>>>>> WindowMode="MultiWindow"
>>>>>> ClientMode="NoClient"
>>>>>> Display="0"
>>>>>> Clipboard="true"
>>>>>> NoAccessControl="true"
>>>>>> FontServer="netbck"
>>>>>> ExtraParams="-nodecoration +bs -wm -dpi 100 -multimonitors -xkbmodel
>>>>>> pc105 -nolisten inet6"
>>>>>> />
>>>>>>
>>>>>> /Wilm
>>>>>
>>>>
>>>> Maybe it's because you have the free version of Xming, and I paid for
>>>> it. Try it without the "-nolisten inet" phrase.
>>>>
>>>> /Wilm
>>>
>>
>> Yeah sorry, text sometines wraps. the pc105 is part of the xkbmodel
>> string, it should all be on one line.
>>
>> If the icon just sits there, it means your X display server is working.
>>
>> You now need to send something there from your VMS clients. I always
>> use (on the VMS X display client system):
>>
>> $ tcpip ping <your Xming node>
>>
>> This is just to verify that the network is OK, then
>>
>> $ set disp /cre /node=<your Xming node> /transp=tcpip
>> $ mc decw$clock
>>
>> You should see a small window with the DECwindows clock in it.
>>
>> Then:
>>
>> $ cre/term /det
>>
>> Should get you an Xterm window
>>
>> NOTE: the name "netbck" is a local Alpha system name on my network
>> that runs an X font server. Delete the FontServer="netbck" phrase or
>> replace with your own font server
>>
>> /Wilm
>>

Let us first get the terminology right:

eXcursion, Xming --> the X display server
VMS, Unix --> contain X clients like clock, xterm, whatever.

The X display server is just that, it accepts command from clients and 
displays them on a screen. Now eXcursion has a clever way to poke a VMS 
client (xCursion calls that "applications"), so that the VMS client 
sends something back to the display server on your PC.

Xming also has that facility, but it is set up differently than 
eXcursion. You access it via the system tray. Anyway, that's too 
advanced for now.

If you have the base functionality working (and you're not there yet) 
you can set up things on the VMS end so that a login dialog appears 
automagically on your PC at VMS startup.

1. what does the "ping" command report? If you can't ping from VMS to 
the xMing PC, it's no point going on. Fix it first.

2. If ping works, try DECW$clock as specified before. Forget about the 
font warning, the font will be replaced by something ugly but working 
(it's a warning). The xlib error is serious though, and could be the 
starting point for some troubleshooting. The xMing log file could give 
you a clue.

Backtranslating should be in place for the X protocol to work, so the PC 
and the VMS sytem shouyld know each others name, not only the IP 
address. Set up DNS or use the hosts file (PC), local host database 
(TCPIP SET HOST) on VMS.

/Wilm