Conference hydra::amiga_v1

>You can upload to CGOU01::DUA1:[PUBLIC.AMIGA.NEW]. In the last release
>of Handshake he said he was thinking of including Zmodem and script
>support, do you know if this is the case? If so, that makes this the
>emulator of choice for my purposes.

Naw. By the looks of it, he's made so many changes in support of VT220
for version 2.0 and, now, version 2.1 that it's kept him too busy for zmodem
and scripting.

The author, Eric Haberfellner, lives just up the road and regularly uses the
Toronto Bloom Beacon BBS. I'll post a query on the schedule of enhancments
and scratch 'em in here...

BTW, thanks for the response on my .0; great response time!

/pete_who_lived_in_Calgary_before_they_had_an_NHL_team!

Whens ARP for 1.3 comming out?  I hear passing mention of it on USENET...

John

>Whens ARP for 1.3 comming out?  I hear passing mention of it on USENET...

I'd heard December timeframe....

Okay, I copied Handshake210.arc to CGOU01""::DUA1:[PUBLIC.AMIGA.NEW]. Enjoy!

Latuh,
/Pete

    Has anyone tried Handshake 2.1 yet? I downloaded it last night and
    de-arced it. (handshake210.arc). Every time I try to invoke it from
    either clicking on the icon or from cli, I get the dreaded GURU.
    An error message appears from  GOMF indicating stack
    something-or-other. I check the stack setting by using "info" on
    the icon and it is set to 5000. (same as the working version of
    Handshake which I am using. Rev ??). Any Ideas?
    
    Roger
    

    
    That's funny, I downloaded the new handshake and it runs like a
    champ.  Why don't you drop by tonight and we'll try your copy in
    miy A2000 and vice versa.
    
    Ed.

    Ok Ed, I'll give you a call around 6:30
    
    Roger
    

Works great for me too.  Thanks for the upload, I had been wishing it had
VT220 support!

...richard

    I had to set my stack size in Handshake.info to 10000 for my handshake
    to work.  What's going on here???  It seems as though there are
    "major" differences in the machines here.  The same piece of software
    Handshake works fine on some systems and requires modification to
    work on others.  Anyways I have an Amiga 500 KS1.2, WB1.2, ARP1.1,
    and a 501 memory expansion.  Could one or a combination of these
    cause the problem.  BTW: Handshake VT220 is GREAT!  I'm just wondering
    what could be causing the problems??
    
    _Mike
    

Re:.9

	The reason it may work fine for some people, and not others, is stack
size.  Some people change the stack size in their startup sequence (mine's
20000).  Some people also only run software from the CLI, so don't care what
the stack size in the icon is.

Mark

    Well, the plot thickens. Ed and I experimented with this problem
    last night and no matter what we did, Handshake would run flawlessly
    on his machine. My machine however still won't work. Well, I
    interrupted my startup sequence and began to enter it line my line.
    After entering a new line, I would try to run Handshake. Guess what?
    I works fine until I invoke a "newshell". If I run from a "cli" (like
    now) everything works fine. As soon as I try to use a shell instead
    of a cli, handshake bombs. I even tried to increase my stack size
    to 10000 as a previous note mentioed, but still the guru raised
    his ugly head. Is/has anyone managed to get handshake 2.10 and "shell"
    to work together? By the way, Ed is not running a SHell.
    
    Also, While trying to get this to work, I tried to make different
    commands resident. BE CAREFUL, when installing 1.3 on my hard drive,
    I copyied the directories and contents using "DiskMaster". Well,
    the files apparently transfer ok, but the pure bits do not!
    I had to "Copy" from source to destination from the cli to get the
    pure bits to also copy. I'm not sure how "diskman" or the
    multitude of other file handler programs work, but be sure to check
    it out. There are quite a few commands in the C directory which
    should have the pure bit set.
    
    Roger
                                    

    Sory to disappoint you, but I ran Handshake 2.1 under the Amigados
    shell last night without a hitch. I'm on an AMiga 2000 with 3 meg
    of memory with 1.3 roms.

    
    Sorry to disappoint you even further, but I too am now running Handshake
    with the new Shell and a slew of resident commands.  No problems
    whatsoever.
    
    Here's a few lines from my hard drive startup file.  It may or may
    not be revelant to your problem...
    
    
    c:CD dh0:
    SYS:System/SetMap usa1
    c:Resident CLI L:Shell-Seg SYSTEM pure add
    c:Resident dh0:c/Execute pure
    c:Run >NIL: Execute dh0:s/ResCom
    Mount NEWCON:
    Mount SPEAK:
    Mount PIPE:
    
    The 'ResCom' file is a seperate batch file that makes a bunch of
    commands resident...
    
    
    c:Resident c:Resident
    Resident c:Assign pure
    Resident c:CD pure
    Resident c:Copy pure
    Resident c:Delete pure
    Resident c:Dir pure
    Resident c:Echo pure
    Resident c:Ed pure
    Resident c:Else
    Resident c:EndCLI pure
    Resident c:EndIF
    Resident c:EndSkip pure
    Resident c:FailAT
    Resident c:If pure
    Resident c:Info pure
    Resident c:List
    Resident c:Makedir pure
    Resident c:Mount pure
    Resident c:NewShell pure
    Resident c:Path pure
    Resident c:Run pure
    Resident c:Skip pure
    Resident c:Type pure
    Resident c:Wait
    Resident dh0:more pure
    break 1 C
    
    All this stuff was entered in exactly as per the examples in the
    1.3 Enhancer manual.  
    
    Ed.

    .11
    
    It's sort of understandable that some of the older file manipulation
    utilities don't retain that protection bit since it only really became
    necessary with WB1.3. In fact, the Amiga DOS copy command only retains
    it if you specify the "CLONE" switch.
    
    I found that out this weekend when I backed up my system with SDBACKUP
    to change over to the FFS. 
    
    I'll be glad when these utilities are updated to retain the pure
    bit if it is set.

    Well, I'm not quite there yet. I did some experimenting last night
    and found that perhaps there IS a bug in 2.1 . I called Eric Hal......
    and we tried a few things, he even got his maching to fudge up on
    occasion. I run conman, machii and virusx in the background and
    by not running either machii or virusx at the same time, handshake
    2.1 works ok. There is over 600K of mem left even when running machii
    and virusx simultaneously so low mem is not a problem. I did get
    2.1 to work when I set my stack to 50000. I then lowered the stack
    allocation to 15000 and the guru appeared again. So, to all those
    people who have successfully be able to get 2.1 to work, are you
    running these background tasks? Eric is looking into the problem
    and will be getting back to me soon.
    
    Bye the way, Eric impressed me as being a pretty good guy. He
    immediately went to work on the problem. I had called him twice
    during the day and after the second call, he insisted that he call
    me in order to save me the $$ in tolls. I really like his program
    and strongly suggest we send him his shareware contribution for
    his efforts. He also informed me that he is working on the next
    version which will support sixel graphics. (don't these people ever
    sleep?)                        
    
    
    Summary of problem symptoms.
    
    Handshake
    1.6   2.1    CLI     Shell     Conman     Virusx     MachII     GURU
    
     x            x                   x          x         x         no
     x                     x          x          x         x         no
           x      x                   x          x         x         no
           x               x          x          x         x         yes
           x               x          x          x                   no
           x               x          x                    x         no
    
    x = active.
    Stack set to 5000 for tests indicated in chart above.
    
    Roger
    

    
    My check is in the mail to Eric.  Handshake really is a teriffic
    program.
    
    I'll try running VirusX.  I always run MachII and Snipit and have
    had no problems even with the default stack.
    
    Ed.

    Handshake looks like a winner!  I have been able to get it to run
    on my A2000 at home, but can't seem to get it to run on my A500
    at work.  I get a stack overflow requester and the guru every time.
    I set my stack to 40k with the same problem.  Any hints?  I'm
    running 1.3, MACHII and Amiga-Shell.
    
    As a side note, I'm probably spoiled, but on a kermit transfer with
    Handshake, how to you send a Kermit Bye to the remote server to
    let it know you want back to Kermit and then VMS?  I'm used to pulling
    it off SMokey's menu...
    
    Thanks,
    
    John
    

    I have an A500 with 1 Meg. I run the Dillon/Drew shell 2.07m,
    MachIIv22, conman, virusX v2.0, WBiconify and FaccII. I have had
    no problems with HandShake 2.1. I just recently started to put my
    stack at 16000 at the end of my startup but I think I ran HandShake
    with the stack at default - not sure though. By the time I start
    everything up I only have 200 - 300 k left before starting handshake.
        
    tom

    How does Handshake compare to Smokey, both pro and con?  Is there
    something better about it to justify paying for shareware over
    freeware?

	Paul

    I just downloaded Handshake last week so I haven't had much experience
    with it. Handshake doesn't support scripts like smokey (at least
    I don't think it does) and I like the key mapping better on smokey.
    But I like the way you can select the colors with sliders in handshake and
    the save them. Handshake also seems much faster than smokey on XMODEM
    transfers. Smokey writes to my floppy on every block during transfers while
    handshake buffers 17 blocks before it writes (I'm talking disk blocks
    here). I've got my smokey buffers set to max. I'm not sure if the
    17 blocks in handshake is fixed or if it would buffer even more
    if I had more available memory when I start it.
    
    tom

    
    I may have mentioned this as a Handshake plus before, but I like
    the fact that Handshake has it's own internal fonts for creating
    the VT character set.  Smokey uses special fonts that you must keep
    in your FONTS directory.  
    
    Ed
    

    Am I just dense, or is there a good reason why I can't get handshake
    to recognize my 2000's keypad?  Handshake looks good, but I'm lost
    without my keypad.  Anyone have any suggestions?
    
    Gary

    
    I give up.  I'd been getting suspicious gurus running the latest
    Handshake.  The program always appears to run fine, but Very Strange
    Things have been happening lately.  A few times I pulled down on
    the Handshake drag bar and my Workbench screen was garbled underneath.
    I'd pull Handshake back up and repeat, and Workbench would be fine.
    
    After exiting Handshake, I'd get a strange requestor telling me
    that the shutdown was going to get messy.
    
    I haven't been able to get my command keypad functioning properly.
    (OK, I HAVEN'T read the docs, but I never had to do anything special
    to get it to work right under 1.6.)
    
    Finally, I had a massive guru today right in the middle of an editing
    session.  I wasn't even touching the keyboard.  Just BLAM! No TASK
    HELD requestor, nothing.  Just the evil red presence of a total
    system crash.
    
    So. it's back to version 1.6 for me.
    
    Ed.

That's really weird that V2.10a is giving you such problems, Ed.  I've been
using it constantly with no problems.  Of course, I am still running 1.2 and
I'll bet you're running it from 1.3.  Could that be the problem?  FWIW, I
always start it from the icon which specifies a stack size of only 5000.

...richard

If anyone wants more specifics on my setup, just holler...

    Mornin' all. I spoke with Eric H again last night and he found what
    could be the problem. The executable was compiled/linked with the
    stack checking option selected. I'm not a software type so this
    means very little to me but he assured me that this would fix the
    problem. (or at least the problem I have been seeing). 
    
    Eric said that the new version is on BIX. Any BIXers out there care
    to upload the new version to notes?
    
    Thank You
    
    Roger
    

Handshake v2.12a is now up in CGOU01::DUA1:[PUBLIC.AMIGA.NEW]Handshake212.ZOO,
for those interested...

DECregards,
/pjp

    I am using Handshake 2.12a. In the docs it says that F1 isn't
    implemented for the VT220. Is there some way to enable pause/unpause
    without using ctrl-s/q? It seems pretty good so far, but it did
    act strange once when using split screens in LSE - it didn't reset
    the screen properly after going back to 1 window, but ^W fixed it.
    
     mark

    Another question
    
    I was trying to use kermit and by mistake specified ram:file_name
    as the destination - this caused handshake to try to put the file
    in ram:filename/filename which failed - but it locked up. The stop
    gadget wouldn't shut down the xfer and i had to soft boot. Was there
    a way out of this? I hit almost every key in desperation.
    
     mark