1 |
Hi, |
2 |
|
3 |
i wrote: |
4 |
> > One big problem is the substantial price of BD-R experiments. |
5 |
|
6 |
Joerg.Schilling@××××××××××××××××.de wrote: |
7 |
> the OP seems to have turned several BD-Rs into coasters already. |
8 |
|
9 |
The OP reports: |
10 |
> > > I compared each and every file on the disk with its original, |
11 |
> > > but yould not find any problem. |
12 |
|
13 |
This matches Andy Polyakov's diagnosis that the media are ok |
14 |
afterwards. |
15 |
The flawless readbility, the timepoint of failure, and the i/o error |
16 |
reported by K3b, alltogether make me believe that it is the 5 year |
17 |
old bug. |
18 |
|
19 |
Of course, everybody has to decide by himself where to invest |
20 |
test media. |
21 |
|
22 |
My proposal is to fix and test growisofs. |
23 |
|
24 |
|
25 |
--------------------------------------------------------------------- |
26 |
(Joerg and i know each other from many encounters in the past. |
27 |
We do not necessarily agree on technical questions. My apologies for |
28 |
getting off the original topic now.) |
29 |
|
30 |
Joerg.Schilling@××××××××××××××××.de wrote: |
31 |
> Many people reported problems even with writing DVDs using growisofs that |
32 |
> went away after upgrading to cdrtools. |
33 |
|
34 |
"With some fantasy you can see the weirdest things in the mist." |
35 |
(Franquin via Gaston Lagaffe) |
36 |
|
37 |
It is not impossible that a drive refuses on one way of burn |
38 |
preparation while still working with a different one. |
39 |
One might get lucky with the defaults of one burn program and |
40 |
experience failure with those of the other burn program. |
41 |
But normally a drive is on the edge of failure if it behaves |
42 |
that way. The luck may turn quite quickly then. |
43 |
|
44 |
|
45 |
Joerg.Schilling@××××××××××××××××.de wrote: |
46 |
> Note that I already mentioned that growisofs is a layzy written program |
47 |
|
48 |
I would compare its style rather to BASIC than to assembler. :)) |
49 |
But that does not influence its SCSI standards compliance. |
50 |
|
51 |
|
52 |
Joerg.Schilling@××××××××××××××××.de wrote: |
53 |
> has many places where is returns the unly slightly modified result of a SCSI |
54 |
> mode sense operation while running a SCSI mode select operation. As it only |
55 |
> slightly modifies the received data instead of constructing SCSI standard |
56 |
> compliant data, these mode select operations do not always have the desired |
57 |
> effect. |
58 |
|
59 |
How else should one learn the current settings in order _not_ |
60 |
to change those which are non-changeable ? |
61 |
|
62 |
In the source files of growisofs i can spot only one occasion |
63 |
of MODE SELECT. This is in transport.hxx where Andy composes |
64 |
a mode page 05 for DVD-R[W]. |
65 |
|
66 |
I read in SPC-3 6.9.3 that the drive shall throw error if one |
67 |
attempts to change a non-changeable value. But not that the drive |
68 |
is allowed to return values which may cause error if sent back |
69 |
to the drive. |
70 |
|
71 |
So if the code of transport.hxx is wrong, then not because it |
72 |
would send back values which it got from the drive, but because |
73 |
it does not inquire by PC=01b whether its self-constructed values |
74 |
are allowed to be changed. |
75 |
(I don't do this either. It is worth consideration, though.) |
76 |
|
77 |
|
78 |
Joerg.Schilling@××××××××××××××××.de wrote: |
79 |
> This kind of problems is independent from the media type |
80 |
|
81 |
Mode page 05 is only appropriate for CD and DVD-R[W]. |
82 |
(MMC-5 7.5.2, 7.5.3) |
83 |
So this problem is highly dependent on the media type. |
84 |
|
85 |
|
86 |
Have a nice day :) |
87 |
|
88 |
Thomas |