vanleejf@udcps3.cps.udayton.edu (James Van Leeuwen) (12/10/90)
I am having problems using Kermit (in UniTerm Version 2.0e) uploading to a Vax system here at the University of Dayton. Specifically, while uploading a .LZH or .ARC file, I'll get about four packets into the transfer and then the Vax comes back with an error to the effect of: "Packet too large for internal buffer." I am in binary mode on my end and in server mode on the Vax (so that all of the settings should be automatically set). I download both .LZH and .ARC files fine, as well as uploading binary files (as long as they are not ARChives or LZHives). Any ideas? Thanks! Jim -- "We didn't start the fire, / ___/_ Jim Van Leeuwen it was always burning / / / \ The University of Dayton since the world's been /___/__/ / Bitnet: VANLEEJF@DAYTON GEnie: JVAN turning..." --Billy Joel /______/ Internet: vanleejf@udcps3.cps.udayton.edu
dmb@wam.umd.edu (David M. Baggett) (12/10/90)
In article <1990Dec10.040058.24452@udcps3.cps.udayton.edu> vanleejf@udcps3.cps.udayton.edu (James Van Leeuwen) writes: > Specifically, while uploading >a .LZH or .ARC file,I'll get about four packets into the transfer and then the >Vax comes back with an error to the effect of: "Packet too large for internal >buffer." I am in binary mode on my end and in server mode on the Vax (so that >all of the settings should be automatically set). I've noticed that with all the Unix C-Kermit implementations I've tried, setting the packet size > 94 (on both ends) will cause sends to fail, but not receives. This happens in binary mode (don't know about text mode). I don't know whether this is a C-Kermit bug or a Uniterm bug, but I don't think the behavior is exclusive to Vax systems. (It happens to me with Suns too.) Interestingly enough, I don't get "packet too large" messages; in my case Uniterm just sends about 15 packets in rapid succession and then says "too many retries". I've never discovered a solution; hence all my uploads now run with 94 byte packets. :( BTW, It does not seem to be the case (for me, at least) that server mode sets all the params automatically... Dave Baggett dmb%wam.umd.edu@uunet.uu.net
wallace@ynotme.enet.dec.com (Ray Wallace) (12/11/90)
In article <1990Dec10.040058.24452@udcps3.cps.udayton.edu>, vanleejf@udcps3.cps.udayton.edu (James Van Leeuwen) writes... >I am having problems using Kermit (in UniTerm Version 2.0e) uploading to a I've found that when uploading I have to tell both ends to do binary. On downloading telling just the ST to do binary is sufficaint. --- Ray Wallace (INTERNET,UUCP) wallace@oldtmr.enet.dec.com (UUCP) ...!decwrl!oldtmr.enet!wallace (INTERNET) wallace%oldtmr.enet@decwrl.dec.com ---
rrd@hpfcso.HP.COM (Ray Depew) (12/18/90)
Try setting your packet size to 94 (bytes?kbytes?), on both ends. It's slow, but safe. A lot of machbines running Kermit like to set an enormous packet size like 1000+, and it really screws up other machines. At least they give you the chance to change it as the need arises. Regards Ray Depew IC's by Bill and Dave rrd@hpfitst1.hp.com