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: Tue, 3 May 2005 19:45:51 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [Fwd: Re: impossible to restore MBR using dd] Message-ID: <20050503174551.GA30980@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4277B099 DOT 2050609 AT echotech DOT ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4277B099.2050609@echotech.ch> User-Agent: Mutt/1.4.2i On May 3 19:10, Matthias Bertschy wrote: > Maybe I should recall you that on Linux, we can safely write 446 bytes > blocks to a raw device. Indeed, the command dd if=boot.MBR of=/dev/sda > bs=446 count=1 works under Linux. > I also don't understand why you are using NTSF raw devices to access the > MBR... after all the MBR isn't formatted at all ! What is an "NTFS raw device" for you? > I think I will fill a bug report for the dd command under Cygwin. Could > you point me where to do it? There's no point in that. I removed the buffering in writing to raw devices last year because the buffering created more problems than it helped when it came to writing multiple-volume archives to, e.g, floppy. Windows calls OTOH only support writes to raw devices in module blocksize chunks. I don't think that's too hard a restriction. 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/