This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: read(): varblk tape records...(& Fix for : read())
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 2 Mar 2004 12:33:37 +0100
- Subject: Re: read(): varblk tape records...(& Fix for : read())
- References: <Sea2-F29FHsBGwtzNc800044bfd@hotmail.com>
- Reply-to: cygwin at cygwin dot com
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@cygwin.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/