=10I don't think it's a driver option. Just an option. So something like

cdrecord -v dev=3D15,0,0 speed=3D24 forcespeed driveropts=3Dburnfree =20
burnme.iso

If that doesn't work, maybe reading the man page, compiling the =20
latest cdrecord from -current pkgsrc or the netbsd-users list could =20
be of more help. I really think it's that cdrecord is playing it safe =20=

by not burning unknown media types at maximum drive speed. (Which is =20
good because as the man page says, if you spin a disk to faster than =20
it's rated speed the disk can explode taking out the drive, and =20
possibly your motherboard in a laptop.)

On May 11, 2005, at 10:44 AM, Davide Zanon wrote:

> On Sunday 08 May 2005 19:58, Chris Tribo wrote:
>
>> Well you can try "forcespeed" and see if that makes it go, or try =20
>> your
>> luck with some other media. Thats about the extent of advice I can =20=

>> give,
>> sorry.
>>
>
> Thank you instead! I tried driveropts=3Dforcespeed, but this is not =20=

> listed in
> the supported driver features :( driver is mmc_cdr) so the writer =20
> burns at 8x
> again. I can't understand why!
>
> Tanks,
> david
>
> !DSPAM:42821a6e313272016619313!
>