Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Mon, 22 Nov 1999 17:51:27 -0500 To: Gareth Williams Cc: cygwin@sourceware.cygnus.com, gareth@dgwsoft.co.uk Subject: Re: 0x1a bug - its not just awk Message-ID: <19991122175127.A6804@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Gareth Williams , cygwin@sourceware.cygnus.com, gareth@dgwsoft.co.uk References: <3.0.6.32.19991122203517.00924d50@146.80.9.11> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.6.32.19991122203517.00924d50@146.80.9.11>; from dgwilliams@dera.gov.uk on Mon, Nov 22, 1999 at 08:35:17PM +0000 On Mon, Nov 22, 1999 at 08:35:17PM +0000, Gareth Williams wrote: >I just downloaded B20.1 and compiled a few C++ programs under NT4. >Those that write data work fine. Those that read fail on the byte >0x1a. > >I have seen the reports that awk can not read the byte 0x1a. If you've seen the reports, you should be aware that this is not a bug but a feature. This character is considered to be an EOF character by both cygwin and MSVC. The solution is to use binary mounts, i.e., mount the directory using the -b option: mount -b c:\somedir /somedir That will cause files in that directory to be interpreted as normal UNIX streams of bytes. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com