• DS10 console issue

    From ihbda@21:1/5 to All on Fri Jan 3 08:47:53 2020
    Hi all,

    Strange DS10 problem that's been bugging me for a while. I have two DS10's and this occurs on both when using the console in graphics mode.

    At the >>> prompt, as soon as I press the shift key, all subsequent keyboard entry is shifted. As soon as the system enters full graphics mode, it behaves as normal.

    Not so much of a problem when installing Unix but when installing VMS, I have to enter a dot in the filename for the backup command but all I get is > (which is obviously SHIFT-.). I can use the numeric keypad but it's a bit annoying...

    Console firmware 7.3-1 dated Feb 27 2007

    Anyone seen this before?

    ih

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stephen Hoffman@21:1/5 to ihbda on Wed Jan 8 13:25:21 2020
    On 2020-01-03 16:47:53 +0000, ihbda said:

    Strange DS10 problem that's been bugging me for a while. I have two
    DS10's and this occurs on both when using the console in graphics mode.

    At the >>> prompt, as soon as I press the shift key, all subsequent
    keyboard entry is shifted. As soon as the system enters full graphics
    mode, it behaves as normal.

    Are you on COM1 with the console prompt input shift-altered as
    described, or—as you should be, when CONSOLE is set GRAPHICS—are you
    over on the VGA with the >>> prompt over there?

    And you probably don't want to be on COM2 for anything console-related.

    The RMC can have some serial settings you'll want to look at, and
    that'll be the usual and often only use of COM1 when CONSOLE is
    GRAPHICS and not SERIAL.

    Check the (presumably) terminal emulator settings, too. On a good day,
    the graphics console can be a VT52. Otherwise, 9600 8N1.

    Directly-attached keyboards for OpenVMS also need scanset 3 support,
    but you've not indicated what you're using with this AlphaServer DS10
    box.


    --
    Pure Personal Opinion | HoffmanLabs LLC

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ihbda@21:1/5 to Stephen Hoffman on Thu Jan 9 03:46:53 2020
    On Wednesday, 8 January 2020 18:25:33 UTC, Stephen Hoffman wrote:
    On 2020-01-03 16:47:53 +0000, ihbda said:

    Strange DS10 problem that's been bugging me for a while. I have two
    DS10's and this occurs on both when using the console in graphics mode.

    At the >>> prompt, as soon as I press the shift key, all subsequent keyboard entry is shifted. As soon as the system enters full graphics mode, it behaves as normal.

    Are you on COM1 with the console prompt input shift-altered as
    described, or—as you should be, when CONSOLE is set GRAPHICS—are you over on the VGA with the >>> prompt over there?

    And you probably don't want to be on COM2 for anything console-related.

    The RMC can have some serial settings you'll want to look at, and
    that'll be the usual and often only use of COM1 when CONSOLE is
    GRAPHICS and not SERIAL.

    Check the (presumably) terminal emulator settings, too. On a good day,
    the graphics console can be a VT52. Otherwise, 9600 8N1.

    Directly-attached keyboards for OpenVMS also need scanset 3 support,
    but you've not indicated what you're using with this AlphaServer DS10
    box.


    --
    Pure Personal Opinion | HoffmanLabs LLC

    Thanks for the response.

    This is all being done on the graphics console. VGA monitor. Admittedly I'm using a non-DEC PS/2 keyboard. Generic HP PC keyboard. "set console graphic"s is configured.

    This behavior occurs within the console itself before either DUnix or OVMS are booted. Once either OS is in it's initial text mode, the behaviour continues to manifest itself. Once either OS goes into a graphics mode (ie X), normal behavior returns.

    I think, from memory, it works fine using COM1.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stephen Hoffman@21:1/5 to ihbda on Thu Jan 16 18:27:07 2020
    On 2020-01-09 11:46:53 +0000, ihbda said:

    This is all being done on the graphics console. VGA monitor. Admittedly
    I'm using a non-DEC PS/2 keyboard. Generic HP PC keyboard.

    And the SRM console has been configured with the matching keyboard definition?

    At the SRM console prompt:
    show kbd_hardware_type
    show language
    show language_name
    etc...
    Make sure those match your expectations.

    I don't immediately recall the DEC name for the generic PC keyboard. PCXAL?

    Scrounge a DEC LK OpenVMS keyboard, preferably.

    The PC keyboards can get "fun" with OpenVMS.

    --
    Pure Personal Opinion | HoffmanLabs LLC

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ihbda@21:1/5 to Stephen Hoffman on Fri Jan 17 04:04:09 2020
    On Thursday, 16 January 2020 23:27:13 UTC, Stephen Hoffman wrote:

    On 2020-01-09 11:46:53 +0000, ihbda said:

    This is all being done on the graphics console. VGA monitor. Admittedly
    I'm using a non-DEC PS/2 keyboard. Generic HP PC keyboard.

    And the SRM console has been configured with the matching keyboard definition?

    At the SRM console prompt:
    show kbd_hardware_type
    show language
    show language_name
    etc...
    Make sure those match your expectations.

    Thanks - I'll check those settings at the weekend.


    The PC keyboards can get "fun" with OpenVMS.

    Not even at the VMS 'stage'. Purely still in the console monitor.

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