Hi,
> Will dvd+rw-mediainfo work on solaris 10 (sparc) ?
Afaik, it works on Solaris.
In growisofs.c i read:
* 5.6:
...
* - Solaris 2.x support is merged, it's volume manager aware, i.e.
* you can run it with or without volume manager;
(5.6 is several years old. Current is 7.1.)
> if not
Hi,
i uploaded
http://scdbackup.webframe.org/xorriso-0.4.3.tar.gz
which performs the new option -pvd_info.
xorriso -version should report "Version timestamp"
2009.10.05.190215 or newer.
Try
xorriso -indev ...device... -pvd_info 2>/dev/null
-
Thomas, thank you for suggesting dvd+rw-tools-7.1
Will dvd+rw-mediainfo work on solaris 10 (sparc) ?
I am definitely interested in the capabilities of growisofs.
Hope to try it soon - if not solaris, then on linux.
> Do you get a different -minfo output from a BD-R
> which never was involved in a
Jörg, thank you for answering the formatting question.
Note that my blu-ray drive is connected to my system via USB 2.0
I do not understand why DMA settings may be a problem for cdrecord.
With cdrecord I can write to DVD (Plextor PX-716UF) over USB 2.0
Memorex (actually RITEK) is definitely not t
These look good.
> Note the subtle differences between -toc line
> Volume id: '...'
> and -pvd_info line
> Volume Id: ...
>
> Would you prefer quoted output in -pvd_info ?
For the sake of programmatic use, the known delimiters of colon-space
and newline (or whatever) serves as implicit
Hi,
libisofs does already provide all PVD components
which you requested. So it was easy to implement
a sketch of -pvd_info.
See some examples from my test runs.
Comments and change wishes are appreciated.
-
Drive current: -indev '/dev/sr1'
PVD add
Hi,
> growisofs's CD001
That's actually mkisofs's "CD001".
growisofs -M examines media TOC resp. the
ECMA-119 PVD in order to get the parameters
for a run of mkisofs -C . growisofs then
starts mkisofs and writes its output to the
media. In case of overwriteable media it
finally copies the Volume
> xorriso does not rely on ECMA-168 but on ECMA-119
> plus some SUSP based extensions like Rock Ridge.
> Afaik the mkisofs runs of growisofs do not refer
> to ECMA-168 either.
Yes, today I perused ECMA-168 and realized it specifies a form of
layout different than what my burnt discs conform to (i.
Hi,
> The explanation for why
> volname returned "CDROM" is that is apparently the default volume
> label when none is specified (which wasn't in the first session). I
> specified "volly" on a later session but volname and vol_id (which
> someone else suggested) appear to not be multi-session awar
9 matches
Mail list logo