Conference iosg::all-in-1_v30

    G'day,
    
    I have some more information the customer is using a VT340 terminal.  He 
    referred me to the ALL-IN-1 Management Guide page 15-29 Graphics 
    Applications.
    
    The customer set's the following terminal attributes SIXEL and REGIS
    support and Terminal type to VT200.  Before he get's into ALL-IN-1 he
    does a set term/inquire.
    
    The customer was under the impression that ALL-IN-1 would support SIXEL
    and REGIS documents. 15-29 it does say VT200 types are supported.  Is
    there anything else I have to do to get SIXEL and REGIS documents to
    display on a VT340 terminal that emulates a VT200 terminal type (set
    term/device_type=vt200) ?
    
    I would be grateful for any help Thanks
    
    Sunil

    Sunil,

    Is the customer placing the ReGIS and SIXEL into an A1ENCODE envelope?

    There is some small detail about using A1ENCODE in the previous
    versions of this conference.

    You might want to give more information about exactly what is contained
    in the document and what appears when the document(s) are displayed.

    Good luck,
    don
    
    P.S. ReGIS is Remote Graphics Interface System so the e is small (like
    me) but it's probably not one of the important trademarks given the sad
    death of the GIGI.

    Don,
    
    This is what I did to solve the problem with your help.
    
    1. Set the terminal characteristics as using command procedure
       SYS$MANAGER:A1WPSPLUS_LOGIN.COM.
    
    Terminal: _NVA4:      Device_Type: VT125         Owner: A1 Manager
                                                  Username: ALLIN1
    
       Input:   9600      LFfill:  0      Width:  80      Parity: None
       Output:  9600      CRfill:  0      Page:   24
    
    Terminal Characteristics:
       Interactive        Echo               Type_ahead         No Escape
       Hostsync           TTsync             Lowercase          Tab
       Wrap               Scope              No Remote          Eightbit
       Broadcast          No Readsync        No Form            Fulldup
       No Modem           No Local_echo      Autobaud           Hangup
       No Brdcstmbx       No DMA             No Altypeahd       Set_speed
       Line Editing       Insert editing     No Fallback        Dialup
       No Secure server   No Disconnect      No Pasthru         NoSyspassword
       SIXEL Graphics     No Soft Characters Printer port       Numeric Keypad
       ANSI_CRT           Regis              No Block_mode      Advanced_video
       No Edit_mode       DEC_CRT            No DEC_CRT2        No DEC_CRT3
       No DEC_CRT4
    
    2. Did a $ SET TERM/DEVICE_TYPE=VT125 OR VT200 for a VT240-style
       graphics language  <---- this is for a ReGIS document.
    
    3. As suggested used $ A1ENCODE/OUTPUT=WHATEVER.REG INPUTGRAPH.REG/REGIS
    
    4. As a test I did a <LIST WHATEVER.REG to display it in ALL-IN-1,
       worked.
    
    This seems like hardwork for a Joe Public user using A1ENCODE from the
    DCL prompt.  Some user's think that they have won LOTTO (it's Bingo in
    England) when they see a "$".  Apart from customizing ALL-IN-1 is there
    a better way ?
    
    By the way just for completeness the MAXBUF size is a factor in all of
    this as per the previous note in the last ALL-IN-1 conference.  The site 
    had it set to 8192.
    
    Sunil
    
    (I feel like telling a New Zealand joke because they lost a cricket
    match and that prevented the Aussies from getting into the Semi-finals
    of the World Cup.  I'll be kind and say nothing for the time being).
    

    Sunil,

    As you have guessed, A1ENCODE was never meant to be used or seen by
    human beings.  No right thinking human should be exposed to the $ or
    other computer prompt.

    The normal usage of A1ENCODE is in an application which creates or
    'imports' graphic document components.  It's not clear what sort of
    application the users are using but it is usually fairly easy to add
    the invocation of A1ENCODE in applications.  Obviously, there is the
    cost of cranking up DCL.  It would have been nice for it to become
    included as an external image capable of being used by the EXECUTE
    function.

    It doesn't sound right that you have to fiddle with the TERMINAL
    settings after using A1WPSPLUS_LOGIN.COM but I'm not sure.

    Finally, don't forget that one of the greatest strength's of the
    ALL-IN-1 product is the ease and safety with which it can be
    customised.  My suggestion is to make the changes to help the users. 
    The users should, of course, always be the center of our focus at all
    times.

    Have fun,
    don

    P.S. Jokes are fine here (they let me in here, don't they?) but it's
         usually not great to insult too many people at once (of course, I
         break that rule with regularity   :').