similar to: isohybrid --uefi - resulting EF00 partition too small

In message <52D90648.4010900 at mattiasschlenker.de>, Mattias Schlenker <ms at mattiasschlenker.de> wrote: >I would be personally interested in the following experiment: > > 1. Download this LessLinux test build: > http://download.lesslinux.org/testing/lesslinux-search-and-rescue/lesslinux >-search-and-rescue-uluru-20140107-193740.iso > 2. dd it to the 8GB thumb

Hi, > I have no reason whatsoecer to even vaguely > suspect that any of the various USB stick I have here are in any way > defective. Yeah. But can that "8GB Patriot" show the failure when you put one of originally failing systems onto it ? You mentioned Clonezilla, UBCD, OpenELEC. > Anyway, I did fetch the file [Ady's FAT32 image], > unzipped it, and then dd'd

Hi, > # Most linux distros dont have `mkisofs' Or they have genisoimage under the name "mkisofs". (e.g. Debian, Archlinux) > mkisofs \ > -o output.iso \ > -no-emul-boot \ > -boot-info-table \ > -boot-load-size 4 \ > -c isolinux/boot.cat \ > -b isolinux/isolinux.bin \ > ISO_root I would add option -R or -r for Rock Ridge names and file

Am 17.01.2014 11:03, schrieb Thomas Schmitt: > The only plausible theory in my mind would be that one of your USB > sticks does not work well with that single mainboard. But if the > Patriot can fail or succeed at will, then i am clueless. Might have to do with drive geometries? Some boards might fail if the C/H/S entries do not indicate a LBA medium. This would explain why all

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477

In message <49973.1389992217 at server1.tristatelogic.com>, I wrote: > >In message <52D90648.4010900 at mattiasschlenker.de>, >Mattias Schlenker <ms at mattiasschlenker.de> wrote: > >>I would be personally interested in the following experiment: >> >> 1. Download this LessLinux test build: >>

Am 18.01.2014 04:30, schrieb Ronald F. Guilmette: > The results were the same in both cases. In both cases, LessLinux > Search & Rescue booted up and began a timed 10 second countdown, which > I allowed it to finish in each case. After that, it started to do > something... I'm not even sure what, exactly... and eventually froze > up while displaying a progress bar,

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

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 -

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

> > It looks like Clonezilla and Ultimate Boot CD both prescribe > special installation procedures for USB stick. > isohybrids can be put onto stick just by e.g.: dd of=/dev/sdb > Make a backup of the stick if you later want to restore its > partitioning. > The (recent yet not latest) versions of Clonezilla that used Syslinux 5.xx will fail in some systems when writing

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

Hi, Ady wrote: > * ISO images, > * burnt to _optical media_, > * and using then the resulting _optical media_ to boot in _UEFI mode_, > * in which the _main bootloader_ for such _optical media_ booting in > such _UEFI mode_ is part of The Syslinux Project. I would be willing to try such an ISO with qemu+OVMF. Regrettably my real test iron has no EFI firmware. Do you know the

> 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

In message <BLU0-SMTP218A5F5400BB0FCA0312DC28BA70 at phx.gbl>, Ady wrote: >By adding technical details, it makes it harder for a non-technical >user to follow, and such user will probably go away looking for a >simpler answer. Yes. >If a user doesn't know what "create a new DOS partition table" means, >there are many ways to find out, including a web

Hi, i'm possibly not the best source of general SYSLINUX knowledge, as my interest in it is only with my xorriso hat on. (As you can see in the SYSLINUX wiki, xorriso can do the isohybridization without the need for the isohybrid program.) Fulalas Caos wrote: > I tried this: > mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \ > -V