Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Wed, 20 Apr 2005 12:38:33 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Reading "raw" disk greater than 1 terabyte Message-ID: <20050420103833.GW16098@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Well, "Anonymous" was right, I just didn't read your mail further after I saw the usage of \\\\.\\physicaldrive1, I apologize. I never heard of such a 1TB border which would result in problems. However, due to the lack of such a big drive, I can't debug that, obviously. On Apr 13 18:47, Loh, Joe wrote: > Same command but using /dev/sdb instead: > $ dd if=/dev/sdb ibs=1024 skip=1610612600 count=10 | od -x > dd: reading `/dev/sdb': Invalid request code > 0+0 records in > 0+0 records out > 0000000 What's weird here is that the "Invalid request code" is never generated manually by Cygwin, but only when some Windows call returns the error code ERROR_INVALID_FUNCTION. So it's a Windows function which chokes. Could you please run the above dd under strace and send the strace output to this list? Perhaps that helps to track this down. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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/