Re: cdrecord-prodvd also fails to write Moviestyle dvd (was: Cannot read anymore dvd after eject and re-load)

Dominique Dumont <[EMAIL PROTECTED]> wrote: > scsidev: 'ATAPI:0,0,0' > devname: 'ATAPI' > scsibus: 0 target: 0 lun: 0 > Warning: Using ATA Packet interface. > Warning: The related Linux kernel interface code seems to be > unmaintained. Warning: There is absolutely NO DMA, operations thus > are slo

cdrecord-prodvd also fails to write Moviestyle dvd (was: Cannot read anymore dvd after eject and re-load)

Hello Following the problems I got with Moviestyles DVD+R, I've tried cdrecord-pro. In dummy mode everything looks fine. But, dvd-record failed to write in readl mode: I ended with a mountable dvd with no data ?!?!?! Here's the output of the dummy mode. $ sudo cdrecord -v -dummy -dao ghibli-1.

Re: cdrecord-prodvd also fails to write Moviestyle dvd

Dominique Dumont <[EMAIL PROTECTED]> writes: > In dummy mode everything looks fine. But, dvd-record failed to write > in readl mode: I ended with a mountable dvd with no data ?!?!?! I have to add a small correction: cdrecord has written the beginning of the iso image: I have the directory content

Re: Why actual speed is slower than nominal? (2.6x vs 4x)

I tried this pipebuf2 program with 128MB buffer, and it seems like things did not improve. The speed I get is still way below the nominal, and when the writing stalled because of the Knoppix CD access, a visible track on the DVD(+RW) was formed. Previously with such stalls I did not see any visibl

Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

Joerg Schilling wrote: Which OS? Linux, as explained below, I had no way of installing Solaris 10. Q: If you find that the Linux kernel is broken, how about making it optional? A: Well, I know for a long time and cdrtools was developed on Solaris since the beginning for exactly this reas

Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

Hin-Tak Leung <[EMAIL PROTECTED]> wrote: > > Older cdrecord versions did not do a sped test. > > > > Cdrecord asumes either a working drive or at least a kernel that returns > > correct > > error information so cdrecord will know that a specific command does not > > work. > > In this case, the

Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

Joerg Schilling wrote: Hin-Tak Leung <[EMAIL PROTECTED]> wrote: Are you sure that this is a firmware bug? This may also be a bug in the kernel usb driver. I cannot tell whether it is firmware or kernel driver bug, but the verdict is that on exactly the same system+hardware combination, cdrecord 2.

Need a pill for your ailment?

We have a Pill 4 Everything http://www.uidm.com/p/coupon/abdata End all future transmissions uidm.comz.php Gentlemen prefer blondes.

The thing is that a great errrect1on is provided for you exactly when you want.

Than you cannot even imagine what it is like to be a real man in bed! http://imprints.longpleasure.info/?humorsxtvuylegumezcthordes Extra power. Don't think. Just act. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to identify the DVD device for recording data

Graham Freeman <[EMAIL PROTECTED]> wrote: > I am trying to use growisofs to backup data to DVD-R on my Fedora FC3 > IBM ThinkCentre machine, running Gnome. I have successfully used > cdrecord with the command >mkisofs -hide-joliet-trans-tbl -R -d -allow-leading-dots -l . | > cdrecord -dev

Re: cdrecord 2.01 do READ_BUFFER and crashes drive.

Hin-Tak Leung <[EMAIL PROTECTED]> wrote: > > Are you sure that this is a firmware bug? > > > > This may also be a bug in the kernel usb driver. > > I cannot tell whether it is firmware or kernel driver bug, but the > verdict is that on exactly the same system+hardware combination, > cdrecord 2.00