> > > now when I: growisofs -M /dev/scd0 -R -J /morefiles
> > >
> > > I get the error: :-( last session is not empty
> > >
> >
> > Do submit dvd+rw-mediainfo output.
>
> INQUIRY:[SONY][DVD RW DRU-510A ][1.0d]
> GET [CURRENT] CONFIGURATION:
> Mounted Media: 1Bh, DVD+R
>
> Have you dealt with anyone at Plextor that I might try to explain this to?
No, I have no contact with Plextor. I considered 708 unit when it was
initially released, as they mentioned DVD+MRW support in specification
sheet. But they couldn't clarify what does it really mean in practice
[well, the
> Have you dealt with anyone at Plextor that I might try to explain this to?
No, I have no contact with Plextor. I considered 708 unit when it was
initially released, as they mentioned DVD+MRW support in specification
sheet. But they couldn't clarify what does it really mean in practice
[well, the
> Im using a SONY DVD+RW drive with Linux RedHat 9 (2.4.20 Kernel).
>
> I got cdtools 2.00.3 going fine as did dvd+rw-tools.5.17.4.8.6.
>
> ...
>
> now when I: growisofs -M /dev/scd0 -R -J /morefiles
>
> I get the error: :-( last session is not empty
>
> Is there something im overlooking here?
> But sometimes it [DVD+RW recording with NEC-ND1300A] goes wrong.
>
> > > After this I can't even mount the dvd unless I reboot or open the
> > > dvd manually.
> >
> >Utterly strange, sounds more like deficient hardware... If upgrading
> >firmware doesn't help, I'd suggest to try to replace the u
> Version with dinfo[32+4]
> ==
> [EMAIL PROTECTED] dvd+rw-tools-5.16.4.8.5]$ ./test /dev/scd0
> :-( unable to READ DISK INFORMATION: Input/output error
> ==
The above program uses READ DISK INFORMATION with length parameter used
by cdrecord.
> Version with dinfo[32]
> ===
> Im using a SONY DVD+RW drive with Linux RedHat 9 (2.4.20 Kernel).
>
> I got cdtools 2.00.3 going fine as did dvd+rw-tools.5.17.4.8.6.
>
> ...
>
> now when I: growisofs -M /dev/scd0 -R -J /morefiles
>
> I get the error: :-( last session is not empty
>
> Is there something im overlooking here?
> But sometimes it [DVD+RW recording with NEC-ND1300A] goes wrong.
>
> > > After this I can't even mount the dvd unless I reboot or open the
> > > dvd manually.
> >
> >Utterly strange, sounds more like deficient hardware... If upgrading
> >firmware doesn't help, I'd suggest to try to replace the u
> > > Everytime I invoke growisofs, it goes through the entire writing
> > > process, but then it hangs when flushing the cache at the end (before
> > > closing the track and the session).
> >
> > Do you mean it hangs more longer than 10-15 minutes?
> I once left it while I was watching a movie (ov
> Version with dinfo[32+4]
> ==
> [EMAIL PROTECTED] dvd+rw-tools-5.16.4.8.5]$ ./test /dev/scd0
> :-( unable to READ DISK INFORMATION: Input/output error
> ==
The above program uses READ DISK INFORMATION with length parameter used
by cdrecord.
> Version with dinfo[32]
> ===
> > > Everytime I invoke growisofs, it goes through the entire writing
> > > process, but then it hangs when flushing the cache at the end (before
> > > closing the track and the session).
> >
> > Do you mean it hangs more longer than 10-15 minutes?
> I once left it while I was watching a movie (ov
> I am making backups to a DVD+RW using growisofs (latest: 5.17.4.8.6)
> on a NEC-1300A (1.05) (on Linux).
> Usually it runs without problems for a while but sometimes it doesn't.
Do you mean it *completes* recordings most of the time and sometimes
fails to complete one? All this is it with same m
> I have an OptoRite DD0203, and I'm having trouble writing DVD+RWs.
> ...
> [EMAIL PROTECTED] dtessier $ growisofs -Z /dev/dvd=/media/pics.iso
Quoting http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html:
"... Unit [Optorite DD020x] seems to fail to resume DVD+RW background
formatting transparentl
> I am making backups to a DVD+RW using growisofs (latest: 5.17.4.8.6)
> on a NEC-1300A (1.05) (on Linux).
> Usually it runs without problems for a while but sometimes it doesn't.
Do you mean it *completes* recordings most of the time and sometimes
fails to complete one? All this is it with same m
> I have an OptoRite DD0203, and I'm having trouble writing DVD+RWs.
> ...
> [EMAIL PROTECTED] dtessier $ growisofs -Z /dev/dvd=/media/pics.iso
Quoting http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html:
"... Unit [Optorite DD020x] seems to fail to resume DVD+RW background
formatting transparentl
> I am sure that if growisofs would check all relevant information
> returned by the driver, it would fail too.
Thomas! Could you run attached program with your /dev/dvd as argument?
Then remove +4 from dinfo declaration, recompile and re-run. To compile
save it in dvd+rw-tools source catalog and
> I am sure that if growisofs would check all relevant information
> returned by the driver, it would fail too.
Thomas! Could you run attached program with your /dev/dvd as argument?
Then remove +4 from dinfo declaration, recompile and re-run. To compile
save it in dvd+rw-tools source catalog and
> >The cdrecord README clearly states that you _need_ working DMA
> >in order to write DVDs. If you have burnfree ON the drive just
> >dramatically slows down.
> >
> >
> If the DVD unit were set to 4x, but data underrun were reducing the
> effective transfer speed to 2x,
Well, this I can agree wit
> >The cdrecord README clearly states that you _need_ working DMA
> >in order to write DVDs. If you have burnfree ON the drive just
> >dramatically slows down.
> >
> >
> If the DVD unit were set to 4x, but data underrun were reducing the
> effective transfer speed to 2x,
Well, this I can agree wit
> INQUIRY:[PHILIPS ][DVDR824P][P1.2]
>
> > > No matter what write speed value I select my DVD-burner always chooses
> > > the highest possible values. I am using dvd+rw-tools-5.17.4.8.6.
> > >
> > > I digged in the source and found that following the "GET PERFORMACE"
> > >
> INQUIRY:[PHILIPS ][DVDR824P][P1.2]
>
> > > No matter what write speed value I select my DVD-burner always chooses
> > > the highest possible values. I am using dvd+rw-tools-5.17.4.8.6.
> > >
> > > I digged in the source and found that following the "GET PERFORMACE"
> > >
> > The burner software can open exclusive - see man open.
>
> You mean O_EXCL? That doesn't seem to make sense?
You must be referring to the fact that O_EXCL is essentially undefined
without O_CREAT. It's absolutely true, but it doesn't mean that it's not
passed down to kernel, most notably when
> > The burner software can open exclusive - see man open.
>
> You mean O_EXCL? That doesn't seem to make sense?
You must be referring to the fact that O_EXCL is essentially undefined
without O_CREAT. It's absolutely true, but it doesn't mean that it's not
passed down to kernel, most notably when
> >> I just did run a test that verifies that the 708 in fact returns 36 bytes.
> >> So the problem is definitely caused by a Linux driver bug.
> >>
> >> I tend to believe that growisofs just does not check the SCSI status
> >> byte
>
> >Quoting myself. "Under Linux kernel 2.4 growisofs counts on
> >> I just did run a test that verifies that the 708 in fact returns 36 bytes.
> >> So the problem is definitely caused by a Linux driver bug.
> >>
> >> I tend to believe that growisofs just does not check the SCSI status
> >> byte
>
> >Quoting myself. "Under Linux kernel 2.4 growisofs counts on
> I just did run a test that verifies that the 708 in fact returns 36 bytes.
> So the problem is definitely caused by a Linux driver bug.
>
> I tend to believe that growisofs just does not check the SCSI status
> byte
Quoting myself. "Under Linux kernel 2.4 growisofs counts on sr_mod to
check the
> If you have burnfree ON the drive just
> dramatically slows down.
*If* it turns to be true, then it would be the first DVD recorder I've
seen to do such thing. I mean I so far haven't seen a single DVD
recorder which would decrease DVD recording velocity because buffer
underrun protection was tu
> I just did run a test that verifies that the 708 in fact returns 36 bytes.
> So the problem is definitely caused by a Linux driver bug.
>
> I tend to believe that growisofs just does not check the SCSI status
> byte
Quoting myself. "Under Linux kernel 2.4 growisofs counts on sr_mod to
check the
> ... tried using -speed=4 and it still took 28 minutes. Here the
> reported speed was 4.1x though. This recording time would seem to
> me to be closer to 2x speed. The "write" LED is illuminated
> constantly so I do not think there are any buffer under-runs that
> would account for the slower p
> > Inserted media into another drive and it appears to be burning
> > normally. Except that it reported the speed at 2.5x instead of 2.4x.
> > This unit was not bound to a raw device. It completed the burn in
> > 22 minutes as I would expect for 4.2 GBytes.
>
> This is interesting. dvd+rw-tools
> If you have burnfree ON the drive just
> dramatically slows down.
*If* it turns to be true, then it would be the first DVD recorder I've
seen to do such thing. I mean I so far haven't seen a single DVD
recorder which would decrease DVD recording velocity because buffer
underrun protection was tu
> # growisofs -Z /dev/scd0 -dvd-video output
> Executing 'mkisofs -dvd-video output | builtin_dd of=/dev/raw/raw1 obs=32k
> seek=0'
> :-( unable to PREVENT MEDIA REMOVAL: Bad file descriptor
>
> This was using a new DVD+RW media on a HP 300n IDE drive unit.
> The device is set to use the /dev/raw
> ... tried using -speed=4 and it still took 28 minutes. Here the
> reported speed was 4.1x though. This recording time would seem to
> me to be closer to 2x speed. The "write" LED is illuminated
> constantly so I do not think there are any buffer under-runs that
> would account for the slower p
> > Inserted media into another drive and it appears to be burning
> > normally. Except that it reported the speed at 2.5x instead of 2.4x.
> > This unit was not bound to a raw device. It completed the burn in
> > 22 minutes as I would expect for 4.2 GBytes.
>
> This is interesting. dvd+rw-tools
> # growisofs -Z /dev/scd0 -dvd-video output
> Executing 'mkisofs -dvd-video output | builtin_dd of=/dev/raw/raw1 obs=32k seek=0'
> :-( unable to PREVENT MEDIA REMOVAL: Bad file descriptor
>
> This was using a new DVD+RW media on a HP 300n IDE drive unit.
> The device is set to use the /dev/raw/ra
> It seems that the Sun volume mamager performs a dummy mount for
> empty medium and remains quiet until you call "eject cd".
Upon CD/DVD media load Solaris volume manager arranges kind of "bypass"
device entry under /vol and then invokes rmmount. Rmmount analyzes the
media to identify the file sy
> It seems that the Sun volume mamager performs a dummy mount for
> empty medium and remains quiet until you call "eject cd".
Upon CD/DVD media load Solaris volume manager arranges kind of "bypass"
device entry under /vol and then invokes rmmount. Rmmount analyzes the
media to identify the file sy
> Does
> this answer mean that cdrecord fundamentally checks some data that is always
> going to give me an error,
Let me re-phrase. Growisofs pulls DISC INFORMATION (that's what the
command 0x51 in question does) in a way different from cdrecord, which I
believe is/offer as the explanation for wh
> Does
> this answer mean that cdrecord fundamentally checks some data that is always
> going to give me an error,
Let me re-phrase. Growisofs pulls DISC INFORMATION (that's what the
command 0x51 in question does) in a way different from cdrecord, which I
believe is/offer as the explanation for wh
> >> >> -a broken drive.
> >> >Again, since growisofs works, I doubt this, but perhaps cdrecord avails
> >> >itself of some facility that growisofs ignores. Is this the case? In
> >> >other
> >> >words, WHY would growisofs either not have or not be stopped by this
> >> >error,
> >> >while c
> >> >> -a broken drive.
> >> >Again, since growisofs works, I doubt this, but perhaps cdrecord avails
> >> >itself of some facility that growisofs ignores. Is this the case? In other
> >> >words, WHY would growisofs either not have or not be stopped by this error,
> >> >while cdrecord is? R
First of all note that 5.17 is strongly recommended update for those who
deploy 5.14 through 5.16. It addresses problems with DVD-dash recordings
performed with -dvd-compat option, i.e. very kind of recordings you're
referring to. I apologize for inconvenience, but do upgrade.
Now to wrap up direc
First of all note that 5.17 is strongly recommended update for those who
deploy 5.14 through 5.16. It addresses problems with DVD-dash recordings
performed with -dvd-compat option, i.e. very kind of recordings you're
referring to. I apologize for inconvenience, but do upgrade.
Now to wrap up direc
> cdrecord development
> was then suspended for a while, and Andy Polyakov made dvd+rw-tools
> (growisofs) which is mainly meant for DVD+ drives, and is open
> source under the GPL.
cdrecord release schedule was never a driving force for dvd+rw-tools, it
was availability of te
> >> -a broken drive.
> >Again, since growisofs works, I doubt this, but perhaps cdrecord avails
> >itself of some facility that growisofs ignores. Is this the case? In other
> >words, WHY would growisofs either not have or not be stopped by this error,
> >while cdrecord is? Recall that cdre
> cdrecord development
> was then suspended for a while, and Andy Polyakov made dvd+rw-tools
> (growisofs) which is mainly meant for DVD+ drives, and is open
> source under the GPL.
cdrecord release schedule was never a driving force for dvd+rw-tools, it
was availability of te
> >> -a broken drive.
> >Again, since growisofs works, I doubt this, but perhaps cdrecord avails
> >itself of some facility that growisofs ignores. Is this the case? In other
> >words, WHY would growisofs either not have or not be stopped by this error,
> >while cdrecord is? Recall that cdre
> > But the catch is that undestanding "why" it happens is most likely the
> > key to solution... Why or why recording just hung half-way and most
> > mysteriously failed with "INVALID ADDRESS FOR WRITE" after a long
> > while... Is there a chance that the drive was opened by another program
> > du
> > But the catch is that undestanding "why" it happens is most likely the
> > key to solution... Why or why recording just hung half-way and most
> > mysteriously failed with "INVALID ADDRESS FOR WRITE" after a long
> > while... Is there a chance that the drive was opened by another program
> > du
> >>[..snip..]
> >>
> >>2509078528/3691623424 (68.0%) @0.0x, remaining 14:45
> >>...
> >>2509078528/3691623424 (68.0%) @0.0x, remaining 14:53
> >>:-[ [EMAIL PROTECTED] failed with SK=5h/ASC=21h/ACQ=02h]: Invalid argument
> >>builtin_dd: 1225136*2KB out
> >>:-( write failed: Invalid argument
The li
> I had a Sony DRU-510A DCD+/-RW drive on SuSE 9.0, and it worked
> fine, until it died. I replaced it with a TDK indiDV+/-RW 440N drive,
> and now I can't burn DVD+R disc.
>
> growisofs -dvd-compat -Z /dev/sr0=/home/user/tmp/temp.iso
> Executing 'builtin_dd if=/home/user/tmp/temp.iso of=/dev/sr0
> >>[..snip..]
> >>
> >>2509078528/3691623424 (68.0%) @0.0x, remaining 14:45
> >>...
> >>2509078528/3691623424 (68.0%) @0.0x, remaining 14:53
> >>:-[ [EMAIL PROTECTED] failed with SK=5h/ASC=21h/ACQ=02h]: Invalid argument
> >>builtin_dd: 1225136*2KB out
> >>:-( write failed: Invalid argument
The li
> I had a Sony DRU-510A DCD+/-RW drive on SuSE 9.0, and it worked
> fine, until it died. I replaced it with a TDK indiDV+/-RW 440N drive,
> and now I can't burn DVD+R disc.
>
> growisofs -dvd-compat -Z /dev/sr0=/home/user/tmp/temp.iso
> Executing 'builtin_dd if=/home/user/tmp/temp.iso of=/dev/sr0
dvd+rw-tools 5.17.4.8.6 are available for download at usual location,
http://fy.chalmers.se/~appro/linux/DVD+RW/. I strongly recommend this
update for those who deploy 5.14.x through 5.16.x. Most notably this
update resolves problem with growisofs -dvd-compat failing to start
DVD-R[W] recording wit
dvd+rw-tools 5.17.4.8.6 are available for download at usual location,
http://fy.chalmers.se/~appro/linux/DVD+RW/. I strongly recommend this
update for those who deploy 5.14.x through 5.16.x. Most notably this
update resolves problem with growisofs -dvd-compat failing to start
DVD-R[W] recording wit
> One difference is that dmesg doesn't report that
> cdrom_newpc_intr: 32768 residual after xfer. It justs reports
> hdb: DMA timeout retry
> hdb: timeout waiting for DMA
> hdb: status timeout: status=0xd0 { Busy }
> hdb: status timeout: error=0xd0LastFailedSense 0x0d
> hdb: drive not ready for com
> [..snip..]
>
> 2509078528/3691623424 (68.0%) @0.0x, remaining 14:45
> ...
> 2509078528/3691623424 (68.0%) @0.0x, remaining 14:53
> :-[ [EMAIL PROTECTED] failed with SK=5h/ASC=21h/ACQ=02h]: Invalid argument
> builtin_dd: 1225136*2KB out
> :-( write failed: Invalid argument
>
> ~~
> >> >> This is definitely wrong!
> >>
> >> It is obvious that "INVALID ADDRESS FOR WRITE" is a possible
> >> result of a buffer underun.
>
> >Do I have to explain the difference between "buffer overruns" and
> >"buffer underruns?" I wrote "buffer *underruns* are denoted as depicted
> >in originat
> One difference is that dmesg doesn't report that
> cdrom_newpc_intr: 32768 residual after xfer. It justs reports
> hdb: DMA timeout retry
> hdb: timeout waiting for DMA
> hdb: status timeout: status=0xd0 { Busy }
> hdb: status timeout: error=0xd0LastFailedSense 0x0d
> hdb: drive not ready for com
> [..snip..]
>
> 2509078528/3691623424 (68.0%) @0.0x, remaining 14:45
> ...
> 2509078528/3691623424 (68.0%) @0.0x, remaining 14:53
> :-[ [EMAIL PROTECTED] failed with SK=5h/ASC=21h/ACQ=02h]: Invalid argument
> builtin_dd: 1225136*2KB out
> :-( write failed: Invalid argument
>
> ~~
> >> >> This is definitely wrong!
> >>
> >> It is obvious that "INVALID ADDRESS FOR WRITE" is a possible
> >> result of a buffer underun.
>
> >Do I have to explain the difference between "buffer overruns" and
> >"buffer underruns?" I wrote "buffer *underruns* are denoted as depicted
> >in originat
> >> >> from all the tests I've run .. I know it's a buffer overrun.
> >>
> >> >Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
> >> >should be handled by application transparently. *Unhandled* buffer
> >> >underruns in turn *are* denoted as depicted in originating post. How
> >> >> from all the tests I've run .. I know it's a buffer overrun.
> >>
> >> >Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
> >> >should be handled by application transparently. *Unhandled* buffer
> >> >underruns in turn *are* denoted as depicted in originating post. How
> >> from all the tests I've run .. I know it's a buffer overrun.
>
> >Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
> >should be handled by application transparently. *Unhandled* buffer
> >underruns in turn *are* denoted as depicted in originating post. How do
> >you com
> ust wanted to tell you that after putting a 80-wire cable, and making my
> DVD writer slave from master, now I get the following messages...
>
> Kernel:
> hdb: DMA timeout retry
> hdb: timeout waiting for DMA
> hdb: status timeout: status=0xd0 { Busy }
> hdb: status timeout: error=0xd0LastFailed
> from all the tests I've run .. I know it's a buffer overrun.
Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
should be handled by application transparently. *Unhandled* buffer
underruns in turn *are* denoted as depicted in originating post. How do
you come to the conclusi
> >> from all the tests I've run .. I know it's a buffer overrun.
>
> >Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
> >should be handled by application transparently. *Unhandled* buffer
> >underruns in turn *are* denoted as depicted in originating post. How do
> >you com
> ust wanted to tell you that after putting a 80-wire cable, and making my
> DVD writer slave from master, now I get the following messages...
>
> Kernel:
> hdb: DMA timeout retry
> hdb: timeout waiting for DMA
> hdb: status timeout: status=0xd0 { Busy }
> hdb: status timeout: error=0xd0LastFailed
> from all the tests I've run .. I know it's a buffer overrun.
Buffer overruns are *not* denoted with "INVALID ADDRESS FOR WRITE," and
should be handled by application transparently. *Unhandled* buffer
underruns in turn *are* denoted as depicted in originating post. How do
you come to the conclusi
> >> I have a Plextor PX-708UF (USB 2.0) on a Red Hat Linux 9 machine.
> >>
> >> cdrecord.prodvd: Input/output error. read disk info: scsi sendcmd: no error
> >> CDB: 51 00 00 00 00 00 00 00 24 00
> >^^ I don't know if following holds true
> >for other USB implement
> >The media is 4x DVD+R from Memorex. This is not an inherent problem
> >with the drive or media, since I can burn the same iso with growisofs.
>
> If something is caused by buggy software outside the application,
> then in many cases it may also work just by luck.
Size of the disc information
> >Pass-through SG_IO (interface is question) is not specific to /dev/hd*.
> >In other words it's not an "/dev/hd* interface" or an IDE-specific hack,
>
> If you previously did write correct code for the Linux /dev/sg* interface, you
> should know better.
>
> The fact that the interfaces share a
> >> I have a Plextor PX-708UF (USB 2.0) on a Red Hat Linux 9 machine.
> >>
> >> cdrecord.prodvd: Input/output error. read disk info: scsi sendcmd: no error
> >> CDB: 51 00 00 00 00 00 00 00 24 00
> >^^ I don't know if following holds true
> >for other USB implement
> >The media is 4x DVD+R from Memorex. This is not an inherent problem
> >with the drive or media, since I can burn the same iso with growisofs.
>
> If something is caused by buggy software outside the application,
> then in many cases it may also work just by luck.
Size of the disc information
> >Pass-through SG_IO (interface is question) is not specific to /dev/hd*.
> >In other words it's not an "/dev/hd* interface" or an IDE-specific hack,
>
> If you previously did write correct code for the Linux /dev/sg* interface, you
> should know better.
>
> The fact that the interfaces share a
> - Try to support the half hearted and badly designed /dev/hd* interface
> from Linux-2.6 in a more usable way.
>
> Note: The Bus mapping function inside the kernel for this interface is
> a dummy. For this reason, we need to do the mapping ourself.
> Busnumm
> OS: Solaris 9, x386
> cdrecord version: cd-record-prodvd-2.01a12-i386-pc-solaris2.9
> DVD Model: Sony DRU-510A
>
> When I try to burn a DVD (using DVD-R media this is the results I get ...
>
> Starting to write CD/DVD at speed 2 in real TAO mode for single
> - Try to support the half hearted and badly designed /dev/hd* interface
> from Linux-2.6 in a more usable way.
>
> Note: The Bus mapping function inside the kernel for this interface is
> a dummy. For this reason, we need to do the mapping ourself.
> Busnumm
> I have a Plextor PX-708UF (USB 2.0) on a Red Hat Linux 9 machine.
>
> cdrecord.prodvd: Input/output error. read disk info: scsi sendcmd: no error
> CDB: 51 00 00 00 00 00 00 00 24 00
^^ I don't know if following holds true
for other USB implementations, but Linux
> OS: Solaris 9, x386
> cdrecord version: cd-record-prodvd-2.01a12-i386-pc-solaris2.9
> DVD Model: Sony DRU-510A
>
> When I try to burn a DVD (using DVD-R media this is the results I get ...
>
> Starting to write CD/DVD at speed 2 in real TAO mode for single
> I have a Plextor PX-708UF (USB 2.0) on a Red Hat Linux 9 machine.
>
> cdrecord.prodvd: Input/output error. read disk info: scsi sendcmd: no error
> CDB: 51 00 00 00 00 00 00 00 24 00
^^ I don't know if following holds true
for other USB implementations, but Linux
> >For this
> >reason I'd like to collect new(!see the above link!) dvd+rw-mediainfo
> >outputs from NEC, SONY, Plextor and Lite-on, optionally BTC and Optorite
> >units with high-speed (faster than 1x) DVD-R media in.
>
> By 'DVD-R' you really mean 'DVD-R' and not 'writeable DVD in general'?
Wel
> >For this
> >reason I'd like to collect new(!see the above link!) dvd+rw-mediainfo
> >outputs from NEC, SONY, Plextor and Lite-on, optionally BTC and Optorite
> >units with high-speed (faster than 1x) DVD-R media in.
>
> By 'DVD-R' you really mean 'DVD-R' and not 'writeable DVD in general'?
Wel
> ... burn a DVD+RW with a movie, which I want to view on
> my TV with an XBOX as the DVD player.
> I used a win program called "Shrink DVD" to create the files, and then
> used "growisofs -dvd-compat -Z /dev/dvd -dvd-video /tmp/a2", and there
> where no error reports. "2286300 extents written (446
> I have discovered that dvd+rw-tools (which I use through k3b) that I
> have the possibility to write the discs in restricted overwrite format.
> I'm not a technical guy and someone adviced it to me as a replacement
> for udf. What are the similarities and the differences between both?
The advice
> >...if one would project SCSI-3 on ISO 7 layer networking
> >model and put command block at transport layer, LUN addressing would end
> >up at network, if not link layer.
>
> True for good old SCSI, not true for ATAPI drives.
??? I don't understand the point with this remark... Do you suggest t
> ... burn a DVD+RW with a movie, which I want to view on
> my TV with an XBOX as the DVD player.
> I used a win program called "Shrink DVD" to create the files, and then
> used "growisofs -dvd-compat -Z /dev/dvd -dvd-video /tmp/a2", and there
> where no error reports. "2286300 extents written (446
> I have discovered that dvd+rw-tools (which I use through k3b) that I
> have the possibility to write the discs in restricted overwrite format.
> I'm not a technical guy and someone adviced it to me as a replacement
> for udf. What are the similarities and the differences between both?
The advice
> >...if one would project SCSI-3 on ISO 7 layer networking
> >model and put command block at transport layer, LUN addressing would end
> >up at network, if not link layer.
>
> True for good old SCSI, not true for ATAPI drives.
??? I don't understand the point with this remark... Do you suggest t
As you might have noticed there were few reports about growisofs 5.16
failing to start DVD-R recording with "COMMAND SEQUENCE ERROR" message
in some units. The problem seems to be intermittent, i.e. growisofs
fails only sometimes, and seems to disappear upon reboot. As I fail to
reproduce it, I hav
As you might have noticed there were few reports about growisofs 5.16
failing to start DVD-R recording with "COMMAND SEQUENCE ERROR" message
in some units. The problem seems to be intermittent, i.e. growisofs
fails only sometimes, and seems to disappear upon reboot. As I fail to
reproduce it, I hav
> > >Speaking for cdrecord, the change not really needed as no writer uses
> > >something differnt from lun 0.
> > >
> > Does this mean that if a real SCSI burner is used with a LUN of >0 it
> > doesn't work with your software, or some part of the standard says it
> > must be zero, or you have neve
> > >Speaking for cdrecord, the change not really needed as no writer uses
> > >something differnt from lun 0.
> > >
> > Does this mean that if a real SCSI burner is used with a LUN of >0 it
> > doesn't work with your software, or some part of the standard says it
> > must be zero, or you have neve
> Now I have ruined a couple of DVD+R
What does it mean exactly? As page requires, exact growisofs output and
dvd+rw-mediainfo for resulting/ruined recording.
> GET PERFORMANCE:
> Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED]
> Speed Descriptor#1:00/2295104 [EMAIL PR
> ...using growisofs (5.16) with mkisofs 2.0
>
> growisofs -Z /dev/scd0=xyz.isofine
> growisofs -M /dev/scd0 abc/deffine - a few times
>
> - THEN did another growisofs - everything went fine but
> attempts to access DVD give message 'no media mounted' ?
>
> ---
> If relevant - none of t
> Now I have ruined a couple of DVD+R
What does it mean exactly? As page requires, exact growisofs output and
dvd+rw-mediainfo for resulting/ruined recording.
> GET PERFORMANCE:
> Speed Descriptor#0:00/2295104 [EMAIL PROTECTED] [EMAIL PROTECTED]
> Speed Descriptor#1:00/2295104 [EMAIL PR
> ...using growisofs (5.16) with mkisofs 2.0
>
> growisofs -Z /dev/scd0=xyz.isofine
> growisofs -M /dev/scd0 abc/deffine - a few times
>
> - THEN did another growisofs - everything went fine but
> attempts to access DVD give message 'no media mounted' ?
>
> ---
> If relevant - none of t
> > star -tv < /tmp/cdev.tar.bz2
> > ...
> > 255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev
> >
> > AS you see, this is a tar archive that includes a character
> > special with major 255 and minor 7000.
Postulate. Restoring of device entries from another architecture was
never guarantee
> > star -tv < /tmp/cdev.tar.bz2
> > ...
> > 255 7000 crw-r--r-- 1 root/other Jan 5 22:06 2004 cdev
> >
> > AS you see, this is a tar archive that includes a character
> > special with major 255 and minor 7000.
Postulate. Restoring of device entries from another architecture was
never guarantee
> > > > > > [EMAIL PROTECTED]:/vol/data/dvd> growisofs -dvd-compat -Z
> > > > > > /dev/scd0=myDVD.udf
> > > > > > Executing 'builtin_dd if=myDVD.udf of=/dev/scd0 obs=32k seek=0'
> > > > > > /dev/scd0: "Current Write Speed" is 4.0x1385KBps.
> > > > > > :-! "COMMAND SEQUENCE ERROR(52c00)" at 0h. Is
401 - 500 of 859 matches
Mail list logo
