search for: boot_sectors

After commit 036fa4e1a8aefeba3, shouldn't bsCodeLen be adjusted to reflect added fields at the end ? Basically: -#define bsCodeLen (offsetof(struct boot_sector, bsSignature) - \ +#define bsCodeLen (offsetof(struct boot_sector, bsMagic) - \

Hi all, I use XP on my laptop PC, with 30 GB HD (single partition), and a 3.5" hard drive (not a stick), accessed through a USB encasing, partitioned as five logical drives. I have successfully set up syslinux to boot several Ubuntu versions from the primary USB hard drive partition, and no problems there. The problem is, I would like to have an entry in the menu, like "Boot from

..._CD-ROM_controllers > I am sure some additional development muscle is very welcome and > needed I feel apt for ISO 9660 related issues, up to isohybrid with MBR, GPT, and APM. My boot knowledge is collected at http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt Have a nice day :) Thomas

...0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 My own cheat sheet: https://dev.lovelyhq.com/libburnia/libisofs/blob/master/doc/boot_sectors.txt says: --------------------------------------------------------------------- ... Apple Partition Map (APM) ... Sources: http://mjg59.dreamwidth.org/11285.html http://opensource.apple.com/source/IOStorageFamily/IOStorageFamily-116/IOApplePartitionScheme.h (type...

.../mjg59.fedorapeople.org/Fedora-LiveCD.iso Matthew advised it to me at his article "Anatomy of a Fedora 17 ISO image" http://mjg59.dreamwidth.org/11285.html The current state of my emerging description is at http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt Newly emerging is the chapter "SYSLINUX isohybrid for UEFI and x86-Mac". Comments, hints, bug reports are welcome. Have a nice day :) Thomas

...00 00 00 00 00 00 00 00 > > 16 : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > My own cheat sheet: > > https://dev.lovelyhq.com/libburnia/libisofs/blob/master/doc/boot_sectors.txt > > says: > --------------------------------------------------------------------- > ... > Apple Partition Map (APM) > ... > Sources: > http://mjg59.dreamwidth.org/11285.html > http://opensource.apple.com/source/IOStorageFamily/IOSto...

...one with the needed > Perl skills stepped up and volunteered to maintain the Perl version, > at least to port bugfixes from the C version? I am willing to explain what is unclear about above options. Theory is in http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt intrigeri: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ Ian Bannerman: > Now I'm confused, if Tails is able to use the .pl for the purpose of > installing on OS X that would suggest it does have the EFI/Mac updates..? Seems to be Macs with BIOS support/emula...

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.

When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: wrlinux-image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Check the offset and call fseek() multi-times if offset is too large.

...... This error message stems from isolinux.bin, not from the MBR. So we really ended up in the running boot image program. The checksum is tested with all isolinux.bin starts. From CD too. It belongs to the Boot Info Table feature inside isolinux.bin (see "man mkisofs" or libisofs-*/doc/boot_sectors.txt): Byte Range | Value | Meaning ---------- | ---------- | ---------------------------------------------------- 8 - 11 | pvd_lba | Block address of the Primary Volume Descriptor. | | This is the session start LBA + 16. | | 12 - 15 | fi...

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

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch try to fix first stage of extlinux bootloader but have some problems with ADV Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- dos/syslinux.c | 2 +- extlinux/main.c | 36

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

Hi, i now realized that http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Geometry http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous are the new wiki sections by Gene Cumm. (Sorry for not reading them when they were announced.) So i ask especially him whether the statement "An examle is a drive of 128,64,32 with a partition ending at