MEMDISK El Torito emulation has been merged into Syslinux' 3.84-pre4 development branch, meaning MEMDISK El Torito users can benefit from all the other fixes/enhancements which H. Peter Anvin (and possibly others) has (or have) committed to MEMDISK "proper." Two recent commits deal with PC-DOS and the PloP boot-loader .ISO, by the way. Enjoy.http://git.zytor.com...x.git;a=summary
now that is an excellent improvement . thanks a lot icecube for the head up .
im wondering if i can use this MEMDISK with G4D and syslinux at the same time ? well i guess i can .
Yes. MEMDISK and GRUB4DOS both install INT 13h "hooks". These hooks typically keep track of the previous hook, so you end up will a pile of hooks. You can hook to your heart's content, or until you run out of available memory.
MEMDISK only does RAM disk mapping at this time. GRUB4DOS does RAM disk mapping as well as mapping to a contiguous range of sectors on another device.
ice cube , i was wondering if u have tested ram based live xp iso with syslinux yet ?
i mean with memdisk approach..
If the OS uses INT 13h to access its boot disk, MEMDISK will provide this service. OSs like XP and Linux do not use INT 13h, so you need a special driver to look for whatever RAM disk that was setup by MEMDISK. I'm developing WinVBlock to accomplish this, but ISO support is not there yet. karyonix has developed Firadisk, but as far as I know it only works with GRUB4DOS.
Just tried LiveXP_RAM.iso (50Meg cab compressed Boot Cd created with the BootSDI script) and it booted OK.
Please note that when you load an .ISO into RAM as a RAM disk, you need enough memory for the image.
When you're booting an XP which itself
loads a RAM disk, then you need enough additional
RAM for this "sub-image". Drivers like WinVBlock and Firadisk help to avoid this redundancy by allowing the OS to find the original RAM disk.
Do you know of any examples in getting the Etherboot PXE (gPXE) images to work with the memdisk ISO version? tftp is very slow and the http functionalities of the Etherboot images offer a great way to circumvent this for large ISO files.
From the gPXE CLI, you do:
chain http://webserver/memdisk-iso iso
where the chain
command is given the path to your El Torito-capable MEMDISK and also given iso
as a "kernel command-line argument." The above commands can go into a gPXE script, also. See ROM-O-Matic and the gPXE Wiki pages for command-line and script reference material.
You could also chain to PXELINUX from gPXE, if you are more comfortable with PXELINUX' familiar config-files. Some folks are not aware that fairly recent ( >= 3.70) PXELINUces can use HTTP when booted from gPXE. Simply use http://webserver/somefile
-style file paths in your config-files.
As noted in another post, gpxelinux.0
undionly.kkpxe (gPXE) -> pxelinux.0 (PXELINUX)
So you simply drop in gpxelinux.0
where you used to use pxelinux.0
and you should have HTTP abilities.
Doesn't seem to work with XP images. Anyone have this working yet?
... And where does it fail, exactly? Please include detail in reports of this nature. As mentioned in a recent post, you need a driver for an OS like XP. Without one, you will either get a Blue Screen of Death or you will have to use XP's /RDPATH=
functionality and load a second RAM disk image (meaning a greater memory requirement.)
- Shao Miller