From owner-freebsd-questions Wed Jun 2 3:27: 3 1999 Delivered-To: freebsd-questions@freebsd.org Received: from control.colossus.dynip.com (pm2-25.sba1.avtel.net [207.71.218.125]) by hub.freebsd.org (Postfix) with ESMTP id 52DD9158A8 for ; Wed, 2 Jun 1999 03:27:00 -0700 (PDT) (envelope-from dburr@control.colossus.dynip.com) Received: (from dburr@localhost) by control.colossus.dynip.com (8.9.3/8.9.2) id DAA01372; Wed, 2 Jun 1999 03:26:51 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9906020438.AA15862@dartagnan.maths.adelaide.edu.au> Date: Wed, 02 Jun 1999 03:26:51 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Gregory Lewis Subject: Re: ATAPI cdr's Cc: freebsd-questions@FreeBSD.ORG, (Jason L. Schwab) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A long time ago in a galaxy far, far away (actually, it was on 02-Jun-99), the great prophet Gregory Lewis once wrote: >> Does freebsd support atapi cdr's? I have mkisofs and cdrecord all >> installed and stuff but i can't figure out how to use it with my >> ATAPI cdr... > > ATAPI writers aren't supported via the cdrecord port at present, only > SCSI. > People have, however, reported success using the scripts in > /usr/share/examples/atapi/ with their ATAPI writers. You might want to > check out those scripts and man pages for the appropriate programs. I > believe the correct device to use with the scripts is acd0c, e.g. you > should do "burndata acd0c iso9660.image" (where iso9660.image is > replaced > by the name of the image you want to burn). > > I'll probably be trying this myself in a couple of days when I get time > to go buy some blanks :). That's correct. This works fine for me with both an HP 8210i and a cheap JVC clone, RW2224. Also, if you wish to use CD-R/CD-RW, It is suggested that you upgrade to 3.2-RELEASE. 3.1 and previous use the "rezero" ATAPI command, which some drives do not support; if your drive does not support it, it causes the writing process to halt, resulting in a ruined disc. 3.2 corrects this problem by only using the rezero command if it is supported by the particular drive. --- Donald Burr | PGP: Your *NEW* WWW HomePage: http://more.at/dburr/ ICQ #16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message