Forum

Downloads work fine...
 
Notifications
Clear all

Downloads work fine, uploads choke

0 Posts
2 Users
0 Reactions
262 Views
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

Do you have access to any non-BSD UNIX machines that you could try?


   
ReplyQuote
(@vanhoose)
Eminent Member
Joined: 55 years ago
Posts: 17
Topic starter  

No. But my admin does. Maybe I can ask him to help out with this. I'll send him the latest beta and see if he has a few minutes to try both file transfer functions on a BSD and non-BSD machine from his PC.

- Van


   
ReplyQuote
(@vanhoose)
Eminent Member
Joined: 55 years ago
Posts: 17
Topic starter  

UPDATE: Even though the errors pile up when I run the 'lrz -be' command on some binaries, it appears that the transfers actually work (once I saw the errors, I was cancelling without trying to transfer the whole file)! The transfer window reports about one error per packet, BUT, whatever the error is, it doesn't actually seem to affect the integrity of the file.

SO, it looks like the latest RC works fine, perhaps it's just too sensitive in it's error reporting?

I'm still working on my admin to do some testing and set you up with a test account, nevertheless...

- Van


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

So, do the transfers actually work with both the -b flag and the -be??? I'll research the error reporting.


   
ReplyQuote
(@vanhoose)
Eminent Member
Joined: 55 years ago
Posts: 17
Topic starter  

Apparently the -e flag is what saves the day... Though again, for me at least AbsoluteTelnet is still reporting the errors...

My Unix admin. wrote:
 > Hi,
 >  I did the -lrz -bev and it worked just fine.  Is it not workening for
 > you?  TTFN
 > 
 > You wrote:
 > > Try adding the -e flag...
 > >
 > > lrz -bev
 > >
 > > You might get errors, but maybe it will work at least?
 > >
 > > - Van
 > >
 > > > -----Original Message-----
 > > >
 > > > Hi,
 > > >  I installed the port :)  This is what I get with lrz -bv:
 > > >
 > > > %lrz -bv
 > > > lrz waiting to receive.Retry 0: TIMEOUT
 > > > Retry 0: Got ZCAN                    **B0900000000a87c
 > > >
 > > > lrz: winamp.exe removed.
 > > >
 > > > Transfer incomplete
 > > >
 > > > I don't see any other errors other than this in messages:
 > > >
 > > > Feb 13 15:46:54 HOSTNAME lrz[52286]: [user]
 > > > no.name/ZMODEM: got error
 > > >
 > > >
 > > > It doesn't make any sense that my firewall would be blocking
 > > > this as it's
 > > > zmodem over the ssh connection that's already established.
 > > > Very strange.
 > > > I wonder if they're making an assumption about the shell
 > > > evnironment that
 > > > you'd be using that would bung it up.  Let me know if I can
 > > > do anything
 > > > else.  TTFN

[size=1][ February 13, 2002, 05:24 PM: Message edited by: vanhoose ][/size]


   
ReplyQuote
(@bpence)
Member Admin
Joined: 8 months ago
Posts: 1374
 

Ok, I think I've got it. The program was counting certain timing conditions as errors, when really they were not. This explains why the file was still getting through even though every packet sent generated an error. The only thing counted as errors now is when the server requests a resend of data due to an error in transit. Still, I'd like to know why the -e is required. I suppose this can be due to interference from the tty (which the -e was designed to work around). You can get the latest here:

http://www.celestialsoftware.net/beta-testing

 

Brian

This post was modified 1 month ago by bpence

   
ReplyQuote
(@vanhoose)
Eminent Member
Joined: 55 years ago
Posts: 17
Topic starter  

The errors are no longer being reported. Thanks for all your help. This is a great app!

- Van


   
ReplyQuote
Page 2 / 2
Share: