Conference jamin::pathworks32

Charlie, thanks for your input. Given the time and the opportunity,
we plan to have PowerTerm support various TE personalities, just
like you can in some editors, or spreadsheets.

>    The Graphical keyboard map was interesting, but a number of the key
>    mappings it indicated didn't match the way the README says the keys
>    are mapped (both mappings appear to work).

Specifically?

>    I notice that the mapped Alt-keys (as opposed to menu Alt-keys) make
>    the PC beep (although they work). That's really annoying.

Try 4.00.32, it's now fixed.

>    > Compose is Ctrl+Alt, followed by the usual LK compose sequence, for
>    > example: AA for @.
>    
>    That's going to be confusing to PC users accustomed to the Alt and Ctrl
>    keys being shift keys; they will react to the above by holding down
>    Ctrl-Alt and typing a twice, then when that doesn't work, probably
>    holding down Ctrl-Alt-Shift and typing a twice.

What do you suggest? We opted for Ctrl-Alt, since KEAterm uses that.
VT320 uses ESC, which may not be popular with people whose host editor
(EMACS, TECO) requires this key. PowerTerm's ESC actually sends ESC,
and this is even useful in DCL when you want to test some escape
sequence directly.

In any case, we'll try to make Compose configurable in the next
version.

>    > Do not confuse the buttons named "F1" - "F12" on the bottom of the
>    > screen with function keys F1 - F12 on your keyboard. These are
>    > actually programmable buttons whose names and behaviour you can modify.
>    
>    Then why aren't the default names something less confusing, like
>    Button1 through Button12?

Agreed, I sure was confused by this initially. My idea for the next
version is to have, instead of:

|   F1   |   F2   |   F3   |   F4   |   F5   |   F6   |   F7   |   F8   |...

something like:

| Right- |  click |   on   |  these |buttons |   to   | define  | them  |...

>    A note on mouse support: I think the cut & paste support for the mouse
>    is very nice, but you might want to consider an option for supporting
>    three-button mice for those people who are used to the way DECterm and
>    VTstar work (which is where my users will be coming from, not VT320).

This is in the plan for the next version. Anything else around mice?

>    > TELNET.PSL
>    
>    It would be much handier if this script prompted for a host name, or at
>    least brought up the Connect Dialog Box, if there was no second
>    parameter given.

Agreed. 

>    ------------------------------------------------------------------------
>    Despite the above, I still consider PowerTerm 525 an improvement over
>    VT320. I don't think I could recommend it over VTstar at this point,
>    though.

Please give us the list of the top 5 features that you can't live
without. We finally have an official, funded, supported TE, after all 
that great talent invested in VTstar, WinVT, VT320...

Going with PowerTerm was not the only option, and, as you well point 
out, it can't match VTstar in some areas. Also, VT320 has better 
keyboard support in some areas.

However, this is what we now have, it comes from the outside, but we 
can totally control how it evolves in the next few releases. Probably
more so than we could with internal products.

I'll be collecting all the wishes -- keep them coming.

Slobodan

> Charlie, thanks for your input. 
    
    You're very welcome. Thank _you_ for asking for and reading it!
    
>>  The Graphical keyboard map was interesting, but a number of the key
>>  mappings it indicated didn't match the way the README says the keys
>>  are mapped (both mappings appear to work).
>Specifically?
    
    For example, if you put the cursor over the Help key, it indicates
    Alt+5 instead of Ctrl-F5. Also, both PF4 and KP- are indicated as PC
    KP+ (I think it's supposed to be Alt+KP+ for the latter).
    
>>  I notice that the mapped Alt-keys (as opposed to menu Alt-keys) make
>>  the PC beep (although they work). That's really annoying.
>Try 4.00.32, it's now fixed.
    
    Did so, thanks. I also notice that it now pops up the Connect Dialog
    Box when I start it, which is nice too.
    
>>>Compose is Ctrl+Alt, followed by the usual LK compose sequence, for
>>>example: AA for @.   
>>  That's going to be confusing to PC users accustomed to the Alt and Ctrl
>>  keys being shift keys; they will react to the above by holding down
>>  Ctrl-Alt and typing a twice, then when that doesn't work, probably
>>  holding down Ctrl-Alt-Shift and typing a twice.
>What do you suggest? We opted for Ctrl-Alt, since KEAterm uses that.
>VT320 uses ESC, which may not be popular with people whose host editor
>(EMACS, TECO) requires this key. PowerTerm's ESC actually sends ESC,
>and this is even useful in DCL when you want to test some escape
>sequence directly.
    
    DECterm and VT320e use Alt-Space. I would have said Alt-C, except that
    you need it for the Communication menu. Having an insert-special-
    character pulldown or pop-up under the Edit menu might be nice, too.
    
    >> Do not confuse the buttons named "F1" - "F12" on the bottom of the
    [...]
    
    Here's a thought. Why not have the default functions of the bottom-row
    buttons be the VT-keyboard keys that are the hardest to do on a PC
    keyboard: Compose, F13, F14, Help, Do, F17-F20, and KP- for example.
    
    

>    For example, if you put the cursor over the Help key, it indicates
>    Alt+5 instead of Ctrl-F5. Also, both PF4 and KP- are indicated as PC
>    KP+ (I think it's supposed to be Alt+KP+ for the latter).

Will look into it.

>    DECterm and VT320e use Alt-Space. I would have said Alt-C, except that
>    you need it for the Communication menu. Having an insert-special-
>    character pulldown or pop-up under the Edit menu might be nice, too.

Alt-Space is another no-no on Windows -- it opens the system menu.

Even if the English version had no Communications menu, some other 
localized UI might have a "C" in the menu, so *all* Alt-<letter> 
combos must be ruled out.

Can you clarify what you would put under that special character pop-up
or menu? I understand that you are willing to reach for it (via the mouse
or the keyboard) and than what -- would you like to enter a numeric
value, or see some sort of table pop up? If the latter, the Windows 
Character Map applet (Accessories group) may serve the purpose.

>    >> Do not confuse the buttons named "F1" - "F12" on the bottom of the
>    [...]
>    
>    Here's a thought. Why not have the default functions of the bottom-row
>    buttons be the VT-keyboard keys that are the hardest to do on a PC
>    keyboard: Compose, F13, F14, Help, Do, F17-F20, and KP- for example.
    
We'll put this on the wish list. 

>Alt-Space is another no-no on Windows -- it opens the system menu.
>Even if the English version had no Communications menu, some other 
>localized UI might have a "C" in the menu, so *all* Alt-<letter> 
>combos must be ruled out.

    I still think an Alt-symbol combination would be less confusing.
    Perhaps Alt-Backslash?
    
>Can you clarify what you would put under that special character pop-up
>or menu? I understand that you are willing to reach for it (via the mouse
>or the keyboard) and than what -- would you like to enter a numeric
>value, or see some sort of table pop up? If the latter, the Windows 
>Character Map applet (Accessories group) may serve the purpose.
    
    I was thinking in terms of a table, with one click on a symbol serving
    as a select-and-insert. The Windows Character Map applet will indeed
    serve, but it's use is somewhat clumsy: Launch the applet, select a
    useful font/subset, double-click the character you want, copy it,
    switch to PowerTerm, and paste it. Rather a pain.
    

>    I still think an Alt-symbol combination would be less confusing.
>    Perhaps Alt-Backslash?

This shows how tough it is to make "the best" choice in this type
of product... The Backslash key may not always be where you expect it
to be: I switch to UK, French, or Russian layouts all the time, and
Backslash moves around.

I think the only solution is to make this configurable. The choice of
Ctrl+Alt in this version was based on mimicing KEAterm, one of the 
leaders.

>    I was thinking in terms of a table, with one click on a symbol serving
>    as a select-and-insert. The Windows Character Map applet will indeed
>    serve, but it's use is somewhat clumsy: Launch the applet, select a
>    useful font/subset, double-click the character you want, copy it,
>    switch to PowerTerm, and paste it. Rather a pain.

Yes, it's a pain like everything else in Windows -- lots of navigation,
especially if you insist on using the mouse. I believe the Character
Map applet can be forced to stay on top, but the way.

Did you try PowerTerm's power pad? Looks like it meets the select-and-insert
requirement, but you only have 36 possibilities.

>This shows how tough it is to make "the best" choice in this type
>of product... The Backslash key may not always be where you expect it
>to be: I switch to UK, French, or Russian layouts all the time, and
>Backslash moves around.

...for example, on the French keyboard you have to press:

    Ctrl+LeftAlt+8	(or RightAlt+8)

to get \

Regards,
Slobodan

    re: .5  copy/paste
    
    could we at least implement right-mouse menus, so I don't have to go up
    to the menu bar to find copy/paste (since my fingers absolutely refuse
    to lear Ctrl-Ins/Shift-Ins)?  Consider that for the wishlist, if you
    would.  I would guess that the quick-paste that's there now will be
    good for some folks, but others would like to be able to have it act
    more like other winders apps - maybe configuable?
    
    
            

>    could we at least implement right-mouse menus, so I don't have to go up
>    to the menu bar to find copy/paste (since my fingers absolutely refuse
>    to lear Ctrl-Ins/Shift-Ins)?  Consider that for the wishlist, if you
>    would.  I would guess that the quick-paste that's there now will be
>    good for some folks, but others would like to be able to have it act
>    more like other winders apps - maybe configuable?

The copy/paste tools are third/fourth from the left -- some eye movement
and one click away. Seems easier than a right-button click for the menu, 
plus more eye movement to locate words "Copy/Paste" and a click. No?
Unless you have removed the toolbar from view...

The current quick-paste with the RIGHT button is there for those coming 
from DECterm. We'll try to implement the other even-quicker-paste from 
DECterm: selecting with the RIGHT button and then releasing will paste 
in the selection. The plan is also to use the MIDDLE mouse button
for the menus, again for DECwindows lovers.

This will obviously clash with the Windows-like RIGHT button menus
preferred by others.

Clearly, there is no other way but to make it fully configurable so that 
everybody could have it their way. It's not so much work, and I hope 
that somebody will fight for this in the coming versions, since Ericom 
folks are very responsive. (In fact, it is so much easier dealing with 
3rd parties than with internal teams to get in almost anything you want.)

Regards,
Slobodan

> folks are very responsive. (In fact, it is so much easier dealing with 
> 3rd parties than with internal teams to get in almost anything you want.)

Tsk, tsk, tsk, you shouldn't work that late, Slo !! ;-)
	Vincent

>Tsk, tsk, tsk, you shouldn't work that late, Slo !! ;-)
>	Vincent

OK, if you agree not to start working so early:

nova05.vbo.dec.com::BERGER                            5 lines  30-JAN-1997 04:26
                                                                           ^^^^^
Slo

The time displayed in notes headers is that of the node hosting the 
conference, I believe. So, unless you happen to know where somebody 
is physically, it's hard to figure out what their local time is. 

As far as the mouse movement goes... double-click,right-click,select copy has
become second nature and I grumble about every application that makes me move up
to the menu or toolbar and take my eyes off the text with which I'm working.

Anyway, I do understand that especially in the TE space there are tough UI choices
to be made -- just trying to offer as many users' input as possible.

Get some sleep :-)

-Steven

>     <<< Note 89.2 by JOBIM::VUJNOVIC "I�t�r��t���l�z�t��L���l�z�t��" >>>
>                -< The kits: ULYSSE::PTW*.ZIP or SUTRA::PTW*.ZIP >-

Does anyone know where I can pick up a 16 bit kit for Powerterm?

I would like to run the Powerterm emulator on all my desktop machines,  which
currently include WfWg 3.11,  Windows 95 and Windows NT.

Hope someone can help,

thanks,  John Kruiniger.

John,

>Does anyone know where I can pick up a 16 bit kit for Powerterm?
>I would like to run the Powerterm emulator on all my desktop machines,  which
>currently include WfWg 3.11,  Windows 95 and Windows NT.

The 16-bit, 60-day, demo version was part of the 4.00.31 kit, but was 
removed. The SSB version is 4.00.32 and contains only the the 32-bit,
60-day, PowerTerm Interconnect demo.

Even if you were to obtain the 16-bit demo version, I don't believe we 
have the rights to use it beyond those 60 days. You'll have to buy it;
please check with Jeff DELNI::Babington, 226-6882.

I'd suggest you go to www.powerterm.com and download the 16-bit demo;
this is the same one we had in 4.00.31.

The deal we made with Ericom was only for the 32-bit software, for
W95 and WNT. In addition, ours is an OEM version that greatly differs
from their standard PowerTerm. 

If you go with their 16-bit version, be aware that it will not require 
any PATHWORKS bits, but will neither have many of the other features of 
our 32-bit PATHWORKS PowerTerm 525:

    Password Assistant
    Multilinguality
    Some keyboard and mouse features
    VT320 scripting mode
    Something will have to provide DECnet and LAT, if you need them
    
Slobodan

  PowerTerm 525 (4.00.34) Release Notes

  05-Feb-1997

  File: PTREADME.TXT, located in the \PTW\INTEL and \PTW\ALPHA 
  directories on the kit.


  CONTENTS 
  ========

    Introduction
    Installation Requirements
    Installing PowerTerm 525
    Canceling the Installation
    Uninstalling PowerTerm 525
    Keyboard Mapping
    Programmable buttons
    Using Kermit
    Connecting to Services
    Long File Names
    Password Assistant (Application Single Login)
    Language Support
    Selecting Font Sizes
    Changing Window Title
    Lost Characters and/or Data Overrun Conditions
    Switching Session Windows
    BETA16.ZIP and PATHWORKS 32 for Windows 95
    Displaying Graphics Files
    PowerTerm InterConnect Demo
    Print Setup
    NT/Alpha Serial Com Port


  INTRODUCTION
  ============

  The following known problems, and usage tips apply to PowerTerm 525, 
  Version 4.00.34.  After installing the product, choose Help-->About 
  from PowerTerm's top-level menu to see the version you are using.

  Wherever possible, PowerTerm settings default to the VT320 terminal
  emulator settings to make migrating easier.

  The two emulators differ in several ways. Please read this document
  and the online Help carefully to become familiar with PowerTerm.

                           IMPORTANT NOTE

  In versions 4.00.31 and later, the PowerTerm 525 executable file, 
  PTW32.EXE, has been renamed to PT525.EXE. Any customized shortcuts, 
  scripts, or batch procedures still referring to PTW32.EXE will not 
  work unless they are updated accordingly.


  INSTALLATION REQUIREMENTS
  =========================

  PowerTerm will install without first checking whether the PATHWORKS
  32 components have been installed.  This occurs because PowerTerm 
  can use only the COM port, which does not require any PATHWORKS 32 
  networking components.

  If CTERM, LAT, and Telnet are to be used, you must also install
  certain PATHWORKS 32 components, before or after installing
  PowerTerm. 

  For example, to install Telnet, DECnet and LAT support, choose the 
  "Custom" option in "Network Connectivity" from the PATHWORKS 32 
  installation menu, and select DECnet and LAT support.

  PATHWORKS 32 can also install the base connectivity to allow a user
  to run PowerTerm over Telnet only, without installing any other 
  PATHWORKS 32 options.

  To install the base functionality, choose the "Custom" option in
  "Network Connectivity" from the PATHWORKS 32 installation menu, and
  deselect all optional choices.  This procedure will install the 
  base functionality that will allow PowerTerm to run without
  installing  DECnet, LAT, VT320, Remote Access, Licensing or PWprint.


  INSTALLING POWERTERM 525 
  ========================

  Select the "PowerTerm 525" item on the PATHWORKS 32 installation 
  screen, which should appear automatically once the PATHWORKS 32 CD
  is inserted in the CD-ROM drive.

  Accept the default installation directory and group names when
  installing PowerTerm 525:

    Directory             Program Group
    ---------             -------------

    C:\PTW525             PATHWORKS PowerTerm 525

  Although you can choose anything you want, it is recommended
  that you do not mix different applications with each other. This
  will make removing, updating, et cetera, easier and safer.

  The installation process does not write anything into the Registry.

  The PATHWORKS 32 installation creates the PCSA variable and inserts
  the PATHWORKS 32 directory into the PATH variable. If these variables 
  do not point to valid directories, PowerTerm will not function properly.


  CANCELING THE INSTALLATION
  ===========================

  If you cancel the installation while the files are being copied,
  PowerTerm's Setup program will display a message asking you to
  confirm the cancellation. If your answer is Yes, Setup aborts the
  installation. However, no clean up will be performed. You must do it
  manually. 
     
  Because the installation usually takes less than one minute, it may
  be safer to wait for it to finish. Then use the Uninstall shortcut
  to remove the installed files.


  UNINSTALLING POWERTERM 525 
  ==========================

  Use the Uninstall shortcut to remove PowerTerm files from the
  directory in which they were installed.  Typically the directory is
  C:\PTW525.

  PowerTerm will ask if you want to remove any (non-PowerTerm) files
  that it finds in its directory. Note that it will fail to delete the
  .GID hidden files, which are created by Windows Help when you use
  the .HLP files for the first time. You will need to remove them
  manually.

  Uninstall will not remove the program group PowerTerm shortcuts were 
  created in, to avoid the risk of inadvertently deleting other
  shortcuts you might have created. You will be asked to do this
  manually.


  KEYBOARD MAPPING 
  ================

  * PowerTerm maps the keyboard in a different way from the VT320
    emulator. If you want it to match VT320 more closely, check
    the following box.  The path to this option is:

            Terminal-->Setup-->Keyboard-->Use VT Keyboard Mode

    which will map the following keys to the standard VT functions:

        F1      Hold Screen
        F2      Print Screen
        Ctrl+F2 Auto Print toggle
        F3      Setup
        F4      Dial
        F5      Break
        Ctrl+F5 Answerback
        F12     BACKSPACE
        F13     LINE FEED         (Use Ctrl+F3 to obtain F13)
        F14     Insert/Overstrike (Use Ctrl+F4 to obtain F14)

    The VT Keyboard mode is the default setting.

  * Keys F13-F20 are obtained using Ctrl+F3 - Ctrl+F10. (Note that 
    VT320 uses Alt+F3 - Alt+F10).

  * Compose is Ctrl+Alt, followed by the usual LK compose sequence, for
    example: AA for @, or // for \. It is important to press Ctrl+Alt
    and then release the keys before starting the compose sequence.

    If you have an LK450 attached, its Compose key should work as normal.


  PROGRAMMABLE BUTTONS
  ====================

  Do not confuse the buttons named "F1" - "F12" on the bottom of the 
  screen with function keys F1 - F12 on your keyboard. These are actually 
  programmable buttons whose names and behavior you can modify.

  For example, RIGHT-CLICK on one of those buttons (for example, F5)
  and give it a name, such as "Time". Then click on OK and enter a
  definition for this button.  For example:

            send "SHOW TIME<CR>"

  Click on OK to exit and then use the mouse to click on the newly configured 
  "Time" button to execute the script behind it. If you need to go beyond 
  these 12 buttons, use the PowerPad tool on the toolbar, which serves 
  the same purpose.

  You may also program these buttons (as well as those from the PowerPad)
  by using script commands such as:

            func 5 "Time" {send "SHOW TIME<CR>"} 
            pad 1 1 "Users" {send "SHOW USERS<CR>"}

  Please study the PTFUNC.INI file for more examples.  The online Help
  currently does not cover these areas.


  USING KERMIT 
  ============

  * The proper way to use Kermit SEND/RECEIVE in binary mode is:


    On OpenVMS:

    1. Execute Kermit.

    2. Enter the command "set file type bin" to change to binary mode.

    3. Enter the command "receive file-name" or "send file-name".


    In PowerTerm:
    
    4. Use Communication-->Receive File...
        or Communication-->Send File...
    
    5. Click on the Kermit tab

    6. Type the file name.

    7. Click on OK.

  The file should be transferred without problems.  Otherwise, an
  error message will be displayed.

  * Note that sometimes the "Percent Copied" progress indicator will remain 
    at 0%. This is normal, because some Kermit implementations do not
    supply the file size to the Kermit client.

  * Receiving a file in a location such as C:\SUBDIR\NEW.DAT will only
    work if the C:\SUBDIR already exists.


  CONNECTING TO SERVICES 
  ======================

  To select the network service to which you want to connect, 
  click on:

    Communication-->Connect-->Session Type

  Then select LAT, CTERM, or TELNET. In the Parameters pane you will see 
  one of the following edit boxes: Services, Node Names, or Host Names,
  respectively.

  Note that there may not be a visible entry in the edit box. To see 
  the list of available services, click on the down arrow on the
  right of the edit box. You may then scroll through the list and
  select a service, rather than having to type in its name.


  SCRIPTS 
  =======

  PowerTerm has a very powerful scripting language.

  There is also a mode provided for backward compatibility with
  the SETHOST/VT320 .SCR files. Specify .SCR files either on
  the command line, or via the Script menu option. Note that this
  mode may still have problems with complex scripts. Migrating your
  old .SCR scripts to PowerTerm's .PSL scripts is recommended.


  SAMPLE SCRIPTS
  ==============

  PowerTerm comes with several sample .PSL scripts that need to
  be modified for your environment:

    COMM.PSL
    LAT.PSL
    CTERM.PSL
    TELNET.PSL

  In general, it is a good idea to keep these original scripts and work 
  on the copies instead.

  If you run the sample scripts as they are, they will display informative 
  messages that may not be clear to all users. Follow these steps:

  On Windows NT 4.0, use the Explorer to locate the directory:

    \Profiles\All Users\Start Menu\Programs\PATHWORKS PowerTerm 525

  On Windows 95, under the main Windows directory, use the Explorer
  to locate:

    \Start Menu\Programs\PATHWORKS PowerTerm 525
   
  By default, the sample scripts are installed there. 

  Select one of the scripts; for example, "PowerTerm Telnet Sample".
  Use the mouse (or type Ctrl+C and Ctrl+V) to make a copy. The copy
  will be called "Copy of PowerTerm Telnet Sample". Rename it to
  something meaningful.

  Press the RIGHT mouse button on this newly created shortcut and
  select Properties. Go to the Shortcut tab, and replace the words
  "Host-Name" in the Target edit box by an existing host name that
  you want to connect to. Click on OK. Your new shortcut will now
  appear in the "PATHWORKS PowerTerm 525 group" that you access via
  the Start button.


  LONG FILE NAMES
  ===============

  There may be instances when long file names (LFNs) and
  directories/files with spaces are not recognized.

  PowerTerm's command line accepts the first parameter as the
  script file:

    PT525.EXE TELNET.PSL MYVAX

  If the script file is a LFN file, supply quotes around it:

    PT525.EXE "C:\Script files\Telnet Connection to MYVAX.PSL" MYVAX


  PASSWORD ASSISTANT (APPLICATION SINGLE LOGIN)
  =============================================

  The Password Assistant, or Application Single Login (ASL), is a 
  mechanism for storing username and password information entries
  for system-wide use by applications.

  The DIGITAL PATHWORKS 32 directory must be on the path and the PCSA
  variable must be defined, for the Password Assistant DLLs to be 
  used by PowerTerm.  For example:

    PATH=C:\PW32;D:\WINDOWS\SYSTEM32;...
    PCSA=C:\PW32

  This is normally the case after a successful installation of the
  PATHWORKS 32 Network Connectivity option.

  VT320 and PowerTerm are examples of applications that are enabled
  for creating, modifying, and deleting these entries. In PowerTerm,
  click on Communication-->Password Assistant-->Add Account-->Help 
  for more information.

  In both emulators you must use the script commands to actually make
  use of those entries.  The following is a PowerTerm script example:

    # ALPHA1.PSL 
    #    
    # Connect to OpenVMS node POWER using the account ALPHA1.
    # ALPHA1 is an account entry created using PowerTerm's 
    # Communication-->Password Assistant-->Add Account
    # option, or the equivalent in VT320.
    #    
    # Usage: 
    #    
    #   1. C:\PTW525.EXE C:\SCRIPTS\ALPHA1.PSL
    #           
    #   2. Script-->Script Command: run c:\scripts\alpha1.psl
    #           
    #   3. Script-->Run Script..., and Open c:\scripts\alpha1.psl
    #           
    # NOTE:  
    #      Be aware that this script will not work if you are currently 
    #      connected, since the command "session open" will be ignored. 
    #      One way to make these types of scripts work is to first do:
    #           
    #       Communication-->Disconnect (or click the Disconnect icon)
    #           
    #      A more general solution would be to wrap the script in another 
    #      script (let's call it BETA.PSL), consisting of a single line:
    #           
    #           exec "C:\\PTW525\\PT525.EXE c:\\scripts\\alpha1.psl"
    #    
    #      Now, using methods 1, 2, or 3 with beta.psl should work
    #      under all circumstances.
    #    
    set comm-type telnet
    set host-name power
    session open
    window title "Waiting..."
    wait 20 for "Username: "
    send username:ALPHA1
    wait 10 for "Password: "
    send password:ALPHA1
    window title "Logged in using the Password Assistant!"
    run keys.psl


  LANGUAGE SUPPORT
  ================

  PowerTerm has built-in support for five languages, in addition
  to English. The list of languages appears under the Terminal
  menu, and may grow as new languages are added.

  Changing the language will automatically update the user interface
  (the online Help, the status bar items, the menus and dialog boxes.)

  However, for maximum flexibility, it will not change the current 
  character set automatically. You must go to the 
  Terminal-->Setup-->General-->UPS Set option and change it manually.

  This allows users who do not speak Russian, for example, to continue
  using the English (or some other) user interface while running
  applications requiring Cyrillic characters.

  On the other hand, users in countries like Poland and Hungary can now
  use the ISO Latin-2 character set using the English (or some other)
  user interface, until the user interface in their own languages
  becomes available.  

  In VT320, the choices were more limited because it was not possible to 
  disassociate the languages from the character sets.


  SELECTING FONT SIZES
  ====================

  In the current version you cannot manually select a particular font
  size, such as 16x14. PowerTerm resizes fonts dynamically as the user
  drags the session window border. VT320, on the other hand, allows
  the user to choose from a list of font sizes, but not resize the
  window area with the mouse.

    
  CHANGING WINDOW TITLE
  =====================

  It is possible to change the current window title using the script 
  command (which you can put in a .PSL file, or define a button for):

        window title "My window title"

  However, the "window title" option is not documented in the current
  online Help.  The complete syntax for this command is:

        window [maximize|minimize|restore|hide|show|title]

  The PowerTerm online Help also explains how you can use a special
  escape sequence from the *host* operating system to execute scripts:

        ESC P $ t <script commands> ST

  The following DCL command procedure will change the window title to
  display some information about your current OpenVMS environment:

    $ ESC[0,7] = 27
    $ ST[0,8]  = 156
    $ node = F$EDIT(F$GETSYI("SCSNODE"),"COLLAPSE")
    $ user = F$EDIT(F$GETJPI("","USERNAME"),"COLLAPSE")
    $ HW      := 'F$GETSYI("HW_NAME")
    $ HWTYPE  := 'F$GETSYI("NODE_HWTYPE")
    $ HWMODEL := 'F$GETSYI("HW_MODEL")
    $ string = "User ''node'::" + "''user'"
    $ string = string + " on ''HW' (''HWTYPE' ''HWMODEL')"
    $ Write Sys$output ESC,"P$twindow title ""''string'""",ST

  Once the command "window title <string>" is executed, the output
  will look similar to:

       User JOBIM::SYSTEM on VAXSTATION 3100-M76/GPX (3100 224)


  LOST CHARACTERS AND/OR DATA OVERRUN CONDITIONS
  ==============================================

  It is recommended that you execute the SET TERMINAL/HOSTSYNC command
  on the OpenVMS host system when you use PowerTerm.

  This will prevent characters being lost, or the transfer being slow,
  when using the ASCII file transfer to an OpenVMS system.

  Also, when pasting into PowerTerm, especially in LAT sessions, data 
  overrun will occur unless SET TERMINAL/HOSTSYNC is in effect. 


  SWITCHING SESSION WINDOWS
  =========================

  The online Help mentions a mechanism for switching from one PowerTerm 
  session window to another by pressing Shift+Ctrl+session identifier.
  However, this feature does not work in the current version.


  BETA16.ZIP AND WINSOCK 2 NOTE
  =============================

  This note is specific to the Windows 95 platform.

  During its beta test, PATHWORKS 32 included the Microsoft
  BETA16.ZIP Software Developer's Kit (SDK) to provide WinSock
  2 support on Windows 95.

  PATHWORKS 32 removed BETA16.ZIP from its kit starting with
  the external field test 2.B release. Microsoft had updated
  the beta SDK and stated that the new beta could not be
  distributed to customers for testing.

  The PATHWORKS 32 V7.0 product release includes all the parts
  of DECnet WinSock 2. However, this functionality is not
  supported on Windows 95 systems until Microsoft officially
  ships the WinSock 2 SDK for Windows 95.  It is expected that
  Microsoft will release its WinSock 2 SDK after PATHWORKS 32
  ships.

  Until the WinSock 2 SDK is available from Microsoft, the
  PATHWORKS 32 components that will not work, over DECnet, on
  Windows 95, are:

    > eXcursion
    > CTERM (which affects VT320 and PowerTerm 525, over CTERM)

  eXcursion works over TCP/IP on Windows 95 systems. VT320
  and PowerTerm 525 work over Telnet on Windows 95; Telnet uses
  WinSock 1.1 and TCP/IP.

  WinSock 1.1 applications that only use TCP/IP work.

  Again: eXcursion, and CTERM for the terminal emulators, will
  work over DECnet on Windows 95 once Microsoft releases its
  WinSock 2 SDK and you install it on your Windows 95 systems.

  Note: Because WinSock 2 is integrated into NT 4.0, DECnet
  WinSock 2 works on NT 4.0, as do the applications layered
  on top of it.

  When the WinSock 2 SDK is Available from Microsoft
  --------------------------------------------------

  The following explanation covers two cases:

  1. You have installed PATHWORKS 32 and you then need 
     to install the Microsoft WinSock 2 SDK
   
  2. You have installed the WinSock 2 SDK from Microsoft
     and you then install PATHWORKS 32.

  Case 1: Follow the instructions in the Microsoft WinSock 2
          SDK when it becomes available.  Running the Microsoft
          install program after installing PATHWORKS 32 will
          automatically enable WinSock 2 DECnet support.

  Case 2: If you already installed the Microsoft WinSock 2 SDK 
          before installing PATHWORKS 32, you must do one of 
          the following after installing PATHWORKS 32:

          *  Run the Microsoft WinSock 2 SDK install program again.

          *  Or run PWS2INST.EXE to enable WinSock 2 DECnet support.


  DISPLAYING GRAPHICS FILES
  =========================

  PowerTerm 525 is a text-only terminal emulator that does not
  support graphics. Therefore, typing ReGIS or SIXEL graphics files 
  may produce unpredictable results.


  POWERTERM INTERCONNECT DEMO
  ===========================

  PowerTerm 525 installation also installs a demo version of  the
  PowerTerm InterConnect product. This product does not support the
  SETHOST/VT320 scripting language, neither is it multilingual.

  Note that this demo expires 60 days after the date of installation.
  The status bar will show "DEMO: xx days left", as a reminder.

  Please click on the PowerTerm InterConnect README icon for more 
  information about this product.


  PRINT SETUP
  ===========

  If selecting File-->Print Setup... does not bring up the Windows
  Print Setup dialog box, delete the PTW_PRT*.CFG files from the 
  Windows directory and try again. This problem should only appear 
  on those systems where field test versions of PowerTerm were used.
  
  NT/ALPHA SERIAL COM PORT
  ========================

  On NT/Alpha only, it is not possible to use the serial COM port as
  a connection method.  This may be fixed in a future release.

    <<< Note 89.2 by JOBIM::VUJNOVIC "I�t�r��t���l�z�t��L���l�z�t��" >>>
                -< PowerTerm kits: SUTRA::SYS$PUBLIC:PTW*.ZIP >-

What's the difference between PTWVN37.ZIP and PTWVN38.ZIP? Is this kit
Alpha or Intel?

Thanks,
Geoff..

>What's the difference between PTWVN37.ZIP and PTWVN38.ZIP?
                                   ^
                                   |
                                   N = iNtel (W95 and WNT)
                                   A = Alpha (WNT)

Minor fixes and improvements for those who want to look at where PowerTerm
is going. At one point, one of those will go into the TIMA release.

Regards,
Slobodan

>What's the difference between PTWVN37.ZIP and PTWVN38.ZIP?
                                   ^
                                   |
                                   N = iNtel (W95 and WNT)
                                   A = Alpha (WNT)

There doesn't appear to be an Alpha kit in that directory. Is an equivalent
Alpha version available?

Thanks,
Geoff..

I installed the .38 version. Started PT and it GPFed on me. I have PW6 
client installed on my W95 PC, not PW32. Is this why ?

Alan

>I installed the .38 version. Started PT and it GPFed on me. I have PW6 
>client installed on my W95 PC, not PW32. Is this why ?

Very likely. Even for telent, it needs the PATHWORKS 32 bits. The COM
port is about the only thing that will work.

Does .32 (SSB) work?

Regards,
Slobodan

No idea. I only have the 38 and 37 releases here.

I'll try and find a recent version of PW32 and update my system and try 
again. But not for a few days.

Alan

RE: .2

SUTRA::sys$pubolic:ptw*.zip is nice if you do DECNET.

Please provide pointer for us TCP/IP only folks.

Thanks

jbn
James B Nuzzo Ph.D.
276.9349 Dtn
508.496.9349 Telephone
508.496.9356 Fax
[email protected]

re:.27

Figured it out:

\\sutra.vbo.dec.com\public

jbn
James B Nuzzo Ph.D.
276.9349 Dtn
508.496.9349 Telephone
508.496.9356 Fax
[email protected]

You can also use: 

http://www-unix.zk3.dec.com/www/dgwy.html

to get to any DECnet location using TCP/IP

	Vincent

You can get the latest versions from my web site:

    		    http://jobim.vbo.dec.com

Click on the PowerTerm 525 link on the clickable map (the graphics
may not look too good if you use NN, IE, Mosaic, Opera, and other 
ASCII-impaired browsers).

You will also find there some keyboard comparison tables to ease
migration from VT320 to PowerTerm. Unfortunately, I never had the 
time to finish this; I don't know how accurate they are...

I've left OSSG and am no longer involved in interfacing with Ericom.
I believe Bruce JAMIN::MCCARRON is the new contact.

Regards,
Slobodan