Setting Reflection 2 window titles from VMS - VMS

This is a discussion on Setting Reflection 2 window titles from VMS - VMS ; I am trying to find a way that I can set the titles of my R2 terminal emulation session from VMS. I am running Reflection R2 version 5.20 This is so that after the frequent reboots of the PC, I ...

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 20 of 43

Thread: Setting Reflection 2 window titles from VMS

  1. Setting Reflection 2 window titles from VMS

    I am trying to find a way that I can set the titles of my R2 terminal
    emulation session from VMS.

    I am running Reflection R2 version 5.20

    This is so that after the frequent reboots of the PC, I can reconnect to
    the existing sessions on VMS and then just run a script or program to
    fix the titles.

    Ideally I would want to identify the terminal emulator in use so that I
    can have one script work for what ever is in use.

    R2 has some private escape sequences that return its serial number, and
    that seems to be a possible way to identify it.

    So far what I have determined:

    R2 (V5.20) claims to be a VT400 with soft characters. It also supports
    ANSI color, but set term/inquire does not appear to probe for this
    feature if there is a way to do so.

    DecTERMs claim to be VT300 with no soft characters and support for ANSI
    color. Decterms use a DEC private escape sequence to set the window titles.

    The free version of IVT claims to be a VT200 with soft characters. I
    have not tested it to see if it supports ANSI colors. IVT window titles
    can be set with the "xterm" escape sequences.

    Putty by default claims to be a VT102. It supports ANSI colors, as
    noted above, set term/inq does not indicate so. Putty window titles can
    be set with the "xterm" escape sequences.

    I have not yet found any way to positively identify any of the above
    terminal emulators. For my local LAN, I can put in a hint in the
    answerback message, but I would prefer a generic solution.

    That way I can also have the SYLOGIN.COM accurately set what the
    terminal emulators can really do for the terminal characteristics.

    -John
    wb8tyw@qsl.network
    Personal Opinion Only

  2. Re: Setting Reflection 2 window titles from VMS

    In article , "John E. Malmberg" writes:
    >
    >
    >I am trying to find a way that I can set the titles of my R2 terminal
    >emulation session from VMS.
    >
    >I am running Reflection R2 version 5.20
    >
    >This is so that after the frequent reboots of the PC, I can reconnect to
    >the existing sessions on VMS and then just run a script or program to
    >fix the titles.
    >
    >Ideally I would want to identify the terminal emulator in use so that I
    >can have one script work for what ever is in use.
    >
    >R2 has some private escape sequences that return its serial number, and
    >that seems to be a possible way to identify it.
    >
    >So far what I have determined:
    >
    >R2 (V5.20) claims to be a VT400 with soft characters. It also supports
    >ANSI color, but set term/inquire does not appear to probe for this
    >feature if there is a way to do so.
    >
    >DecTERMs claim to be VT300 with no soft characters and support for ANSI
    >color. Decterms use a DEC private escape sequence to set the window titles.
    >
    >The free version of IVT claims to be a VT200 with soft characters. I
    >have not tested it to see if it supports ANSI colors. IVT window titles
    >can be set with the "xterm" escape sequences.
    >
    >Putty by default claims to be a VT102. It supports ANSI colors, as
    >noted above, set term/inq does not indicate so. Putty window titles can
    >be set with the "xterm" escape sequences.
    >
    >I have not yet found any way to positively identify any of the above
    >terminal emulators. For my local LAN, I can put in a hint in the
    >answerback message, but I would prefer a generic solution.
    >
    >That way I can also have the SYLOGIN.COM accurately set what the
    >terminal emulators can really do for the terminal characteristics.


    When/if you do, I'd be very very interested to know how you determine these.

    I maintain a product that writes VT escape sequences. I have been plagued
    in recent years by the terminal emulators claiming to be VT200/300/400 com-
    patible when they are not. I have been urged to just modify the product to
    work with Reflections as I was told *everybody* uses Reflections today. I
    don't! The Reflections and other terminal emulator makers should simply do
    a better job at emulating the VTs.

    However, if there *IS* a way to determine the emulator in use, I'd like to
    know as then I can add support for these terminal emulators.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  3. Re: Setting Reflection 2 window titles from VMS

    On Dec 27, 12:38*am, "John E. Malmberg" wrote:
    > Ideally I would want to identify the terminal emulator in use so that I
    > can have one script work for what ever is in use.


    Putting aside the issue of emulators that don't emulate properly, the
    principal behind them is that they don't "look" any different than the
    old physical terminal. So, other than knowing what private sequence
    to send to get a non-emulated response you're probably out of luck.

    That being said, however, my trusty KEA! emulator has a set up page
    where you can set the response that gets transmitted during a "Device
    Attributes" request. It has an option for all the usual VT suspects,
    as well as a KEA! private sequence. The default is the KEA! sequence.

    Maybe Reflection has the same thing?

  4. Re: Setting Reflection 2 window titles from VMS

    In article <625b3809-627d-4e6e-9c17-18026ed3b289@f52g2000hsa.googlegroups.com>, FrankS writes:
    >
    >
    >On Dec 27, 12:38=A0am, "John E. Malmberg" wrote:
    >> Ideally I would want to identify the terminal emulator in use so that I
    >> can have one script work for what ever is in use.

    >
    >Putting aside the issue of emulators that don't emulate properly, the
    >principal behind them is that they don't "look" any different than the
    >old physical terminal. So, other than knowing what private sequence
    >to send to get a non-emulated response you're probably out of luck.
    >
    >That being said, however, my trusty KEA! emulator has a set up page
    >where you can set the response that gets transmitted during a "Device
    >Attributes" request. It has an option for all the usual VT suspects,
    >as well as a KEA! private sequence. The default is the KEA! sequence.
    >
    >Maybe Reflection has the same thing?


    That would be great! Then build the SMGTERMS.TXT for the particular
    emulator and define it a FT* value that can be set with SET TERM/DEV.
    Then I could figure out what I am talking to at the remote end which
    is NOT a well-behaved VTwhatever.

    FWIW, KEA has several ugly warts when it is hit with escape sequences
    it purports to support by claiming it's a VTx00. It's far worse than
    Reflections in many cases.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  5. Re: Setting Reflection 2 window titles from VMS

    VAXman- wrote:
    > I maintain a product that writes VT escape sequences. I have been plagued
    > in recent years by the terminal emulators claiming to be VT200/300/400 com-
    > patible when they are not. I have been urged to just modify the product to
    > work with Reflections as I was told *everybody* uses Reflections today. I
    > don't! The Reflections and other terminal emulator makers should simply do
    > a better job at emulating the VTs.


    > However, if there *IS* a way to determine the emulator in use, I'd like to
    > know as then I can add support for these terminal emulators.


    There's no reliable way. Some of them identify in the primary device
    attributes as a VT102, some use cut/paste technology to adapt xterm's
    VT220 response - take a look at this one for instance:

    http://bugzilla.gnome.org/show_bug.cgi?id=344258
    http://bugzilla.gnome.org/show_bug.cgi?id=130671
    http://bugzilla.gnome.org/show_bug.cgi?id=398401

    Some, such as IVT claim to do well with vttest, though I've not found that
    to be true.

    --
    Thomas E. Dickey
    http://invisible-island.net
    ftp://invisible-island.net

  6. Re: Setting Reflection 2 window titles from VMS

    In article <13n7fasikre8b58@corp.supernews.com>, Thomas Dickey writes:
    >
    >
    >VAXman- wrote:
    >> I maintain a product that writes VT escape sequences. I have been plagued
    >> in recent years by the terminal emulators claiming to be VT200/300/400 com-
    >> patible when they are not. I have been urged to just modify the product to
    >> work with Reflections as I was told *everybody* uses Reflections today. I
    >> don't! The Reflections and other terminal emulator makers should simply do
    >> a better job at emulating the VTs.

    >
    >> However, if there *IS* a way to determine the emulator in use, I'd like to
    >> know as then I can add support for these terminal emulators.

    >
    >There's no reliable way. Some of them identify in the primary device
    >attributes as a VT102, some use cut/paste technology to adapt xterm's
    >VT220 response - take a look at this one for instance:
    >
    > http://bugzilla.gnome.org/show_bug.cgi?id=344258
    > http://bugzilla.gnome.org/show_bug.cgi?id=130671
    > http://bugzilla.gnome.org/show_bug.cgi?id=398401
    >
    >Some, such as IVT claim to do well with vttest, though I've not found that
    >to be true.


    I've been using VTTEST as well as some of my own VT suite of tests (taken
    from real world cases of applications which failed with these emulators).
    VTTEST doesn't have tests for some of the VT400 and VT500 sequences. Are
    there any terminal emulators claiming to be VT400 or VT500 terminals? I
    think the Reflection one does IIRC. It's been quite a while.

    I don't really care if a there is no way to determine the emulator in use.
    What I *DO* care about is that they lie to me when they claim to be a VTx00
    and then can't handle the VTx00 escapes sent to them. I get shat upon by a
    customer because they perceive it to be a problem with my software when, in
    fact, it's their terminal emulator. My software works, as advertised, when
    used with a VTx00 terminal; ergo, the emulators need to clean up their act.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  7. Re: Setting Reflection 2 window titles from VMS

    In article
    <625b3809-627d-4e6e-9c17-18026ed3b289@f52g2000hsa.googlegroups.com>,
    FrankS wrote:

    > On Dec 27, 12:38*am, "John E. Malmberg" wrote:
    > > Ideally I would want to identify the terminal emulator in use so that I
    > > can have one script work for what ever is in use.

    >
    > Putting aside the issue of emulators that don't emulate properly, the
    > principal behind them is that they don't "look" any different than the
    > old physical terminal. So, other than knowing what private sequence
    > to send to get a non-emulated response you're probably out of luck.
    >
    > That being said, however, my trusty KEA! emulator has a set up page
    > where you can set the response that gets transmitted during a "Device
    > Attributes" request. It has an option for all the usual VT suspects,
    > as well as a KEA! private sequence. The default is the KEA! sequence.
    >
    > Maybe Reflection has the same thing?


    I did something similar many years ago to distinguish between "standard"
    VT100s and an OEM VT100 wannabe which had extended functionality.

    To keep the explanation as simple as possible...

    Before invoking the application software, I sent all terminals the OEM
    private sequence to change to OEM-VT100 mode, followed by a "what are
    you?" request, and then invoked the application accordingly. This of
    course relied on the "standard" VT100s to not change their mode or
    otherwise screw up in response to the OEM private sequence.

    On application exit, for the OEM-VT100s I sent the sequence to switch
    back to vanilla VT100 mode so as not to interfere with standard VMS or
    other third party software.

    --
    Paul Sture

    Sue's OpenVMS bookmarks:
    http://eisner.encompasserve.org/~stu...bookmarks.html

  8. Re: Setting Reflection 2 window titles from VMS

    On Dec 27, 9:23 am, VAXman- @SendSpamHere.ORG wrote:
    > In article <13n7fasikre8...@corp.supernews.com>, Thomas Dickey writes:
    >
    > >VAXman- wrote:
    > >> I maintain a product that writes VT escape sequences. I have been plagued
    > >> in recent years by the terminal emulators claiming to be VT200/300/400 com-
    > >> patible when they are not. I have been urged to just modify the product to
    > >> work with Reflections as I was told *everybody* uses Reflections today. I
    > >> don't! The Reflections and other terminal emulator makers should simply do
    > >> a better job at emulating the VTs.

    >
    > >> However, if there *IS* a way to determine the emulator in use, I'd like to
    > >> know as then I can add support for these terminal emulators.

    >
    > >There's no reliable way. Some of them identify in the primary device
    > >attributes as a VT102, some use cut/paste technology to adapt xterm's
    > >VT220 response - take a look at this one for instance:

    >
    > > http://bugzilla.gnome.org/show_bug.cgi?id=344258
    > > http://bugzilla.gnome.org/show_bug.cgi?id=130671
    > > http://bugzilla.gnome.org/show_bug.cgi?id=398401

    >
    > >Some, such as IVT claim to do well with vttest, though I've not found that
    > >to be true.

    >
    > I've been using VTTEST as well as some of my own VT suite of tests (taken
    > from real world cases of applications which failed with these emulators).
    > VTTEST doesn't have tests for some of the VT400 and VT500 sequences. Are
    > there any terminal emulators claiming to be VT400 or VT500 terminals? I
    > think the Reflection one does IIRC. It's been quite a while.
    >
    > I don't really care if a there is no way to determine the emulator in use.
    > What I *DO* care about is that they lie to me when they claim to be a VTx00
    > and then can't handle the VTx00 escapes sent to them. I get shat upon by a
    > customer because they perceive it to be a problem with my software when, in
    > fact, it's their terminal emulator. My software works, as advertised, when
    > used with a VTx00 terminal; ergo, the emulators need to clean up their act.
    >
    > --
    > VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM
    >
    > "Well my son, life is like a beanstalk, isn't it?"
    >
    > http://tmesis.com/drat.html


    We still use Powerterm (by Ericom) simply because it came with
    Pathworks and our customers got used to it. Our code required no
    changes to work with it compared to stock VT220/320 terminals so it
    was good enough.

    You can select VT420 and VT525 emulation. We don't use any more
    advanced features so I don't know how capable they are.

    Unfortunately I also don't see anything in the lesser docs I have here
    that explains how a program can determine that Powerterm is talking to
    it... I can see some ways that would work with pre-setup work (like
    putting a script in the powerterm directory and having the program try
    to 'run' that script via an escape sequence), but nothing more
    general. I don't have the full docs available here though.

    Rich

  9. Re: Setting Reflection 2 window titles from VMS

    In article <1dc697a2-0ee7-449c-8c3d-96819a4c1cfb@s19g2000prg.googlegroups.com>, Rich Jordan writes:
    >
    >
    >On Dec 27, 9:23 am, VAXman- @SendSpamHere.ORG wrote:
    >> In article <13n7fasikre8...@corp.supernews.com>, Thomas Dickey writes:
    >>
    >> >VAXman- wrote:
    >> >> I maintain a product that writes VT escape sequences. I have been plagued
    >> >> in recent years by the terminal emulators claiming to be VT200/300/400 com-
    >> >> patible when they are not. I have been urged to just modify the product to
    >> >> work with Reflections as I was told *everybody* uses Reflections today. I
    >> >> don't! The Reflections and other terminal emulator makers should simply do
    >> >> a better job at emulating the VTs.

    >>
    >> >> However, if there *IS* a way to determine the emulator in use, I'd like to
    >> >> know as then I can add support for these terminal emulators.

    >>
    >> >There's no reliable way. Some of them identify in the primary device
    >> >attributes as a VT102, some use cut/paste technology to adapt xterm's
    >> >VT220 response - take a look at this one for instance:

    >>
    >> > http://bugzilla.gnome.org/show_bug.cgi?id=344258
    >> > http://bugzilla.gnome.org/show_bug.cgi?id=130671
    >> > http://bugzilla.gnome.org/show_bug.cgi?id=398401

    >>
    >> >Some, such as IVT claim to do well with vttest, though I've not found that
    >> >to be true.

    >>
    >> I've been using VTTEST as well as some of my own VT suite of tests (taken
    >> from real world cases of applications which failed with these emulators).
    >> VTTEST doesn't have tests for some of the VT400 and VT500 sequences. Are
    >> there any terminal emulators claiming to be VT400 or VT500 terminals? I
    >> think the Reflection one does IIRC. It's been quite a while.
    >>
    >> I don't really care if a there is no way to determine the emulator in use.
    >> What I *DO* care about is that they lie to me when they claim to be a VTx00
    >> and then can't handle the VTx00 escapes sent to them. I get shat upon by a
    >> customer because they perceive it to be a problem with my software when, in
    >> fact, it's their terminal emulator. My software works, as advertised, when
    >> used with a VTx00 terminal; ergo, the emulators need to clean up their act.
    >>
    >> --
    >> VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM
    >>
    >> "Well my son, life is like a beanstalk, isn't it?"
    >>
    >> http://tmesis.com/drat.html

    >
    >We still use Powerterm (by Ericom) simply because it came with
    >Pathworks and our customers got used to it. Our code required no
    >changes to work with it compared to stock VT220/320 terminals so it
    >was good enough.
    >
    >You can select VT420 and VT525 emulation. We don't use any more
    >advanced features so I don't know how capable they are.
    >
    >Unfortunately I also don't see anything in the lesser docs I have here
    >that explains how a program can determine that Powerterm is talking to
    >it... I can see some ways that would work with pre-setup work (like
    >putting a script in the powerterm directory and having the program try
    >to 'run' that script via an escape sequence), but nothing more
    >general. I don't have the full docs available here though.


    We could resort to the high-tech unix mechanism: setenv TERM {type}

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  10. Re: Setting Reflection 2 window titles from VMS

    John E. Malmberg wrote:
    > I am trying to find a way that I can set the titles of my R2 terminal
    > emulation session from VMS.


    Given that a real terminal does not have a title, then I doubt that will
    work.

    Reflection online help does not seem to contain any non-standard
    escape sequences for it either.

    > This is so that after the frequent reboots of the PC, I can reconnect to
    > the existing sessions on VMS and then just run a script or program to
    > fix the titles.


    What about a low tech solution.

    Create a bunch of short cuts with different settings files
    with the desired name as filename ?

    Arne

  11. Re: Setting Reflection 2 window titles from VMS

    VAXman-, @SendSpamHere.ORG wrote:
    >
    > [snip]
    > I maintain a product that writes VT escape sequences. I have been plagued
    > in recent years by the terminal emulators claiming to be VT200/300/400 com-
    > patible when they are not. I have been urged to just modify the product to
    > work with Reflections as I was told *everybody* uses Reflections today.


    In my experience, Reflection (singular) remains THE most complete VT
    emulation available, and even includes something none of the others do,
    AFAIK: smooth scroll.

    > I
    > don't! The Reflections and other terminal emulator makers should simply do
    > a better job at emulating the VTs.
    >
    > However, if there *IS* a way to determine the emulator in use, I'd like to
    > know as then I can add support for these terminal emulators.


    There is a program that ships with Reflection called WRQINQ (I think).
    It's a host-based program, and so may not be available for I64 or Alpha,
    though the VAX version should VEST nicely and the resulting Alpha .EXE
    should AEST to I64 - I've not tried it. WRQINQ queries the terminal for
    the Reflection serial number from which can be determined the product
    (Reflection/2, -/4, etc.) and other characteristics. It was documented
    on the old WRQ KB, but since Attachmate, dunno how to find that.

    Reflection/2 is the character-cell emulator (VT10x, VT220, VT320, VT420,
    VT510, VT520). It is now called "Reflection for UNIX and Digital".

    Reflection/4 is the graphic terminal emulator (VT125, VT230/VT240,
    VT330/VT340, VT525). It is now called "Reflection for ReGIS Graphics".

    Other versions, Reflection/1 and -/3 for example, may offer only VT10x
    and/or VT220 emulation, and ALL (1-4) may or may not support
    downloadable fonts, etc. in VT220 mode.

    I'd be curious to know what you're attempting that R/2 or R/4 chokes on.
    Their capabilities will be restricted somewhat by their operating
    environment, especially performance on slower PCs. Older versions may
    not perform as well/accurately as newer ones.

    David J Dachtera
    DJE Systems

  12. Re: Setting Reflection 2 window titles from VMS

    "P. Sture" wrote:
    > [snip]
    > I did something similar many years ago to distinguish between "standard"
    > VT100s and an OEM VT100 wannabe which had extended functionality.
    >
    > To keep the explanation as simple as possible...
    >
    > Before invoking the application software, I sent all terminals the OEM
    > private sequence to change to OEM-VT100 mode, followed by a "what are
    > you?" request, and then invoked the application accordingly. This of
    > course relied on the "standard" VT100s to not change their mode or
    > otherwise screw up in response to the OEM private sequence.
    >
    > On application exit, for the OEM-VT100s I sent the sequence to switch
    > back to vanilla VT100 mode so as not to interfere with standard VMS or
    > other third party software.


    ....which is fine until the user hits while in your app. and
    connects to a session on another system. (We're talking terminal servers
    here, of course!)

    Same deal if one s out of an EDT session and goes to do something
    else on another machine - you usually end up with a 22-line display
    instead of a 24 line display, and the key pad(s) are still in
    application mode.

    David J Dachtera
    DJE Systems

  13. Re: Setting Reflection 2 window titles from VMS

    Arne Vajh°j wrote:
    >
    > John E. Malmberg wrote:
    > > I am trying to find a way that I can set the titles of my R2 terminal
    > > emulation session from VMS.

    >
    > Given that a real terminal does not have a title, then I doubt that will
    > work.
    >
    > Reflection online help does not seem to contain any non-standard
    > escape sequences for it either.
    >
    > > This is so that after the frequent reboots of the PC, I can reconnect to
    > > the existing sessions on VMS and then just run a script or program to
    > > fix the titles.

    >
    > What about a low tech solution.
    >
    > Create a bunch of short cuts with different settings files
    > with the desired name as filename ?
    >
    > Arne


    The window title IS user-configurable, but I've never seen a way to do
    that from the host, to the best of my memory. If it could be done, one
    would need to send only the requisite literal string, packed in the
    required escape sequences, if any are actually available.

    There was a way to send old-style RCL commands from the host (haven't
    done that since I tried to write a BBS in All-in-1). Sample scripts were
    available in the old WRQ KB; however, since the buyout by Attachmate,
    dunno if those can still be found without a lot of hacking. It may still
    work in the current versions, even though RCL has been deprecated in
    favor of "Visual BASIC" (VASTLY more verbose!). I think RCL could be
    used to set/change the window title. Not sure just now.

    I think the old Reflection Programmer's Reference manuals may be
    available as .PDFs now, but darned if I can find them on short notice.
    Let me dig throughthe on-line help in V9...

    O.K. If you could find how to send RCL commands from the host, you'd
    want to SET WINDOW-TITLE "string", where "string" is whatever you want
    to have in the window title.

    David J Dachtera
    DJE Systems

  14. Re: Setting Reflection 2 window titles from VMS

    David J Dachtera wrote:
    > [snip]
    > There is a program that ships with Reflection called WRQINQ (I think).
    > It's a host-based program, and so may not be available for I64 or Alpha,
    > though the VAX version should VEST nicely and the resulting Alpha .EXE
    > should AEST to I64 - I've not tried it. WRQINQ queries the terminal for
    > the Reflection serial number from which can be determined the product
    > (Reflection/2, -/4, etc.) and other characteristics. It was documented
    > on the old WRQ KB, but since Attachmate, dunno how to find that.


    Follow-up...

    WRQINQ is supplied as WRQINQ.IMG for VAX. There is also a WRQINQA.IMG
    which may be an Alpha executable. Upload as binary and rename to .EXE
    for ease of RUNning it.

    On my laptop here, WRQINQ is in the C:\Program Files\Reflection\Support
    path. However, the images are corrupt (extraneous text at the beginning
    of the image file, appears to be LINK qualifiers).

    If you could fix them, they'd return two DCL symbols: REFLECTION_ID and
    REFLECTION_UPI. REFLECTION_ID would indicate which product you're
    dealing with, as I recall.

    David J Dachtera
    DJE Systems

  15. Re: Setting Reflection 2 window titles from VMS

    On Dec 27, 6:32 am, VAXman- @SendSpamHere.ORG wrote:
    > In article , "John E. Malmberg" writes:
    >
    >
    >
    >
    >
    > >I am trying to find a way that I can set the titles of my R2 terminal
    > >emulation session from VMS.

    >
    > >I am running Reflection R2 version 5.20

    >
    > >This is so that after the frequent reboots of the PC, I can reconnect to
    > >the existing sessions on VMS and then just run a script or program to
    > >fix the titles.

    >
    > >Ideally I would want to identify the terminal emulator in use so that I
    > >can have one script work for what ever is in use.

    >
    > >R2 has some private escape sequences that return its serial number, and
    > >that seems to be a possible way to identify it.

    >
    > >So far what I have determined:

    >
    > >R2 (V5.20) claims to be a VT400 with soft characters. It also supports
    > >ANSI color, but set term/inquire does not appear to probe for this
    > >feature if there is a way to do so.

    >
    > >DecTERMs claim to be VT300 with no soft characters and support for ANSI
    > >color. Decterms use a DEC private escape sequence to set the window titles.

    >
    > >The free version of IVT claims to be a VT200 with soft characters. I
    > >have not tested it to see if it supports ANSI colors. IVT window titles
    > >can be set with the "xterm" escape sequences.

    >
    > >Putty by default claims to be a VT102. It supports ANSI colors, as
    > >noted above, set term/inq does not indicate so. Putty window titles can
    > >be set with the "xterm" escape sequences.

    >
    > >I have not yet found any way to positively identify any of the above
    > >terminal emulators. For my local LAN, I can put in a hint in the
    > >answerback message, but I would prefer a generic solution.

    >
    > >That way I can also have the SYLOGIN.COM accurately set what the
    > >terminal emulators can really do for the terminal characteristics.

    >
    > When/if you do, I'd be very very interested to know how you determine these.
    >
    > I maintain a product that writes VT escape sequences. I have been plagued
    > in recent years by the terminal emulators claiming to be VT200/300/400 com-
    > patible when they are not. I have been urged to just modify the product to
    > work with Reflections as I was told *everybody* uses Reflections today. I
    > don't! The Reflections and other terminal emulator makers should simply do
    > a better job at emulating the VTs.
    >
    > However, if there *IS* a way to determine the emulator in use, I'd like to
    > know as then I can add support for these terminal emulators.
    >


    On Dec 26, 11:38 pm, "John E. Malmberg" wrote:
    > I am trying to find a way that I can set the titles of my R2 terminal
    > emulation session from VMS.
    >
    > I am running Reflection R2 version 5.20
    >
    > This is so that after the frequent reboots of the PC, I can reconnect to
    > the existing sessions on VMS and then just run a script or program to
    > fix the titles.
    >
    > Ideally I would want to identify the terminal emulator in use so that I
    > can have one script work for what ever is in use.
    >
    > R2 has some private escape sequences that return its serial number, and
    > that seems to be a possible way to identify it.
    >
    > So far what I have determined:
    >
    > R2 (V5.20) claims to be a VT400 with soft characters. It also supports
    > ANSI color, but set term/inquire does not appear to probe for this
    > feature if there is a way to do so.
    >
    > DecTERMs claim to be VT300 with no soft characters and support for ANSI
    > color. Decterms use a DEC private escape sequence to set the window titles.
    >
    > The free version of IVT claims to be a VT200 with soft characters. I
    > have not tested it to see if it supports ANSI colors. IVT window titles
    > can be set with the "xterm" escape sequences.
    >
    > Putty by default claims to be a VT102. It supports ANSI colors, as
    > noted above, set term/inq does not indicate so. Putty window titles can
    > be set with the "xterm" escape sequences.
    >
    > I have not yet found any way to positively identify any of the above
    > terminal emulators. For my local LAN, I can put in a hint in the
    > answerback message, but I would prefer a generic solution.
    >
    > That way I can also have the SYLOGIN.COM accurately set what the
    > terminal emulators can really do for the terminal characteristics.
    >


    Reflection2 V6.0 has some DCL examples that I don't find on my later
    versions (they're in the PC's ...\Reflection\VT\Support\ folder) and
    have .dcl extensions rather than .com

    Since there's no copyright notice, here's one below that will probably
    wrap. It "detects" Reflection and sends a Reflection command:

    $!++
    $!SETWIDTH.COM -- sets the terminal to match the Display width of
    $! Reflection 2 or Reflection 4.
    $!
    $!To invoke: @SETWIDTH (from LOGIN.COM is handy)
    $!
    $!This assumes a SET TERM/INQUIRE has been done before this procedure,
    $!or that the terminal line has been set correctly in advance.
    $!--
    $!if not an interactive process exit
    $ if .not. f$environment("INTERACTIVE") then exit
    $!if not a DEC crt exit
    $ if .not. f$getdvi(f$logical("TT"), "TT_DECCRT") then exit
    $ esc[0,8] = 27
    $! save the terminal settings we're about to alter
    $ had_echo = ""
    $ if .not. f$getdvi(f$logical("TT"), "TT_NOECHO") then -
    had_echo := /ECHO
    $ had_esc = ""
    $ if .not. f$getdvi(f$logical("TT"), "TT_ESCAPE") then -
    had_escape := /NOESCAPE
    $ set term/noecho/escape
    $!if not Reflection, then exit
    $ read/prompt="''esc'[2h''esc'[0;1234c"/error=unlock/timeout=5 sys
    $command p1
    $ if f$length(p1) .eqs. 0 then goto unlock
    $!set terminal width to match
    $ read/prompt="''esc'P1234;2{transmit value(display-columns) &
    ""^M""''esc'\"-
    /error=unlock/timeout=5 sys$command p1
    $ set term/width='p1'
    $unlock:
    $ set term'had_echo''had_escape'
    $ write sys$output "''esc'[2l"
    $!++

    Note the two read/prompt lines. The first asks for the Reflection
    serial number, the second sends a Reflection command. There are some
    other WRQ special commands listed in the Programming guide under Help.

    I've used the other emulators mentioned but not as extensively as
    Reflection. ISTR that Powerterm (included with Pathworks) also has
    some way to identify itself but I don't have that anyplace handy to
    look at right now.

    John:
    Afa changing windows titles, if you mean dynamically throughout the
    session, I don't know. There might be a command to do that and if so
    it would be buried someplace in the Programming section of
    Reflection's Help, or you'd need to use a WRQ command to communicate
    with Windows. If you can figure out how to change titles in VB (or
    Reflection Basic), then you could write a script and execute it from
    the host via one of the WRQ commands.

    VAXman:
    I, too, would be curious to know what you've found lacking in
    Reflection. If you can be more specific, maybe someone can offer a
    solution or a work-around.


  16. Re: Setting Reflection 2 window titles from VMS

    In article <47745023.A32E17D@spam.comcast.net>,
    David J Dachtera wrote:

    > "P. Sture" wrote:
    > > [snip]
    > > I did something similar many years ago to distinguish between "standard"
    > > VT100s and an OEM VT100 wannabe which had extended functionality.
    > >
    > > To keep the explanation as simple as possible...
    > >
    > > Before invoking the application software, I sent all terminals the OEM
    > > private sequence to change to OEM-VT100 mode, followed by a "what are
    > > you?" request, and then invoked the application accordingly. This of
    > > course relied on the "standard" VT100s to not change their mode or
    > > otherwise screw up in response to the OEM private sequence.
    > >
    > > On application exit, for the OEM-VT100s I sent the sequence to switch
    > > back to vanilla VT100 mode so as not to interfere with standard VMS or
    > > other third party software.

    >
    > ...which is fine until the user hits while in your app. and
    > connects to a session on another system. (We're talking terminal servers
    > here, of course!)


    Ouch! Fortunately we didn't have to cope with that scenario.

    >
    > Same deal if one s out of an EDT session and goes to do something
    > else on another machine - you usually end up with a 22-line display
    > instead of a 24 line display, and the key pad(s) are still in
    > application mode.
    >


    But you get the same problem if you CTRL-Y out of an editor.

    Back to the question in hand - in a purely DECwindows (CDE) environment
    without terminal emulators involved, I have this little procedure for
    swapping between hosts:

    $ set noon
    $ set host 'p1'
    $ node = f$getsyi("NODENAME")
    $ icon_title = f$extract (3,3,node)
    $ write sys$output "]21;''node' \" !set window_name
    $ write sys$output "]2L;''icon_title' \" !set icon_name
    $ show time

    And oops, I just tried it from my Mac using iTerm, and on logging out of
    the SET HOST session, the iTerm session locked up completely.

    --
    Paul Sture

    Sue's OpenVMS bookmarks:
    http://eisner.encompasserve.org/~stu...bookmarks.html

  17. Re: Setting Reflection 2 window titles from VMS

    In article <391ada0a-b681-4228-920b-ec005dade16d@s8g2000prg.googlegroups.com>, Doug Phillips writes:
    >{...snip...}
    >VAXman:
    >I, too, would be curious to know what you've found lacking in
    >Reflection. If you can be more specific, maybe someone can offer a
    >solution or a work-around.


    First, I'll ask the customer to verify the version of Reflection in use
    at his site. When I get this, I'll post back to this thread with that
    information and a link to a demo. If you can't reproduce it, it may be
    that Reflection has finally fixed the problem. BTW, the program uses
    SMG which I should hope would perform the same on any VTx00 assuming it
    is a VTx00.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  18. Re: Setting Reflection 2 window titles from VMS

    VAXman- wrote:

    > I've been using VTTEST as well as some of my own VT suite of tests (taken
    > from real world cases of applications which failed with these emulators).
    > VTTEST doesn't have tests for some of the VT400 and VT500 sequences. Are
    > there any terminal emulators claiming to be VT400 or VT500 terminals? I
    > think the Reflection one does IIRC. It's been quite a while.


    xterm can be told to pretend that it's a vt420, etc.
    (That's the way to enable the rectangle feature).
    But I'll agree that it's not a complete VT400 or VT500.

    > I don't really care if a there is no way to determine the emulator in use.
    > What I *DO* care about is that they lie to me when they claim to be a VTx00
    > and then can't handle the VTx00 escapes sent to them. I get shat upon by a
    > customer because they perceive it to be a problem with my software when, in
    > fact, it's their terminal emulator. My software works, as advertised, when
    > used with a VTx00 terminal; ergo, the emulators need to clean up their act.


    true - it's a nuisance.

    --
    Thomas E. Dickey
    http://invisible-island.net
    ftp://invisible-island.net

  19. Re: Setting Reflection 2 window titles from VMS

    On Dec 27, 8:17 pm, David J Dachtera
    wrote:
    > VAXman-, @SendSpamHere.ORG wrote:
    >
    > > [snip]
    > > I maintain a product that writes VT escape sequences. I have been plagued
    > > in recent years by the terminal emulators claiming to be VT200/300/400 com-
    > > patible when they are not. I have been urged to just modify the product to
    > > work with Reflections as I was told *everybody* uses Reflections today.

    >
    > In my experience, Reflection (singular) remains THE most complete VT
    > emulation available, and even includes something none of the others do,
    > AFAIK: smooth scroll.


    Quick question (QQ): Can you select an entire line by triple-clicking?
    I have SmarTerm at work and this is one of my few gripes about it. You
    cannot select an entire line without carefully dragging the mouse
    pointer. I have trouble using the mouse that finely and have to
    struggle to select ONLY ONE LINE.

    (Interestingly, our London office uses Reflection. I'll have to ask if
    they can send me a copy.)

    Thanks.

    [...]

    AEF

  20. Re: Setting Reflection 2 window titles from VMS

    In article <13na7047i814d44@corp.supernews.com>, Thomas Dickey writes:
    >
    >
    >VAXman- wrote:
    >
    >> I've been using VTTEST as well as some of my own VT suite of tests (taken
    >> from real world cases of applications which failed with these emulators).
    >> VTTEST doesn't have tests for some of the VT400 and VT500 sequences. Are
    >> there any terminal emulators claiming to be VT400 or VT500 terminals? I
    >> think the Reflection one does IIRC. It's been quite a while.

    >
    >xterm can be told to pretend that it's a vt420, etc.
    >(That's the way to enable the rectangle feature).
    >But I'll agree that it's not a complete VT400 or VT500.


    The rectangle features are where I have encountered some of the problems
    with the emulators.

    DECBI, DECFI, DECSLRM, DECSACE, DECDC, DECIC, DECCRA, DECCARA, DECRARA,
    DECERA, DECFRA, DECSERA have all been problematic with the terminal em-
    ulators. These do not typically fail to perform by themselves in simple
    tests of these functions but combine them with other fucntions in a more
    complex screen painting and things fall to pieces quickly. I've created
    a number of tests and I've run them against real VT400 and VT500 series
    (a VT420 and VT525) terminals for comparison. I would expect the output
    of the emulators to result with the exact same display as seen on these
    VTs; they do not.


    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast