similar to: Booting a bootable CD-ROM

Hello, I am working on a legacy BIOS extension that is used to provide a centralised and managed boot process for a secure environment. Due to an assortment of reasons the access to hard disk / CD-ROM devices has had to be implemented at a low level (reading/writing IDE controller registers) rather than relying on the int 13h services provided by the system BIOS. Booting hard disks is working

H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two

To elaborate a little further.... The code that currently does the following is executed as part of a replacement for the BIOS interrupt 19h bootstrap process. 1) Issue an ATAPI command to read sector 11h 2) Use the value at offset 47h to read the validation entry and initial section entry 3) Use the loadrba value from the initial section entry to read the first sector of

The previous MEMDISK El Torito code merge did not actually work without this. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca> --- memdisk/setup.c | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git a/memdisk/setup.c b/memdisk/setup.c index 40f3f8c..5a45f39 100644 --- a/memdisk/setup.c +++ b/memdisk/setup.c @@ -338,6 +338,7 @@ struct geometry

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

Whoops, apologies. The intent was to send this email to ipxe-devel. I'll repost to that list. On Mon, Jan 23, 2017 at 10:12 AM, Shao Miller <ipxe at sha0.net> wrote: > On 1/23/2017 09:17, Rick Miller via Syslinux wrote: > >> Hi all, >> >> I currently use iPXE to load memdisk and, subsequently, a FreeBSD disk >> image to perform an OS installation to

On 7/7/2013 23:37, Patrick Verner wrote: > On Sun, Jul 7, 2013 at 10:25 PM, Shao Miller <sha0.miller at gmail.com > <mailto:sha0.miller at gmail.com>> wrote: > > On 7/7/2013 21:25, Patrick Verner wrote: > > On Sun, Jul 7, 2013 at 6:11 PM, Shao Miller > <sha0.miller at gmail.com <mailto:sha0.miller at gmail.com> >

What about using linux.c32?? It has some special initrd features, which someone has very kindly documented: ? http://www.syslinux.org/wiki/index.php?title=Linux.c32 Shao Miller Synthetel Corporation W: https://www.synthetel.com

I looked into Linux.c32 and added that to my setup.menu file. LABEL Install Windows MENU LABEL ^Install Windows COM32 linux.c32 APPEND wimboot initrdfile=Windows7SP2/bootmgr,Windows7SP2/boot/bcd, Windows7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim Now it boots so I have the installation startup page, but when I start the installation I get where I should "select the driver to

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

On 7/7/2013 21:25, Patrick Verner wrote: > On Sun, Jul 7, 2013 at 6:11 PM, Shao Miller <sha0.miller at gmail.com > <mailto:sha0.miller at gmail.com>> wrote: > > On 7/6/2013 09:20, Patrick Verner wrote: > > Same CD. Any Linux distribution without the 5.X series boots on this > machine. We can use 4.06 and it boots just fine. It's not the >

Should be restored, now!? Sorry for the delay; thanks for your patience, folks. Shao Miller Synthetel Corporation W: https://www.synthetel.com

Good day to all. Since we've adopted Gary Tong's and Bart Lagerweij's ElTorito.sys (now modified by H. Peter Anvin and tiny changes from myself), I'd appreciate if anyone with more El Torito experience might criticize my comments below and advise as to how they might be wrong. Some of it is off-topic GRUB4DOS detail; safe to ignore. A bit of history: FDUBCD ("FreeDOS

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

On 2/24/2016 05:55, Gene Cumm wrote: > On Tue, Feb 23, 2016 at 1:38 PM, Shao Miller via Syslinux > <syslinux at zytor.com> wrote: >> I don't think the MySQL daemon is running. I'm looking around for someone >> who can help. - Shao > [...] > > Nicer clients can fold. I know GMail's web interface is but one example > I wonder if Mozilla Thunderbird

On 3/31/2016 00:35, Shao Miller wrote: > Good day, Tal. > > I doubt that threads exist or that they're very warranted in a pre-OS > environment. (Co-operative threads, maybe.) > > Having typed that, there is Lua support in lua.c32 and Lua has > co-routines... But I'm wrong, from time to time: http://git.zytor.com/syslinux/syslinux.git/commit/?id=884e5778 > -

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

On 2/24/2016 08:02, Pete Batard via Syslinux wrote: > The variable 'ok' is never used and generates a warning. Remove it. Also > ntfssect.c is designed to be compiled in non Unicode mode when using > MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use > of 'A' API calls) so that it doesn't break when compiled in Unicode > mode, which is

On 8/4/2017 17:04, Bret Schuhmacher wrote: > This is kind of related to my other question about putting extra data > on the disc after the bootable ISO image... I want to write a bootable > ISO and include some extra stuff on it... the hash and some customer > data. The idea is that when the disc is booted from, this preboot > program calculates the hash of the ISO *only*,

On 8/4/2017 12:44, Bret Schuhmacher via Syslinux wrote: > I see there's a memtest on the Linux discs I've created... would it be > possible to put another program in place (a module, perhaps?) that can > calculate a hash using a certain algorithm (i.e. SHA512 or similar) to > validate and print out the hash of the boot ISO before booting it? The > integrity of the ISO is