You can subscribe to this list here.
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2015 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(5) |
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
2021 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
From: (Joerg S. <sc...@sc...> - 2021-09-11 20:06:50
|
bod...@gt... wrote: > Hello, > My last version of cdda2wav is 3.02. The default cddb server of > freedb.freedb.org is defunct. Currently gnudb.gnudb.org should be > used. Could you please change the default server for applicable > cdr-tools to gnudb.gnudb.org? > > I tried to see if the latest version has already been changed, but > could find any indication of such. Please upgrade to the most recent version, that change has been done June 24 2020 already. cdda2wav -version cdda2wav 3.02a10 2021/07/23 (x86_64-unknown-linux-gnu) Copyright (C) 1993-2004,2015,2017,2019 Heiko Eissfeldt (C) 2004-2020 Joerg Schilling Jörg -- EMail:jo...@sc... Jörg Schilling D-13353 Berlin Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/ |
From: <bod...@gt...> - 2021-09-11 19:27:16
|
Hello, My last version of cdda2wav is 3.02. The default cddb server of freedb.freedb.org is defunct. Currently gnudb.gnudb.org should be used. Could you please change the default server for applicable cdr-tools to gnudb.gnudb.org? I tried to see if the latest version has already been changed, but could find any indication of such. Thanks, Don Wilburn |
From: (Joerg S. <sc...@sc...> - 2021-03-20 14:28:41
|
Hi, if you like to send mails to the sourceforge mailing lists, you need to first register yourself for the mailing list. st xu <xu....@gm...> wrote: > ---------- Forwarded message --------- > ???????????? st xu <xu....@gm...> > Date: 2021???3???19????????? ??????6:27 > Subject: An issue about cdrtools > To: <joe...@fo...> > > > Hi Schilling, > Sorry to bother you, I'm a noob with the cdrtools, and I've met an issue > that I cannot append files to a *DVD-R* disc which was burned on Windows by > Windows Explorer with the *CD/DVD mode.* > and here are my commands: > // 1. get the start sector no. > *cdrecord -msinfo -dev /dev/sr0* Given that you do not send any information from cdrecord, I am wondering how I could help you.... in special since you do not use the cdrecord command line syntax that is explained in the cdrecord man page. Using /dev/* arguments for the dev= option from cdrecord is explicitly called unsupported in the man page and typically causes cdrecord to fail on Linux as a result of the bugs in the Linux kernel or simply as from the fact that Linux implements more than one driver interface for a single device and /dev/* typicalls enforces cdrecord to use the driver variant that does not work correctly. > // 2. make an iso with -C -M > *mkisofs -J -udf -C 0,93952 -M /dev/sr0 -V mki_burn -v -o image.iso > somefiles* > then an error occurred: > *mkisofs: unable to find previous session PVD '/dev/sr0'* > so i cannot accomplish my expectation. > this is the result of cd_session command for this nonempty disc. > [image: image.png] This error message is not from mkisofs :-( What software are you using? In case of problems with multi session disks, it may be that the option argument for the -C option is wrong. It helps to call "cdrecord -media-info -v" to retrieve the media information that I would need to be able to help. > and sometimes I will get a cdrecord error while appending files to an > nonempty disc using the command: *cdrecord -multi -eject -v -dev /dev/sr0 > targetIsoFile*: Again the unsupported dev= parameter :-( > * cdrecord: Data does not fit on current disk.* > I followed the codes and found that cdrecord cannot get the correct block > size of disc, in file drv_dvd.c, > [image: image.png] > after converting uchar to ulong, the nonzero value turned zero, so the > next process will abort. That message may appear when the medium is unable to hold the next session data or when you use a cdrecord variant that has been created (destroyed) by bad people that like to harm the cdrtoos project. What version of cdrecord are you using? What do you get from "cdrecord -version"? > I'm looking for something which could support appending files to a > nonempty disc which was burned on windows before then I found your project, > and the manpage said this project supports udf hybrid file system, I think > it will be useful until i met the issue. A disk written to before from windows may be in a bad state that prevants further data from being appended. What do you get from: cdrecord -media-info -v > Could you please give me some advice about how to solve these problems or > how to append files to a nonempty disc which was burned on windows before? > Or could you please let me know how to contact Schilling? Really need to > solve this. I'll be very grateful. > Thank you anyway. Expect your reply. As long as you do not send real information from cdrtools programs, I have no idea how I could help. Jörg -- EMail:jo...@sc... Jörg Schilling D-13353 Berlin Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/ |
From: st xu <xu....@gm...> - 2021-03-19 06:32:02
|
---------- Forwarded message --------- 发件人: st xu <xu....@gm...> Date: 2021年3月19日周五 上午6:27 Subject: An issue about cdrtools To: <joe...@fo...> Hi Schilling, Sorry to bother you, I'm a noob with the cdrtools, and I've met an issue that I cannot append files to a *DVD-R* disc which was burned on Windows by Windows Explorer with the *CD/DVD mode.* and here are my commands: // 1. get the start sector no. *cdrecord -msinfo -dev /dev/sr0* // 2. make an iso with -C -M *mkisofs -J -udf -C 0,93952 -M /dev/sr0 -V mki_burn -v -o image.iso somefiles* then an error occurred: *mkisofs: unable to find previous session PVD '/dev/sr0'* so i cannot accomplish my expectation. this is the result of cd_session command for this nonempty disc. [image: image.png] and sometimes I will get a cdrecord error while appending files to an nonempty disc using the command: *cdrecord -multi -eject -v -dev /dev/sr0 targetIsoFile*: * cdrecord: Data does not fit on current disk.* I followed the codes and found that cdrecord cannot get the correct block size of disc, in file drv_dvd.c, [image: image.png] after converting uchar to ulong, the nonzero value turned zero, so the next process will abort. I'm looking for something which could support appending files to a nonempty disc which was burned on windows before then I found your project, and the manpage said this project supports udf hybrid file system, I think it will be useful until i met the issue. Could you please give me some advice about how to solve these problems or how to append files to a nonempty disc which was burned on windows before? Or could you please let me know how to contact Schilling? Really need to solve this. I'll be very grateful. Thank you anyway. Expect your reply. |
From: Robinson, H. <Her...@st...> - 2019-12-04 21:57:54
|
The sig in the e-mail I just got from cdrtools-developers said to resend anything sent since Match 2018 and I see you haven't picked up this patch, yet.. The line numbers in eltorito.c still match the patch... From: Robinson, Herbie Sent: Wednesday, November 14, 2018 12:37 PM To: cdr...@li... Subject: Patch for UEFI Boot I have to make a UEFI boot disk with a UEFI System Partition that is larger than 65K sectors. In order to do that, I have to get the "Sector Count" in the boot catalog set to zero. I made the following patch to make that work: --- orig>eltorito.c 2018-11-14 12:18:47 -0500 +++ eltorito.c 2018-11-14 12:17:49 -0500 @@ -429,7 +429,7 @@ * However, round up to the nearest integral CD (2048-byte) sector. * This is only used for no-emulation booting. */ - nsectors = boot_entry->load_size ? boot_entry->load_size : + nsectors = (boot_entry->load_size >= 0) ? boot_entry->load_size : ISO_BLOCKS(de->size) * (SECTOR_SIZE/512); if (verbose > 0) { @@ -634,6 +634,7 @@ current_boot_entry = (struct eltorito_boot_entry_info *) e_malloc(sizeof (struct eltorito_boot_entry_info)); memset(current_boot_entry, 0, sizeof (*current_boot_entry)); + current_boot_entry->load_size = -1; if (!first_boot_entry) { first_boot_entry = current_boot_entry; This patch is against the 3.01 sources. The version we are using is actually 2.01 (with the fix to allow EFI partitions from the latest code and our own Rockridge extensions), but it looks like the patch is still relevant. FYI, we have ported CDRTools to the Stratus VOS operating system, but only use it in house to generate distribution media for the OS. We don't make it available to customers and version 2.01 does the job.... [That's why we haven't upgraded.] Herbie Robinson Software Architect Stratus Technologies | www.stratus.com<http://www.stratus.com> 5 Mill and Main Place, Suite 500 | Maynard, MA 01754 T: +1-978-461-7531 | E: Her...@st...<mailto:Her...@st...> [Stratus Technologies]<http://go.stratus.com/US> |
From: Joerg S. <Joe...@fo...> - 2019-11-27 11:18:17
|
>I've been using your program recently to play some classic PC games that I've >missed, but I keep running into errors when burning BIN/CUE file for mixed mode >d >iscs: >cdrecord: Unsupported sector size 2352 for data on line 2 col 16 in 'Insert >file.cue'. So you used a cue file that is in conflict with the CUE definition from CDRWIN Data sectors _always_ have 2048 bytes sector size. Multi media sectors use other sector type names. If you wrote the CUR file yourself, read the cdrecord man page, if you received the CUE file from somewhere else, make a bug report against your source. The cdrecord CUE parser has been written after the official CDRWIN documentation and tested with various example CUE files from CDRWIN. >-Using Brasero and cdrdao (doesn't work) These commands do not implement CUE sheets at all. BTW: cdrdao is dead since a long time. >-Making a TOC file from scratch to replace the CUE sheet (Works on linux, but >causes ear bleeds on Windows) ??? If you create a CUE file that is aligned with the definitions from CDRWIN, it should work. >-Reinstalling cdrecord from the repositories (couldn't find it) >-Reinstalling cdrecord with "sudo pacman -S cdrecord" (doesn't work) This does not apply to this project but rather to your distro. >So I'm out of ideas and I've been at this for about a week. I've looked online >for some answers and the closest thing I found was that this may be a bug in cdr >ecord. >https://mandrivausers.org/index.php?/topic/8962-k3b-cdrecord-and-unsupported-sector-size/ >It's old, but it pretty much describes my problem. >Here is the version of cdrecord according to the manual: >Version 3.02 2017/09/21 This is extremely old. Here is the output from a recent version: Cdrecord-ProDVD-ProBD-Clone 3.02a10 2019/01/08 (i386-pc-solaris2.11) Copyright (C) 1995-2019 Joerg Schilling >I hope this is enough information to figure out what's happening, again I'm >still new to Linux and I want to keep using it as I love it compared to >Windows. I >prefer to have little road blocks like these compared to the virus minefield of >Windows. Since you do not mention your defective cue file, there is few hope that I can help. BTW: IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII imortant IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII in March 2018, Sourceforge did implement their rotten understanding of the General Data Protection Regulation and as a result, they made it impossible for me to see the subscriber list and they did even kick me from the list and made it impossible for me to subscribe again. Today, it seems to work again to re-subscribe. If soneone did send a mail that did not get an answer, please resend it... Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/' |
From: Anthony B. <ant...@ho...> - 2019-11-27 07:04:23
|
Hello, I've been using your program recently to play some classic PC games that I've missed, but I keep running into errors when burning BIN/CUE file for mixed mode discs: cdrecord: Unsupported sector size 2352 for data on line 2 col 16 in 'Insert file.cue'. I've tried a couple different workarounds like: -Mounting it on a virtual drive in Win98 (works but no sound) -Using Brasero and cdrdao (doesn't work) -Using Xfburn (only supports ISO files) -Copying the raw data and re-stitching it back as ISO and Wave files (takes a while, but won't work for every game) -Making a TOC file from scratch to replace the CUE sheet (Works on linux, but causes ear bleeds on Windows) -Reinstalling cdrecord from the repositories (couldn't find it) -Reinstalling cdrecord with "sudo pacman -S cdrecord" (doesn't work) So I'm out of ideas and I've been at this for about a week. I've looked online for some answers and the closest thing I found was that this may be a bug in cdrecord. https://mandrivausers.org/index.php?/topic/8962-k3b-cdrecord-and-unsupported-sector-size/ It's old, but it pretty much describes my problem. Now I'm still a noob with Linux so if I did something wrong, I would love to know how to improve. I'm currently using: Manjaro Xfce version 18.1.3 (Juhraya) Here is the version of cdrecord according to the manual: Version 3.02 2017/09/21 I hope this is enough information to figure out what's happening, again I'm still new to Linux and I want to keep using it as I love it compared to Windows. I prefer to have little road blocks like these compared to the virus minefield of Windows. I wish you good luck improving this app, and hopefully this means I won't need to find another workaround. ~Anthony.B |
From: wdlkmpx <wd...@gm...> - 2019-07-17 21:50:46
|
I wonder if Jorg is still alive |
From: Мироненко Е. <mir...@ru...> - 2019-07-16 13:24:41
|
Hi, We found out that it's not possible to create UDF images with hidden files using mkisofs, though UDF specification supports this feature. The patch below adds support into mkisofs (v3.02a09). May the patch be considered to be added to (hopefully) upcoming version? >From 268973af2e3fa0f19e873ace23d5d339bd3b85ee Mon Sep 17 00:00:00 2001 From: Eugene Mironenko <mir...@ru...> Date: Mon, 15 Jul 2019 20:54:04 +0300 Subject: [PATCH] Support setting 'hidden' FileCharacteristic in UDF Options '-hidden' and '-hidden-list' work for UDF images the same way as for IS09660. --- mkisofs/udf.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/mkisofs/udf.c b/mkisofs/udf.c index 50587d5..b6cd9c3 100644 --- a/mkisofs/udf.c +++ b/mkisofs/udf.c @@ -150,7 +150,7 @@ LOCAL void set_unallocated_space_desc __PR((unsigned char *buf, UInt32_t lba)); LOCAL void set_terminating_desc __PR((unsigned char *buf, UInt32_t lba)); LOCAL void set_logical_vol_integrity_desc __PR((unsigned char *buf, UInt32_t lba)); LOCAL void set_file_set_desc __PR((unsigned char *buf, UInt32_t rba)); -LOCAL int set_file_ident_desc __PR((unsigned char *, UInt32_t, char *, int, UInt32_t, unsigned)); +LOCAL int set_file_ident_desc __PR((unsigned char *, UInt32_t, char *, int, int, UInt32_t, unsigned)); LOCAL void set_file_entry __PR((unsigned char *buf, UInt32_t rba, UInt32_t file_rba, off_t length, int is_directory, unsigned link_count, unsigned unique_id, hfsdirent *hfs_ent, @@ -282,7 +282,7 @@ directory_size(dpnt) Uchar dummy_buf[SECTOR_SIZE]; /* parent directory */ - size_in_bytes = set_file_ident_desc(dummy_buf, 0, 0, 0, 0, 0); + size_in_bytes = set_file_ident_desc(dummy_buf, 0, 0, 0, 0, 0, 0); /* directory contents */ for (de = dpnt->jcontents; de; de = de->jnext) { @@ -291,7 +291,7 @@ directory_size(dpnt) /* skip . and .. */ if (name[0] == '.' && (name[1] == 0 || (name[1] == '.' && name[2] == 0))) continue; - size_in_bytes += set_file_ident_desc(dummy_buf, 0, name, 0, 0, 0); + size_in_bytes += set_file_ident_desc(dummy_buf, 0, name, 0, 0, 0, 0); } } return (size_in_bytes); @@ -870,11 +870,12 @@ set_file_set_desc(buf, rba) } LOCAL int -set_file_ident_desc(buf, rba, name, is_directory, file_entry_rba, unique_id) +set_file_ident_desc(buf, rba, name, is_directory, is_hidden, file_entry_rba, unique_id) unsigned char *buf; UInt32_t rba; char *name; int is_directory; + int is_hidden; UInt32_t file_entry_rba; unsigned unique_id; { @@ -883,7 +884,8 @@ set_file_ident_desc(buf, rba, name, is_directory, file_entry_rba, unique_id) set16(&fid->file_version_number, 1); set8(&fid->file_characteristics, (is_directory ? UDF_FILE_CHARACTERISTIC_DIRECTORY : 0) - + (name == 0) * UDF_FILE_CHARACTERISTIC_PARENT); + + (name == 0) * UDF_FILE_CHARACTERISTIC_PARENT + + (is_hidden ? UDF_FILE_CHARACTERISTIC_HIDDEN : 0)); set32(&fid->icb.extent_length, SECTOR_SIZE); set32(&fid->icb.extent_location.logical_block_number, file_entry_rba); set16(&fid->icb.extent_location.partition_reference_number, 0); @@ -1777,6 +1779,7 @@ write_one_udf_directory(dpnt, outfile) base_sector, 0, 1, + 0, parent->self->udf_file_entry_sector - lba_udf_partition_start, (parent == root) ? 0 : parent->self->udf_file_entry_sector); xfwrite(buf, ident_size, 1, outfile, 0, FALSE); @@ -1816,6 +1819,7 @@ write_one_udf_directory(dpnt, outfile) base_sector + (size_in_bytes / SECTOR_SIZE), name, !!(de1->isorec.flags[0] & ISO_DIRECTORY), + !!(de1->de_flags & HIDDEN_FILE), de1->udf_file_entry_sector - lba_udf_partition_start, de1->udf_file_entry_sector); xfwrite(buf, ident_size, 1, outfile, 0, FALSE); -- 2.21.0 С уважением, Евгений Мироненко Системный программист ЗАО <Актив-софт> mir...@ru...<mailto:mir...@ru...> / www.aktiv-company.ru<http://www.aktiv-company.ru/> |
From: Robinson, H. <Her...@st...> - 2018-11-14 17:52:57
|
I have to make a UEFI boot disk with a UEFI System Partition that is larger than 65K sectors. In order to do that, I have to get the "Sector Count" in the boot catalog set to zero. I made the following patch to make that work: --- orig>eltorito.c 2018-11-14 12:18:47 -0500 +++ eltorito.c 2018-11-14 12:17:49 -0500 @@ -429,7 +429,7 @@ * However, round up to the nearest integral CD (2048-byte) sector. * This is only used for no-emulation booting. */ - nsectors = boot_entry->load_size ? boot_entry->load_size : + nsectors = (boot_entry->load_size >= 0) ? boot_entry->load_size : ISO_BLOCKS(de->size) * (SECTOR_SIZE/512); if (verbose > 0) { @@ -634,6 +634,7 @@ current_boot_entry = (struct eltorito_boot_entry_info *) e_malloc(sizeof (struct eltorito_boot_entry_info)); memset(current_boot_entry, 0, sizeof (*current_boot_entry)); + current_boot_entry->load_size = -1; if (!first_boot_entry) { first_boot_entry = current_boot_entry; This patch is against the 3.01 sources. The version we are using is actually 2.01 (with the fix to allow EFI partitions from the latest code and our own Rockridge extensions), but it looks like the patch is still relevant. FYI, we have ported CDRTools to the Stratus VOS operating system, but only use it in house to generate distribution media for the OS. We don't make it available to customers and version 2.01 does the job.... [That's why we haven't upgraded.] Herbie Robinson Software Architect Stratus Technologies | www.stratus.com 5 Mill and Main Place, Suite 500 | Maynard, MA 01754 T: +1-978-461-7531 | E: Her...@st... [Stratus Technologies]<http://go.stratus.com/US> |
From: Lutz L. <lu...@pr...> - 2018-09-12 07:02:43
|
Hi, if there are newlines in directory- or filenames the output-format of the isoinfo -l breaks. Example: Directory listing of / 275 dr-xr-xr-x 3 0 0 2048 Aug 21 2018 [ 275 02] . 275 dr-xr-xr-x 3 0 0 2048 Aug 21 2018 [ 275 02] .. 280 -r--r--r-- 1 0 0 6144 Aug 16 2018 [ 280 00] file_with_newline 283 -r--r--r-- 1 0 0 21 Aug 13 2018 [ 283 00] file_does_not_exist It seems that there are two files. But it is only one with the name "file_with_newline\n 283 -r--r--r-- 1 0 0 21 Aug 13 2018 [ 283 00] file_does_not_exist". I replaced the newline with \n in this example. The following patch introduces a backslash as escape character, so that newlines in directories or filenames are displayed as \n. Backslashes are displayed as \\: --- mkisofs/diag/isoinfo.c.org 2018-09-10 14:47:44.591623840 +0200 +++ mkisofs/diag/isoinfo.c 2018-09-12 08:09:39.378615018 +0200 @@ -168,6 +168,7 @@ LOCAL struct stat fstat_buf; LOCAL int found_rr; LOCAL char name_buf[256*3]; +LOCAL char name_buf_esc[256*3*2]; LOCAL char xname[8192]; LOCAL unsigned char date_buf[9]; /* iso_directory_record.date[7] */ /* @@ -731,6 +732,29 @@ "Aug", "Sep", "Oct", "Nov", "Dec"}; /* + * str_esc must point to a field with a size: sizeof(str)*2 + */ +LOCAL void +esc_newlines(str_buf, str_buf_esc) +char *str_buf; +char *str_buf_esc; +{ + int i, j; + for (i = 0, j = 0; i < strlen(str_buf); i++, j++) { + if (str_buf[i] == '\n') { + str_buf_esc[j++] = '\\'; + str_buf_esc[j] = 'n'; + } else if (str_buf[i] == '\\') { + str_buf_esc[j++] = '\\'; + str_buf_esc[j] = '\\'; + } else { + str_buf_esc[j] = str_buf[i]; + } + } + str_buf_esc[j] = '\0'; +} + +/* * Return TRUE if this file was "selected" either based on find rules * or for all files if there was no find rule. */ @@ -830,7 +854,8 @@ if (outline[i] == 0) outline[i] = ' '; } outline[off] = 0; - printf("%s %s %s\n", outline, name_buf, xname); + esc_newlines(&name_buf, &name_buf_esc); + printf("%s %s %s\n", outline, name_buf_esc, xname); return (TRUE); } @@ -1163,6 +1188,7 @@ struct stat dstat; unsigned char cl_buffer[2048]; unsigned char flags = 0; + char *rootname_esc = 0; Llong size = 0; int sextent = 0; int rlen; @@ -1172,10 +1198,13 @@ static int nlen = 0; - if (do_listing && (!do_find || !find_print)) - printf(_("\nDirectory listing of %s\n"), rootname); - rlen = strlen(rootname); + if (do_listing && (!do_find || !find_print)) { + rootname_esc = (char *) malloc(rlen*2 + 1); + esc_newlines(rootname, rootname_esc); + printf(_("\nDirectory listing of %s\n"), rootname_esc); + free(rootname_esc); + } while (len > 0) { #ifdef USE_SCG Best regards, Lutz Lümken -- Lutz Lümken lu...@pr... PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Wir sind auf der it-sa: 9.-11.10.2018 www.pre-sense.de/it-sa |
From: Γιώργος Κ. <gio...@gm...> - 2018-04-12 01:17:21
|
Hi! :-) 1) I think cdrtools needs a x64 edition. Running through an emulation layer (SysWOW64) is always possible, but a bit problematic in certain conditions. 2) Abillity to creat an ISO from a directory. Currently (if I'm not wrong) it supports only from CD. Bye! :-) G. |
From: wdlkmpx <wd...@gm...> - 2018-03-17 19:55:17
|
This project doesn't have a git repo on sourceforge (i can't find it). Althught sf's git repos are not that appealing. I follow many projects on github, and it's great to see how people open issues and pull requests and everything seems to flow faster.. the official cdrtools git repo is missing there, or maybe i'm blind A git repo (on github) would make cdrtools way more popular and visible, at least to developers and people interested in following a project's history and changes |
From: Roman M. <rom...@gm...> - 2018-02-04 18:36:36
|
Hi I want to use mkisofs as DLL on Windows, created by Cygwin or (better) Visual Studio. I don't know how to configure make to use Visual Studio instead cygwin+gcc. I was able to build latest alpha using Cygwin and as exe. But, I need DLL (I'll add required API). Can somebody help me? -- ------------------------------------------------------------------------------------------- Roman Minyaylov |
From: Steve B. <sw...@gm...> - 2017-09-28 21:42:29
|
Hello, Looking at the code in cdrecord\scsi_cdr.c, I have a question about code in mode_select_g0 and mode_select_g1. In both of the functions there is the following line: scmd->cdb.g0_cdb.high_addr = smp ? 1 : 0 | pf ? 0x10 : 0; It seems to me that the desired result from this would be: scmd->cdb.g0_cdb.high_addr = (smp ? 1 : 0) | (pf ? 0x10 : 0); However, since there are no parenthesis I think that the operator precedence would be: scmd->cdb.g0_cdb.high_addr = smp ? 1 : (0 | pf) ? 0x10 : 0; I have not traced the usage of the high_addr field to see if it is really used anywhere. These routines are also in the libscgcmd\modesense.c Just checking that the original code is what is intended. Thanks. Steve. |
From: Joerg S. <Joe...@fo...> - 2017-05-22 10:24:15
|
Szabó Tibor <sza...@gm...> wrote: > Dear cdrtools developers, > > I have found the following bug in the module cdda2wav.c: > > gargs defines userverbose as int, while handle_verbose_opts expects > long*. On a 64 bit machine, handle_verbose_opts writes beyond > userverbose (to outfd). Thus, the output is redirected to stdin (fd == > 0) Hi, the bug was fixed March 28 2017. So check cddrtools-3.02a08 Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/' |
From: Szabó T. <sza...@gm...> - 2017-05-19 22:07:59
|
Dear cdrtools developers, I have found the following bug in the module cdda2wav.c: gargs defines userverbose as int, while handle_verbose_opts expects long*. On a 64 bit machine, handle_verbose_opts writes beyond userverbose (to outfd). Thus, the output is redirected to stdin (fd == 0) You can reproduce the bug with a 64 bit build as follows: cdda2wav -J -v titles > outfile 2>&1 (outfile remains empty) cdrtools version: 3.02a07 Best regards, Tibor Szabó |
From: Pascal <pat...@gm...> - 2016-12-22 15:54:40
|
why hard disk emulation boot : to boot in all cases (bios/uefi) from only one image :-) Le jeudi 22 décembre 2016, Joerg Schilling < Joe...@fo...> a écrit : > Pascal <pat...@gm... <javascript:;>> wrote: > > > this is the answere from syslinux : > > > > """ isohybrid is for "El Torito no-emulation" boot images (such as those > using > > isolinux.bin) and you are using "El Torito hard disk emulation". """ > > OK, I was wondering anyway why you like to create a hard dick emulation > boot. > > This may not be supported with all computers today. > > Jörg > > -- > EMail:jo...@sc... <javascript:;> (home) Jörg > Schilling D-13353 Berlin > joe...@fo... <javascript:;> (work) Blog: > http://schily.blogspot.com/ > URL: http://cdrecord.org/private/ http://sf.net/projects/ > schilytools/files/' > |
From: Joerg S. <Joe...@fo...> - 2016-12-22 09:27:26
|
Pascal <pat...@gm...> wrote: > this is the answere from syslinux : > > """ isohybrid is for "El Torito no-emulation" boot images (such as those using > isolinux.bin) and you are using "El Torito hard disk emulation". """ OK, I was wondering anyway why you like to create a hard dick emulation boot. This may not be supported with all computers today. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/' |
From: Pascal <pat...@gm...> - 2016-12-22 07:43:24
|
this is the answere from syslinux : """ isohybrid is for "El Torito no-emulation" boot images (such as those using isolinux.bin) and you are using "El Torito hard disk emulation". """ so isohybrid is not for my case :-( Le mercredi 21 décembre 2016, Joerg Schilling < Joe...@fo...> a écrit : > Pascal <pat...@gm... <javascript:;>> wrote: > > > what about the eltorito boot catalog generated by mkisofs ? > > isohybrid seems to say that the catalog is not well formed... > > I did never receive any report about problems in this area. > > Without kowing the related data, I cannot comment. > > I recommend you to first get a better error message from the "isohybrid" > program by asking for an update from it's author. > > Jörg > > -- > EMail:jo...@sc... <javascript:;> (home) Jörg > Schilling D-13353 Berlin > joe...@fo... <javascript:;> (work) Blog: > http://schily.blogspot.com/ > URL: http://cdrecord.org/private/ http://sf.net/projects/ > schilytools/files/' > |
From: Joerg S. <Joe...@fo...> - 2016-12-21 17:39:11
|
Pascal <pat...@gm...> wrote: > hello every body, > > I'm trying to build an isohybrid image based on syslinux able to boot on > bios and uefi with optical disk or usb key. > > I've build a 16Mb hard disk image (core.img) with necessary parts for bios > (legacy bootable partition, protective mbr, gptmbr.bin & syslinux > installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux > files). > > my hard disk image is ok - eg. bootable - with qemu on bios and uefi > (vmlinux & core.gz from tinylinux 7.2 are used). > > I've generated an iso image with : > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, and with qemu as hard disk > on uefi but not on bios. > > for the last case, I've use : > > isohybrid core.iso > > but I've this error : > > isohybrid: core.iso: unexpected boot catalogue parameters Did you ask the author of "isohybrid" for a possible reason for that error message? Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/' |
From: Pascal <pat...@gm...> - 2016-12-21 17:09:51
|
hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok - eg. bootable - with qemu on bios and uefi (vmlinux & core.gz from tinylinux 7.2 are used). I've generated an iso image with : mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ my iso image is ok with qemu on bios and uefi, and with qemu as hard disk on uefi but not on bios. for the last case, I've use : isohybrid core.iso but I've this error : isohybrid: core.iso: unexpected boot catalogue parameters what's my problem :-) regards. |
From: Thomas G. <os...@th...> - 2016-12-14 00:12:16
|
Hello, I've read through the release notes and the mailing list and I'm not sure if this already known and maybe part of the mentioned "HELIOS TODO", or a still unknown problem, so I decided to give you a heads-up. I experience some file name weirdness with Unicode file names in 3.02 (Last test with 3.02a06). The Unicode characters themselves are always right as far as I have seen, but the file extension is sometimes mangled. With a compiled mkisofs from the latest 3.01 tree and the latest 3.02 tree the 3.01 binary seems to work correct, the 3.02 binary shows the phenomenon. With the this short test for example: ----- ls -l ./mkisofs-301 --version ./mkisofs-302 --version mkdir test echo "FooBar" >./test/日本語.txt echo "FooBar" >./test/日本語祭り.txt echo "FooBar" >./test/くじけないで.txt ./mkisofs-301 -JR -udf -o 301.iso test ./mkisofs-302 -JR -udf -o 302.iso test mkdir mnt_301 mkdir mnt_302 mount -o loop 301.iso mnt_301 mount -o loop 302.iso mnt_302 ls -l mnt_301 ls -l mnt_302 ----- I get the following results: ----- # ls -l total 996 -rwxr-xr-x 1 root root 502064 13. Dez 23:14 mkisofs-301 -rwxr-xr-x 1 root root 514808 13. Dez 23:14 mkisofs-302 # ./mkisofs-301 --version mkisofs 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2015 Joerg Schilling # ./mkisofs-302 --version mkisofs 3.02a06 (x86_64-unknown-linux-gnu) Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2016 Joerg Schilling # mkdir test # echo "FooBar" >./test/日本語.txt # echo "FooBar" >./test/日本語祭り.txt # echo "FooBar" >./test/くじけないで.txt # ./mkisofs-301 -JR -udf -o 301.iso test Setting input-charset to 'UTF-8' from locale. Using _____000.TXT;1 for /くじけないで.txt (日本語祭り.txt) Using _____001.TXT;1 for /日本語祭り.txt (日本語.txt) Total translation table size: 0 Total rockridge attributes bytes: 479 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 429 extents written (0 MB) # ./mkisofs-302 -JR -udf -o 302.iso test Setting input-charset to 'UTF-8' from locale. Using _____000.TXT;1 for /くじけないで.txt (日本語祭り.txt) Using _____001.TXT;1 for /日本語祭り.txt (日本語.txt) Total translation table size: 0 Total rockridge attributes bytes: 479 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 429 extents written (0 MB) # mkdir mnt_301 # mkdir mnt_302 # mount -o loop 301.iso mnt_301 mount: /dev/loop1 is write-protected, mounting read-only # mount -o loop 302.iso mnt_302 mount: /dev/loop2 is write-protected, mounting read-only # ls -l mnt_301 total 6 -r--r--r-- 1 root root 7 13. Dez 23:26 くじけないで.txt -r--r--r-- 1 root root 7 13. Dez 23:26 日本語.txt -r--r--r-- 1 root root 7 13. Dez 23:26 日本語祭り.txt # ls -l mnt_302 total 6 -r--r--r-- 1 root root 7 13. Dez 23:26 くじけないで#5261.t_ -r--r--r-- 1 root root 7 13. Dez 23:26 日本語.txt -r--r--r-- 1 root root 7 13. Dez 23:26 日本語祭り#1AA4.tx_ ----- When the problem occurs, the file always shows up in the mounted images as [correct part of name]#XXXX.[mangled extention]. Platform is ArchLinux. uname -a Linux starfury 4.8.12-2-ARCH #1 SMP PREEMPT Fri Dec 2 20:17:06 CET 2016 x86_64 GNU/Linux Kind regards, Thomas |
From: Joerg S. <Joe...@fo...> - 2016-07-28 10:44:52
|
?????? ??????? <vel...@gm...> wrote: > I use Debian 8.5.0, and found a bug in the source code. That conclusion is all > the errors in the file > ... > > In file included from sun.c:2:0: > > config.h:34:21: fatal error: lconfig.h: No such file or directory > > #include "lconfig.h" > > > > > I started watching the files and found a solution. > in config.h it was necessary to replace 34 lines of a file > > > #include "./cdda2wav/OBJ/x86_64-linux-cc/lconfig.h" > > > The old value was there #include "lconfig.h" > > > The file itself is in ./cdda2wav/config.h > Thus, the error was corrected. > > > root@linux:~# make --version > > GNU Make 4.0 The related bug in gmake has been reported in 1998 - 18 years ago and the makefile system intentionally prints this warning in case gmake is used: /*--------------------------------------------------------------------------*/ W A R N I N G Messages like: gmake[2]: Entering directory `/tmp/cdrtools-2.01/libschily' ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/cvmod.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/dat.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fcons.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fdown.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fdup.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/ffileread.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/ffilewrite.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fgetline.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fgetstr.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/file_raise.d: No such file or directory ../RULES/r-gmake.dep:76: OBJ/<arch-dir>/fileclose.d: No such file or directory .... are caused by a GNU make bug and not by the Schily makefile system. The related bug has been reported to the GNU make maintainers in 1998 but as the bug has not yet been fixed, it seems that GNU make is unmaintained :-( A working highly portable make program is at https://sourceforge.net/projects/s-make/files/ /*--------------------------------------------------------------------------*/ in order to inform people about the cause of the problem. BT: If you use "schilytools" to compile instead of just compiling cdrtools, this includes a bootstrap "smake" compile and thus avoids the problem. Jörg -- EMail:jo...@sc... (home) Jörg Schilling D-13353 Berlin joe...@fo... (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
From: Кирилл Ф. <vel...@gm...> - 2016-07-28 05:38:23
|
I use Debian 8.5.0, and found a bug in the source code. That conclusion is all the errors in the file ../RULES/local.cnf:45: OBJ/x86_64-linux-cc/Inull: No such file or directory > ../RULES/local.cnf:46: OBJ/x86_64-linux-cc/local.cnf: No such file or > directory > In file included from base64.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from ioctl.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from aifc.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from aiff.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > compilation terminated. > In file included from sndconfig.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from ringbuff.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from setuid.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from raw.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > ^ > compilation terminated. > In file included from sun.c:2:0: > config.h:34:21: fatal error: lconfig.h: No such file or directory > #include "lconfig.h" > > I started watching the files and found a solution. in config.h it was necessary to replace 34 lines of a file > #include "./cdda2wav/OBJ/x86_64-linux-cc/lconfig.h" > The old value was there #include "lconfig.h" > The file itself is in ./cdda2wav/config.h Thus, the error was corrected. > root@linux:~# make --version > GNU Make 4.0 > Please correct this error |