<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
The only workaround I can think of is gPXE booting a stripped down Win/WinPE that boots directly into your linux.iso through virtualization software. Then Windows took care of the hooking and linux did not know it was actually running in ram. It would of course add substantially to the boot time and required ram, and may not be very easy to configure quickly. If it was for installing linux locally, then it would be pointless. Very likely no one would bother with this, at least I can't think of any good reason (except for the fun of testing and verification).<BR>
<BR>
At least it works with vmware.<BR>
<BR>
Joakim Schicht<BR> <BR>
<HR id=stopSpelling>
Date: Fri, 14 May 2010 15:24:27 -0700<BR>From: lucarx76@gmail.com<BR>To: Shao.Miller@yrdsb.edu.on.ca<BR>CC: gpxe@etherboot.org<BR>Subject: Re: [gPXE] gPXE booting an .iso image<BR><BR>Oh ok, thanks a lot.<BR><BR>So there is no way to gPXE a Linux .iso image yet, right?<BR><BR>Thanks,<BR> Luca <BR><BR>
<DIV class=ecxgmail_quote>On Fri, May 14, 2010 at 3:21 PM, Miller, Shao <SPAN dir=ltr><<A href="mailto:Shao.Miller@yrdsb.edu.on.ca">Shao.Miller@yrdsb.edu.on.ca</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=ecxgmail_quote style="PADDING-LEFT: 1ex">Good day Luca,<BR><BR>There is not yet a MEMDISK driver for Linux, so your .ISO file in RAM<BR>will not be available when Linux is running. Linux doesn't use BIOS INT<BR>13h for disk access, which is what MEMDISK hooks.<BR><FONT color=#888888><BR>- Shao Miller<BR></FONT></BLOCKQUOTE></DIV><BR> <br /><hr />Få nye Windows Live™ Messenger. <a href='http://download.live.com/messenger' target='_new'>Last ned her.</a></body>
</html>