For a list of "reported to work" drives that work with cdrecord check out:
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdwriters-1.8.html
Also, notice the "It should run on: All SCSI-3/mmc compliant drives, All
ATAPI/mmc compliant drvies"
The HP 7200 drive is listed, so maybe it will work with your drive.
- kevin
On Tue, 17 Aug 1999, Andrew Atrens wrote:
>
> Hi Amancio,
>
> I've got a:
>
> acd0: <HP CD-Writer+ 7200/V:003.01> CDROM drive at ata1 as master
> acd0: drive speed 1034KB/sec, 768KB cache
> acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
> acd0: supported write types: CD-R, CD-RW, test write
> acd0: Audio: play, 128 volume levels
>
> (HP 7200i) which works great. Burning is done via wormcontrol + dd as per
> Soren's recommendations. Data starvation was never a problem with my old
> 430Tx based motherboard, but became a problem when I moved up to Asus
> P5A/ALi board. The solution, it turns out, was to give dd a larger
> input/output block size - 20k instead of 2k (yes, I used team, and no, it
> didn't solve the problem ;)).
>
> Unfortunately there is no FreeBSD/cdrecord support for this or any other
> ATAPI drive. I've suggested to Soren that it wbn if his ATAPI stuff was
> layered under CAM, since this might possibly make porting things like
> cdrecord a bit more straightforward. As I understand it though the ATAPI
> spec is such that ATAPI devices can fail in ways that are not currently
> handled by CAM so this wouldn't be, shall we say, `a piece of cake'. So,
> as the saying goes beggars can't be choosers, and I am happy with and
> grateful for all of Soren's efforts. :)
>
> To conclude, I like 7200i, the FreeBSD support is reasonable (for what I
> need), and this device is somewhat cheaper than it's SCSI cousins.
>
>
> Cheers,
>
> Andrew.
>
> --
> +--
> | Andrew Atrens Nortel Networks, Ottawa, Canada. |
> | All opinions expressed are my own, not those of any employer. |
> --+
> Heller's Law: The first myth of management is that it exists.
> Johnson's Corollary: Nobody really knows what is going on
> anywhere within the organization.
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message