[Info-vax] X-terminals again

[Mark Daniel]

FredK wrote:
> The XDM that currently ships with TCPIP does not provide for any security, 
> even MIT Magic Cookie.
> 
> The DECwindows group plans to take over XDM sometime this year, and bring it 
> up-to-date.  We believe that remote thin-client access will become more 
> common with users as network speeds increase and latency declines.

It might just be a question of better phrasing Fred but I'm guessing for 
most of us this happened a decade-plus ago, and XDM has been around for 
two.  If there wasn't sufficient VMS client-base demand shaping 
priorities and resource allocation back then, I'm gobsmacked there's a 
perception there is now.  Potius sero quam numquam.

--
Amicus Curiae.

[Sometimes you just can't stop yourself picking at particular scabs.]

http://groups.google.com/group/comp.os.vms/browse_thread/thread/2bb10af59be7be61

> "Joseph Huber" <joseph.huber at NOSPAM.web.de> wrote in message 
> news:gkq3f2$13ds$1 at gwdu112.gwdg.de...
>> tadamsmar wrote:
>>
>>>> ¨snip*
>>> The remote node is a PC running some version of Windows.
>>>
>>> What do I have to have running on the remote node to make this work?
>> Under the assumption XDM is acceptable security-wise,
>> then for a "one-click" to VMS login solution, I propose to get the free
>> Xming X11 server.
>>
>> http://www.straightrunning.com/XmingNotes/
>>
>> To setup, start the Xlaunch program, select XDMCP mode, enter the node 
>> name
>> of the VMS node to connect, finish by saving the coniguration on the
>> desktop.
>>
>> From then on, the VMS login will be started by double clicking on the 
>> saved
>> Xlauch config file.
>> Depending on the windows version, the Xlaunch start can be put into the
>> startup folder or setup as a windows service, so it starts automatically 
>> at
>> windows boot.
>>
>>
>> --
>> Joseph Huber, http://www.huber-joseph.de 
> 
>