Conference hydra::amiga_v1

>>If I type Kermit-32>Server, the vax locks.
     
     When you type Server, does kermit then say something about
     continuing from your remote session? If so, kermit is waiting
     for a kermit get from the amiga terminal emulator.
     
     Also, If this is straight text, you should probably arc the file
     to compress the size. You can then dearc it on the Amiga. This
     is explined in detail in other notes in the conference.
     Dave

    I have been very successful using Handshake in Ymodem and Ymodem
    Batch mode on the Amiga side and the lastest version of Xmodem on
    the VAX side.  Xmodem on the VAX side does require some setup(i.e.
    defining the symbol to run xmodem).  I have not had a bad download
    since, and I no longer bother to check the format of the VAX file
    (i.e. Stream_LF, or fixed 128).
    
    To send a single file I use a command of the form:
    
    $xmodem/send=binary/onek foo.bar
    
    This is received on the Amiga with the Handshake YMODEM tranfer protocol.
    NOTE: YMODEM is also called Xmodem 1K and the /onek tells xmodem
    to use 1K blocks instead of the default 128 byte blocks.  The transfer
    is much faster using 1K blocks.
    
    To send a group of files I use a command in the form:
    
    $xmodem/send=binary/onek/ymodem *.zoo
    
    This is received on the Amiga with the Handshake YMODEM Batch tranfer
    protocol.  I am fortunate to have a 3MB system, so I usually tell
    Handshake to load to RAM: and as a file is completed I deARC it
    move it to disk then delete it from RAM: while the next transfer
    is continuing.
    NOTE: in YMODEM Batch when Handshake asks where to put the recieved
    files you specify a path not a file spec, the protocol sends the
    filename.
    
    Another side note: I don't know remember if I ever had a successful
    Kermit transfer in Handshake, but I know I had a lot of failures.
    If for some reason I must use Kermit, I always use VT100 or VT200
    on the Amiga side.  VT100 and VT200 seem to do an execellent job
    with Kermit and standard 128 byte block Xmodem.

    well, my version of handshake does not support server functions,
    does yours? Smokey is supposed to but handshake does not to my
    knowledge. To use the server function of kermit you must have a
    get function on your amiga end. Handshake does not have this. To
    copy the file set the vax end up as this.
    
    	1) mc kermit
    	2) kermit-32 > set delay 15
    	3) kermit-32 > set file type ascii (for text file)
    	4) kermit-32 > send filename.ext
    
    	   now goto handshake transfer menu and select recieve text
    file menu. You will be asked for destination, simply type in your
    disk unit DF0: or DF1: and hit return or click ok. The file should
    COPY IF YOU DO THIS.
    
    	Mike

    I have a version of zmodem for the vax if anyone wants it. There
    are 2 images, SZ and RZ; SZ is for sending and RZ is for receiving.
    They work pretty well and are much faster than xmodem or kermit.
    
    	CSC32::DISK1:[J_PARSONS.AMIGA]SZ.EXE,RZ.EXE

Are the files (W)orld accessible?  I get:

>>%SYSTEM-F-INVLOGIN, login information invalid at remote node<< 

    re .5
    
    The protections are fine, just checked them and they are w:re. If
    this is a problem for everyone I can copy the images somewhere else
    if someone will just tell me where to put them.

    I can't access it either.  The default DECNET account was probably
    changed to not allow remote access.
    

    Re .4
    
    Neat, ZMODEM VMS.   Now who's got the Ami side?   Did I miss something?
    
    Gary
    

    I put the files in NORSE::AMIGA:[UPLOAD]

    After struggling w/ kermit some more last night, I realized that
    a pretty easy (yet slow) way to download a text file is to just
    type it and capture in a buffer.
    
    It's not the most extravagant way, but It gets the job done.
    
    Steve O

    I second .8     .....  Is there a ZMODEM for Ami out there?
    

    re .11
    
    Do you have AZComm?  Great PD term w/ z-modem!
    
    Steve O

    AZComm is indeed very good. I also have another comm program called
    JRComm which I will upload over the weekend if I get time. It's
    shareware, very well done, and its main claim to fame is very high
    speed zmodem transfers. I have routinely got 224-228 cps on a 2400
    baud transfer to and from the vax from my Amiga, which is much better
    than I've done with other terminal programs which do zmodem.

    There is a Zmodem for the Amiga in two forms.  The first is AzComm
    which is a  crude  terminal emulator that supports Zmodem Receive,
    Zmodem Send and Zmodem  Resume.    It  can  be  found in the usual
    places by the name of  AZCOMM.ARC.   The second is a collection of
    Amiga executables that will do Zmodem send and receive, I have not
    used these as AzComm works great for  me.    This  one  is  called
    AmiSZRZ.ARC. Both of these should be on Tape:: or Norse::.
    
    You  will also need the Vax Zmodem stuff.    The  sources  are  in
    CGOU01::[PUBLIC.AMIGA.TOOLS]SZRZ.ARC.    The executable (compiled
    under version 5) can be obtained from CGOU01::[PUBLIC.TOOLS]SZ.EXE
    and RZ.EXE. SZ is the Zmodem send and RZ is the Zmodem receive.
    
    As an example of the usage:
    
        - run AzComm at the Ami end and dial up the host
        - once on the host define a symbol SZ:==$disk:[directory]SZ.EXE
        - then type SZ file1 file2 file3 ....
        - at the Ami end select the pulldown "Zmodem Receive" and 
    watch the bits fly.
        - for uploading, do the same for RZ.exe and do a "Zmodem Send".
     
    
    The other thing  that  may  be  handy is a DCL command file that I
    wrote called SZ_SEND.COM (in the same  dir  as the executable) that
    will allow you to batch Zmodem downloads using a VMS file spec rather
    than putting all the filenames on one line (as above). See the
    comments in the file for more information on using it and the VMS
    Zmodem programs.
    
    The beauty of the AzComm version of Zmodem is that it can resume
    interrupted file transfers with "Zmodem Resume" on the Ami and and RZ
    -r on the VMS end. This is great if your wife picks the phone up,
    starts dialing and knocks you off two hours into downloading a
    collection of XXX pictures or something else important. You can just
    dial up and resume where you left off. Zmodem also has a throughput
    of 113 CPS at 1200 baud (Kermit is about 62 CPS). 
    
    The big downside to Zmodem is that it REQUIRES an 8 Bit path to the
    host.  If you dial up a server make sure the port your on is eight
    bit (show port??). Also, when you do a show term from VMS it should
    be set to Eightbit. If you dial up through Tymnet or some of the
    others I think they are 7 bit only and you have to use Kermit and the
    "quote 8th bit" feature.
    
    One more great thing about Zmodem is that is doesn't care about file
    format the way that Xmodem or Kermit do. That makes the whole process
    easier and more reliable because you don't have to do any CVTARC or
    other trash. Just fire up AZComm and download.
    
        Regards....   Clint
    

    All this stuff about ZMODEM is just wonderful.  I'll d/l the whole
    mess when I get a bit of time.  But for now, the discussion about
    Handshake piqued my curiosity.  I decided to install it alongside
    "Smokey" on my Comms disk.  It seemed to be fairly straightforward.
    
    Unfortunately, when I went to dial into the VAX at work the whole
    thing went into garble mode and ultimately disconnected me at the
    DECserver.  
    
    The strange thing is I am able to communicate with the modem (Scholar)
    but when I get connected to the server we go to garble.  I've tried
    various settings of word size, parity, stop-bits...nothing seems
    to help.
    
    Incidently, I have an A1000 w/512K, Scholar modem.  "Smokey" works
    just fine.  Just thought I'd give YMODEM a try.  This is really
    frustrating!
    
    Any suggestions?
    
    
    Bob.
    

    
    What's wrong here !   I download an .ARC file using ZModem and then
    can't get to it using ARC on the Amiga end.   I get a message to
    the effect - "Can't load ARC, file is not an object module" or
    something close to that.
    
    1. I dial in and run AZComm, all my data paths are eightbit, etc
    2. The ARC file is stream_lf on the VAX
    3. Do a SZ foo.arc on the VAX side
    4. Do a Receive ZModem on the Amiga side
    5. Bits, fly and a message say's "transfer successful"
    6. But! I can't even list its contents with ARC.  What the %$#@
        is going on?
    
    What does the option "chop file" do in AZComm?
    
    Thanks
    

    
    Good day,
    		VMSARC is using stream_lf standard but AMIGAarc is using
    fixed length mode.
    You will have to use CVTARC on the VAX to convert your file first.
    As Clint said ZModem will transfer any standard witout error but,
    I don't think it can convert from one standard to the other.
    
    Hubert
    

re: .16

	Sounds like your Amy can't get to the ARC executable program.  Is the
ARC executable in you current search path?  I keep ARC in my C: directory. 
Since it's in my search path, anything there can be ran from anywhere. 
Also, if there's a file named ARC in your current directory that's not the ARC
executable, this would screw things up.  


					John

    Either .17 or .18 sounds possible.  I'll give it a closer look tonight.
    Thanks for the help.
    
    Frank
    

    Is Handshake v2.12 available on the net?  My copy seems to be corrupt
    and the copy on NORSE:: is v1.60.
    
    Thanks
    bob
    

    I downloaded Handshake212a... just fine.  It works wonderfully.
    Now about AZComm.... I try to d/l a large file (800+ blocks on VAX)
    and it gets about 25% through the file and I get TIMEOUT...TIMEOUT..
    ...etc.  I've set the server at passthru and done a set term/eightbit
    on the vax end...  AZComm works fine for smaller files but anyone
    got any ideas about how to do it for larger ones??   This would
    be ideal if it would work.
    
    
    Thanks in advance...
    
    bob.
    

    I've run into the same symptoms using AZComm in conjunction with
    thew YModem protocol. But! what  I've noticed is that the timeout
    message seems to be for "info" only.   It continues to plug along
    and eventually completes sucessfully.  I assume there must be retry
    which follows the timeout message.
    
    Frank
    

    re: .23
    
    Would that it be true... However, after about a dozen or so TIMEOUT
    messages, I get an "aborted by sender" or somesuch message.  This
    is most frustrating.  Haven't tried it in YMODEM protocol...by the
    way what is WXMODEM?? is that the equiv of YMODEM??
    
    Bob.
    

    correction to .23
    
    I gave incorrect information.  I've been using ZModem (not YModem)
    with AZComm and have survived the timeout messages.
    
    Another point. I've never gotten more than 2-3 timeouts per transfer.
    Even in downloading the both startrek disks I think there were only
    3 timeouts.
    
    I've never tried YModem.
    
    Frank
    

    
    WXMODEM (Windowed Xmodem) is a proprietary protocol of PLINK (American
    PeopleLink) that sends larger packets than Xmodem resulting in faster
    transfers.
    
    Ed.