delorie.com/archives/browse.cgi | search |
Date: | Mon, 03 Jun 2002 20:00:33 +0300 |
From: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | JT Williams <jeffw AT darwin DOT sfbr DOT org> |
Message-Id: | <1483-Mon03Jun2002200032+0300-eliz@is.elta.co.il> |
X-Mailer: | emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 |
CC: | djgpp AT delorie DOT com |
In-reply-to: | <20020603142344.GA9949@kendall.sfbr.org> (message from JT |
Williams on Mon, 3 Jun 2002 09:23:44 -0500) | |
Subject: | Re: create disk image using dd |
References: | <20020603142344 DOT GA9949 AT kendall DOT sfbr DOT org> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> Date: Mon, 3 Jun 2002 09:23:44 -0500 > From: JT Williams <jeffw AT darwin DOT sfbr DOT org> > > Is there any way to do the equivalent of > > dd if=/dev/fd0 of=disk.img > > with the djgpp port of `dd'? DOS doesn't allow to access block devices directly. So the only way to do that is to use the DJGPP Filesystem Extensions feature to redirect such requests to BIOS functions. The current `dd' port doesn't have such code, so it can only access disk files and character devices. I once wrote a prototype implementation of this (it needs work to cope with bad blocks and other failures returned by BIOS functions). I can dust it off and mail it to you, if you are interested in working on this.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |