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: Thu, 1 Apr 2004 10:36:29 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 64-bit file operations (lseek64() etc) misbehaving Message-ID: <20040401083629.GB28999@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040331183428 DOT GA1710 AT esd-mbrown DOT us DOT dg DOT com> <20040331201910 DOT GC1710 AT esd-mbrown DOT us DOT dg DOT com> <20040331215849 DOT GD1710 AT esd-mbrown DOT us DOT dg DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Mar 31 17:36, Igor Pechtchanski wrote: > Mike, > > Please make sure your mailer respects the Reply-To: header. Thanks. > > Frankly, I don't see any reason why open() *wouldn't* succeed on > \\.\PhysicalDrive0... All it'll do is recognize a Win32 pathname (because > of the '\'), and pass it along to Windows. OTOH, Cygwin will not see this > name as special -- from Cygwin's point of view it's just another file. So > any operations invoked on it (including "open") will be regular Windows > file calls, not special ones (e.g., NtOpenFile with the right attributes, > as done in fhandler_dev_raw::open). This might be the reason for your > initial problem. > Igor Perfect explanation, Igor! 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/