X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: dd Bug using \\.\PhysicalDriveX ? Date: Wed, 19 Sep 2007 13:35:14 -0400 Message-ID: <200709191738.l8JHc8sW019686@zuul.kastle.com> From: "Scalzott, Todd" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l8JHZPr1006319 I believe that this is part of CORE, which I have at 6.9-5. I did update to all of the latest just a short while ago and reverified the problem. I've discovered what I believe to be a problem with "dd" on several different XP SP2 systems with Cygwin installed involving the usage of Windows' \\.\PhysicalDrive nomenclature. That is, reading from \\.\PhysicalDrive1 with the below command works flawlessly: dd if=^\^\.^\PhysicalDrive1 of=tmp.img bs=16384 However, writing to \\.\\PhysicalDrive1 in similar fashion fails with an error: dd if=tmp.img of=^\^\.^\PhysicalDrive1 bs=16384 dd: opening `\\\\.\\PhysicalDrive1': Invalid argument PhysicalDrive1 is a removeable drive. Thank you. -- 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/