similar to: problem with isolinux or mkisofs?

Hello, I want to modify isolinux.cfg of a given, bootable iso (of Linux CentOs installation) according to my needs. The things is : I copy the contents of that iso to a different directory. I modify the isolinux.cfg according to my needs. Then what? I had of course googled for it. I had tried afterwards: mkisofs -o centos1.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-i But

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

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

[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

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

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

hi, i'm doing my own windows multiboot dvd's using latest ultraiso and isolinux 3.09, and everything was fine till now. now i tried 3.11 and this release doesn't load any windows cd boot sectors while other stuff like memtest works fine. same for isolinux 3.10, both the normal and the debug version. the attachment shows a vmware 5.5 beta window with an error message by isolinux 3.11

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?

i tried to make a bootable CD with isolinux,but met some problem. the error is as follows. i don't know what cause the problem. anyone met the same problem? thanks for help. ===================================================================================== mkisofs 1.13 (i686-pc-linux-gnu) Scanning . Scanning ./boot Scanning ./isolinux Scanning ./isolinux/help Excluded by match:

Hello, i'm just curious, why the -boot-load-size 4 for mkisofs with isolinux.bin is needed. I searched the list archive and found nothing and found nothing anywhere else. Since the isolinux.bin is much bigger than 4 * 512 byte, I'd suspect, it wont get completely loaded. With -boot-load-size 4, mkisofs reports: Size of boot image is 4 sectors -> No emulation Without it, mkisofs

> 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

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

Greetings, I have been using isolinux with Microsoft's cdimage.exe for my Utility / Preinstallation cds. I just upgraded from 3.36 to 3.55 and found it to be non functional. I didn't use the -debug version, it just hangs at the version banner. I went through several previous versions, and it appears that 3.50-pre23 is the last working version. I didn't see anything between that

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 -

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 also booting in hard disk mode (qemu -hda core.iso -bios uefi.fd). Le mercredi

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)

Hello List, I have used isolinux for years without problems. Recently I decided to upgrade from 3.09 to 3.11. Every CD I create can be read on my Vectra (Pentium 3) and all other Pentium 3 boxes, but all my Pentium 4 boxes will not boot (they ignore the CD and boot from hard disk). The bochs VM will boot the CDs fine just like the Pentium 3 machines. I have tried 3.09 (which worked

I'm having a problem booting Slackware 10.1 boot CD's as well as an isolinux image of my own. The system is a VIA Epia M10000 and the drive is an AOpen ISU-8424E CD/DVD writer. If I use a Toshiba CD-RW/DVD-ROM Drive SD-R2612 in place of the AOpen DVD writer, the cd boots fine and everything works as expected. What's the best course for further debugging of this problem? The only

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the