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: Fri, 4 Nov 2005 10:53:23 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.5.18 and //./PhysicalDrive?? Message-ID: <20051104095323.GU2988@calimero.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 On Nov 3 16:56, Loh, Joe wrote: > Folks, > Since updating the Cygwin 1.5.18, we started seeing problem similar to > the what "dd" is experiencing. The previous Cygwin DLL we used was > Cygwin 1.5.16, at that works flawlessly. Is anyone out there > experiencing the same issue? > > I have reverted back to the Cygwin 1.5.16 and everything start working > normally again. Due to legacy support requirement we are still using > the //./PhysicalDrive?? to accessing raw device in Cygwin. > > I am also attaching the "strace" output at the end of this mail for the > "dd" that failed. Please advise what additional information is needed. > > See the example and result below: > > $ dd if=//./physicaldrive0 count=1 | od -x > dd: opening `//./physicaldrive0': No such host or network path > 0000000 Sorry, but using //./foo was deprecated already for a long time, see http://cygwin.com/cygwin-ug-net/using-specialnames.html#id4676548 Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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/