From owner-freebsd-questions@FreeBSD.ORG Wed Jan 5 04:17:19 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB0B616A4CE for ; Wed, 5 Jan 2005 04:17:19 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46B9343D1F for ; Wed, 5 Jan 2005 04:17:19 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j054HCmG035621; Tue, 4 Jan 2005 22:17:12 -0600 (CST) (envelope-from dan) Date: Tue, 4 Jan 2005 22:17:12 -0600 From: Dan Nelson To: Doug Poland Message-ID: <20050105041712.GA18285@dan.emsphone.com> References: <20050105033712.GA43732@polands.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050105033712.GA43732@polands.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: questions@freebsd.org Subject: Re: Ultra Speed CD-RW media and cdrecord X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 04:17:19 -0000 In the last episode (Jan 04), Doug Poland said: > My son gave me a package of Memorex Ultra Speed CD-RW blanks for > Christmas. I was going to burn an ISO on my 5.3-STABLE system but > ran into a brick wall. > > cdrecord tells me that it's "Trying to use ultra high speed medium on > improper writer." I've used "MultiSpeed 1x2x4x" media and "1x-4x > Compatible" media in the past with no problems. >From a quick scan of the cdrecord source and some searches, it looks like Ultra Speed media require write speeds of 16x or faster, but your 2100S can only write CD-RW media at 10x (it can do CD-R's at 16x). You can use the -force flag to make cdrecord write to the disks, but no guarantees. It'd be nice if cdrecrd's error message printed the limits of drive and media instead of just saying that something's "improper" :) -- Dan Nelson dnelson@allantgroup.com