Re: Test results growisofs + BTC 1004
> Test 1, mediainfo:
> INQUIRY: [DVDRW ][IDE1004 ][0048]
> MODE SENSE[#3Fh]:
Verbose dvd+rw-mediainfo outputs mostly serve debugging purposes and
therefore should be provided upon explicit demand only. I mean in most
cases [this one included] it only makes harder to grasp the problem:-)
To summarize:
DVD+RW 2223149(*) blocks 2x OK
DVD-R 2223152 blocks 4x OK
DVD-R 2271680 blocks 4x coaster(**)
DVD-R 2271680 blocks 4x accessible in recorder only
(*) all sizes are collected from "Fabricated TOC."
(**) but you could collect dvd+rw-mediainfo output?
So you get varying results with your DVD-R media... That's how it might
look like if your media is poorly supported by firmware... But "MCC
01RG20" seems to be Verbatim brand (just feed the string in quotes to
google), which means that you probably have all rights to expect that
it's properly supported... Yet note that there actually were reports
about bad Verbatim spindle batches, which Verbatim was just exchanging
without asking too much questions. So talk to your media vendor.
Secondly, it also might be that your particular unit is simply
defective. I would suggest to a) check for firmware update, b) test
couple of other brands and if problem with varying recording results
persists, exchange your unit or return it for rebate.
Oh! Also try to lower recording speed with -speed=1. Might help to
mitigate both factors, deficient hardware and bad media that is...
> 3) The burned DVD-Rs are appendable, but I used -dvd-compat option!
Well, this's most likely firmware deficiency. Note that there were other
reports about BTC unit producing malformed DVD-R recordings (see BTC
paragraph at http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html). Even
though you run elder unit and firmware you might have to complement your
command line with -use-the-force-luke=dao as well. Well, given that
cdrecord-ProDVD [which unconditionally applies DAO procedure] failed,
growisofs will most likely fail to reserve track as well... I don't
know...
> 4) Window$ people with same drive, same firmware, same media, don't have
> this problem
But it's not *your* drive and not *your* media:-) A.
Reply to: