Conference hydra::amiga_v1

    Try  		sz 'filename'
    
    When I downloaded sweep.zoo last night this was my command line on the
    VAX:
    
    
    		sz rk sweep.zoo	;r is the restart option
    				 k is the 1k blocks option
    
    for multiple files place spaces between the files like Unix or AmigaDos
    do not use the VMS convention (,).
    
    mark

    Do this first:
    
    	$ SZ == "$ dev:[dir]SZ"
    	(replacing dev:[dir] with device and directory where you have
    	 stored SZ.EXE, i.e. your directory.)
    
    Then proceed as described in the previous reply.

    Thanks!!!  That solved the problem, no worries!
     
    JK
    

    Is there a way to cancel the "rz" command in VMS.  I've tried most of
    the control-n characters with no results.  I usually end up having to
    kill my process from another account.  There must be a better way.
    
    mark

    
>    Is there a way to cancel the "rz" command in VMS...
    
    Yes, it's 5 (five) control X's in a row. Now, was'nt that obvious :-)
    
    Steve.
    

    
    I eperience some funny RZ behavior I'd like to understand, can anybody
    shed some light on this ....
    
    For the most part I run RZ/SZ with Atalk III without incident. But
    sometimes I get a message from RZ (latest version) that goes something
    like "device is not in configuration tables".   What is it trying to
    tell me?
    
    Most often I seem to bring this upon myself by trying to upload a file
    which already exists.  Somehow RZ doesn't seem to care for that
    strategy. Does that make any sense?
    
    When the error occurs I seem hopelessly unable to upload anything 
    further using RZ.  The only way I've been able to recover is hang up
    and re-dial.  Logining in and out at VMS doesn't seem to help.
    
    SZ appears bullet proof.  Works great and seems to handle lots of 
    things amazingly well.
    
    Thanks
    Frank
    
    

    Re: .6 
    
    I would look at you terminal characteristics on VMS before and after
    you have the problem. Although logging out and back in should fix
    these. Sounds like the ATALK ZModem is getting messed up, or perhaps
    the terminal server (if you are using one). 
    
    By the sound of the error message I would guess that RZ gets confused
    by the fact the file already exists and reports a bogus error message.
    If the message is a VMS message (ie %SYSTEM-F-... ) then it probably is
    a random number left in R0 upon exit of RZ. If not a VMS message then
    I'd have to take a look at the source to find out what it is supposed
    to mean. 
    
    John

    I have often experienced the same problem, but with VLTjr. Although
    I can't tell you what exactly it is, I can tell you what it's not.
    It isn't due to the file already existing (I've verified that),
    or incorrectly sending the "full filename and device" to the VAX
    system. For me, it appears to happen during a handshaking failure. Even
    with the recently improved version, I still cannot upload anything
    but very small files through TSN. If I upload a file through TSN,
    the transfer will always abort (after a minute or two) with the
    VMS side displaying that error.
    
    It IS better behavior than I use to get though -- which was a
    dropped communicatio0n link.
    
    When this error occurs for others -- are they using TSN?
    
    Keith

        
    P.S. In case you are trying to reproduce it, this a a TSN 1200
    baud transfer through a LAT port. Also, VMS SYSGEN buffering parameters
    have been increased already.

    re .-1
    
    Kieth,
    
    What you say makes sense (handshake failure).  I don't use a TSN but
    dial directly into a LAT.   I've never experience a problem with length
    of files.  Once I get it to start up properly I never seem to have a
    problem.
    
    I will check terminal params before/after.  I did notice last night
    that my keyboard inpt was screwed up after the failure.  I was in a 
    hurry and didn't bother to find out why.
     
    Frank
    

    
    1.) If rz is told to receive a file it already has, but default it
        will issue a "SKIP" command to the sender. VLT displays the 
        message back from rz as "Skip command received" and proceeds to the
        next file.
    
        To avoid this behavoir use "rz -y" to force creating a new version
        of the file.
    
    2.) Also make sure you are running the version of rz,sz that I fixed
        a few months back for VMS. (There were a few bugs with terminal
        charactistics and flow control in the original source).
    
    	Check CGOU01::AMNEW:RZ.EXE,SZ.EXE
    
    
    /Steve.
    

    Re: -1
    
    1) The problem happens when the file DOESN'T exist also (at least
    for me).
    
    2) I have been using the new version. It actually runs much better
    through TSN -- it allows small transfers and no longer drops the
    line, but it eventually aborts with the "device" error on larger
    1200 baud TSN-LAT-VMS transfers.
    
    It it would help, I'd be willing to try this some night "SET HOST"'ed
    to your system so that you could watch the receiver. It would be
    worthwhile if someone attempted a 1200 baud TSN (TELENET) to LAT
    to VAX transfer and see if the problem is reproducible elsewhere.
    
    Another strange thing to me is no matter what's going on with my
    situation or with other people's -- why a "device" error message?
    
    
    Keith