Conference hydra::amiga_v1

     FWIW I'll second the request. 
     Dave

    I like Access! for its feature-richness and jazzy user interface.
    But without at _least_ VT100 emulation, its useless for serious
    work.  Maybe the developer (can't think of his name) could be convinced
    to put a VTx00 capability in there.  Except for the multi-session
    capability its close to the ultimate comm package, IMHO.
    
    <<< t >>>

    Well, I (and many others I know) use Handshake.  It provides VT100 and
    VT200 emulation and supports KERMIT, XMODEM and YMODEM transfers.  It's
    "freely distributable" so the price is right.  You can find it on Fish
    disks, most online services, BBS systems, etc. or grab it from TAPE, et
    al.
    
    You might look at another PD offering called "VLT".  It's supposed to
    do VTxxx emulation, handles the usual transfer protocols and allows
    externally provided transfer protocols (XPR) to be added.  There was a
    XprZModem package recently released which you're supposed to be able to
    use with VLT.  These are also available on the net, Fish disks, etc...

    I would really like a multi-session capable terminal emulator. To be
    able to downline load in one session while noting/working in another
    would really be nice.
    
    Is the source for Wheat (is that it's name) around ? Or how diffcult
    would it to be upgrade Smokey ?
    
    Regards
    	Mike

    Has anybody seen BaudBandit??? 
    
    mat
    

    RE: .2    It doesn't have zmodem.
    
    RE: .3    Ditto.
    
    RE: .4    Wheat was one of Mike Leibow's projects. Dunno
              if he is still at DEC.

I use Handshake all the time with only one problem:  it occasionally has
locked up when I get a few garbage characters.  As far as the VT200 emulation
goes, it's the best I've seen.  (I still can not seem to get my tab settings
set up perfectly though - SMG$ code screws up a bit)

I agree that Access! has a slick looking in-your-face.  I know some people
complain that they don't like the "flashy" look, they just want functionality.
I like a mix of both.  (also the "flashiness" takes more CHIP RAM, oh well)

Hey, by the way, has anyone ever got a response from Eric Haberfellner (the
author of Handshake)?  I sent him my shareware fee and a list of a few things
(bugs, features, etc) I thought about Handshake and I never heard back.  Then
I sent him another note with still no response.  Of course, he cashed my check.

Sorry, I'm rambling now...

...richard

    You mean someone cashed your cheque ?

re:  < Note 2874.8 by AMIGA2::MCGHIE "Thank Heaven for small Murphys !" >

>    You mean someone cashed your cheque ?

Yep, he sure did.  (I did take a couple of months though)   Hey!  I just noticed
your node name - good stuff.

Did I miss the point of your question?  (Sometimes I'm slooooow :-)

...richard

    I tried for the node name AMIGA, but someone is already using it ? I've
    never noticed it in the notesfile, I should track it down and see where
    it lives. The DECNET address is 9.984. Setting host to it gives a
    welcome text that it appears to be running VAX/VMS 5.2
    
    As regards to the cheque, on my statements there is no indication who
    cashed it, just that it was cashed. Do your banks do it differently on
    your side of the world ?
    
    Regards
    	Mike

    VTX NODE_LOCATION shows node AMIGA::  as
    
    	Low End Manufacturing in LJO.
    
    Someone beat ya to it  :-(
    
    -bw
    

Is either really an Amiga?

John

    Well I can vouch that mine isn't an Amiga, it's a VS2000 (at least it
    windows !).
    
    As for the other...
    
    My point was that I had tried to get the node name AMIGA, however it
    was already in use. But then I've never seen the node name show up in
    this notes conference, so I wonder if it is being used by an Amiga user
    at all ?????
    
    By the way, our other cluster members include NOTIBM, NOTDG, NOTHP,
    NOTNEC, NOTCDC. I also have an ELN node registered called NOTPDP.
    
    Regards
    	Mike

re: .10

>    As regards to the cheque, on my statements there is no indication who
>    cashed it, just that it was cashed. Do your banks do it differently on
>    your side of the world ?
    
No,  but we get the cancelled check back and it has his signature.  I guess
someone else *COULD* have cashed it, but I sent it to the address listed in
the lastest version of the program.

Regarding AMIGA::, maybe it is a workstation that belongs to a friendly lady
who speaks Spanish.  Well, *MAYBE*!  :-)

...richard

I snarfed AMIGA a couple of months ago when I got this system (a VAXstation II).
I used to run notes on CANIS, but just started running notes from AMIGA. I was
really surprised to find that AMIGA had not been taken yet. Guess I got it
just in time!

Frank

Hm.  So are there any Amiga on the net?

john

    re: -.2 I must have just missed then, 'cause I tried to register my
    nodes only a few months ago (drats!)
    
    As for an Amiga on the net, well I'm not sure Network
    Management/Security would accept an Amiga as a DECNET node on easynet.
    I suppose you could kuldge your away around it by declaring it as a
    (shudder !) PC !
    
    Regards
    	Mike

    Re.. .3
        
    >You might look at another PD offering called "VLT".  It's supposed to
    >do VTxxx emulation, handles the usual transfer protocols and allows
    >externally provided transfer protocols (XPR) to be added.  There was a
    >XprZModem package recently released which you're supposed to be able to
    >use with VLT.  These are also available on the net, Fish disks, etc...


    I put this together last night, it's pretty straight  forward  and
    for the most part worked.
    
    I    installed    VLT    version   4.058  (can  be  obtained  from
    CGOU01::AMNEW:VLT.ZOO) and  the  XPRZmodem.library  from Fish disk
    236.  That's  about all there is to it, once the XPRZmodem library
    is available, it is  activated  by selecting the External Protocol
    in  the Transfer pull down.    I  downloaded  a  bunch  of  stuff,
    although the downloads were successful, at the end of the transfer
    I got a "Script- Error opening ARexx  Port"  and upon returning to
    the VLT screen, everything echoed was garbage.   My  understanding
    is that ARexx is not required for VLT but it does support an ARexx
    port.   The  docs  talked about installing the ARexxARPlib.library
    and I did, but still the same error message. 
    
    VLT is a decent vt100 emulator with  lots  of  features and proper
    keymapping for 2000/500's  as  well  as  a good scripting language
    (sounds close to what  we're  looking  for  eh...).  I am not sure
    what is required to get  by  this ARexx thing (I don't want to buy
    it).  There is a new  version  of  VLT  (4.064)  around  (on BIX I
    believe) that has some bug fixes to  do with the XPR stuff.  Maybe
    that will help.
    
    Maybe  somebody  with  ARexx  could give it a  try  and  see  what
    happens.
    
        Regards....   Clint

    
    VLT V4.064 is on Fish disk 226 I believe.  I downloaded it a few
    nights ago along with FF 236.  XPRZMODEM.LIBRARY worked ok.  VLT didn't
    support ZMODEM RESUME though.  VLT is either buggy or doesn't like some
    of the utilities I have running cause it hung (hanged??) on me several
    times.  Not the whole system, just the program.  One nice thing, it
    translates mouse clicks into ANSI cursor movements so you can actually
    position the mouse while using EDT/TPU!!!  Well...sort of.  Funny
    things happen if you have scrolling regions defined.
    
    regards,
    
    steve

    Re.. .19
    
    The version  of  VLT on Fish 226 is 4.036 (according to the poster
    with it). 
    
    The XPRZmodem.library supports  resume  by  changing the "External
    Option" "ON" to "OR" (resume if filename match).
    
    Do you have ARexx,  if not, did you get any errors at the end of a
    transfer?
    
    I'm going to play with it some more and will keep you posted.
    
        Regards...   Clint
    

    Where is xprzmodem.library?

>< Note 2874.21 by DICKNS::MACDONALD "WA1OMM 7.093/145.05/223.58 AX.25" >


>    Where is xprzmodem.library?


    On Fish 236 or CGOU01::amnew:xprzmodem.zoo
    

    re: 19
    
>    The version  of  VLT on Fish 226 is 4.036 (according to the poster
>    with it). 
    
    Yes.  You're right I wasn't sure about that from memory.
    
>    The XPRZmodem.library supports  resume  by  changing the "External
>    Option" "ON" to "OR" (resume if filename match).
    
    As I said VLT doesn't support this.  When I set this option it comes
    back and says something about a certain callback not being supported.
    
>    Do you have ARexx,  if not, did you get any errors at the end of a
>    transfer?
    
    Yes, I do.  And no I did not get any errors.  However (and this is
    really wierd).  I can't seem to get VLT to work with xprzmodem again.
    Everything is exactly the way it was on my hard disk when it worked
    the other night.  Now I get some uninformative message.  I'm sure it's
    just "user error", but the thing's too buggy for my tastes anyhow.
    Maybe V4.064 is better...
    
    - steve

    .064? Okay, where is that located?

Is it possible to get a copy ( for internal use only ) of Mike Leibow's
VT200 terminal emulator v1.1a to add zmodem to???  I would be willing to give 
this a try if we could come up with sources.

	Dick

    
    Re...   .23
    
>>    The XPRZmodem.library supports  resume  by  changing the "External
>>    Option" "ON" to "OR" (resume if filename match).
>    
>    As I said VLT doesn't support this.  When I set this option it comes
>    back and says something about a certain callback not being supported.

    I have successfully resumed a transfer using this method.
        
>>    Do you have ARexx,  if not, did you get any errors at the end of a
>>    transfer?
    
>    Yes, I do.  And no I did not get any errors.  However (and this is
>    really weird).  I can't seem to get VLT to work with xprzmodem again.
>    Everything is exactly the way it was on my hard disk when it worked
>    the other night.  Now I get some uninformative message.  I'm sure it's
>    just "user error", but the thing's too buggy for my tastes anyhow.
>    Maybe V4.064 is better...
    
>    - steve
    
    The  Arexx  messages I have been seeing is when VLT is  trying  to
    ring  the  bell,  if I set VLT to "Program Yes" (???), it  doesn't
    happen.    Also,  for some reason, at the end of a Zmodem transfer
    the "Parity" setting gets changed.  If you set it back to 8N1 (in my
    case) all is  back  to  normal.    Hopefully .064 will fix some of
    this.
    
    Re...  .24
    
    I have heard that .064  is  available  from  BIX  (that's were the
    author Willy Langeveld lives).
    
    Re...  .25
    
    Steve Drew (of Shell fame) tried to  get the sources some time ago
    to try this, he's still waiting to here  from who ever was looking
    after them (read gave up).
    
    Actually,  VLT is a decent emulator and VT200 isn't  without  it's
    problems.  I am tired of using two packages and would like to find
    one that would meet my requirements.
    
                Regards....   Clint
    
    

Re:.26
	The sources for Mike's VT200 pkg. is not supposed to be available to 
the world as it has DEC terminal code in it that is DEC's property. What I
wanted to do was upgrade this pkg. for internal use only.
	Dick

    re: .26
    
    If you are using the version of VLT from FF 226, I would like to
    know how you did a ZMODEM resume.  Try it again.  The support just
    isn't in the V4.036 code.  Take a look at
    Vlt/xprlib/comm-program/xprfuncs.c.  xpr_finfo() is NULLed out. This is
    EXACTLY what the program tells me when I try to set the OR option. 
    xpr_finfo() is the callback function which the protocol specifies to get
    the file info for the local file so it knows  where to resume.
    
    Sorry, if it seems like I'm beating this to death, but something's
    fishy here... (pun intended)
    
    - steve

    Oddly, when VLT completes a zmodem transfer, it somehow switches
    to 8M1 parity from the original setting of 8N1. I have to manually
    select 8N1 to continue reading the screen. Anyone else experience
    this problem, or know why it is happening?

    Re: .29
    
    Yeah, "works" for me, too.
    
    Hopefully 4.064 will fix this and other "features".
    Otherwise I like VLT a lot...
    
    Regards,
    
    <CB>

From: [email protected] (Fred Fish)
Subject: Re: VLT and XPR
Date: 10 Sep 89 19:31:11 GMT
 
In article <[email protected]> [email protected] (Shan D Duncan) writes:
>I have looked at the fish disk 226 for the latest Vlt (3 series).  This
>has some problems that have been corrected in the 4 series (I've found
>4.059 on a local BBS, but have not seen 4.064).  I have never seen
>any xpr library except the ascii.
 
Vlt version 4.065 is on disk number 245, finished just a few days
ago.  It is the first of a new batch that should be released in
about a week.  Disks 237-244 were released about a week ago.
An update to xprlib from disk 226 is on disk 240.
 
-Fred
-- 
# Fred Fish, 1835 E. Belmont Drive, Tempe, AZ 85284,  USA
# 1-602-491-0048           asuvax!{nud,mcdphx}!estinc!fnf

    
    VLT Version 4.069 can be found at cgou01::amnew:vlt4p069.zoo.  The
    readme just says bug fixes for the XPR stuff.
    
    I ran it up and the parity and flow control settings stay the same
    after a download. 
    
    For the money ;>) , this is the best emulator to come along yet.
    
        Regards... Clint
    
    

    re: .32
    
    Thanks Clint.  This version seems much better.  I used it all evening
    last night without a single problem.  Zmodem resume even works for
    me now.
    
    I think I will probably use this exclusively now.  The only thing which
    is slightly annoying is that sometimes when garbage comes over the line
    VLT throws me into the TEK graphics window.  Only happened once or
    twice though.  I'd like to totally disable the TEK capability, but I 
    haven't figured out how yet?
    
    regards,
    
    steve

    
    Steve, one way of keeping you from going into Tek mode is to goto the
    far right menu (Graphics) in VLT and select the "Lock Graphics" option. 
    This will keep you from getting changed over by accident.  BTW, I have
    VLT 4.036, what is the latest version and is it availalbe on TAPE:: ?
    
    John
    
     

I like the idea of having VTxx and ZMODEM in one comm program.

BUT - I like JRComm's ZMODEM  "transfer in progress" window that gives you
lots of nice information - like estimated time to complete, real time,
size, amont transfered etc..

Is there an XPRZMODEM option which will give this info?

John

There is still an annoying bug with deselecting the numeric keypad. Try
it by going into VTX.

    
    You can find a copy of XprZmodem on one of the last 10 Fred Fish Disks
    or so.  I've got it setup on my machine, but I haven't tried it yet.  
    For my money, VLT is the best comm program around.  Better than comm
    1.34 which was my favorite for ages!  But VLT is here to stay.
    
    

I'm using VLT exclusively now, although I wish it would emulate a 220 or
340! setiing the number of lines to either 24 or 48 is critical if you
want to use SNIPIT V1.2A though. Oh, how could I ever live without
SNIPIT.

-Paul
    

    I currently use SMOKEY (the advantage of being a DEC employee). Is VLT 
    better than it? Is SMOKEY still being worked on and improved?

1   One of the earlier replies to this note suggested that the pingserver
    problem could be fixed by setting Program Mode On ... this is all
    very well but ... how do you get the bell to work?
    
2   Also, could someone who has got VLT to do a good job with the function
    keys post their VLT.Prefs file for me?

3   I have found some funnies with TPU (like right now).  When I use
    the uparrow key the cursor doesnt move until I type it a second
    time ... strange??  Also when inserting chars on a line the screen
    appears like I am in overstrike mode then if I delete a char or
    cause a screen refresh the hidden chars reappear.  Can anyone make
    sense of this?
    
    I have generally been using Smokey for terminal emulation up to
    now but VLT has better comms.  Being able to use a 1k packet size
    with Kermit certainly cuts down on the overhead.
    
    Peter

    Re: .40
    
    First of get VLT 4.069, available form CGOU01::AMNEW: if my memory
    serves me correctly.
    
    Regarding (3), be sure to set your terminal to VT100 mode, since
    VLT is after all only a VT100 emulator...
    I've been bitten by this, too. Started to swear loudly, reflected
    a bit over the docs, did a "set term/dev=vt100" and voila, works
    like advertised. 
    Someone with the ability to contact Willy Langeveld (sp??) should
    try to convince him to upgrade this baby to VT200 support... 
    
    Regards,
    
    <CB>

Funny thing about VLT in interlace mode ... it defaults to the VLT132
font and indents about 2 inches into the window. Seems like wasted space
to me. Is there a setting I am missing? Why does it indent like that?

-Paul

    OK ... Ive upgraded to V4p069 and set terminal to VT100.  That has
    fixed the funnies but I still dont have a bell and could do with
    a VLT.init with the function key defs in it.
    
    Can anyone help.
    
    Regards
    Peter

    To get the bell working I had to  delete the VTPrefs.dat that came
    with the distribution and create a new one (just  del  the VTprefs
    and do a save config.).  The one that comes  with  seems to assume
    that  you have Arexx or something.  Also set your bell  volume  to
    64.  Worked for me.
    
    As far as function keys, I don't  define  any, I don't even have a
    vlt.init.
    
        regards....   Clint
    
    

    I'm still hoping that someone can post a VLT.init or VTPrefs.dat file
    with the VT200 function key definitions for VLT.  Surely someone who is
    using VLT has already been through all this. 
         
    Peter

I hear that VLT4J226.ZOO has been released on BIX. The "J" stands for
junior. It omits the TEKtrronix stuff. The complete shibang is available
as VLT4226.ZOO.

Does anyone have this yet?

    I finally got VLT working (am using it).  I am able to login with a
    script up to the password prompt.  Could go further but will not for
    obvious reasons.  Anyway, my question is how do I implement ZMODEM? 
    I've got the library but how do I start it on the VAX?  Does it work
    with VLT4p069?  Does your terminal default to TEK whenever you end your
    terminal session?  Can I get rid of that annoyance?  More questions but
    will spend more time with VLT.
    
    mark

>> Anyway, my question is how do I implement ZMODEM? 

On the VLT Transfer Menu, select "Protocol" followed by "External."
A requester will appear listing the xpr  libraries in your libs:
directory. Choose xprzmodem.library. Now your VLT is all set up. You
shouldn't have to alter any of the default settings.

On the VAX side you need a couple programs, ZMODEMR and ZMODEMS (receive
and send). Define them in your login.com file as foreign commands.

To send a file to the Amiga.you would type,

ZMODEMS filename.typ

ZMODEM is a "smart" transfer protocol, so all you need to do is select
"Receive File" from the VLT Transfer Menu to get things going. If a
requester appears, just hit RETURN.

>> Does your terminal default to TEK whenever you end your
>> terminal session?  Can I get rid of that annoyance?

Under the Graphics Menu, select the "Lock Graphics" option. That should
take care of your problem. Be sure to save your configuration.

-Paul

    Thanks, Paul.  One last question, is "ZMODEMS/ZMODEMR" the same as
    RZ/SZ found on the net and where can I find the latest versions?
    
    mark

>>    Thanks, Paul.  One last question, is "ZMODEMS/ZMODEMR" the same as
>>    RZ/SZ found on the net and where can I find the latest versions?
    
  
Yup.

dickns::user:[macdonald.amiga.vms]

  I am unable to get ZMODEM in VLT working.  I have xprzmodem.library in my
s: directory and a "pretty standard" VLT.init.  Here's what happens:

	I run "sz" on the VAX.  It waits..  On VLT I select external 
	protocol and get a requestor within which I select xprzmodem.
	library, then I select receive file.  I immediately get a
	small window that says, "menu - not external protocol" or
	something very close to that.  Eventually the VAX times out
	with a "W" message saying that it was unable to connect with
	device.

	I've tried vlt4p058, vlt4p064, and vlt4p069 with the same
	results.  I copied  xprzmodem.zoo from the net and used with 
	the above results.  I've used the xprzmodem from FF236(?) with
	the same results.

	I know some of you are using ZMODEM/VLT.  What are your procedures?
	Is there a VLT menu item that I am not setting or some hack in VLT.init
	that I am unaware?  Do I sound obsessed?  �^)


Mark  
p.s. rz/sz is defined foreign.  Should I do an assign on the AMIGA?  Maybe
     build a new VTprefs.dat?
	
    

    You should have XPRZMODEM.LIBRARY in your LIBS directory
    
    Glenn

    VLT is very strange about capitalization. I converted my
    dialwork.script from smokey to S:DIALWORK.SCP for use with VLT.
    It worked fine when I selected VLT Macro from the menu, but when
    I bound it to F10 in vlt.init VLT told me it was not a script file.
    It didn't say it couldn't find it (which it did if I put it somewhere
    where it really could find it). Anyway, making it all lowercase fixed
    my problem.
    
    The same thing happened with zmodem. I had XPRzmodem.library in
    LIBS: and VLT would always tell me it wasn't an external protocol.
    I made it all lowercase and it worked fine. Well not fine, I got
    Software Task Held and the GURU after 4 blocks of the transfer.
    So then I renamed xprzmodem.nosflush to xprzmodem.library and
    everything worked fine.
    
    tom

    re. .-1
    
    I forgot to mention I'm using VLT version 4.069 and
    xprzmodem version 1.0
    
    tom

V4.226 of VLT has some nice new features:

o  All of the zmodem values now update on the screen during the transfer

o  The file transfer screen no longer forces the terminal screen behind
   Workbench

o  There is a nicely executed review buffer facility 

Various other little fixes and features. I tried both the upload and
download zmodem last night and it works fine. However, the upload to
the VAX seems to take a couple minutes to start.


(BTW, the LHARC'ed version is about 40K smaller than the ZOO'ed version!)

-Paul

>Various other little fixes and features. I tried both the upload and
>download zmodem last night and it works fine. However, the upload to
>the VAX seems to take a couple minutes to start.
    
    This is because VLT now implements XPR protocol 2.0 Spec, which changed
    the handling of the serial port, But XPRZmodem still uses the old XPR 
    spec. This results in VLt waiting about 30 secs or so until is returns
    the characters read to Zmodem. (I ran into this myself when I wrote a
    interface into XPRZmodem for my AUX: handler.)
    
    I read on usenet that XPRZmodem version 2 will be sent to .binaries
    shortly.
    
    As for VLT in general, its the best! I see no need to ever bother 
    with Vt100, I can't think of anything that VT100 can do that VLT 
    can't, and does it faster and better.
    
    /Steve.

    Re: .46
    
    Is VLT4J226 avaliable on the net?
    
    Peter

 XPRZmodem V2.0 is great!  If you don't have it, GET IT!

I am unable to get VLT to sound a beep when logged onto a host.  For instance,
when VMS should beep the terminal I get nothing.  When I had VLT beep volume set
to 64 (in the past) and VMS sounded a beep, VLT put "6464" on my VMS command
line.  Now I have "beep volume" defined as "0", "playbeep or installbeep or
whatever the sound-instead-of-flash util is" installed and VLT will beep if I
make a mistake "locally" but not when the VAX beeps.

I typed "^G" on the VAX with no results.  In my dialup scripts I had to redefine 
"^M" to "*X2" to get <cr> to work.  Maybe I need to do the same with "^G".

		Any ideas?

		mark
    

    There is a pull down, that contains an item "program mode" if enabled,
    I believe VLT interprets the bell item as a command. (See the docs).
    
    For a working VLT, XPRZMODEM, Bell init file, you can try
    
    	AMNEW::VTPrefs.DATA
    
    /Steve.
    

>> I am unable to get VLT to sound a beep when logged onto a host.  For 
>> instance, when VMS should beep the terminal I get nothing.  

Piece of cake .. 

1. Turn ON Program Mode.

2. Select the Bell Volume option.

3. Delete the information in the requester and exit the requester.

4. Turn OFF Program Mode.

5. Select the Bell Volume option and set the value (-64 through 64) and
   exit the requester.

6. Save the configuration.

I have noticed some possible bugs in VLT V4.226.


1.  When attempting to upload a .zoo file with zmodem, the transfer
    aborted due to receipt of a "Skip" command. Dunno why or how.

2.  When performing a Kermit upload, ZMODEM appears in the status window
    rather then KERMIT.

3.  The file transfer status window does not close automatically at the
    conclusion of a file transfer (perhaps a feature).

4.  The ASCI color display does not respond properly to IBM color ascii
    commands.

    I read in the latest VLT notes that upon termination of transfers
    VLT will beep twice.  Is this only with its internal protocols?  It
    would be nice if I could get some indication when my ZMODEM transfers
    are finished.  Has anyone gotten it to beep after ZMODEM transfer
    completion??
    
    mark

Ok, I'm lazy, I didn't read the manual yet.

How do I get VLT to use a font which gets 80 chars/line and DOESN'T switch
to that skinny, putrid , unreadable font?

John

    <add-on to .62>
    
    VLT(jr) will beep twice upon completion of a ZMODEM file send but will
    not on a file receive.
    
    md

    	Is VLT the program of choice amoung DEC employees? Should I
    switch from SMOKEY (is SMOKEY even being worked on anymore)? Does
    VLT support SIXEL or REGIS?

Does anybody know what the key-bindings are for the Amiga 1000 in VLT? I
can't find it in the documentation anywhere. I like using VLT for zmodem
transfers, but I hate not having full key-bindings.

Anybody?...Anybody?


Chris

>                        -< Key-bindings for the a1000 >-
>
>Does anybody know what the key-bindings are for the Amiga 1000 in VLT? I
>can't find it in the documentation anywhere. I like using VLT for zmodem
>transfers, but I hate not having full key-bindings.
>
>Anybody?...Anybody?
>
>
>Chris

Somebody must have the answer to this simple question. Or is it that 
there are no loyal a1000 owners left. I believe there is some additional
documentation somewhere that I don't have privy to.


Trying again...

Chris

    Or it could be that Amiga 1000 owners like myself don't use VLT.
    
    dennis