Dave Platt [EMAIL PROTECTED] wrote:
The problem is that they have called wodim cdrecord and provided (or
in some cases not) different functionality. Obviously distributions
thought people wouldn't use it if people knew it was another program. I
feel the same way as I do when I order
Joerg Schilling wrote:
Dave Platt [EMAIL PROTECTED] wrote:
The problem is that they have called wodim cdrecord and provided (or
in some cases not) different functionality. Obviously distributions
thought people wouldn't use it if people knew it was another program. I
feel the same way as
Thomas Schmitt wrote:
Hi,
Andy Polyakov wrote:
Could you explain why writing a new program should
help to fix the hostile habbit of some Linux kernel
developers?
I see this as a more complex system of animosity.
To exchange one component might change that
system completely.
But
The problem is that they have called wodim cdrecord and provided (or
in some cases not) different functionality. Obviously distributions
thought people wouldn't use it if people knew it was another program. I
feel the same way as I do when I order coke and get pepsi, it's a scam.
I can't
mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD
2086912 blocks = 4076 MiB
Track 01: 4075 of 8124 MB written (fifo 99%) [buf 99%] 8.2x.cdrecord:
faio_wait_on_buffer for writer timed out.
cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 1F
Thomas Schmitt [EMAIL PROTECTED] wrote:
The 1F in CDB means 31 blocks are to be written
by this WRITE10 command.
The 1F D7 E9 means write address is 2086889.
(Confirmed by: 4273948672 / 2048 == 2086889)
The write size of 31 blocks seems systematic:
2086889 % 31 == 0
The man page of
Hi,
Andy Polyakov wrote:
The unit in question [Gregoire's] obviously crashes (power cycle is
required to bring it back, i.e. reboot of unit) if write request crosses
layer break position.
It sounds as if their [Rob's and CJ's]
units can't handle arbitrary layer break positions and has to be
Hi,
_all_ other OS forbid to send SCSI commands
from a normal user account.
There are obviously workarounds for that restriction.
As soon as the demand occurs i will try to learn.
In worst case i would propose some client-server
architecture.
Another approach would be to create a new
So the current consolidated theory would be
about like this:
-
Problem number 1:
-
Problem number 2:
-
Problem number 3:
-
Agreed.
Let me add another growisofs problem report which
i got from a scdbackup user:
With DVD+R DL, growisofs seems to read the
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
Cdrskin in addition is based on a library that
is based on specific security holes in Linux.
Could you describe those holes ?
I mentioned already: _all_ other OS forbid to send SCSI commands
from a normal user account. The only exception is
Hi,
Question
is if above is actually complete growisofs command line?
It comes out of a wrapper script that converts
cdrecord options into runs of dvd+rw-tools.
The write command is supposed to be:
growisofs \
-use-the-force-luke \
-use-the-force-luke=bufsize:16m \
Gregoire Favre [EMAIL PROTECTED] wrote:
Hello,
I have tried with
mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD
tsize=$SIZEs -
Which I am not sure of the syntax... I don't fully understand cdrecord
man page.
Unfortunately :
Track 01: 4041 of 8124 MB written
Question
is if above is actually complete growisofs command line?
It comes out of a wrapper script that converts
cdrecord options into runs of dvd+rw-tools.
The write command is supposed to be:
growisofs \
-use-the-force-luke \
-use-the-force-luke=bufsize:16m \
Hi,
Andy Polyakov wrote:
Question
is if above is actually complete growisofs command line?
Very good question, indeed.
Somehow -dvd-compat sneaked into the growisofs_wrapper
of scdbackup since i made the last round of media
tests.
The command line is most probably this:
growisofs
Question
is if above is actually complete growisofs command line?
Very good question, indeed.
Somehow -dvd-compat sneaked into the growisofs_wrapper
of scdbackup since i made the last round of media
tests.
The command line is most probably this:
growisofs -use-the-force-luke \
Thomas Schmitt wrote:
Problem number 1:
Rob and CJ have drives which do not like any
other layer break address than the one which
is their default.
...
(This would mean that cdrskin has no problem
with those drives. I would appreciate
confirmation.)
Yeah, no problem. I'm heading out for
-
Problem number 1:
Rob and CJ have drives which do not like any
other layer break address than the one which
is their default.
Thus growisofs and cdrecord fail if their
automatically computed layer breaks get set.
The remedy is to enforce the drive's default
layer break address and
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
_all_ other OS forbid to send SCSI commands
from a normal user account.
There are obviously workarounds for that restriction.
As soon as the demand occurs i will try to learn.
In worst case i would propose some client-server
architecture.
Thomas Schmitt [EMAIL PROTECTED] wrote:
It is most likely a combination od 2 and 3.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL:
Hi,
Andy Polyakov wrote:
[-dvd-compat] will still allow you to pad DVD+R,
DVD-R Incremental, even DVD-R DL recordings,
not to mention rewritables..
Yeah. That's why this development glitch could
stay undetected for quite a while.
It is harmless if the image comes from a regular
disk file, i
[-dvd-compat] will still allow you to pad DVD+R,
DVD-R Incremental, even DVD-R DL recordings,
not to mention rewritables..
Yeah. That's why this development glitch could
stay undetected for quite a while.
It is harmless if the image comes from a regular
disk file, i understand from reading your
Thomas Schmitt [EMAIL PROTECTED] wrote:
Could you explain why writing a new program should
help to fix the hostile habbit of some Linux kernel
developers?
I see this as a more complex system of animosity.
To exchange one component might change that
system completely.
But for now, the
On Fri, May 16, 2008 at 03:34:52PM +0200, Joerg Schilling wrote:
I'll write a fix for cdrecord soon, tghen he may try again ;-)
Oh great :-)
I am quiete used to cdrecord which I would be pleased to be able to use
for DVD+R DL also !
Thank.
--
Grégoire FAVRE
Hi,
i wrote:
the official Linux world rather settled with wodim.
Joerg Schilling wrote:
They will stop doing this stupid move after they realized that
this move did create them dozens of unfixed bugs and that there is no
maintanance for wodim.
What maintenance would it need for its
core
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
i wrote:
the official Linux world rather settled with wodim.
Joerg Schilling wrote:
They will stop doing this stupid move after they realized that
this move did create them dozens of unfixed bugs and that there is no
maintanance for wodim.
Hello,
just burned a DVD+R DL with a little script (included) which fails with:
97.77% done, estimate finish Thu May 15 10:21:30 2008
97.89% done, estimate finish Thu May 15 10:21:30 2008
:-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error
:-( write failed: Input/output
Gregoire Favre [EMAIL PROTECTED] wrote:
Hello,
just burned a DVD+R DL with a little script (included) which fails with:
97.77% done, estimate finish Thu May 15 10:21:30 2008
97.89% done, estimate finish Thu May 15 10:21:30 2008
:-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]:
On Thu, May 15, 2008 at 03:04:13PM +0200, Joerg Schilling wrote:
You did not use cdrecord here. Cdrecord would print a more readable/complere
error message. This is most likely growisofs.
Yes and no : cdrecord just freeze itself and afterthat I don't get my
burner again... I have to power down
Hi,
97.89% done, estimate finish Thu May 15 10:21:30 2008
:-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error
What does that mean ?
The drive responded to the computer and told it
that writing to the given sector failed.
This would normally be a case of poor drive-media
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
Hello :-)
If you do extensive experiments and comparisons then
i would like to submit to the competition my own program
cdrskin in version 0.4.4 or later. (Earlier won't do DL)
I don't think that it (or Nero) is better
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
If you do extensive experiments and comparisons then
i would like to submit to the competition my own program
cdrskin in version 0.4.4 or later. (Earlier won't do DL)
OK, just copied cdskin to my path and tried a burn with the
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
By the way, I got :
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res
Gregoire Favre [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
Hello :-)
If you do extensive experiments and comparisons then
i would like to submit to the competition my own program
cdrskin in version 0.4.4 or later. (Earlier won't do DL)
I
Gregoire Favre [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
If you do extensive experiments and comparisons then
i would like to submit to the competition my own program
cdrskin in version 0.4.4 or later. (Earlier won't do DL)
OK, just copied
On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote:
I asume that cdrecord works also?
If you speak about single layer DVD, yes, cdrecord works just perfectly
:-)
But if we speak about DVD+R DL no it has the same behaviour than
cdrskin.
--
Grégoire FAVRE
Hi,
I would like to just try to burn one big file into a DVD+R DL (about
8Gb), what command using cdrskin would you recommend ?
In general it should work on DVD with the
same options as cdrecord accepts for DVD
and some options known from cdrecord with
CD.
Well, meanwhile you found out
Hi,
Cdrskin in addition is based on a library that
is based on specific security holes in Linux.
Could you describe those holes ?
Porting it to other platforms will result in insufficient
privilleges for sending SCSI commands
So you can predict properties of future
software with yet
Gregoire Favre [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote:
I asume that cdrecord works also?
If you speak about single layer DVD, yes, cdrecord works just perfectly
:-)
But if we speak about DVD+R DL no it has the same behaviour than
Joerg Schilling wrote:
Gregoire Favre [EMAIL PROTECTED] wrote:
On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote:
I asume that cdrecord works also?
If you speak about single layer DVD, yes, cdrecord works just perfectly
:-)
But if we speak about DVD+R DL no it
Thomas Schmitt wrote:
Hi,
I would like to just try to burn one big file into a DVD+R DL (about
8Gb), what command using cdrskin would you recommend ?
In general it should work on DVD with the
same options as cdrecord accepts for DVD
and some options known from cdrecord with
CD.
Well,
On Thu, May 15, 2008 at 03:24:17PM -0400, Rob Bogus wrote:
If you get a write error, this is an incompatibility of the drive and the
medium.
That is likely to be true, but I was able to avoid this behavior with
manual layer break.
Maybe it's what nero does ?
Could you tell us how you
Rob Bogus wrote:
Is it intended that butning an 8.2GB image would just work? I tried the
current versions of various software (va36 of cdrecord, I believe) and none
worked without specifying a break.
Hello - FWIW, it seems like we may have run up against the same thing.
I started a thread a
Hi,
I suspect that layer break is a (the?) cause here,
It is the natural suspect indeed.
But the traces do not really point to it.
so I assumed that the break didn't happen
by itself, even with a single large ISO image.
I have three DVD+R DL user reports so far:
Two say that burning DVD+R
Hello,
is there something that could be learnt from 6/6 sucesses when using
nero ? (I use md5sum to test result if someone know a faster way, I am
interested...).
With growisofs, it was alsmost complete, cdrskin and cdrecord seemed to
be able to wrote only half of my file.
Maybe I should retry
Hello,
I have tried with
mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD
tsize=$SIZEs -
Which I am not sure of the syntax... I don't fully understand cdrecord
man page.
Unfortunately :
Track 01: 4041 of 8124 MB written (fifo 100%) [buf 99%] 8.4x. 61.66% done,
estimate
Hi,
is there something that could be learnt from 6/6 sucesses
Probably yes.
I will re-read the specs about the layer break
and any variation which could be tried with
DVD+R DL.
With growisofs, it was alsmost complete, cdrskin and cdrecord seemed to
be able to wrote only half of my file.
46 matches
Mail list logo
