From owner-freebsd-hackers Tue Dec 17 0:38:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3265637B401 for ; Tue, 17 Dec 2002 00:38:27 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3506243EA9 for ; Tue, 17 Dec 2002 00:38:26 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.5/8.12.6) id gBH8d600075537; Tue, 17 Dec 2002 09:39:06 +0100 (CET) (envelope-from sos) From: Soeren Schmidt Message-Id: <200212170839.gBH8d600075537@spider.deepcore.dk> Subject: Re: burncd raw mode In-Reply-To: <001701c2a57c$4587a340$9b18e8d8@slugabed.org> To: Sean Hamilton Date: Tue, 17 Dec 2002 09:39:06 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Sean Hamilton wrote: > Greetings, > > I have a 2352-byte block mode1 CD image, and wish to burn this with burncd. > I know I can use bin2iso or bchunk to decode it, but I'd rather keep the > block metadata intact from the file itself instead of having the > burner/driver(?) reconstruct it. > > I assembled a small stack of coasters by trying a few combinations of -d, > 'raw', etc, to no avail. The best I got was from raw, a track which needed > to be read with 2352 byte blocks, so it wasn't being interpreted as > metadata. I presume if I were to dd this entire disc into a file, I would > have a verbatim copy of my original, albeit less fault tolerant. > > Can this be done with burncd? Not as is, but it could be done, however there is absolutly no point in doing it, *unless* its to make an exact copy of a CD that is copyprotected in one of the usual ways. So, assuming you have a legit image, you simply rip out the 2048 bytes of real data from each 2352 byte block in that file, and burn it as a normal data CD, bingo.. > How does the drive/driver know to interpret the remaining 304 bytes as > metadata? Thats a long explanation, its checksumming etc etc. > Is it possible to extract the full 2352 byte blocks from a track which is > advertised as only 2048, ie a typical data track? There are a few Windows > apps for doing exactly this. Sure it is, but why would you need to ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message