similar to: [PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

From 8be8951015673d6279d7d49b0138645194317dc2 Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Wed, 9 Dec 2009 19:11:38 +0000 Subject: [PATCH] doc: document mBFT and "safe hook" --- doc/memdisk.txt | 40 ++++++++++++++++++++++++++++++++++++++++ 1 files changed, 40 insertions(+), 0 deletions(-) diff --git a/doc/memdisk.txt b/doc/memdisk.txt

For UBCD, we have a lot of config files. Isolinux will load /boot/isolinux/isolinux.cfg, which will load /ubcd/menus/syslinux/main.cfg Syslinux will load /boot/syslinux/syslinux.cfg, which will load /ubcd/menus/syslinux/main.cfg The /ubcd/menus/syslinux/main.cfg loads several other config files when you select the appropriate menu. From all those menus you can go back to

I tested the memdisk-acpi branch with following results: - Bochs The BIOS provides a RSDT. Available tables are RSDT, FACP, DSDT, FACS, APIC, SSDT. memdisk-acpi is able to hook the SSDT. - VMware The BIOS provides a RSDT and XSDT. Available tables are RSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*) and XSDT, FACP, DSDT(*), FACS(*), BOOT(*), APIC(*). Tables marked with an asterisk (*) are

Hello HPA, In the changelog for v.4.05: ifmemdsk.c32 was added, BUT com32/modules has only ifmemdsk.c , not the final binary, ifmemdsk.c32 . This is not the only module in such situation, but since it was explicitly added in the v.4.05 changelog... So, unless there is some reason not to, you should add ifmemdsk.c32 in com32/modules/Makefile . As of v.4.06-pre10, the issue is still not

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

Applies to Syslinux 4.06. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: nictype - Shao Miller ----- From 2764e260e12d9769e3b699e4213b9a164e64924a Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Thu, 22 Nov 2012 20:43:25 -0500 Subject: [PATCH] nictype.c32: PXELINUX module to display UNDI NIC bus

I know there's a module to check which syslinux bootloader was used, but is there also a module for detecting MEMDISK? Basicly I want to use the same isolinux.cfg for a CD which boots an ISO. Issue is that the inner ISO also uses same Isolinux (+ menu), which isn't very user-friendly. So: CD --> ISOLINUX (menu) --> MEMDISK CDROM.ISO --> ISOLINUX (menu) --> diskette

Applies to Syslinux 5.00-pre9. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: hexdump - Shao Miller From c9c67dd61ba0b11e46d514601cf0722e1b43017c Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Sun, 4 Nov 2012 00:26:32 -0400 Subject: [PATCH] hexdump.c32: Simple file hex-dumper Usage: %s

Hi, I've just pushed out a last -pre release before 4.06 final. The purpose of this prerelease was to make sure that all the build infrastructure is configured correctly and to ensure that the win installer problem is now gone (I've done the build on an F16 machine which should have a working mingw toolchain). Barring any major problems I'll do the final release this week. -- Matt

Hi I have a scenario where I need to test for whether I have booted via a syslinux ISO image in init-premount as opposed to (say) PXE boot. Is there any variable that I can test for this? thanks vk

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Syslinux 3.84 has been released. This is a mixed minor new features/minor bug fixes release. Changes in 3.84: * SYSLINUX: make the DOS installer work for MS-DOS 7.x/8.x (Win9x/ME) again. * HDT: updated to version 0.3.6 (numerous changes.) * mboot.c32: now supports video mode setting if requested by the image. * MEMDISK: Fix floppy images of

Syslinux 3.86 is out; it is a bug fix release. Syslinux 4.00, starting with Syslinux 4.00-pre38, is now officially in beta test. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.86: * chain.c32: fix chainloading the MBR of a hard disk (broken in 3.85). * mboot.c32: report the boot loader name in the information structure. *

Yes, MENU HIDE would work as well, but still requires additional entries for each case (possible entries for pxe, syslinux, isolinux, cpu architectures, PCI devices, lua scripting scenarios, etc.) By blocking modules, I meant that as long as I disable user editing of menu commands via ALLOWOPTIONS 0, I cannot use any of the following com32 modules without creating duplicate LABEL entries for each

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

Changes in 4.05: * HDT updated, and now supports uploading data to a TFTP server. * ISOLINUX: remove the .img file support; it has been broken on virtually all systems since the beginning, and has been totally broken since 4.00 at least. Use MEMDISK instead. * chain.c32: Support chaining ReactOS' FreeLdr (Shao Miller) * isohybrid: