[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

2724.0. "Comm/Handshake Woes" by SSDEVO::YESSE (Computing at 6200 ft.) Fri Jul 07 1989 23:25

	OK, communications gurus, your expertise is requested...

	In recent months, I've been having intermittent problems with
	the comm line into CXO from home. Manual I/O works fine, but 
	downloading SW has become a hit-or-miss proposition. I am using
	Handshake 2.12a and Vax Xmodem;  a Multitech 224E modem;  and
	line noise is virtually nonexistent.

	In short, what works one night (with a specific server port)
	fails the next.  After verifying the proper Stream_LF format,
	a d/l attempt soon causes Handshake to show "Timeout waiting
	for block", and 0 blocks are shown transmitted.  What's really
	interesting is that sometimes, upon login, a  $ SET TERM/SPEED=2400
	and a  $ SHO TERM shows that the terminal is still at 9600...
	other times, it shows 2400 (required for any downloads to work).

	I've contacted our networks people, but there's been little action
	from them, and it's probably not proper to push too hard for PD
	Amiga software (!) from all you great noters. However, here's
	another anomaly:  Kermit (a la VT100) *does* work, all the time,
	when Handshake fails! So I'm not truly cut off.

	So, has anyone who uses Handshake regularly seen behavior like
	this? Or hazard a guess whether the problem lies with Handshake or
	the server?  [FYI, yes, I always check file formats, use CVTARC, use
	xmodem -is  convention, etc.]  Again, I emphasize that repeating
	the exact same steps from one night to another yields differing	
	results.  I'd like to stick with Handshake for the faster file 
	xfer rate, but it's no good if there's no transfer to begin with...

	Thanks for any assistance!
T.RTitleUserPersonal
Name
DateLines
2724.1Check the terminal server port settingsCSOA1::LENDavid M. LenSat Jul 08 1989 13:0712
    You are probably connecting thru a terminal server of some type.
    It it possible that some of the ports on the server are set up
    differently from others.  I have occationally had problems when
    the computer and my terminal emulator were set to 8 bit characters
    but the terminal server port was in 7 bit characters.  Some things
    work correctly and some things don't.
    
    At the local prompt on the terminal server use the command
    SHOW PORT this will tell you how the terminal server is set.  The
    important thing is to make certain that all 3 pieces (i.e. Host,
    terminal server, and terminal emulator) have the same character size
    (8 bit), parity (off/none), and XON/XOFF flow contol (enabled).
2724.2USE ZMODEM its better by farVIVIAN::S_GOLDSTEINSteve G...01-234-5935Sat Jul 08 1989 17:549
    When you do get it working UPLOAD JRComm93 and then use :-
    
    		ZMODEM
    
    This is a lot faster and it does not matter what the file mode is in 
    ie stream_lf or 510 bytes
    
    		Regards
    		Steve G..
2724.3OR AZCommVIVIAN::S_GOLDSTEINSteve G...01-234-5935Mon Jul 10 1989 05:471
    
2724.4Me too...FRAMBO::BALZERChristian Balzer DTN:785-1029Mon Jul 10 1989 07:4916
    
    There is definitivly something wrong with the Xmodem part of Handshake,
    I can receive from our server at 19200bps, but sending to the VAX
    fails at nearly any speed with those timeout errors. Kermit works
    great in both ways, but is sooooo sloooooow. :-)
    
    Whilst the ZModem stuff sounds great, I would hate to switch programs
    for down/uploading, since I believe none of the mentioned programs
    does a comparable job in emulating a VT200 like HS.
    
    I sure hope that Wheat will be extended with some transfer protocols
    in the near future...
    
    Regards,
    
    <CB> 
2724.5Zmodem protocol workingSSDEVO::YESSEComputing at 6200 ft.Mon Jul 10 1989 15:2810
	Thanks for the responses - I decided to make a go at Zmodem,
	using AZComm (Amiga) and SZ (Vax).  Works *much* better;  there's
	still a large file (400+ blocks) that I'm having trouble with,
	but it might be cockpit error...have to work on it a bit.

	Steve - I couldn't find JRComm93 anywhere, got a pointer to it?
	And how does it compare with AZComm?  Finally, are they shareware?

	Thanks again...Never saw the "transmit" light on so *steadily*!!
	Keith Y.
2724.6Have you looked in NorseWELSWS::FINNISTue Jul 11 1989 06:247
    JRComm93 seems more resilient
    However if you still have problems try th following
    SZ -bkL512 file.name  
    	This makes it about half as slow but works every time for me.
    
    		Pete
    
2724.7WonFRAMBO::BALZERChristian Balzer DTN:785-1029Thu Jul 13 1989 05:5112
    
    Why do these things never work for me???
    I grapped SZ/RZ and JRComm 0.93 from the Enet and installed them
    here. While uploading to the VAX at 19200 bps works like a charm,
    downloading to the Ami only gives me TimeOut errors.
    What gives? Anybody?
    
    Advanced Thanks...
    
    <CB>
    
    
2724.8do sz on vax to see optionsKLO::COLLINSSTEVEThu Jul 13 1989 11:1020
    Hi CB
    
    I did the EXACT same thing this morning and had the same problem.
    I've been using VT200 and ZMODEM all along without any problems
    but I wanted to try using ZMODEM cos it's supposed to be faster.
    
    I got time out errors if I do 
    
    SZ filename.zoo on the vax side 
    
    but when I did
    
    SZ -2 filename.zoo it worked ok
    
    this is with autoload set in one of the menus
    
    Hope this helps
    steve..
    
    
2724.9Still no go...FROCKY::BALZERChristian Balzer DTN:785-1029Thu Jul 13 1989 12:2713
    
    Re: .8
    
    Hi Steve,
    
    yeah I already did a plain sz on the Vax and stared at all the options,
    however to no avail. Your "sz -2" won't even start a transfer for
    me. A "sz filename" at least started a transfer once, but "sz *.*"
    never. I'm close to give up on this...
    The sz I use is version 2.12, if that is any help for you folks.
    
    Regards,
    <CB>
2724.10Just a thoughtWJG::GUINEAUThu Jul 13 1989 16:0710
Are you transferring a binary file (arc, zoo)? Maybe you need some
kind of image/binary mode switch?

I've used sz/rz to go to Amiga form VAX but at 2400.

John  

P.S. I use DNET or KA9Q from VAX to Amiga at 19200.

John
2724.11POBOX::ANDREWSI&#039;m the NRAThu Jul 13 1989 18:414
>   P.S. I use DNET or KA9Q from VAX to Amiga at 19200.

    How do you do this? I thought DNET only runs under UNIX?
    (Or are you on an Ultrix node?)
2724.12I'm NOT the NRA!!!FRAMBO::BALZERChristian Balzer DTN:785-1029Fri Jul 14 1989 04:388
    Re: .10,.11
    
    Yeah, I wanna know that, too. And KA9Q would be fine, too.
    
    And I tried either binary and text files with SZ/JRcomm with their
    respective flags, to no avail. 
    
    <CB>
2724.13DNET/KA9qWJG::GUINEAUFri Jul 14 1989 08:287
For DNET you need Unix/Ultrix on the other end. I have Ultrix on my VAX at home.

KA9q requires TCP/IP. Again ok with Ultrix (or if you have ENET, VMS and the
Ultrix Connection - UCX - software which gives VMS TCP/IP sockets on ENET).

John
2724.14MoreWJG::GUINEAUFri Jul 14 1989 08:3212
I should add that I used DNET very briefly once KA9q came around.

DNET allows only 2 machines on the network while KA9q is an IP network
so it's only limited by the IP addressing scheme (which I guess ends up being
 2^32 nodes!?!).

Both allow multiple links between any 2 machines.

At one point I have 3 machines on the net at home - 2 Amiga's and a VAXstation
with the VSII being a gateway.

John
2724.15Seek professional helpSMAUG::SPODARYKScaring the pedestrians...Fri Jul 14 1989 14:563
    .13 & .14  -  John, you are a sick man. :^)  
    
    Steve - green with envy
2724.16Who, me?WJG::GUINEAUFri Jul 14 1989 16:136
sick? Actually by now just a bit mad 8^}

It's really all just to learn. 

john