similar to: isolinux-3.70: Doesn't Load .BSS Images

Is there a practical reason that the NTLDR clause of the CHAIN module isn't operable under ISOLINUX ? The reason for my question is that I like the SYSLINUX suite over the alternatives, that is GRUB and BCDW, however these pkgs all can chainload (just about anything) from an ISO. That is, they can handle .BSS files and the various NT/XP boot files, like SETUPLDR.BIN, etc. I make/update

I was doing a laptop repair job today and needed to boot from a USB thumb drive, in order to free up the CD/DVD burner. Fortunately, the laptop to be repaired permitted one to boot from a USB thumb drive. However, there are still PCs out there that can't boot from a thumb drive (I have two), so I was wondering if it's pos to use the CHAIN module to boot from a thumb drive ? I looked at

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

Hello Recently I've been happily experimenting with syslinux, replacing grub and my old bootmanager. All works beautifully, but I have one question - in case of .bss bootsectors - what exactly and under what circumstances is patched in ? With syslinux used as main bootmanager - bootsectors from xp64, xp32 and [pre-syslinux] msdos 7.1 (98se) work perfectly fine when chainloaded natively as

My compliments on the release of syslinux-5.0 and happy holidays to the entire Syslinux team.? I have a longer message in me.? Lots of curiousity about the direction of the project, but that will have to wait until I finish my first 5.0 project (*not* my first Syslinux project), which just happens to touch past problems: drive enumeration. This particular effort is on a USB flash drive, with two

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

Hi, I would like to ask if there are any known issues with booting an ISOLINUX hybrid iso image from a USB Flash Drive on older Dell PC's (i.e. P4 2.2GHz). I've tried several that one should just be able to write to UFD and boot, but they all fail on my hardware. I get "isolinux.bin missing or corrupt" message on screen. This function would be very convenient for me, so

Hi - I've attached a patch to make the assembly parser recognise the .bss directive on Darwin targets as a switch to the (__DATA,__bss) section. The ELF & COFF assembly parsers already recongnise the .bss directive. I've added a test case for it too. Thanks - Nick -------------- next part -------------- A non-text attachment was scrubbed... Name: bss.patch Type:

I believe it's a feature missing in MC - https://github.com/opensource-apple/cctools/blob/4da58fd2fc026317ed9e9ef1feabf21ed0bb7a81/cctools-836/as/i386.c line 539 adds support for the .bss directive if certain variables are defined, and mainline gas supports it on all ARM targets: https://sourceware.org/binutils/docs/as/ARM-Directives.html . Supporting the directive on all Darwin targets could

Is this an extension to what cctools' assembler provides or a missing feature in MC? On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com> wrote: > Hi - I've attached a patch to make the assembly parser recognise the > .bss directive on Darwin targets as a switch to the (__DATA,__bss) > section. The ELF & COFF assembly parsers already recongnise the .bss

LGTM On 29 September 2013 06:08, Nicholas White <n.j.white at gmail.com> wrote: > I believe it's a feature missing in MC - > https://github.com/opensource-apple/cctools/blob/4da58fd2fc026317ed9e9ef1feabf21ed0bb7a81/cctools-836/as/i386.c > line 539 adds support for the .bss directive if certain variables are > defined, and mainline gas supports it on all ARM targets: >

On Mon, Apr 24, 2017 at 2:53 PM, Friedman, Eli <efriedma at codeaurora.org> wrote: > On 4/23/2017 10:10 AM, Andrew Kelley via llvm-dev wrote: > >> Here is a module: >> >> @vals = internal unnamed_addr global [20000000 x i32] undef, align 4 >> >> LLVM puts the global in the .data section, and results in a 77MB .o file >> of mostly zeroes. Why does

Hello, I noticed that the SPU assembly printer prints just ".bss", when gas requires ".section .bss". Now the gas prints out: Assembler messages: Error: expected symbol name Attached is a test case and a patch to fix this. (This time 'make check' passes also ;) kalle -------------- next part -------------- A non-text attachment was scrubbed... Name: spu_bss.patch

Here is a module: @vals = internal unnamed_addr global [20000000 x i32] undef, align 4 When I compile it into an .o file: $ clang -c test.ll $ objdump -t test.o test.o: file format elf64-x86-64 SYMBOL TABLE: 0000000000000000 l df *ABS* 0000000000000000 test.ll 0000000000000000 l O .data 0000000004c4b400 vals LLVM puts the global in the .data section, and results in a 77MB .o file

Hello, I'm Rene living in Germany. I have a problem when I use syslinux versions greater than 3.xx for booting DOS (over dos.bss) and DSL-linux from a hard disk. (I've tried version 3.11 and the newest 3.36). The problem occurred after booting DOS - I can not access to the ordinary 3.5'-floppy drive (e.g. the command "dir a:" fails after a while). DOS not even notices

Hi, I am writing a function that clears the BSS section on an Cortex-M4 embedded system. The LLVM (version 3.7.0rc3) code I had wrote is : ;------------ target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64" target triple = "thumbv7em-none--eabi" @__bss_start = external global i32 @__bss_end = external global i32 define void @clearBSS () nounwind { entry:

I'm working on a debugging/diagnostic image in order to debug/diagnose an issue with very recent machines using a UFD (USB Flash Drive) which really _should_ be partitioned but someone decides to be a little too quick and uses it raw. (FAT* file system on /dev/sdb rather than /dev/sdb1). Anyways, I've got a successful first iteration that'll say what the BIOS thinks about geometry and

Hello, Is it possible for syslinux to boot from a different partition ? I have a UFD with 2 partitions. The first one is fat32 and the second one is a squashfs. I have the OS files in the squashfs partition. As the syslinux won't boot from a squashfs partition, I thought of creating a fat32 (first partition) and install syslinux in it. If I do that, is it possible to configure syslinux to

Basic support for Small bss and data. The rest is implemented with target specific logic and will be commited as soon as it's ok to commit this patch. -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative." -------------- next part -------------- A non-text attachment was scrubbed... Name: smallsections.patch

Hi, On SPU, variables in the .bss section that are allocated with the .lcomm directive are not aligned on 16 byte boundaries. This causes misaligned loads, as the generated assembly assumes this "default" alignment. A patch to disable .lcomm in favour of '.local .comm' is attached. kalle P.s. As an example, the following function returns '3', when '5' is