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
Delivered-To: corinna-cygwin AT cygwin DOT com
X-Originating-IP: [203.61.170.204]
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
Cc: corinna-cygwin AT cygwin DOT com
Subject: read(): varblk tape records...(& Fix for : read())
Date: Tue, 02 Mar 2004 10:51:04 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <Sea2-F29FHsBGwtzNc800044bfd@hotmail.com>
X-OriginalArrivalTime: 02 Mar 2004 10:51:04.0500 (UTC) FILETIME=[42666740:01C40044]

Hi Corinna,

Rereading the MSDN: Q161338 document I refered to before, Cygwin will need 
to use a minimum 128KB buffer when 'reading' data from tapes - the NT 
specification doesn't allow access to the 'last bytes' in a variable-block 
any other way.  128KB allows for any SCSI device under windows.

(I noticed there was a memcpy for each ReadFile call - so I assume CygWin 
uses its own internal buffers, which may or maynot be large enough for tape 
support.)
Jason.

_________________________________________________________________
SEEK: Now with over 50,000 dream jobs! Click here  
http://ninemsn.seek.com.au/


--
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/