Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!ox.com!ox.com!emv
From: emv@ox.com (Ed Vielmetti)
Newsgroups: news.software.nntp
Subject: Re: Nntpxmit error 0 (I have the answer & fix)
Message-ID: <EMV.90Dec31135407@crane.aa.ox.com>
Date: 31 Dec 90 18:54:07 GMT
References: <1990Dec28.234730.8332@cmcl2.nyu.edu>
	<1990Dec29.034048.27998@ni.umd.edu> <pst.662588576@ack.Stanford.EDU>
	<16363@cs.utexas.edu>
Sender: usenet@ox.com (Usenet News Administrator)
Organization: OTA Limited Partnership, Ann Arbor MI.
Lines: 14
In-Reply-To: fletcher@cs.utexas.edu's message of 31 Dec 90 18:05:41 GMT

In article <16363@cs.utexas.edu> fletcher@cs.utexas.edu (Fletcher Mattox) writes:

   The messages which passed through here actually had the eighth
   bit turned on, 0xff.  This appears as DEL, 0x7f, in many pagers
   and editors.  Some (broken) versions of putc() will extend the
   sign and return -1.  

There's comments in the ultrix (mips) 4.1 stdio.h saying that putc()
was changed in 09 Nov 1989 to properly handle this case; I take that
to mean that early mips ultrix might have had it broken (I'm fuzzy on
dates).  It would be useful to know some more details of the systems
where nntp fails (name, os level and release date, etc.)

--Ed