similar to: problem with mkisofs :((((

I need to make a iso image with the filesystem like nero does and i need it for the windows platform not for linux... I need something that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l

Hello! I have a problem with a bootable cd that i'm trying to make .. The problem is that i don't know what all the mkisofs parameters do and because that weird things happen, if the filenames or directorynames contain spaces they do not open and if i'm in windows's safe mode it gives me an error message stating that the file or folder does not exist! Can anyone help with that?

Hi everyone; I noticed today while watching my syslog, a few entries like this: Nov 8 15:17:08 [machine] smbd[26137]: Attempt to create file (FILE.GHO) with volid set - please report this Nov 8 15:28:08 [machine] smbd[26137]: Attempt to create file (FILE0001.GHS) with volid set - please report this Nov 8 15:41:46 [machine] smbd[26137]: Attempt to create file (FILE0002.GHS) with volid

Hello, I'm Jacques living in France. I have a problem when I use isolinux. I'm working on a multiboot cdrom so I make many "mkisofs" for testing. The problem is that when I modify the "isolinux.cfg" file and then build my image with mkisofs it's the previous configuration of my "isolinux.cfg" which appears on my screen (I run the .iso file with qemu...)

I have some users reporting problems creating isolinux bootable DVD bigger than 2 GB in Windows. The resulting DVD doesn't boot. I've found this problem also mentioned in some forums, but I wasn't able to find a mkisofs binary for Windows without this bug. Please note that this isn't a problem of isolinux. Creating the same DVD with a recent mkisofs in Linux results in a

Hello again ! I have another problem and now is with mkisofs... I understand that i cannot use nero to make isolinux bootable cd's but can you help me with mkisofs because i don't understand what all his params do ! I need a iso filesystem like nero does ...relaxed restrictions 31 characters in filename and most important nero doesn't convert "-" to underscores this is

hi there, hope this is not too much out of topic here... i give it a try anyway :-) when i try to build the iso with: mkisofs i get the following error: [...] Using TTYX2000.;1 for ./dev/ttyX2 (ttyx2) Using TTYS0000.;1 for ./dev/ttys0 (ttyS0) Using TTYY3000.;1 for ./dev/ttyY3 (ttyy3) Using FD0H360000.;1 for ./dev/fd0H360 (fd0h360) Using TTYX1000.;1 for ./dev/ttyx1 (ttyX1) Size of boot

Tried both normal and debug images with Roxio 6 and Nero 6.6. Everything worked fine. Also tried cdrwin and ran into an interesting issue with it regarding it's support of image files >8k -- reported it to them. FYI, tried booting on 2 Intel and 2 Asus planars all reported no info returned in the spec packet. David >Okay, after a bit more research I ended up implementing this

Hi, Pascal wrote: > 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, Astounding. As CD-ROM this is not supposed to work with UEFI unless the firmware emulates BIOS. What particular UEFI firmware did you use ? > and with qemu as hard disk on uefi but not on bios. That's even more astounding. The UEFI

> 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 &

> Hi, > > Ady wrote: > > the UEFI specs do state that the ESP is supposed > > to be set/used as no-emulation mode > > ... > > the UEFI specs should tolerate / accept this situation, rather than > < restricting the ESP to no-emulation mode. > > My criticism towards this UEFI implementation is that it probably cannot > serve as realistic test bed

2016-12-22 10:19 GMT+01:00 Thomas Schmitt via Syslinux <syslinux at zytor.com>: > Hi, > > Didier Spaier wrote: > > The issue is the inability of booting of a *physical* (not virtual) > optical > > media, like for instance a DVD or a CD, using syslinux.efi. > > Actually firmware cannot find any UEFI specified booting starting points > in an ISO 9660

Hi All, I am following: http://www.linuxinsight.com/how-to-flash-motherboard-bios-from-linux-no-dos-windows-no-floppy-drive.html to make a bootable CD to flash my bios I get to mkisofs step, but what I get is not what I think I want. I dont understand if I unmount /tmp/floppy how the Mkisofs command of: mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144 how I get everything in /tmp/floppy Here is

Le 22/12/2016 ? 08:53, Pascal via Syslinux a ?crit : > when you say """ Unfortunately, syslinux.efi v.6.03 is not capable of > booting optical """, you talk about isolinux.bin ? > > because my iso image with a "good" alternate eltorito boot image (eg. "uefi > ready") is booting with qemu (qemu -cdrom core.iso -bios uefi.fd) and is

[cross-posted to nntp://comp.os.linux.setup, sorry] Dear Everyone, I'm writing this message merely to publish this information somewhere visible, so that others can find it when debugging a linux-based bootable CD compilation setup... For many months now, I've been using cdrtools 2.0 with isolinux 2.04 to create bootable Linux CD's. I know there are newer versions of both

Hi, Ady wrote: > [hard disk emulation boot image works with VirtualBox] For a reader of the UEFI specs this comes very unexpected. Together with the report of Pascal that a hard-disk-emulation works even with mkisofs option -b (i.e. Platform Id x86 BIOS) it appears that the UEFI implementation treats the El Torito boot image like the whole device, regardless of Platform Id. On (virtual)

2016-12-23 9:20 GMT+01:00 Thomas Schmitt via Syslinux <syslinux at zytor.com>: > Hi, > > Ady wrote: > > the UEFI specs do state that the ESP is supposed > > to be set/used as no-emulation mode > > ... > > the UEFI specs should tolerate / accept this situation, rather than > < restricting the ESP to no-emulation mode. > > My criticism towards this

Le mercredi 21 d?cembre 2016, Ady Ady via Syslinux <syslinux at zytor.com> a ?crit : > > > Hi, > > > > Pascal wrote: > > > 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, > > > > Astounding. As CD-ROM this is not supposed to work with UEFI unless the >

> Hi, > > Didier Spaier wrote: > > The issue is the inability of booting of a *physical* (not virtual) optical > > media, like for instance a DVD or a CD, using syslinux.efi. > > Actually firmware cannot find any UEFI specified booting starting points > in an ISO 9660 filesystem that was created with mkisofs -b and > -hard-disk-boot, but without a boot image

Due to limitations of equipment, I have need of using the isolinux boot loader with .iso files generated by roxio. After trying (and of course failing) with an off the shelf version of isolinux, I grabbed the source for isolinux (syslinux 2.11 package) and started looking. It took a few hours to orient myself, but I ended up doing the modification below to isolinux.asm. I then had to write