From owner-freebsd-stable Sun Apr 16 23:20:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wanadoo.fr (Raspail-22-128.abo.wanadoo.fr [164.138.34.128]) by hub.freebsd.org (Postfix) with ESMTP id 5AB4437BA53 for ; Sun, 16 Apr 2000 23:20:36 -0700 (PDT) (envelope-from dockes@wanadoo.fr) Received: (from dockes@localhost) by hautmedoc.dockes.com (8.9.3/8.9.2) id IAA25805; Mon, 17 Apr 2000 08:02:56 +0200 (MEST) From: Jean-Francois Dockes Message-ID: <14586.43280.638627.541595@hautmedoc.dockes.com> Date: Mon, 17 Apr 2000 08:02:56 +0200 (MEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Rod Taylor Cc: freebsd-stable@freebsd.org Subject: Re: BurnCD In-Reply-To: <38FA1311.DEF2484B@fallesen.dk> References: <20000416104133.B3353@peon.zort.on.ca> <38FA1311.DEF2484B@fallesen.dk> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jens Fallesen writes: > Rod Taylor wrote: > > > However, I did the upgrade to v4 shortly after moving, so perhaps the > > drive got knocked around during that time. > > I wouldn't go for that explanation--the exact same thing happened on > my machine after going to 4.x and I haven't moved my computer an inch. > Besides, other people have reported the same problem. > > If I boot my computer into Windows I have no problem burning CDs > either... Well, if several persons see this happening after an upgrade, it obviously becomes a software problem and I made a fool of myself. To save the face, I'll just mention again that some drives do 'creative' error reporting and will report MEDIUM ERROR for what is really a loss of streaming, or another nondescript error, which could be caused by a driver problem. Obviously, I we follow my proposed cure (replace the drive) in such a situation, my company is going to become a great customer for our cdr drive vendor :-) J.F. Dockes. -- Jean-Francois Dockes dockes@musicmaker.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message