Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Originating-IP: [203.61.170.154]
X-Originating-Email: [jasonwinter AT hotmail DOT com]
X-Sender: jasonwinter AT hotmail DOT com
From: "Jason Winter" <jasonwinter AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: read(): varblk tape records...
Date: Mon, 01 Mar 2004 13:32:25 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <Sea2-F58zPZrIkyPzGN0002760a@hotmail.com>
X-OriginalArrivalTime: 01 Mar 2004 13:32:26.0146 (UTC) FILETIME=[A2B29820:01C3FF91]

The NT API 'ReadFile' for reading variable block tape records indicates the 
block length by returning only one full-block at a time (per read call) 
which isn't being honored by CygWin's read() function.

Can CygWin be changed to detect a *tape* read() call and not continue to 
fill the user-buffer after the first ReadFile call returns?

The Tape Block Length information is in MSDN, within the document Q161338 in 
the knowledge base.

It *may* also be the case that setting a SCSI tape (/dev/st0) to 
variable-block mode is required before each write operation under NT/2000 - 
which is slightly different to the way my RetHat Linux 8.0 works, which 
keeps the mode set even after a write call.  Then again it could be my 
setup: Adaptec 1520B SCSI Adaptor w/ 4mm DDS-2 DAT Drive.

_________________________________________________________________
You could be a genius! Find out by taking the IQ Test 2003. $5.50 (incl 
GST).  Click here  http://sites.ninemsn.com.au/minisite/testaustralia/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/