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
Date:	Tue, 2 Mar 2004 12:33:37 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: read(): varblk tape records...(& Fix for : read())
Message-ID:	<20040302113337.GG21589@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Sea2-F29FHsBGwtzNc800044bfd AT hotmail DOT com>
Mime-Version:	1.0
In-Reply-To:	<Sea2-F29FHsBGwtzNc800044bfd@hotmail.com>
User-Agent:	Mutt/1.4.2i

On Mar  2 10:51, Jason Winter wrote:
> 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.

If you have a look into the source code, you'll see that Cygwin in variable
block size case creates a buffer of the maximum block size allowed by the
tape drive (or driver), returned by GetTapeParameters().

I've not investigated so far if read behaves correctly or not, but now
I understand what you're up to.  I'll look into it.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -