Conference 7.286::atarist

    First you need to know what escape sequences are generated by the
    function keys on your terminal (VT220, Workstation, etc..). One way to
    do this is to use the TPU editor ^V (quote character) command. When in
    the editor type ^V then press the function key you want to know the
    sequence to. TPU will insert the sequence. For example ^V followed by
    the F10 key will generate "[21~" (without the quotes). The backward ?
    actualy indicates the ESCape character. So F10 actualy generates escape
    followed by [21~ a total of five "characters". The DO key generates
    escape followed by [29~ . 
    
    Getting it into UNITERM -
    Once UNITERM is running do the following
    	o Hit the HELP key (this gets you to the help screen with menu bar)
    	o Move mouse to "OTHER" in the menu bar, click on "EDIT FUNCTION KEYS"
	  (this gets you the function key screen)
    	o Click on the dotted line to the right of "F10:" (or use the
    	  down arrow key to get there)
    	o Type ^[ (thats the escape character) a small E over S character
    	  will be displayed
    	o Type [21~
    	o Do this again for a shifted F10 (there is a SHIFT button to
    	  click on in newer uniterms, older versions have seperate lines
    	  for F10 and f10
    	o Click on OK
    	o Your F10 key is now programmed however you will probably want
    	  to save this function key inforation by clicking on "SAVE
    	  SETUP" under the "FILE" menu.
    
    For F12 and F13 (backspace and linefeed) you can program your function
    keys with the actual control characters ^H and ^J, which show up
    as a check-mark and a bell on the ST I beleive.
    
    	Ray

Thanks a bunch!  Finally, after all this time I can go log in and actually
use the ST like an LK201 terminal!  I don't know where I went wrong all the
times I did it.

Thanks again,

Rich Murray

We'll, since I've been turned on to this key definition stuff, for those
of you who are at home, sans VT2xx manual, here's the list of key sequences
for the LK201 keys (if you're using Uniterm, you might want to try them
out now:

       I will show the "escape" character as <esc>.  The rest of the chars
       shown in the sequences are to be typed "as is":

		KEY		SEQUENCE
		===		========

	       FIND		<esc>[1~
	     INSERT		<esc>[2~
	     REMOVE		<esc>[3~
	     SELECT		<esc>[4~
	       PREV		<esc>[5~
	       NEXT		<esc>[6~

		 F6		<esc>[17~ 
		 F7		<esc>[18~
		 F8		<esc>[19~
	       	 F9		<esc>[20~
		F10		<esc>[21~
		F11		<esc>[23~  !gotcha!
		F12		<esc>[24~
		F13		<esc>[25~
		F14		<esc>[26~
	 (Help) F15		<esc>[28~  !gotcha!
	   (Do)	F16		<esc>[29~
		F17		<esc>[31~  !gotcha!
		F18		<esc>[32~
		F19		<esc>[33~
		F20		<esc>[34~

These sequences have been lifted from Simon Poole's Uniterm User's guide
which I found among the rubble at home while looking for a VT240 pocket 
programmer's guide.
guide.

Is there some reason you don't want to use Whack?  It emulates a VT320
in ISO-Latin 1 mode, in most respects, and gives you multiple sessions
in multipe windows as well, and VWS compatible mouse controls. 

    Although the previous question was not directed at me I'll answer
    it anyway.
    
    I prefer uniterm over whack for the following reasons -
    
    Uniterm's dialing directory and the ability to execute script files
    as part of dialing.
    
    Uniterm's ability to enable/disable Xon flow control as well as
    most of the other RS232 parameters
    
    Uniterm's meta key mode
    
    Whack's screen doesn't completely fit on a color monitor

VWS mouse controls and multiple sessions don't interest me on an Ultrix
system (does SSU for Version 3 of Ultrix even exist?) since I have mutiple
screens already through the screen and grotwin programs

Jeff,

Why don't I use WHACK?  But, *I DO*!  For VS-like environment, *FAST*
file transfers, and SIXELs it can't be beat.  Also, the idea of everything
is one file is how everything should be done!  However, I tend to use UNITERM
more often because of:

	1)  Autodialing

	2)  Capturing stuff to my printer with a single keystroke
		(alt-F4 or alt-F8)

	3)  It has a nice manual (when I can find it) and Help screen.
	    I have to guess he's got some folks helping him with the docs.
	    The WHACK manual, WHACK.TXT is more like a collection of notes
	    than an organized manual.

	4)  That element of Human Nature that says:  If you know how to use
	    it and it does the job, stick with it.  (ever notice how many
	    people STILL use EDT??)

	5)  Overall, thru the time I've had my ST (1.5 years), it's been
	    more reliable.  I think UNITERM versions 1.6 thru 2.0D and WHACK
	    versions 1(?) thru 7 are what I've been thru, so my earliest
	    recollections are of a fairly stable UNITERM and a less stable
	    WHACK.

But, I *DON'T* still use EDT, so there's hope for me.  I will be giving
WHACK a better trial and will keep my eyes open for new releases.

Don't you just love critics?
                                                       
Regards,

Rich Murray

    We do not have SSU on our VAX which means (if I understand
    correctly) that I can not use WHACK to transfer files. Transfering
    files is a majority of what I use "remote login" for (as well as
    a small amount of reading mail and notes) so I don't need and wouldn't
    use multiple windows/sessions in WHACK. Since WHACK/transf(sp?)
    is faster than kermit I think it would be great to use just for
    that feature. But I don't think I can (or should even try) to convince
    my system managers to install SSU just so I can transfer files to
    my ST.
    
    From what I've seen and read about WHACK I think it's a great program
    and Jeff should be commended. With a few more features and the
    removable of the SSU requirement to transfer files maybe WHACK will
    become the terminal program of choice for 99% of DEC employed ST
    owners instead of just 75% (75% is a wild guess but I know a lot
    of people are currently use WHACK).
    
    Uniterm features I use that I don't think are in WHACK -
    	Dialing (I don't want to add a DA just so I can dial a # from
    		WHACK, I need to dial the phone every time I use WHACK
    		so it seems like a feature that should be there).
    	Programable function keys (there are a couple that I use
    		frequently).
    	Wild cards in file transfers (I don't know if WHACK allows this
    		but I typically transfer a number of files and don't want to
    		sit around waiting for one to complete so I can issue the next
    		command).
    	Can't think of any others right now.
    
    Ray

I used whack when I brought my ST in to work.  I used it as a second
workstation.  I always use UNITERM for calling up and whenever I transfer
files.  The reason is that I haven't taken the time to read the
WHACK.TXT  and really learn how to use it for file transfers.  I've tried a few
times with STRANSF but it didn't work, (and it didn't tell me that it didn't
work).  I would assume pilot error on my part.  Also, whack tends to be
more susceptible to noisy lines.  WHACK is a great product though.  I use it
when I only need terminal emulation, because I have figured out that part of
it without reading anything.  (Yes, when I by a new toy I just open it up and
I don't read the manual until latyer when I can't figure it out.)

Chad

Note that I don't expect Whack to replace Uniterm.

- I use Uniterm any time I want to do a Kermit or Xmodem transfer, such as with
BBoard systems or other funny computers.

- Uniterm makes more sense for most users that don't have SSU.  (The exception is
those users that use a lot of DEC-specific features like the function keys and
multinational characters, which Whack does the DEC way.)

- Uniterm is the only thing that works with non xon/xoff interfaces, such as
the KIM-1 serial port.  I've used Uniterm's SEND FILE stuff to load code into
a KIM-1 when Whack's SEND FILE stuff just didn't work at all (and I don't
entirely know why.)

A few notes that may help you along:

- Wild card "GET" transfers can be easily done with a DCL command file that
uses F$SEARCH and F$PARSE to build up a sequence of command lines that invoke
STRANSF.  I have never written such a thing, since I would typically ARC
everything I want into one compressed file when transferring a large number
of things.  (I have a VERY reliable phone connection.)  Whack can be made to
support wild card copies the other direction, but does not currently do it.

- Dialing the phone is the Modem's problem.  If you have a reasonable modem, it
should have a nice user interface already and not need support from the terminal
emulator.  UDK support, however, is my current top priority item for Whack.
User Defined Keys can be used to dial most modems.

    >> - Dialing the phone is the Modem's problem.  If you have a
    >> reasonable modem, it should have a nice user interface already and
    >> not need support from the terminal emulator.
    
    I have what I think is a "reasonable" modem (maybe there are more
    reasonable ones out there that I don't know about). The modem lets
    me type-
    	D 1-508-555-1234;	(Dial into digital)
    	D 3-5678		(Dial the VAX's ext. and wait for answer)
    and it procedes to tell me when it's connected. My problem (complaint?)
    is that in order to use this feature of my reasonable modem, I need to
    first look up this phone number and extension (or the number for
    anyone of the other four systems/bbs's I call) and then type it
    in. I much prefer being able to CLICK on the name GENIE or DIGITAL
    and have the number be dialed (yes I'm lazy, I like the computer
    to do as much work for me as possible, especialy redundant and/or
    things prone to human error).
    
    Now if by "reasonable" modem you're implying that there are modems
    out there that store a handfull of phone numbers and present you
    with a menu of numbers and associated names that are easily selectable,
    then I guess I better save up some bucks for a new modem.
    
    I do realize that any program is a tradeoff of features (a program
    overburdened with features can get huge, difficult to use, etc.., not
    to mention it takes man-hours to add each feature) and one persons
    desired combination of features is probably not the same as the next
    persons. This particular feature (dialing) is just one feature that I
    personally like in a terminal emulator. 
            
    	Ray

        I used Whack for a bit, with SSU and STRANSF.  I don't anymore.
        
        The reasons are mixed but here they are:
        
                . I don't have a hi-res monitor so dealing with Whacks
                  partial screen display mode in med-res is not pleasant.
        
                . No autodial directory - not that it matters, my modem
                  doesn't have an autodialer, but the directory is useful
                  as it contains all the specifics needed to dial-in and
                  allows me to store some notes - like password and user
                  number on various bbs's.
        
                . Whack and a mere 512k of memory don't get along real
                  well - but most programs are limited in this respect.
        
                . Whack only supports stransf - I'd prefer Zmodem or the
                  ability to select the transfer protocal.
        
        I do use STalk Professional (I have just received a copy of
        Uniterm and will be trying it out next week) and the features of
        it are:
        
                . Vt102 - 8-bit emulation - It says Vt200, but like most
                  com program developers, they didn't take the time to
                  figure out what that means.
        
                . Comes with X/Ymodem, something they call Fmodem (why
                  they did this I don't know). Supports Compuserv's B
                  protocal and has buitin Videx (?sic?) graphics support.
                  They are promising a Kermit in the future and has hooks
                  for using serial lines 1,2,3,4 and the midi port - no
                  promises though.
        
                . The weakest feature is the built-in item selector.  I
                  wish they would have used the standard item selector so
                  that I could use A&D's Universial Item Selector II.
        
                . It has 8 built-in editing buffers and a simple
                  editor.  The buffers are sizable based on available
                  memory.
        
                . It supports background transfer - but due to the
                  limited memory I have, I haven't used it.
        
                . ARC is callable so it is possible to specify Dcopy
                  instead of ARC.
        
                . There is a very complete script language included which
                  can be used to perform some auto answer and batch
                  functions.
        
                . The screen and fonts are not as bad as I had been led
                  to believe and it is much more useable than Whack when
                  doing simple things like reading mail, notes or
                  editing.
        
                . The built-in help is very useful.
        
                . The manual is execellent.
        
                . The setup's are easy and the functions keys can be
                  defined in any manner you want and saved  (multiple
                  setups and function keys can be saved in different
                  files).

        It's not perfect, but it only cost $25 (list is $29.95).
        
        Bob

    
    Maybe I am just being stupid, but the reason I use Uniterm over
    Whack is that when I tried using Whack I could not (no matter
    what I tried) get a decent font size, that and the fact that
    the window was larger than the screen. Still I have seen
    in in action and it does look rather good.
    
    My suggestion for what its worth....better documentation
    for WHACK.
    
    
    Jason.

	A year later and I'm still using Uniterm but I haven't been able to
	figger out how to do "compose character".  Any suggestions?

	Thanks for any help.

	Rich

See topic 3.  Whack does full IOS Latin 1 NR

>    re -1: Jeff, why do I not like Whack too much? One point is the Kbd. It does
>    not produce the characters that are written on the keycaps (german
>    kbd/atari).

I worked very hard to make sure that Whack would generate the correct
IOS LATIN 1 NR code for every key on all the international keyboards. 
If this is not the case, I want to know the details about it right away!

    Hi Jeff,
    
    Here are the details:
    
    first of all, I must state it could be my fault: I am running the
    developers version of TOS 1.4 (RAMbased).
    
    Although the initial notice at startup is written in English I get
    a german desktop (menues and alerts etc.). I found that uniterm
    translates ALL the keys of the standard ASCII (first 128 chars)
    as expected. (no editing with the keyedit prog). This also works
    for the [{]} etc. Whack translates the special chars in the lower
    128 chars of ASCII different. $ is mapped to the key RIGHT to return
    but the keycap there reads tilde. Also SOME other special chars are
    differently mapped. Strange thing is that punctuation like ,.;:
    are where the kbd says they should be, but all the shifted keys
    from the top row (1,2,..) are different.
    
    I seems to me that the keyboard translation is a mix between a german
    layout and an american one. Again it could be the TOS but anyway
    it is really strange.              
    
    And to make it VERY CLEAR: Whack is a great thing and I do use it
    from time to time.
    
    ---markus---

We have a German Atari which we run on a modem from home.  I must admit that I
am a VERY casual user but my experience is as follows:

With WHACK everything works as if I were using my LK201 blindfolded except that
if I type the German keys they seem to come out right.  There are some logical
things (like the function keys, etc.) that work as I'd expect.  I use EVE as my
editor with a lare set of self defined key bindings.  They all work PERFECTLY.

The only problem with WHACK is starting a session.  There is so much noise on 
the line that it seldom succeeds.  What we normally do is connect with UNITERM
and then switch the session to WHACK.

But, as I say, I am a really casual ATARI user.  As long as it looks like my
workstation I'm happy.

Cheryl