similar to: mkisofs for Windows and 2 GB limitation

Only to inform that I've just released the version 1.2 of makebootfat. makebootfat is a GPL command line utility able to create bootable USB disks for Linux and Windows using the FAT filesystem and syslinux. As far I know it's the most advanced tool available able to make bootable USB disks. It's able to autodetect/partition/format/populate the USB disk in a single step without any

Only to signal that in version 2.10-pre5 the "Out of memory, better reorganize something..." message is commented out. This is a diff extract from 2.09 to 2.10-pre5 : diff -u syslinux-2.09/ldlinux.asm syslinux-2.10-pre5/ldlinux.asm --- syslinux-2.09/ldlinux.asm 2004-04-23 06:14:15.000000000 +0200 +++ syslinux-2.10-pre5/ldlinux.asm 2004-05-30 00:11:23.000000000 +0200 @@

This patch fixes ISOLINUX/SYSLINUX when using the kernel mem= option with a value greater than the effective memory on the system. At present, in this condition the kernel doesn't boot correctly. The default Linux behaviour (verified on 2.4.22) is to ignore this option if the BIOS reports less memory than the value manually specified. This patch force the same behaviour for ISOLINUX/SYSLINUX.

With the new 3.01 and 3.07 version I found a big slowdown booting from USB devices. On my PC it takes more than 2 minutes to load the kernel and the initrd filesystem. Compared with the previous behaviour of syslinux 2.13 with takes only 10 seconds or little more. The BIOS boots in FDD mode (DriveNumber variable is 0). I've also tried to disable the EDD support in the source. But the boot

Hi, I've a usb-key that boot regularly on a PC using syslinux 2.09; well, this PC (a thin-client) at the moment is the only PC that can boot from USB in my office... and it usually booted oretty well, without any hacks... After changed to syslinux 3.07, it stopped booting, showing a simple "BOOT ERROR" message, nothing more... Reverting to syslinux 2.09, it restarted to work...

Quick summary: Syslinux stops at "Boot failed". Which, from a quick look at the raw disk image, seems to indicate that the boot sector loads but it fails to load the .sys loader. The details: I've been trying to load Linux (or etherboot...or anything at all that is not NT embedded) into a set of Compaq Evo T20 48/64 for a while now. What I finally managed to do is using the

Hi all! I don't cnow where can i ask about this and I hope you can halp me. I have a digital voice recorder olymus ds-2300, it's working with *.dss files (digital speech standart). There is Olympus Dss Player for Windows but nathing can play it with linux. On olympus development homepage i found "Sound SDK for WIndows" but they don't wont to make it open. Please can you

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...)

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

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

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

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?