More hunt for "allow to"
This commit is contained in:
parent
df52e79df6
commit
0dd3ff606c
49
README
49
README
@ -174,8 +174,8 @@ The project components (list subject to growth, hopefully):
|
||||
content.
|
||||
|
||||
- libisoburn is an add-on to libburn and libisofs which coordinates both and
|
||||
also allows to grow ISO-9660 filesystem images on multi-session
|
||||
media as well as on overwriteable media via the same API.
|
||||
also can grow ISO-9660 filesystem images on multi-session media
|
||||
as well as on overwriteable media via the same API.
|
||||
All media peculiarities are handled automatically.
|
||||
It also contains the methods of command oriented application
|
||||
xorriso and offers them via a C language API.
|
||||
@ -355,7 +355,7 @@ Project history as far as known to me:
|
||||
- 27th Apr 2008 libisofs-0.6.4 can now read data file content from images
|
||||
and can map pieces of disk files onto image files. Image directory iteration
|
||||
has been enhanced. Input data streams and extended information have been
|
||||
exposed in the API to allow future development.
|
||||
exposed in the API to enable future development.
|
||||
|
||||
- 29th Apr 2008 libisoburn-0.1.4 was made more efficient with reading of
|
||||
image tree nodes. It now depends on libisofs-0.6.4 and libburn-0.4.4.
|
||||
@ -369,7 +369,8 @@ Project history as far as known to me:
|
||||
type with automatic media state recognition.
|
||||
|
||||
- 17th May 2008 an old bug with DVD-RAM and now with BD-RE is fixed by
|
||||
libburn-0.4.8 to allow libisoburn emulation of multisession on those media.
|
||||
libburn-0.4.8. So libisoburn can now perform emulation of multisession
|
||||
on those media.
|
||||
|
||||
- 19th May 2008 libisoburn-0.1.6 brings better table-of-content emulation
|
||||
on overwriteble media and disk files.
|
||||
@ -394,8 +395,8 @@ Project history as far as known to me:
|
||||
- 24th Aug 2008 libisoburn/xorriso-0.2.4 introduces a media readability check
|
||||
with data retrieval option.
|
||||
|
||||
- 18th Sep 2008 libisofs-0.6.8 supports ISO 9660 Level 3 which allows very
|
||||
large data files in the image.
|
||||
- 18th Sep 2008 libisofs-0.6.8 supports ISO 9660 Level 3 which can represent
|
||||
very large data files in the image.
|
||||
|
||||
- 20th Sep 2008 libisoburn/xorriso-0.2.6 takes into respect the new Level 3
|
||||
capabilities of libisofs.
|
||||
@ -413,7 +414,7 @@ Project history as far as known to me:
|
||||
of an aborted burn run.
|
||||
|
||||
- 26th Nov 2008 libisofs-0.6.12 can produce a ISOLINUX isohybrid MBR on the fly
|
||||
and allows to produce ISO images which resemble old mkisofs images.
|
||||
and can produce ISO images which resemble old mkisofs images.
|
||||
|
||||
- 2nd Dec 2008 libisoburn-0.3.0. xorriso now is ready for exotic character
|
||||
sets, for legacy FreeBSD systems which expect an outdated Rock Ridge
|
||||
@ -425,7 +426,7 @@ Project history as far as known to me:
|
||||
|
||||
- 9th Dec 2008 Our project received a donation from Thomas Weber.
|
||||
|
||||
- 2nd Jan 2009 libburn-0.6.0 allows to format BD-R and to write to either
|
||||
- 2nd Jan 2009 libburn-0.6.0 learned to format BD-R and write to either
|
||||
formatted or unformatted BD-R.
|
||||
|
||||
- 6th Jan 2009 libisoburn-0.3.2. xorriso can produce and execute commands for
|
||||
@ -448,15 +449,16 @@ Project history as far as known to me:
|
||||
|
||||
- 13 Mar 2009 libburn-0.6.4 got a dummy adapter for SCSI/MMC command transport.
|
||||
It will show no drives and thus libburn will only be able to perform
|
||||
operations on "stdio:" pseudo drives. Nevertheless this allowed to lift the
|
||||
ban to build libburn on operating systems other than Linux and FreeBSD.
|
||||
operations on "stdio:" pseudo drives. Nevertheless this was precondition
|
||||
to lift the ban to build libburn on operating systems other than Linux
|
||||
and FreeBSD.
|
||||
|
||||
- 16 Mar 2009 libisoburn-0.3.6: xorriso uses RRIP version 1.10 as default
|
||||
in order to be mountable where mkisofs images are mountable.
|
||||
|
||||
- 17 Apr 2009 libisofs-0.6.18 introduces content filtering of data files.
|
||||
Built-in filters allow compression to formats gzip and zisofs. External
|
||||
filter processes allow arbitrary data conversions like encryption.
|
||||
Built-in filters implement compression to formats gzip and zisofs. External
|
||||
filter processes can perform arbitrary data conversions like encryption.
|
||||
|
||||
- 19 Apr 2009 libisoburn-0.3.8 makes use of the new libisofs capability to
|
||||
perform content filtering of data files.
|
||||
@ -481,10 +483,10 @@ Project history as far as known to me:
|
||||
Affected are releases since libisoburn-0.3.2 in january 2009.
|
||||
|
||||
- 25 Aug 2009 libisofs-0.6.22 can record MD5 checksums for the whole session
|
||||
and for each single data file. Checksum tags allow to verify superblock and
|
||||
directory tree before importing them.
|
||||
and for each single data file. Checksum tags can be used to verify superblock
|
||||
and directory tree before importing them.
|
||||
|
||||
- 27 Aug 2009 libburn-0.7.0 allows to calm down a drive and to inquire its
|
||||
- 27 Aug 2009 libburn-0.7.0 learned to calm down a drive and to inquire its
|
||||
supported profiles. It works around some pitfalls with U3 enhanced memory
|
||||
sticks which emulate a CD-ROM.
|
||||
|
||||
@ -518,7 +520,7 @@ Project history as far as known to me:
|
||||
provides throughput enhancements with hampered busses on Linux, and new
|
||||
API calls to log SCSI commands and to control the libburn fifo.
|
||||
|
||||
- 09 Dec 2009 libisoburn-0.4.6 allows performance tuning of output to DVD
|
||||
- 09 Dec 2009 libisoburn-0.4.6 now offers performance tuning of output to DVD
|
||||
drives or disk files.
|
||||
|
||||
- 26 Dec 2009 libburn-0.7.4.pl01 fixes the release tarball which was lacking
|
||||
@ -531,7 +533,7 @@ Project history as far as known to me:
|
||||
portability.
|
||||
|
||||
- 22 Jan 2010 libburn-0.7.6 has an improved system adapter for FreeBSD,
|
||||
fixes bugs about the generic X/Open system adapter, and allows to use
|
||||
fixes bugs about the generic X/Open system adapter, and can use
|
||||
libcdio >= 0.83 as SCSI transport facility.
|
||||
|
||||
- 10 Feb 2010 libisofs-0.6.28 fixes a regression about bootable images which
|
||||
@ -553,7 +555,8 @@ Project history as far as known to me:
|
||||
|
||||
- 03 May 2010 Version 0.6.32 of libisofs is able to create ISO images with
|
||||
multiple boot images. All boot catalog parameters described in El-Torito
|
||||
specs can be set and inquired. This allows to use GRUB boot images for EFI.
|
||||
specs can be set and inquired. This was needed to use GRUB boot images
|
||||
for EFI.
|
||||
|
||||
- 04 May 2010 Release 0.5.6.pl00 of libisoburn makes use of the new libisofs
|
||||
capabilities about boot images.
|
||||
@ -607,11 +610,11 @@ Project history as far as known to me:
|
||||
- Mon Jan 17 2011 we go for release 1.0.0. This does not indicate a
|
||||
technological overhaul but shall emphasize the maturity of the software.
|
||||
libisofs-1.0.0 fixes a bug about the length of ECMA-119 directory names and
|
||||
is ready to allow untranslated ECMA-119 names (violating the specs).
|
||||
libburn-1.0.0.pl00 allows umask to create stdio-drive files with
|
||||
rw-permissions for all. cdrskin now refuses to burn if the foreseeable size
|
||||
exceeds media capacity
|
||||
libisoburn-1.0.0.pl00 allows to create an ISO 9660:1999 directory tree,
|
||||
is ready to store untranslated ECMA-119 names (violating the specs).
|
||||
libburn-1.0.0.pl00 is now willing to create stdio-drive files with
|
||||
rw-permissions for all, if umask really asks for it. cdrskin now refuses
|
||||
to burn if the foreseeable size exceeds media capacity
|
||||
libisoburn-1.0.0.pl00 can now create an ISO 9660:1999 directory tree,
|
||||
improved the emulation fidelity of command -as mkisofs, lowered the default
|
||||
abort threshold for xorriso batch mode, and increased that threshold for
|
||||
xorriso dialog mode.
|
||||
|
||||
@ -128,10 +128,10 @@ the archivers afio and star. Not suitable seems GNU tar.
|
||||
.br
|
||||
In general there are two approaches for writing media:
|
||||
.br
|
||||
A permissive mode depicted by option
|
||||
A permissive mode selected by option
|
||||
.B -tao
|
||||
which needs no predicted track size and is able to make use of
|
||||
eventual multi-session capabilities.
|
||||
which needs no predicted track size and can use
|
||||
multi-session capabilities if offered by drive and medium.
|
||||
.br
|
||||
A more restrictive mode
|
||||
.B -sao
|
||||
@ -156,7 +156,7 @@ read-only. Closing is done automatically unless option
|
||||
is given which keeps the media appendable.
|
||||
.br
|
||||
Write mode
|
||||
-tao s able to use track sources of unpredictable length (like stdin) and
|
||||
-tao is able to use track sources of unpredictable length (like stdin) and
|
||||
to write further sessions to appendable media.
|
||||
-sao produces audio sessions with seamless tracks but needs predicted track
|
||||
sizes and cannot append sessions to media.
|
||||
|
||||
@ -39,8 +39,8 @@ About any CD, DVD, or BD recorder produced in the recent ten years.
|
||||
<BR>
|
||||
<A HREF="http://libburnia-project.org">libburn</A>
|
||||
supports recorders which are compliant to standards MMC-1 for CD and
|
||||
MMC-5 for DVD or BD. Linux, FreeBSD, Solaris, and NetBSD allow to access drives
|
||||
connected via SCSI, PATA (aka IDE, ATA), USB, or SATA.
|
||||
MMC-5 for DVD or BD. Linux, FreeBSD, Solaris, and NetBSD can communicate
|
||||
with drives connected via SCSI, PATA (aka IDE, ATA), USB, or SATA.
|
||||
<BR>
|
||||
</P>
|
||||
|
||||
@ -474,7 +474,7 @@ cdrecord but not vice versa.
|
||||
<BR>
|
||||
<BR>
|
||||
I was a long time user of cdrecord and it worked fine for me.
|
||||
Especially i do appreciate its write mode -tao which allows to pipe arbitrary
|
||||
Especially i do appreciate its write mode -tao which can pipe arbitrary
|
||||
data on CD and CD-RW via stdin. cdrecord is reliable, versatile and well
|
||||
maintained. So for me - there would be no problem with using it for
|
||||
burning CDs.
|
||||
|
||||
@ -1 +1 @@
|
||||
#define Cdrskin_timestamP "2015.08.30.185714"
|
||||
#define Cdrskin_timestamP "2015.09.01.065852"
|
||||
|
||||
@ -23,11 +23,6 @@ About libburn API for burning CD, DVD, and BD: http://api.libburnia-project.org
|
||||
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
For yet unsupported media types see the advice to use dvd+rw-tools at
|
||||
the end of this text.
|
||||
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
About the command line options of cdrskin:
|
||||
|
||||
They are described in detail in [http://scdbackup.sourceforge.net/man_1_cdrskin_devel.html#OPTIONS section OPTIONS] of
|
||||
@ -61,7 +56,7 @@ Some are of general user interest, though:
|
||||
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
--devices allows the sysadmin to scan the system for possible drives
|
||||
--devices can be used by the sysadmin to scan the system for possible drives
|
||||
and displays their detected properties.
|
||||
The drives are listed one per line, with fields:
|
||||
libburn-drive-number, sysadmin-device-file, permissions, vendor, type
|
||||
@ -172,7 +167,7 @@ media with a single session and track on it. blank= invalidates ISO images.
|
||||
|
||||
--------------------------------------------------------------------------
|
||||
|
||||
assert_write_lba=<lba> allows to ensure that the start block address which
|
||||
assert_write_lba=<lba> ensures that the start block address which
|
||||
was used with the formatter program (e.g. mkisofs -C) matches the start block
|
||||
address which will be used by the upcoming burn.
|
||||
|
||||
@ -220,7 +215,7 @@ With a very fat fs=# buffer (128 MB for 12x CD is not unrealistic) this
|
||||
can cause a big delay until burning finally starts and takes its due time.
|
||||
|
||||
fifo_start_at=<num> makes cdrskin start burning after the given number of bytes
|
||||
is read rather than waiting for the FIFO to be completely full resp. the data
|
||||
is read rather than waiting for the FIFO to be completely full or the data
|
||||
stream to end. It risks a few drive buffer underruns at the beginning of burn
|
||||
- but modern drives stand this.
|
||||
|
||||
|
||||
@ -647,7 +647,7 @@ In the reply, BG Format 0 indicates unformatted media (or unsuitable media).
|
||||
(mmc5r03c.pdf 6.22.3.1.13)
|
||||
|
||||
Formatting has to be started by command 04h FORMAT UNIT, Format Type 26h.
|
||||
Different from other format types, 26h allows to send a fantasy size of
|
||||
Different from other format types, 26h is allowed to send a fantasy size of
|
||||
0xffffffff blocks and does not require the caller to know the exact maximum
|
||||
size offered with that format.
|
||||
(mmc5r03c.pdf, 6.5 FORMAT UNIT, 6.5.4.2.14 Format Type = 26h)
|
||||
@ -753,7 +753,7 @@ be unnecessary to do any further formatting.
|
||||
But in order to make the DVD-RW surely accept its maximum number of bytes,
|
||||
partial formatting may be expanded by command 04h FORMAT UNIT, Format Type 13h,
|
||||
which is supposed to be offered by the drive in this state. This brings the
|
||||
session again into Intermediate state and thus allows expansion by sequential
|
||||
session again into Intermediate state and thus enables expansion by sequential
|
||||
writing. As with Format Type 15h it is ok to set Number Of Blocks to 0, so that
|
||||
no fixed size formatting work is done and writing can begin soon after.
|
||||
(mmc5r03c.pdf, 6.5.4.2.8 Format Type = 13h)
|
||||
@ -803,8 +803,8 @@ Two format types are relevant for DVD-RAM : 00h and 01h.
|
||||
00h offers the default size format and usually a maximum payload size format.
|
||||
Even with that maximum size payload there is hardware defect management.
|
||||
(mmc5r03c.pdf 6.5.4.2.1.2)
|
||||
01h allows to convert payload capacity into spare blocks for defect
|
||||
managment. There is no way to increase payload capacity by format 01h.
|
||||
01h can convert payload capacity into spare blocks for defect managment.
|
||||
There is no way to increase payload capacity by format 01h.
|
||||
(mmc5r03c.pdf 6.5.4.2.2.1)
|
||||
|
||||
With BD-RE there are three format types : 00h, 30h and 31h.
|
||||
@ -978,10 +978,10 @@ DVD-RW Sequential Recording 0014h
|
||||
DVD-R/DL Sequential Recording 0015h (can only do single-session)
|
||||
|
||||
There are two approaches for writing to sequential DVD-R[W]: DAO and
|
||||
Incremental. Not all media and drives offer Incremental which allows
|
||||
Incremental. Not all media and drives offer Incremental which can do
|
||||
multi-session as with CD media and does not demand a predicted track size.
|
||||
DAO seems to be the older method. It allows only one single session and
|
||||
track and it demands an exactly predicted track size.
|
||||
DAO seems to be the older method. It can only write one single session and
|
||||
track, and it demands an exactly predicted track size.
|
||||
|
||||
- About overwriteable, blank, appendable and finalized DVD-R[W] media
|
||||
- Incremental writing
|
||||
@ -1025,7 +1025,7 @@ brings back this feature.
|
||||
-------------------------------------------------------------------------------
|
||||
Incremental writing :
|
||||
|
||||
Incremental writing allows to produce multi-session DVDs. It is indicated
|
||||
Incremental writing can produce multi-session DVDs. It is indicated
|
||||
by feature 0021h being marked current in the reply of 46h GET CONFIGURATION.
|
||||
growisofs inquires 0021h by setting Starting Feature Number to 0x21 and
|
||||
Allocation Length to 16 in order to get only this one. The feature descriptor
|
||||
@ -1042,8 +1042,8 @@ which are returned by ACh.
|
||||
|
||||
growisofs fetches a mode page 05h template by MODE SENSE and inserts its own
|
||||
parameters. It sets Multi-session to 11b, unless dvd_compat is nonzero.
|
||||
libburn composes its mode page 05h from zero and allows control of
|
||||
Multi-Session by the application.
|
||||
libburn composes its mode page 05h from zero and enables the application
|
||||
to control Multi-Session.
|
||||
BUFE Buffer Underrun protection 0=off, 1=on
|
||||
LS_V Link size valid 1=true
|
||||
Test Write -dummy mode for writing 0=off, 1=on
|
||||
@ -1456,7 +1456,7 @@ eventually RRM) chosen by the format sub-type:
|
||||
10b = (RRM)
|
||||
(mmc5r03c.pdf 6.5.4.2.1.6)
|
||||
|
||||
Format type 32h uses the same sub-types but allows to allocate non-default
|
||||
Format type 32h uses the same sub-types but can allocate non-default
|
||||
amounts of spares. Similar to BD-RE format 31h, three format descriptors are
|
||||
offered: #1: default size, #2: maximum spare area, #3: minimal spare.
|
||||
The size may be chosen within that range.
|
||||
|
||||
@ -80,7 +80,7 @@
|
||||
Addition and subtraction are identical with the binary exor operator.
|
||||
Multiplication and division would demand polynomial division, e.g. by the
|
||||
euclidian algorithm. The computing path over logarithms and powers follows
|
||||
algebra and allows to reduce the arithmetic task to table lookups, additions
|
||||
algebra and reduces the arithmetic task to table lookups, additions
|
||||
modulo 255, and exor operations. Note that the logarithms are natural
|
||||
numbers, not polynomials. They get added or subtracted by the usual addition
|
||||
(not by exor) and their polynomial power depends on their value modulo 255.
|
||||
|
||||
@ -416,13 +416,14 @@ struct burn_toc_entry
|
||||
|
||||
|
||||
/** Data source interface for tracks.
|
||||
This allows to use arbitrary program code as provider of track input data.
|
||||
This allows you to use arbitrary program code as provider of track input
|
||||
data.
|
||||
|
||||
Objects compliant to this interface are either provided by the application
|
||||
or by API calls of libburn: burn_fd_source_new() , burn_file_source_new(),
|
||||
and burn_fifo_source_new().
|
||||
|
||||
The API calls allow to use any file object as data source. Consider to feed
|
||||
The API calls may use any file object as data source. Consider to feed
|
||||
an eventual custom data stream asynchronously into a pipe(2) and to let
|
||||
libburn handle the rest.
|
||||
In this case the following rule applies:
|
||||
@ -499,7 +500,7 @@ struct burn_source {
|
||||
|
||||
|
||||
/** Get the size of the source's data. Return 0 means unpredictable
|
||||
size. If application provided (*get_size) allows return 0, then
|
||||
size. If application provided (*get_size) might return 0, then
|
||||
the application MUST provide a fully functional (*set_size).
|
||||
*/
|
||||
off_t (*get_size)(struct burn_source *);
|
||||
@ -1178,7 +1179,7 @@ int burn_drive_probe_cd_write_modes(struct burn_drive_info *drive_info);
|
||||
@param d The drive to influence.
|
||||
@param flag Bitfield for control purposes
|
||||
bit0= become alert (else start snoozing)
|
||||
This is not mandatory to allow further drive operations
|
||||
This is not mandatory for further drive operations
|
||||
@return 1= success , 0= drive role not suitable for calming
|
||||
@since 0.7.0
|
||||
*/
|
||||
@ -1530,7 +1531,7 @@ int burn_disc_get_profile(struct burn_drive *d, int *pno, char name[80]);
|
||||
/** Obtain product id and standards defined media codes.
|
||||
The product id is a printable string which is supposed to be the same
|
||||
for identical media but should vary with non-identical media. Some media
|
||||
do not allow to obtain such an id at all.
|
||||
cannot provide such an id at all.
|
||||
The pair (profile_number, product_id) should be the best id to identify
|
||||
media with identical product specifications.
|
||||
The reply parameters media_code1 and media_code2 can be used with
|
||||
@ -3138,8 +3139,8 @@ int burn_write_opts_set_leadin_text(struct burn_write_opts *opts,
|
||||
|
||||
|
||||
/* ts A61222 */
|
||||
/** Sets a start address for writing to media and write modes which allow to
|
||||
choose this address at all (for now: DVD+RW, DVD-RAM, formatted DVD-RW).
|
||||
/** Sets a start address for writing to media and write modes which are able
|
||||
to choose this address at all (for now: DVD+RW, DVD-RAM, formatted DVD-RW).
|
||||
now). The address is given in bytes. If it is not -1 then a write run
|
||||
will fail if choice of start address is not supported or if the block
|
||||
alignment of the address is not suitable for media and write mode.
|
||||
@ -3401,7 +3402,7 @@ int burn_drive_free_speedlist(struct burn_speed_descriptor **speed_list);
|
||||
*/
|
||||
struct burn_multi_caps {
|
||||
|
||||
/* Multi-session capability allows to keep the media appendable after
|
||||
/* Multi-session capability can keep the media appendable after
|
||||
writing a session. It also guarantees that the drive will be able
|
||||
to predict and use the appropriate Next Writeable Address to place
|
||||
the next session on the media without overwriting the existing ones.
|
||||
@ -3414,7 +3415,7 @@ struct burn_multi_caps {
|
||||
*/
|
||||
int multi_session;
|
||||
|
||||
/* Multi-track capability allows to write more than one track source
|
||||
/* Multi-track capability can write more than one track source
|
||||
during a single session. The written tracks can later be found in
|
||||
libburn's TOC model with their start addresses and sizes.
|
||||
1= multiple tracks per session are allowed
|
||||
@ -3422,7 +3423,7 @@ struct burn_multi_caps {
|
||||
*/
|
||||
int multi_track;
|
||||
|
||||
/* Start-address capability allows to set a non-zero address with
|
||||
/* Start-address capability can set a non-zero address with
|
||||
burn_write_opts_set_start_byte(). Eventually this has to respect
|
||||
.start_alignment and .start_range_low, .start_range_high in this
|
||||
structure.
|
||||
@ -3524,7 +3525,7 @@ void burn_session_get_leadout_entry(struct burn_session *s,
|
||||
The result array contains *num + burn_disc_get_incomplete_sessions()
|
||||
elements. All above *num are incomplete sessions.
|
||||
Typically there is at most one incomplete session with one empty track.
|
||||
DVD+R and BD-R seem to allow more than one track with even readable data.
|
||||
DVD+R and BD-R seem support more than one track with even readable data.
|
||||
@param d Disc to get session array for
|
||||
@param num Returns the number of sessions in the array
|
||||
@return array of sessions
|
||||
@ -3634,7 +3635,7 @@ At runtime (via *_is_compatible()):
|
||||
|
||||
Vreixo Formoso advises to compare the application's
|
||||
requirements of library revisions with the runtime
|
||||
library. This is to allow runtime libraries which are
|
||||
library. This is to enable runtime libraries which are
|
||||
young enough for the application but too old for
|
||||
the lib*.h files seen at compile time.
|
||||
|
||||
@ -4059,8 +4060,8 @@ int burn_drive_get_drive_role(struct burn_drive *d);
|
||||
and drive role 5 "random access write-only".
|
||||
By default a random access file assumes drive role 2 "read-write"
|
||||
regardless whether it is actually readable or writeable.
|
||||
If enabled, random-access file objects which recognizably allow no
|
||||
writing will be classified as role 4 and those which allow no reading
|
||||
If enabled, random-access file objects which recognizably permit no
|
||||
writing will be classified as role 4 and those which permit no reading
|
||||
will get role 5.
|
||||
Candidates are drive addresses of the form stdio:/dev/fd/# , where # is
|
||||
the integer number of an open file descriptor. If this descriptor was
|
||||
|
||||
@ -4515,7 +4515,8 @@ int mmc_get_write_performance(struct burn_drive *d)
|
||||
|
||||
|
||||
/* ts A61229 : outsourced from spc_select_write_params() */
|
||||
/* Note: Page data is not zeroed here to allow preset defaults. Thus
|
||||
/* Note: Page data is not zeroed here in order not to overwrite preset
|
||||
defaults. Thus
|
||||
memset(pd, 0, 2 + d->mdata->write_page_length);
|
||||
is the eventual duty of the caller.
|
||||
*/
|
||||
|
||||
@ -46,7 +46,7 @@ struct burn_write_opts
|
||||
2 indicates burn_write_opts_set_obs_pad(,1)
|
||||
*/
|
||||
|
||||
/* ts A61222 : Start address for media which allow a choice */
|
||||
/* ts A61222 : Start address for media which offer a choice */
|
||||
off_t start_byte;
|
||||
|
||||
/* ts A70213 : Wether to fill up the available space on media */
|
||||
@ -142,7 +142,7 @@ struct burn_read_opts
|
||||
|
||||
/* ts B21119 */
|
||||
/* >>> Needs API access */
|
||||
/** Whether to set DAP bit which allows drive to apply
|
||||
/** Whether to set DAP bit which allows the drive to apply
|
||||
"flaw obscuring mechanisms like audio data mute and interpolate"
|
||||
*/
|
||||
unsigned int dap_bit;
|
||||
|
||||
@ -81,7 +81,7 @@ burn_os_is_2k_seekrw() tells whether the given path leads to a file object
|
||||
|
||||
burn_os_stdio_capacity() estimates the emulated media space of stdio-drives.
|
||||
|
||||
burn_os_open_track_src() opens a disk file in a way that allows best
|
||||
burn_os_open_track_src() opens a disk file in a way that offers best
|
||||
throughput with file reading and/or SCSI write command
|
||||
transmission.
|
||||
|
||||
|
||||
@ -78,7 +78,7 @@ burn_os_is_2k_seekrw() tells whether the given path leads to a file object
|
||||
|
||||
burn_os_stdio_capacity() estimates the emulated media space of stdio-drives.
|
||||
|
||||
burn_os_open_track_src() opens a disk file in a way that allows best
|
||||
burn_os_open_track_src() opens a disk file in a way that offers best
|
||||
throughput with file reading and/or SCSI write command
|
||||
transmission.
|
||||
|
||||
|
||||
@ -84,7 +84,7 @@ burn_os_is_2k_seekrw() tells whether the given path leads to a file object
|
||||
|
||||
burn_os_stdio_capacity() estimates the emulated media space of stdio-drives.
|
||||
|
||||
burn_os_open_track_src() opens a disk file in a way that allows best
|
||||
burn_os_open_track_src() opens a disk file in a way that offers best
|
||||
throughput with file reading and/or SCSI write command
|
||||
transmission.
|
||||
|
||||
|
||||
@ -83,7 +83,7 @@ burn_os_is_2k_seekrw() tells whether the given path leads to a file object
|
||||
|
||||
burn_os_stdio_capacity() estimates the emulated media space of stdio-drives.
|
||||
|
||||
burn_os_open_track_src() opens a disk file in a way that allows best
|
||||
burn_os_open_track_src() opens a disk file in a way that offers best
|
||||
throughput with file reading and/or SCSI write command
|
||||
transmission.
|
||||
|
||||
|
||||
@ -78,7 +78,7 @@ burn_os_is_2k_seekrw() tells whether the given path leads to a file object
|
||||
|
||||
burn_os_stdio_capacity() estimates the emulated media space of stdio-drives.
|
||||
|
||||
burn_os_open_track_src() opens a disk file in a way that allows best
|
||||
burn_os_open_track_src() opens a disk file in a way that offers best
|
||||
throughput with file reading and/or SCSI write command
|
||||
transmission.
|
||||
|
||||
|
||||
@ -101,7 +101,7 @@ static int current_profile= -1;
|
||||
static char current_profile_name[80]= {""};
|
||||
|
||||
|
||||
/* Some in-advance definitions to allow a more comprehensive ordering
|
||||
/* Some in-advance definitions make possible a more comprehensive ordering
|
||||
of the functions and their explanations in here */
|
||||
int libburner_aquire_by_adr(char *drive_adr);
|
||||
int libburner_aquire_by_driveno(int *drive_no);
|
||||
@ -434,7 +434,7 @@ int libburner_format(struct burn_drive *drive)
|
||||
In case of external signals expect abort handling of an ongoing burn to
|
||||
last up to a minute. Wait the normal burning timespan before any kill -9.
|
||||
|
||||
For simplicity, this function allows memory leaks in case of failure.
|
||||
For simplicity, this function has memory leaks in case of failure.
|
||||
In apps which do not abort immediately, one should clean up better.
|
||||
*/
|
||||
int libburner_payload(struct burn_drive *drive,
|
||||
|
||||
@ -71,7 +71,7 @@ static unsigned int drive_count;
|
||||
static int drive_is_grabbed = 0;
|
||||
|
||||
|
||||
/* Some in-advance definitions to allow a more comprehensive ordering
|
||||
/* Some in-advance definitions to make possible a more comprehensive ordering
|
||||
of the functions and their explanations in here */
|
||||
int telltoc_aquire_by_adr(char *drive_adr);
|
||||
int telltoc_aquire_by_driveno(int *drive_no, int silent);
|
||||
@ -296,15 +296,15 @@ int telltoc_media(struct burn_drive *drive)
|
||||
/* Media appears writeable */
|
||||
printf("Write multi : ");
|
||||
printf("%s multi-session , ",
|
||||
caps->multi_session == 1 ? "allows" : "prohibits");
|
||||
caps->multi_session == 1 ? "offers" : "cannot do");
|
||||
if (caps->multi_track)
|
||||
printf("allows multiple tracks\n");
|
||||
printf("offers multiple tracks\n");
|
||||
else
|
||||
printf("enforces single track\n");
|
||||
printf("offers only single track\n");
|
||||
printf("Write start : ");
|
||||
if (caps->start_adr == 1)
|
||||
printf(
|
||||
"allows addresses [%.f , %.f]s , alignment=%.fs\n",
|
||||
"offers addresses [%.f , %.f]s , alignment=%.fs\n",
|
||||
(double) caps->start_range_low / 2048 ,
|
||||
(double) caps->start_range_high / 2048 ,
|
||||
(double) caps->start_alignment / 2048 );
|
||||
|
||||
Loading…
Reference in New Issue
Block a user