[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

2028.0. "XMODEM problems.." by CSOA1::CURTIS () Tue Dec 20 1988 19:19

    What is the secret for getting XMODEM to work ? I have copied various
    AMIGA stuff from the DEC public network using the COPY command,
    then I go home, dial up from the AMIGA, call XMODEM from DCL, and
    try to get a transfer going. It seems either it completes or just
    seems to transfer forever and not complete. If it completes, the
    file cannot be de-ARCED. It comes  back and says "file is not an
    ARCHIVE". I got my copy of XMODEM from LEDS3::ACCIARDI. What might
    I be doing wrong ? It was a 128 byte file I was trying to transfer.
    Also, the CVTARC program does not want to run,at least on my system. 
    I get an Access Violation message.  Any ideas ?
T.RTitleUserPersonal
Name
DateLines
2028.1try thisFSCORE::KAYEBe seeing youWed Dec 21 1988 00:0022
    I'm new to this and been all through this kind of thing for the
    last 2 weeks.
    
    1st) make sure you define the things on the VAX as foreign commands
    	ie: CVTARC:==$CVTARC
    
    	same for XMODEM
    
    I use Handshake 2.12a in YMODEM 1K mode. To send a file i type the
    following on the VAX:
     $ XMODEM file_name.ARC/YMODEM/ONEK/SEND=BIN
    
    and then select the 'receive' menu item in Handshake
    
    It works like a charm. To get the version of XMODEM i used the
    following:

    $ ftsv copy CVG""::WORK1:[CAMPANELLA.KITS]XMODEMVMS.BCK []
    
    It was in a note somewhere - search for tit=xmodem
    
     mark
2028.2Just between you and me, here's the secretTALLIS::JFOLEYWed Dec 21 1988 00:0945
    Here's what I do to make clean binary transfers.  It may
    or may not work for your configuration.
    
    In the Serial Preferences window, select 8 read bits, 8 write bits,
    no parity, one stop bit, and select "none" for handshaking. On your
    terminal emulator (I use Handshake) make the same selections - 
    8 data bits, one stop bit, no parity, no handshaking, and no flow
    control.
    
    On the VAX, after you log in send a break signal, and type to the
    LAT
    
Local> set session passall     
Local> resume     
                                  
    This stops the LAT from trying to interpret any keystrokes.
    Before you transmit your file run cvtarc on it.  Then tell VMS
    to stop converting keystrokes:
    
$ cvtarc u <filename>
$ set term /passall   
    
    Unfortunately, this also turns off command line editing, so 
    type carefully from this point on.  Now you're ready to send 
    your file:
    
$ xmodem -is <filename>
    
    On your terminal emulator, select the XMODEM protocol, and tell
    it to receive a binary file.  It should count off the blocks
    as it gets them and beep when it's done. 
    
    If this doesn't work, there are a few things you can check:
    
    Run "arc -x <filename>" on the VAX.  You may have a bad .arc
    file to begin with.
    Do a "show term" and look for things that don't match with 
    the transfer protocol (number of data bits, etc.)
    There might be some other magic needed for you VAX and terminal
    server configuration.  
    
    				- Jim
    
    
    
2028.3XMODEM...CSOA1::CURTISWed Dec 21 1988 14:272
    Thanks for the replies, I'll try some of these suggestions....