Gary I Kahn wrote:
> 
> I'm having trouble ftp'ing a file which contains NUL characters.
> The file begins with 32K of NUL characters, in fact, and the most
> that I've been able to ftp is about 2K of the file.  The transfer
> usually stops dead after NO bytes have been transferred.  It's
> not the only file with which I've had the problem, but it's the
> first file that stopped transferring after nl bytes had been
> moved.

I had a similar poblem  two months back when I tried to download a file
that contained a long string of '+'s, which is, of course, the default
escape character (a series of three in a row, at least).  Naturally,
this caused me all kinds of grief until I disabled escapes altogether
with 'ATS2=128'.  You will probably want to make that part of your
initialization string rather than saving it in your modem's non-volatile
RAM with the '&W0' parameter so that you can still escape from a locked
session with minicom or another terminal program.

> This problem is isolated to linux, since I can ftp the file on
> the same computer under Win95.

More than likely, Win95 includes the escape code disabling string with
its dialup string by default.

> I've tried various asyncmaps (00000000, ffffffff, 00000001),
> various MTU/MRU sizes, several versions of PPP, and several
> kernels, and several ftp sites.  Right now, I'm using ppp 2.3.7
> and kernel 2.2.3.
> 
> I can browse Web pages OK, and I can ftp other files.  My problem
> seems to be tied to the content of this file.  What other
> software in my (modified) RH5.1 linux system could be involved
> with my problem?  I think that I either need to upgrade something
> or reconfigure something.
> 
> The file being ftp'd is
> http://donut.tho.org/redhat-6.0/redhat-6.0-i386.iso.
> 
> Thanks.  This is getting frustrating.
> 
> Gary Kahn
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to