For anyone wanting to boot an .ISO with MEMDISK: http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref s/heads/memdisk-iso NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a MEMDISK will not magically find the MEMDISK image in RAM and use it as a CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in the field, but that might change someday. NOTE: DOS is happy. NOTE: An .ISO which itself loads a ton of stuff into RAM will effectively use twice as much RAM; once for the .ISO, then again for what gets loads from the .ISO into RAM for the to-be-booted OS. H. Peter: If you feel like reviewing/merging, could I request that you cherry-pick the commits instead of merging? That would help me to identify bugs in the future. Thanks! Enjoy! - Shao Miller
On 08/03/2009 08:01 PM, Miller, Shao wrote:> For anyone wanting to boot an .ISO with MEMDISK: > > http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref > s/heads/memdisk-iso > > NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a > MEMDISK will not magically find the MEMDISK image in RAM and use it as a > CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in > the field, but that might change someday. > > NOTE: DOS is happy. >Depends on the DOS image. Using something like ELTORITO.SYS it'll work (or an ISO with disk emulation.) However, there are a lot of DOS out there that use an ATA driver + MSCDEX.> NOTE: An .ISO which itself loads a ton of stuff into RAM will > effectively use twice as much RAM; once for the .ISO, then again for > what gets loads from the .ISO into RAM for the to-be-booted OS. > > H. Peter: If you feel like reviewing/merging, could I request that you > cherry-pick the commits instead of merging? That would help me to > identify bugs in the future. Thanks!That's a bit of a strange request? Normally a merge would be a lot better. If you want a clean string of commits, you probably want to produce a rebased branch for me to merge instead... -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
Op 20090803 om 23:01 schreef Miller, Shao:> For anyone wanting to boot an .ISO with MEMDISK: > > http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=refs/heads/memdisk-isoCurrently that yields a 403 error. Which URL to use to `git clone` it? Cheers Geert Stappers -- On behalf of the archive readers: Thank you for replying below the text
Op 20090920 om 09:10 schreef Geert Stappers:> Op 20090803 om 23:01 schreef Miller, Shao: > > For anyone wanting to boot an .ISO with MEMDISK: > > > > http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=refs/heads/memdisk-iso > > Currently that yields a 403 error. > > Which URL to use to `git clone` it? >Sorry about the outdated git URI for MEMDISK-ISO. The proper git URI is now: http://git.etherboot.org/?p=people/sha0/syslinux.git;a=shortlog;h=refs/heads/memdisk-iso - Shao Miller
Op 20090920 om 22:31 schreef Miller, Shao:> Op 20090920 om 09:10 schreef Geert Stappers: > > > > Which URL to use to `git clone` it? > > Sorry about the outdated git URI for MEMDISK-ISO. The proper git URI is > now: http://git.etherboot.org/?p=people/sha0/syslinux.git;a=shortlog;h=refs/heads/memdisk-iso$ git clone http://git.etherboot.org/?p=people/sha0/syslinux.git;a=shortlog;h=refs/heads/memdisk-iso Initialized empty Git repository in /tmp/syslinux/.git/ fatal: http://git.etherboot.org/?p=people/sha0/syslinux.git/info/refs download error - The requested URL returned error: 403 Stappers
> For anyone wanting to boot an .ISO with MEMDISK: > > http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shor > tlog;h=ref > s/heads/memdisk-iso > > NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted > from such a MEMDISK will not magically find the MEMDISK image > in RAM and use it as a CD without a MEMDISK driver. There > are currently 0 MEMDISK drivers in the field, but that might > change someday.If anyone is contemplating booting a WinPE ISO using memdisk-iso, I have tried it and it works if I append "raw", example: KERNEL mdiso APPEND iso raw initrd=images/install/winpe_amd64.iso "mdiso" is memdisk renamed. Since WinPE can be booted over PXE without using memdisk-iso, the above might seem redundant. However, when using Microsoft's method of booting WinPE over PXE, you are limited to one BCD file (path and name hard coded in binary file), which means that if you want/need to boot several WinPE versions you can't separate them in the PXELINUX menu. Using memdisk-iso, separating and optionally password protecting selected WinPE images is trivial. Cheers, Daniel