• Oh, Now I have broken my edit command

    From Ronald Hudson@21:1/5 to All on Wed Aug 30 19:41:16 2023
    Before when I issued the 'change' command to edit it would clear the screen and display the file, or at least the top screen full.

    Now it just types the file out and the cursor keys do not move me to parts of the file.

    I have checked and my show terminal/full still shows I am on a 'scope' and my terminal type is 'vt100' which should work with telnet under Linux.

    What did I do? How do I undo it?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to Ronald Hudson on Wed Aug 30 19:42:53 2023
    On Wednesday, August 30, 2023 at 7:41:18 PM UTC-7, Ronald Hudson wrote:
    Before when I issued the 'change' command to edit it would clear the screen and display the file, or at least the top screen full.

    Now it just types the file out and the cursor keys do not move me to parts of the file.

    I have checked and my show terminal/full still shows I am on a 'scope' and my terminal type is 'vt100' which should work with telnet under Linux.

    What did I do? How do I undo it?
    P.s. I have finally set the date properly - I am living big in 1995!
    That is the biggest change since it was working.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to All on Wed Aug 30 20:23:42 2023
    I may have stumbled on a workaround - I was doing this in my own login.com:

    set terminal/type=6

    I changed it to:

    set terminal/device=vt100

    Now edit is happy again...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave McGuire@21:1/5 to Ronald Hudson on Thu Aug 31 11:07:32 2023
    On 8/30/23 23:23, Ronald Hudson wrote:
    I may have stumbled on a workaround - I was doing this in my own login.com:

    set terminal/type=6

    I changed it to:

    set terminal/device=vt100

    Now edit is happy again...

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to Dave McGuire on Thu Aug 31 08:21:11 2023
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator. I wonder what /inquire will make of that :^)
    I am setting up my other laptop with an external keyboard and mouse so I have a numberpad, so far it looks like my f1 key is the gold key... I don't suppose anyone sells a VT100 clone these days.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave McGuire@21:1/5 to Ronald Hudson on Thu Aug 31 11:52:51 2023
    On 8/31/23 11:21, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator. I wonder what /inquire will make of that :^)

    It should work fine, and should pick it up as a VT100.

    I am setting up my other laptop with an external keyboard and mouse so I have a numberpad, so far it looks like my f1 key is the gold key... I don't suppose anyone sells a VT100 clone these days.

    There are many standalone terminals on the hobbyist market, and many
    shared as open-source hardware. Trouble is, they all use PeeCee keyboards.

    Here's a set of X resources that I use for xterm, to make it behave reasonably well as a VT100:

    ---------------
    XTerm*VT100.translations: #override \n \
    ~Shift <Key>F1: string(0x1b) string("OP") \n \
    ~Shift <Key>F2: string(0x1b) string("OQ") \n \
    ~Shift <Key>F3: string(0x1b) string("OR") \n \
    ~Shift <Key>F4: string(0x1b) string("OS") \n \
    ~Shift <Key>F5: string("Break") \n \
    ~Shift <Key>F6: string(0x1b) string("[17~") \n \
    ~Shift <Key>F7: string(0x1b) string("[18~") \n \
    ~Shift <Key>F8: string(0x1b) string("[19~") \n \
    ~Shift <Key>F9: string(0x1b) string("[20~") \n \
    ~Shift <Key>F10: string(0x1b) string("[21~") \n \
    ~Shift <Key>F11: string(0x1b) string("[23~") \n \
    ~Shift <Key>F12: string(0x1b) string("[24~") \n \
    Shift <Key>F1: string(0x1b) string("[23~") \n \
    Shift <Key>F2: string(0x1b) string("[24~") \n \
    Shift <Key>F3: string(0x1b) string("[25~") \n \
    Shift <Key>F4: string(0x1b) string("[26~") \n \
    Shift <Key>F5: string(0x1b) string("[28~") \n \
    Shift <Key>F6: string(0x1b) string("[29~") \n \
    Shift <Key>F7: string(0x1b) string("[31~") \n \
    Shift <Key>F8: string(0x1b) string("[32~") \n \
    Shift <Key>F9: string(0x1b) string("[33~") \n \
    Shift <Key>F10: string(0x1b) string("[34~") \n \
    Shift <Key>F11: string(0x1b) string("[28~") \n \
    Shift <Key>F12: string(0x1b) string("[29~") \n \
    <Key>Print: string(0x1b) string("[28~") \n \
    <Key>Cancel: string(0x1b) string("[29~") \n \
    <Key>Pause: string(0x1b) string("Om") \n \
    <Key>Insert: string(0x1b) string("[2~") \n \
    <Key>Delete: string(0x1b) string("[3~") \n \
    <Key>Home: string(0x1b) string("[1~") \n \
    <Key>End: string(0x1b) string("[4~") \n \
    <Key>Prior: string(0x1b) string("[5~") \n \
    <Key>Next: string(0x1b) string("[6~") \n \
    <Key>BackSpace: string(0x7f) \n \
    <Key>Num_Lock: string(0x1b) string("OP") \n \
    <Key>KP_Divide: string(0x1b) string("OQ") \n \
    <Key>KP_Multiply: string(0x1b) string("OR") \n \
    <Key>KP_Subtract: string(0x1b) string("OS") \n \
    <Key>KP_Add: string(0x1b) string("Ol") \n \
    <Key>KP_Enter: string(0x1b) string("OM") \n \
    <Key>KP_Decimal: string(0x1b) string("On") \n \
    <Key>KP_0: string(0x1b) string("Op") \n \
    <Key>KP_1: string(0x1b) string("Oq") \n \
    <Key>KP_2: string(0x1b) string("Or") \n \
    <Key>KP_3: string(0x1b) string("Os") \n \
    <Key>KP_4: string(0x1b) string("Ot") \n \
    <Key>KP_5: string(0x1b) string("Ou") \n \
    <Key>KP_6: string(0x1b) string("Ov") \n \
    <Key>KP_7: string(0x1b) string("Ow") \n \
    <Key>KP_8: string(0x1b) string("Ox") \n \
    <Key>KP_9: string(0x1b) string("Oy") \n \
    Ctrl <Key>0: string(0x1b) string("Op") \n \
    Ctrl <Key>1: string(0x1b) string("Oq") \n \
    Ctrl <Key>2: string(0x1b) string("Or") \n \
    Ctrl <Key>3: string(0x1b) string("Os") \n \
    Ctrl <Key>4: string(0x1b) string("Ot") \n \
    Ctrl <Key>5: string(0x1b) string("Ou") \n \
    Ctrl <Key>6: string(0x1b) string("Ov") \n \
    Ctrl <Key>7: string(0x1b) string("Ow") \n \
    Ctrl <Key>8: string(0x1b) string("Ox") \n \
    Ctrl <Key>9: string(0x1b) string("Oy") \n \
    Ctrl <Key>Return: string(0x1b) string("OM") \n \
    ~Shift <Key>Up: string(0x1b) string("[A") \n \
    Shift <Key>Up: scroll-back(1,lines) \n \
    ~Shift <Key>Down: string(0x1b) string("[B") \n \
    Shift <Key>Down: scroll-forw(1,lines) \n \
    <Key>Right: string(0x1b) string("[C") \n \
    <Key>Left: string(0x1b) string("[D")
    ---------------

    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bill@21:1/5 to Dave McGuire on Thu Aug 31 12:35:53 2023
    On 8/31/2023 11:52 AM, Dave McGuire wrote:
    On 8/31/23 11:21, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

      It should work fine, and should pick it up as a VT100.

    He didn't say what terminal emulator he is using. :-)

    bill

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bill@21:1/5 to Ronald Hudson on Thu Aug 31 12:34:35 2023
    On 8/31/2023 11:21 AM, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator. I wonder what /inquire will make of that :^)

    That is up to the terminal emulator. By default Putty returns
    "PuTTY" but it can be anything you want.

    I am setting up my other laptop with an external keyboard and mouse so I have a numberpad, so far it looks like my f1 key is the gold key... I don't suppose anyone sells a VT100 clone these days.

    Depends on your abilities. I bought a couple of small PCB's that
    are supposed to be VT100 compatible terminals but haven't gotten
    around do building any of them. I usually use Putty under both
    Windows and Linux and it works just fine.

    bill

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis Boone@21:1/5 to All on Thu Aug 31 16:46:03 2023
    My 'terminal' is a Linux box running a terminal emulator. I wonder what /inquire will make of that :^)

    My xterm, which hasn't been told specifically which type to emulate,
    when queried about device attributes, reports:

    ^[[?64;1;2;6;9;15;16;17;18;21;22;28c

    which translates (I think) to:

    vt420
    132 columns
    printer
    selective erase
    national replacement character sets
    technical characters
    locator port
    terminal state interrogation
    user windows
    horizontal scrolling
    ansi color
    rectangular editing

    De

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johnny Billquist@21:1/5 to bill on Thu Aug 31 18:50:28 2023
    On 2023-08-31 18:34, bill wrote:
    On 8/31/2023 11:21 AM, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

    That is up to the terminal emulator.  By default Putty returns
    "PuTTY" but it can be anything you want.

    How would it return "PuTTY"? The escape sequence to identify a terminal
    is not answering with a string. You are probably confusing this with the terminal name that can be sent as an option in telnet or ssh sessions.

    With that said, putty probably have some options for setting exactly
    what to respond to the escape sequence as well, as there are first of
    all the primary response, which is different for a VT100, VT102, VT102,
    VT200, VT300, VT400 or VT500 (as well as having some other types in
    there as well), and then there is the secondary response, which tells if
    you have things like AVO, a printer port, can do color, sixel, regis,
    and a whole bunch of other things...

    Johnny

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave McGuire@21:1/5 to bill on Thu Aug 31 13:03:24 2023
    On 8/31/23 12:35, bill wrote:
    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

       It should work fine, and should pick it up as a VT100.

    He didn't say what terminal emulator he is using.  :-)

    Hi Bill! Earlier he did mention connecting from a Linux box, which
    will be either xterm or similar, which will identify themselves as a
    VT100. By default, anyway; the response string can be changed.

    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to Ronald Hudson on Thu Aug 31 12:26:44 2023
    On Thursday, August 31, 2023 at 12:22:29 PM UTC-7, Ronald Hudson wrote:
    He didn't say what terminal emulator he is using. :-)
    I am using both Putty and the Konsole program (which Is the native terminal program for KDE).
    I just found in Putty there is a setting under 'Keyboard' (I think) that lets you specify VT100 keycodes.

    I have worked up a cheat sheet for Putty/VT100 when using EDIT *change mode. How can I attach it (it is in LibreOffice write

    Further detail, but I think I am repeating myself, I SSH into the server where simh is running. Then from there I Telnet localhost 10000 and I am connected to one of the DZs then I seem to have to hit return 2 or 3 times to get the system's attention
    whereupon it asks me for my PPN.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to All on Thu Aug 31 12:22:27 2023
    He didn't say what terminal emulator he is using. :-)
    I am using both Putty and the Konsole program (which Is the native terminal program for KDE).
    I just found in Putty there is a setting under 'Keyboard' (I think) that lets you specify VT100 keycodes.

    I have worked up a cheat sheet for Putty/VT100 when using EDIT *change mode. How can I attach it (it is in LibreOffice write

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave McGuire@21:1/5 to Ronald Hudson on Thu Aug 31 17:00:02 2023
    On 8/31/23 15:26, Ronald Hudson wrote:
    Further detail, but I think I am repeating myself, I SSH into the server where simh is running. Then from there I Telnet localhost 10000 and I am connected to one of the DZs then I seem to have to hit return 2 or 3 times to get the system's attention
    whereupon it asks me for my PPN.

    Why don't you just telnet directly to the machine? If it's on the
    local network, there shouldn't be any worry of people sniffing packets. Assuming unencrypted telnet.

    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ronald Hudson@21:1/5 to Dave McGuire on Thu Aug 31 15:24:08 2023
    On Thursday, August 31, 2023 at 2:00:04 PM UTC-7, Dave McGuire wrote:
    On 8/31/23 15:26, Ronald Hudson wrote:
    Further detail, but I think I am repeating myself, I SSH into the server where simh is running. Then from there I Telnet localhost 10000 and I am connected to one of the DZs then I seem to have to hit return 2 or 3 times to get the system's attention
    whereupon it asks me for my PPN.
    Why don't you just telnet directly to the machine? If it's on the
    local network, there shouldn't be any worry of people sniffing packets. Assuming unencrypted telnet.
    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    I was worried about the fact that Linux now supports IPV6, which is routeable. I really don't know much about IPV6 so Firewall on the server only allows SSH in. I am working on setting up Fail2Ban too.
    I sure wish I could SSH into simh.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave McGuire@21:1/5 to bill on Thu Aug 31 20:36:13 2023
    On 8/31/23 20:20, bill wrote:
    Remember, you can also do "set terminal/inquire", which will work for >>>>> many terminal types.

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

    That is up to the terminal emulator.  By default Putty returns
    "PuTTY" but it can be anything you want.

    How would it return "PuTTY"? The escape sequence to identify a
    terminal is not answering with a string. You are probably confusing
    this with the terminal name that can be sent as an option in telnet or
    ssh sessions.

    On the "Terminal" setup screen it says:
    Answerback to ^E

    and has text block below it with "PuTTY" in it by default.

    I just tried it on my Linux box and sending a ^E to putty  did, in
    fact, return "PuTTY".  Windows version did the same. Changing it to
    "VT100" caused it to return VT100.

    That's the answerback string. That's not the same as querying for
    the terminal type. The answerback string is an ASCII string, and that's
    not what's retrieved with "set term/inq".

    -Dave

    --
    Dave McGuire, President/Curator
    Large Scale Systems Museum
    New Kensington, PA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bill@21:1/5 to Johnny Billquist on Thu Aug 31 20:20:44 2023
    On 8/31/2023 12:50 PM, Johnny Billquist wrote:
    On 2023-08-31 18:34, bill wrote:
    On 8/31/2023 11:21 AM, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote:

    Remember, you can also do "set terminal/inquire", which will work for
    many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

    That is up to the terminal emulator.  By default Putty returns
    "PuTTY" but it can be anything you want.

    How would it return "PuTTY"? The escape sequence to identify a terminal
    is not answering with a string. You are probably confusing this with the terminal name that can be sent as an option in telnet or ssh sessions.

    On the "Terminal" setup screen it says:
    Answerback to ^E

    and has text block below it with "PuTTY" in it by default.

    I just tried it on my Linux box and sending a ^E to putty did, in
    fact, return "PuTTY". Windows version did the same. Changing it to
    "VT100" caused it to return VT100.


    With that said, putty probably have some options for setting exactly
    what to respond to the escape sequence as well, as there are first of
    all the primary response, which is different for a VT100, VT102, VT102, VT200, VT300, VT400 or VT500 (as well as having some other types in
    there as well), and then there is the secondary response, which tells if
    you have things like AVO, a printer port, can do color, sixel, regis,
    and a whole bunch of other things...

      Johnny


    bill

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johnny Billquist@21:1/5 to Dennis Boone on Fri Sep 1 23:28:36 2023
    On 2023-08-31 18:46, Dennis Boone wrote:
    > My 'terminal' is a Linux box running a terminal emulator. I wonder what
    > /inquire will make of that :^)

    My xterm, which hasn't been told specifically which type to emulate,
    when queried about device attributes, reports:

    ^[[?64;1;2;6;9;15;16;17;18;21;22;28c

    which translates (I think) to:

    vt420
    132 columns
    printer
    selective erase
    national replacement character sets
    technical characters
    locator port
    terminal state interrogation
    user windows
    horizontal scrolling
    ansi color
    rectangular editing

    Interesting. I've never seen an xterm version that identified as a VT420 before.

    What version of xterm, on what kind of system?

    Johnny

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johnny Billquist@21:1/5 to bill on Fri Sep 1 23:16:59 2023
    On 2023-09-01 02:20, bill wrote:
    On 8/31/2023 12:50 PM, Johnny Billquist wrote:
    On 2023-08-31 18:34, bill wrote:
    On 8/31/2023 11:21 AM, Ronald Hudson wrote:
    On Thursday, August 31, 2023 at 8:07:34 AM UTC-7, Dave McGuire wrote: >>>>
    Remember, you can also do "set terminal/inquire", which will work for >>>>> many terminal types.

    -Dave

    My 'terminal' is a Linux box running a terminal emulator.  I wonder
    what /inquire will make of that :^)

    That is up to the terminal emulator.  By default Putty returns
    "PuTTY" but it can be anything you want.

    How would it return "PuTTY"? The escape sequence to identify a
    terminal is not answering with a string. You are probably confusing
    this with the terminal name that can be sent as an option in telnet or
    ssh sessions.

    On the "Terminal" setup screen it says:
    Answerback to ^E

    and has text block below it with "PuTTY" in it by default.

    I just tried it on my Linux box and sending a ^E to putty  did, in
    fact, return "PuTTY".  Windows version did the same. Changing it to
    "VT100" caused it to return VT100.

    Yes... And the answerback message can be set to anything, and is *not*
    used to figure out what terminal you have.

    On a real VT100, you go into setup and press (I think it is) SHIFT+A,
    and then you can type in what you want the terminal to respond as the answerback message.

    It's completely unrelated to how you identify what terminal you have.

    Johnny

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis Boone@21:1/5 to All on Sat Sep 2 01:28:45 2023
    Interesting. I've never seen an xterm version that identified as a VT420 before.

    What version of xterm, on what kind of system?

    344 and 379 on two different Debian releases.

    De

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)