This is the mail archive of the
cygwin
mailing list for the Cygwin project.
read(): varblk tape records...
- From: "Jason Winter" <jasonwinter at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 01 Mar 2004 13:32:25 +0000
- Subject: read(): varblk tape records...
- Bcc:
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/