HP3000-L Archives

May 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Glenn Cole <[log in to unmask]>
Reply To:
Date:
Thu, 13 May 1999 10:06:36 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Wirt (after Rick Clark) writes:

>>  I received the following error when we ftp'd certain files to a HP9000
>>  and cannot find any clues as to what this means.
[snip]
>>   150 Opening ASCII mode data connection for ACT999.
>>   226-WARNING! 1918 bare linefeeds received in ASCII mode
>>      File may not have transferred correctly.

>The problem is that the file is not formatted in a standard ASCII format
>with CRLF at the end of each line.

There's no such thing as "a standard ASCII format," is there?
I mean, there's "standard ASCII characters," but not a "standard
ASCII format" -- the format is platform-dependent.

Actually, I think Jeff Kell was on the right track:

> for Unix the <cr> must be removed [leaving only <lf>]


Thus, it looks like Rick is getting this when transferring bytestream
files (remember, he's sending *to* a 9000), which have only "bare
linefeeds."

For confirmation, Rick, try this in the POSIX shell:

        head -3 < ACT999 | od -cx

'od' means 'octal dump', but the 'x' forces hex, while 'c'
shows the char equivalent.  It's not nearly as compact as fcopy's
;CHAR;HEX options, but it's more obvious what char is what code.
The '\n' values you see are the "newline" (linefeed) char.

--Glenn

.......................................................................

Item Subject: cc:Mail Text

ATOM RSS1 RSS2