From owner-freebsd-questions@FreeBSD.ORG Thu Jun 8 04:23:20 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 8031216EC1F for ; Thu, 8 Jun 2006 02:49:37 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB93643D67 for ; Thu, 8 Jun 2006 02:49:29 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id BF8DD5CE7; Wed, 7 Jun 2006 22:49:28 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jbNwPFKB7w5; Wed, 7 Jun 2006 22:49:27 -0400 (EDT) Received: from [192.168.1.251] (pool-68-160-201-170.ny325.east.verizon.net [68.160.201.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id B05CA5CB2; Wed, 7 Jun 2006 22:49:26 -0400 (EDT) Message-ID: <4487902D.80001@mac.com> Date: Wed, 07 Jun 2006 22:49:17 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Napoleon Dynamite References: <200606071503.00025.groundedforlife@verizon.net> In-Reply-To: <200606071503.00025.groundedforlife@verizon.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: burncd error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2006 04:23:22 -0000 Napoleon Dynamite wrote: [ ...top posting recovered... ] > On Wednesday 07 June 2006 10:44, Michael S wrote: >> I had the same kind of issue, also with 6.1-RELEASE, and just fixed it >> the Windows way - reboot. And it worked fine. > > I got that error pretty routinely for a while. The cd-r was always usable, > though. I switched to k3b for cd burning and have not seen that error since. k3b uses dvd+rw-tools rather than burncd underneath. It's possible that they would work better for the original poster too. It also sounds like the issue with burncd is reproducible, anyone filed a PR...? -- -Chuck