similar to: 2 disks boot patch

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

Hi, I have an interesting question for you. Given the output of scramble(initrd) = S, I am interested in having [iso|sys|pxe]linux perform unscramble(S) = initrd before they load it into high memory. As a simple example, suppose scramble() were simply a XOR with a constant value of the gzip magic number at the front of the initrd image. I would like to insert the following, but I can't seem

Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G

Hello, pxelinux does not has any password protection, unfortunately my Assembler skills are not that good to extend pxelinux with a global password option. Nevertheless this feature is important, because not every user should have the right to startup an installation of a machine over network. The following patch is only a dirty hack, but other might find it usefull too.(so I post it here) It

Hello List, I have below a patch (against Syslinux-1.62), which adds a pseudo-kernel 'swap' which swaps device numbers of the boot device and the first harddisk. It was made for a system equipped with a DiskOnChip (www.msys.com) device which 'steals' the device# of teh first harddisk, This patch is used to enable the syslinux on the DoC to continue booting from the harddisk as if

Hi all! It's my first message on this ML. I just installed Fedora Core and I had a small problem... kernel + initrd do not fit in a 1.44 disks... I looked at documentation and at code (kernel.inc) and I saw that syslinux - load kernel - load initrd - boot kernel So perhaps a small workaround for above problem should be to add a configuration to initrd (ie initrd=@initrd.img) to just ask to

Well, there are some issues about adding code to syslinux. Mainly there are no space to add code. I propose to move data to 0000:F000 (now in 0000:5000) and font data to 0000:5000 (now at 0000:E000). So we have additional 4K to code. I don't understand however why we have to retain font data... Does EGA card read from system memory all the time?? I don't think so... Perhaps it's better

Hello Peter, The attached patch contains three small (although 2 of them are fundamental :) fixes for pxelinux 1. Alignment error when more than one initramfs are loaded using initrd - the alignment of the last disk is discarded in calculations but is ALWAYS present when the loading procedure is called. As a result - the second image (cpio) is not recognized. 2. On some platforms

Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the

I have released SYSLINUX 2.04, mostly to address the 2.03 MEMDISK bug. At the same time I'm getting the PXELINUX blksize and SYSLINUX installer changes out there, which hopefully is a good thing. New release mostly to address the MEMDISK corruption issue. Changes in 2.04: * ALL: Reclaim even more low memory by observing that comboot_seg == real_mode_seg is perfectly fine,

Hello Dear experts, I am new to Ruby on Rails. Though I want to access to MSSQL 2005 from ruby. I installed tiny_tds using following commands: >sudo apt-get install freetds-dev >gem install tiny_tds And now when I executed @client = TinyTds::Client.new( :username => ''username'', :password => ''password'', :host =>

From: Sylvain Gault <sylvain.gault at gmail.com> Some linker scripts were splitted into i386 and x86_64 versions in commit d8eede3f2a360163235fad222a0190cd7c5bef38 but older scripts were left there. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- core/syslinux.ld | 414 ------------------------------------------------ core/x86_64/syslinux.ld | 389

From: Tom Lendacky <thomas.lendacky at amd.com> As part of the GHCB specification, the booting of APs under SEV-ES requires an AP jump table when transitioning from one layer of code to another (e.g. when going from UEFI to the OS). As a result, each layer that parks an AP must provide the physical address of an AP jump table to the next layer via the hypervisor. Upon booting of the