Bug fix: Unsuitable write modes were caught silently and later than desired

This commit is contained in:
Thomas Schmitt 2008-11-01 12:13:26 +00:00
parent 5c3c2f192a
commit 4fef4932b6
3 changed files with 4 additions and 3 deletions

View File

@ -1 +1 @@
#define Cdrskin_timestamP "2008.10.15.103224" #define Cdrskin_timestamP "2008.11.01.121240"

View File

@ -495,7 +495,7 @@ void burn_disc_write(struct burn_write_opts *opts, struct burn_disc *disc)
*/ */
strcpy(reasons, "Write job parameters are unsuitable:\n"); strcpy(reasons, "Write job parameters are unsuitable:\n");
if (burn_precheck_write(opts, disc, reasons + strlen(reasons), 1) if (burn_precheck_write(opts, disc, reasons + strlen(reasons), 1)
== BURN_WRITE_NONE) { <= 0) {
libdax_msgs_submit(libdax_messenger, libdax_msgs_submit(libdax_messenger,
opts->drive->global_index, 0x00020139, opts->drive->global_index, 0x00020139,
LIBDAX_MSGS_SEV_SORRY, LIBDAX_MSGS_PRIO_HIGH, LIBDAX_MSGS_SEV_SORRY, LIBDAX_MSGS_PRIO_HIGH,

View File

@ -813,7 +813,8 @@ void burn_allow_untested_profiles(int yes);
If the path does not exist in the filesystem yet, it is attempted to create If the path does not exist in the filesystem yet, it is attempted to create
it as a regular file as soon as write operations are started. it as a regular file as soon as write operations are started.
The capabilities of role 3 resemble a blank DVD-R. The capabilities of role 3 resemble a blank DVD-R. Nevertheless each
burn_disc_write() run may only write a single track.
One may distinguish pseudo-drives from MMC drives by call One may distinguish pseudo-drives from MMC drives by call
burn_drive_get_drive_role(). burn_drive_get_drive_role().