PWS 433a new problems... - DEC

This is a discussion on PWS 433a new problems... - DEC ; Well, discovering that it was in serial console mode was a step in the right direction, but not a large one. I've tried several terminal clients (minicom and cu on Linux, hyper terminal and alphacom on win2k), and the results ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: PWS 433a new problems...

  1. PWS 433a new problems...

    Well, discovering that it was in serial console mode was a step in the
    right direction, but not a large one.

    I've tried several terminal clients (minicom and cu on Linux, hyper
    terminal and alphacom on win2k), and the results have been pretty
    disappointing. cu is the only client that'll allow me to access the
    BIOS setup via F2. But the terminal displays mostly gibberish, which i
    assume are codes telling the client how to display the terminal. Making
    sure the terminal emulation is set to VT52, VT100, or VT102 changes
    nothing. The clients actually display better when terminal emulation is
    set to ANSI or SCOLinux. But no response to hitting the F2 key. And
    minicom has issues with disconnecting and having to reconnect.

    Connections set at 9600 8 n 1

    Am I missing something obvious?

  2. Re: PWS 433a new problems...

    9600 8 n 1 for setup the Serial console is right.
    DPWS support two console modes.
    SRM console support for OpenVMS and OSF and
    with prompt ">>>" for enter SRM commands
    AlphaBIOS (ARC) console support for WindowsNT and
    you should press F2 from Keyboard to enter console setup mode.
    So, I think you should connect Keyboard,Mouse,Monitor to enter the
    AlphaBIOS setup mode.
    Good luck. M.T.
    PS: 433a used for running Windows NT by default.



  3. Re: PWS 433a new problems...

    Do this

    1) Install a Matrox or S3 Trio 64 card in one of the bottom slots
    2) Plug in a regular PC keyboard and Mouse
    3) DO the following if it goes into AlphaBIOS mode

    F2 then F6 advanced mode

    Change the console to VMS or Tru64 and save the changes (F10)

    4) Power cycle the system
    5) Restart the system and if it goes back into Alphabios you need to go buy
    a battery CR2032 from Batteries Plus etc

    If the battery is OK it should get a blue screen ... then hit the return key
    4) Do this afterwards

    >>>set console graphics to keep using a monitor OR
    >>>set console graphics
    >>> set os_type OpenVMS (or Unix)
    >>>set boot_osflags 0,0 (for VMS) or A (for tru64) or 0 for Linux


    >>>init


    This should do it for you


    --

    David B Turner
    Island Computers US Corp
    2700 Gregory St, Suite 180
    Savannah GA 31404
    Tel: 912 447 6622 X201
    Cell: 912 447 6622 X251
    Fax: 912 201 0402
    Email: dbturner@icusc.com
    Web: http://www.islandco.com
    =====================================
    All orders are subject to the following terms and conditions
    of sale. These should be read before ordering.
    http://www.islandco.com/warranty.html

    "DrSlinky" wrote in message
    news:YFS4g.46$pP6.0@fe12.lga...
    > Well, discovering that it was in serial console mode was a step in the
    > right direction, but not a large one.
    >
    > I've tried several terminal clients (minicom and cu on Linux, hyper
    > terminal and alphacom on win2k), and the results have been pretty
    > disappointing. cu is the only client that'll allow me to access the
    > BIOS setup via F2. But the terminal displays mostly gibberish, which i
    > assume are codes telling the client how to display the terminal. Making
    > sure the terminal emulation is set to VT52, VT100, or VT102 changes
    > nothing. The clients actually display better when terminal emulation is
    > set to ANSI or SCOLinux. But no response to hitting the F2 key. And
    > minicom has issues with disconnecting and having to reconnect.
    >
    > Connections set at 9600 8 n 1
    >
    > Am I missing something obvious?




  4. Re: PWS 433a new problems...

    In article , "David Turner, Island Computers US Corp" writes:
    > >>>set console graphics to keep using a monitor OR
    > >>>set console graphics


    This should be

    >>>set console serial to use "headless" via COM1 as console 9k6 8n1


    > >>> set os_type OpenVMS (or Unix)
    > >>>set boot_osflags 0,0 (for VMS) or A (for tru64) or 0 for Linux


    which means for VMS do a non-conversational (=full) boot (,0) from SYS0 (0,)
    For other values of the BOOT command and os flags please see the VMS faq

    http://www.openvms.digital.com/faq/

    > >>>init

    >
    >This should do it for you


    Yup

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  5. Re: PWS 433a new problems...

    Peter 'EPLAN' LANGSTOEGER wrote:
    > In article , "David Turner, Island Computers US Corp" writes:
    >
    >>>>>set console graphics to keep using a monitor OR
    >>>>>set console graphics

    >
    >
    > This should be
    >
    > >>>set console serial to use "headless" via COM1 as console 9k6 8n1

    >
    >
    >>>>>set os_type OpenVMS (or Unix)
    >>>>>set boot_osflags 0,0 (for VMS) or A (for tru64) or 0 for Linux

    >
    >
    > which means for VMS do a non-conversational (=full) boot (,0) from SYS0 (0,)
    > For other values of the BOOT command and os flags please see the VMS faq
    >
    > http://www.openvms.digital.com/faq/
    >
    >
    >>>>>init

    >>
    >>This should do it for you

    >
    >
    > Yup
    >


    Found my answer buried in the install docs of one of the BSD systems.
    When using serial console, ^B corresponded to F2. ^A was F1.

    Not sure if that's a configuration error, but I've got Debian up and
    running on it now.

+ Reply to Thread