similar to: missing syslinux details/docs

Displaying 20 results from an estimated 1000 matches similar to: "missing syslinux details/docs"

2004 Dec 09
1
EDD error RE: Re: SYSLINUX 2.12-pre7 released
(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a
2014 Mar 04
2
6.03-pre6 minor building suggestions
In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,
2014 Mar 15
2
6.03-pre6 minor building suggestions
On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > In Syslinux 6.03-pre6: > > > > _ The txt/html/*.html files are currently created 3 times, one for > > each firmware. I think they should be created only once (under the > > main txt/html/ directory), just as the rest of the documentation is. > > In that case, the
2011 Dec 18
3
nopassany parameter causing trouble
I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks
2015 Oct 22
2
Isohybrid wiki page and UEFI
On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > confs) stored on a iso9660 media by genisoimage and its > -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't > work. I get a red screen with debug info (attached). However, I'm not >
2005 Sep 03
3
MSCDEX over NDIS ethernet
I would like to implement a replacement MSCDEX driver (based on the replacement in FreeDOS SHSUCDX http://johnson.tmfc.net/freedos/shsucdx.html and SYSLINUX) however instead of talking to disk BIOS calls or PATA chipset I would like it to talk to the NDIS driver and act as a TFTP client simply forfulling application get block requests through TFTP. Its not clear where the ISO9660 CD
2012 Jun 25
1
how to create bootable FreeDOS HDD or USB flash drive?
Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, > Unfortunately I get the error message: > isohybrid: slint64-14.1.iso: unable to find mac efi image This is probably due to El Torito Platform id "Mac" in -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ -eltorito-boot isolinux/macboot.img \ This caused in the image http://slint.fr/misc/MacBoot/slint64-14.1.iso platform id 1 with the third image. (I would
2015 Oct 25
2
Isohybrid wiki page and UEFI
> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux > ><syslinux at zytor.com> wrote: > > > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > >> confs) stored on a iso9660 media by genisoimage and its > >> -eltorito-alt-boot -efi-boot
2005 Jan 16
0
ElTorito from Floppy (was: Re: Can I use...)
a member of the FreeDOS project has transformed Smart Boot Manager into a COM32 module for Syslinux. Might be a bit more usefull than Syslinux -> memdisk -> imagefile -> Smart Boot Manager ( -> 'boot from cd -> cdrom ) I've inserted it into this diskette image: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta9sr1/fdos1440.img That's nice to
2014 Jul 29
1
isohybrid: slint64-14.1.iso: unable to find mac efi image
> HI, > > On 29/07/2014 22:23, Ady wrote: > > > Even without such "Mac" hardware at hand, it might still be helpful > > to test mkisofs 3.01a24 and then check the resulting ISO image. > > Perhaps Didier can update his current version of mkisofs and retry > > with his current scripts/receipts. > > I will upgrade the cdrtools package from
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI, On 29/07/2014 22:23, Ady wrote: > Even without such "Mac" hardware at hand, it might still be helpful > to test mkisofs 3.01a24 and then check the resulting ISO image. > Perhaps Didier can update his current version of mkisofs and retry > with his current scripts/receipts. I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the coming days and see what I
2015 Oct 25
0
Isohybrid wiki page and UEFI
Hello, Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux ><syslinux at zytor.com> wrote: > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 >> confs) stored on a iso9660 media by genisoimage and its >> -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't
2014 Nov 13
0
Boot fails in a VMware player VM - syslinux 6.03
> > Hi, > > On 11/11/2014 02:55, Ady wrote: > > Again, dd'ing your isohybrid image onto your (virtual or real) drive > > will fail to boot in EFI mode. Your "syslinux.efi-based" > > "/isolinux/efiboot.img" will not be capable of booting. This is one > > of the steps that corresponds to grub2, not to whichever other EFI > >
2013 Nov 15
2
Image checksum error while booting Isolinux
Hi, I am trying to build a custom installer for a popular linux distro on MacOS. Here is how: makehybrid \ -o isos/muaaa.iso temp/ \ -eltorito-boot temp/isolinux/isolinux.bin \ -no-emul-boot \ -iso -joliet -boot-load-size 4 \ -default-volume-name "Custom Installer" \ -eltorito-platform temp/isolinux/boot.cat This happens when I boot up the new image:
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
> Hi, > > > I don't understand why you say "*But* the El Torito...". I don't see > > a difference with what the mkisofs manual says. > > The manual announces "Mac" for Apple Mac. > The program obviously writes Platform Id 1 in this case. > The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". > In the sum this
2013 Nov 24
2
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB
2014 Mar 15
0
6.03-pre6 minor building suggestions
> On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > > > > In Syslinux 6.03-pre6: > > > > > > _ The txt/html/*.html files are currently created 3 times, one for > > > each firmware. I think they should be created only once (under the > > > main txt/html/ directory), just as the rest of the documentation
2010 Jun 19
0
ELTORITO.SYS, MEMDISK, MDISKCHK.COM Commits
H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
> Hi, > > > Unfortunately I get the error message: > > isohybrid: slint64-14.1.iso: unable to find mac efi image > > This is probably due to El Torito Platform id "Mac" in > > -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ > -eltorito-boot isolinux/macboot.img \ > > This caused in the image >