[Info-vax] X-terminals again

[Alan Winston - SSRL Central Computing]

In article <cef8fd6e-c819-4061-a27b-e2efd992f375 at v5g2000prm.googlegroups.com>, tadamsmar <tadamsmar at yahoo.com> writes:
>On Jan 13, 6:30=A0pm, wins... at SSRL.SLAC.STANFORD.EDU (Alan Winston -
>SSRL Central Computing) wrote:
>> In article <3e4c7324-fd37-49be-9f31-3eccf06d6... at q30g2000prq.googlegroups=
>.com>, tadamsmar <tadams... at yahoo.com> writes:
>>
>>
>>
>>
>>
>> >On Dec 8 2008, 3:56=3DA0pm, Wilm Boerhout <w6.boerh... at planet.nl> wrote:
>> >> tadamsmarvaguely mentioned on 8-12-2008 21:41:
>>
>> >> > I am trying to meet these requirements:
>>
>> >> > 1. =3DA0X-terminal software that will run on Windows XP.
>>
>> >> > 2. =3DA0For a user-friendly subset of these X-terminals, I need the
>> >> > interface to be as user- friendly as some old Tectronix x-terminals
>> >> > that we are currently using. =3DA0When you power these up, the Decwi=
>ndows
>> >> > username and password comes up automatically.
>>
>> >> > 3. =3DA0The rest need to be more teckie-friendly. =3DA0 The user nee=
>ds acce=3D
>> >ss
>> >> > to XP.
>>
>> >> > I wonder if I can do this with a single product?
>>
>> >> > We use XFREE on Windows 98 and 2000 now for the teckie-friendly
>> >> > systems, and you have to log into VMS and run a command procedure to
>> >> > set up the connection.
>>
>> >> > We have old Tectronix X-terminal so the user-friedly systems, and th=
>ey
>> >> > came with software for VMS. =3DA0The VMS software is always running =
>and
>> >> > handles setting up access to the X-terminal automatically.
>>
>> >> Use any X11 display server software.
>> >> Put DEFINE DECW$IGNORE_WORKSTATION into the VMS SYSTARTUP_VMS.COM (tha=
>t
>> >> is, if VMS does not have it's own X11 graphical interface.
>>
>> >I am not sure what you mean by "if VMS does not have it's own X11
>> >graphical interface." =A0All my units are workstations with a terminal
>> >plugged it. =A0We need a few other X-terminals to run over the ethernet
>> >on one of the workstations.
>>
>> >Should I add that line to startup or not?
>>
>> The line keeps Decwindows software from trying to use local graphics hard=
>ware,
>> if any.
>>
>> If your workstation units have a keyboard and a monitor plugged into to t=
>hem,
>> directly and use their own graphics hardware to display X windows stuff, =
>then
>> you don't want to disable their use by putting that line in the startup. =
>=A0
>>
>> If you only have a erial terminal plugged into them,
>> then you do want to put that line into the startup.
>>
>> For completeness, note that the line is
>>
>> $ DEFINE/SYSTEM DECW$IGNORE_WORKSTATION "TRUE"
>>
>> -- Alan- Hide quoted text -
>>
>> - Show quoted text -
>
>You explanation does not match the comment in SYSTARTUP_VMS.COM:
>
>"
>$! The following command should be used only if you do not wish the
>DECwindows
>$! startup file to be run.  The DECwindows startup file should be run
>on all
>$! types of machines, even if they are not using a DECwindows
>display.  If
>$! you wish to run the DECwindows startup file at a later time during
>system
>$! startup remove the comment from the line below.
>$!
>$!$ DEFINE DECW$IGNORE_DECWINDOWS TRUE
>"
>
>I have a keyboard and monitor plugged in.  And I also will have some
>PCs on the ethernet running Xcursion.
>
>Do I add the line or not?

You want to run DECW$STARTUP (to make your system have a DecWindows console and
to feed your PCs.)

If you don't add that line, it should run automatically.

If you do add that line, you'll have to run it manually or arrange some
other mechanism to start it. 

>From your problem statement so far, I'd say don't add the line.

-- Alan