Jump to content

- - - - -


  • Please log in to reply
102 replies to this topic

#101 erwan.l


    Gold Member

  • Developer
  • 2249 posts
  • Location:Nantes - France

Posted 13 January 2018 - 01:00 PM

@erwan.l: There are like a gazillion softwares out there that can create an ISO. So I really have to ask:


Why another? What makes your program unique/special? What does it do better than the rest?


I just don't see a need in flooding the software market with yet another whatever that does pretty much the same thing that others already do perfectly fine. Unless, of course, there is something better about yours.


Just asking.....


My criterias :

-be freeware

-offers a GUI (for users who dont want to fiddle with/remember lengthy/complex command line)

-supports as many windows version as possible

-supports multiboot

-uses windows builtin features (i.e does not require a 3rd party library or executable)


I may be wrong but I am not sure there are actually gazillions of softwares matching these criterias.

A few may be.

You would be surprised actually to find out that there are very few "friendly" freewares that support multiboot.


Why another?

-To bring some interesting discussion onto reboot.pro (like the one around isolinux) and possibly customize it to this community's need (by linking it to other ongoing projects/discussions)

-for my own selfish fun


What does it better than the rest?

This is not how I approach life :)


As for flooding the software market?

This is only me releasing a freeware on reboot.pro : I dont advertise it anywhere else as I dont have any claims.


By the end, all we do, all we say, may have already been done or said somewhere else.

Does it mean we shall not say/do it again for the sake of possibly bring some more interesting discussions?

I believe this is what reboot.pro is about : "freely explore" :)

#102 ady


    Frequent Member

  • Advanced user
  • 155 posts

Posted 13 January 2018 - 03:13 PM

@Erwan and Wonko,

Syslinux.efi does not understand ISO9660 (not at the moment, at least; it might never get there).

At the moment, the bootloaders of the Syslinux family know how to access only their own volumes. There has been some initial development towards having access to multiple volumes (and multiple disks), but not _that_ much.

As I said, booting optical media in UEFI mode by means of syslinux.efi could be done, by cheating a "bit".

First, create either a floppy or hard disk image containing the _default_ path(s) for UEFI applications. The respective syslinux.efi files and their respective modules would populate such image. This procedure is equivalent/similar to building such images for/with GRUB2 (or any other UEFI application) for UEFI-booting optical media.

The UEFI specs establish that the bootloader should use the El Torito "no emulation" mode (eventhough the boot catalog is pointing to a floppy or hard disk image containing a UEFI application in the standard default path).

Now, here is the cheating "bit": instead of following the UEFI specs by selecting "El Torito no emulation" mode for UEFI boot, you need to choose one of the floppy or HDD emulation modes (depending on the type of image you built).

Although this "cheat" would achieve the goal of booting the optical media in UEFI mode (that is, if the specific UEFI implementation doesn't care/complain about using the "emulation" mode), syslinux.efi is capable of accessing the boot volume only (i.e. either the floppy image or the partition within the hard disk image, not the ISO9660 filesystem they "live in").

The case I am describing here would/could be one potential excuse for ISO-building tools to accept non-typical "superfloppies" as images for El Torito "floppy emulation" modes (as opposed to strictly accepting 1.2/1.44/2.88 floppy images, whereas other sizes would be rejected, or even crash with).

IMHO, there are still too many limitations for syslinux.efi, but, if someone wants to use it for booting optical media in UEFI mode, it is not completely impossible.

Please note: The procedure I just described is for optical media and/or ISO9660; please do not confuse this procedure, nor syslinux.efi's capabilities, with _extracting_ the _content_ of an ISO image onto a different storage device (such as USB disks/drives) that uses FAT.

#103 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14075 posts
  • Location:The Outside of the Asylum (gate is closed)

Posted 13 January 2018 - 05:53 PM


Thanks for the "cheat" mode :).


I believe however that even the largest possible superfloppy wouldn't be enough to boot any recent Windows, but maybe it could contain *something* else that could act as "bridge", otherwise the "Hard Disk emulation" is the only possibility.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users