<HTML>
<STYLE>
<!--
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }
-->
</STYLE>
<B>On Thu 11/11/10 6:06 PM , Michael Brown mbrown@fensystems.co.uk sent:<br>
</B>
<BLOCKQUOTE style="BORDER-LEFT: #5167c6 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">On Thursday 11 Nov 2010 17:24:29 <A href="javascript:top.opencompose('carlyoung@keycomm.co.uk','','','')">carlyoung@keycomm.co.uk</A> wrote:<br>
<SPAN style="COLOR: #666666">> I disabled the VMware E1000 gPXE BIOS and booted from ipxe.iso and</SPAN><br>
<SPAN style="COLOR: #666666">> the boot sequence (from 1.0.1+ GIT obtained source) does go into</SPAN><br>
<SPAN style="COLOR: #666666">> autoboot OK with appropriate boot server type specified in the DHCP</SPAN><br>
<SPAN style="COLOR: #666666">> discover frame.</SPAN><br>
<br>
OK, glad to know it does what I expect!<br>
<br>
<SPAN style="COLOR: #666666">> I want to verify this via a boot ROM. Can someone help me create an</SPAN><br>
<SPAN style="COLOR: #666666">> iPXE 1.0.1 Intel E1000 ROM BIOS of 65536 bytes as ESX is choking on</SPAN><br>
<SPAN style="COLOR: #666666">> it as it is 68,608 bytes as built on a Suse 11 machine. Could I</SPAN><br>
<SPAN style="COLOR: #666666">> remove an object file, etc?</SPAN><br>
<br>
Disabling AoE and iSCSI (by uncommenting the lines<br>
<br>
#undef SANBOOT_PROTO_ISCSI<br>
#undef SANBOOT_PROTO_AOE<br>
<br>
in config/general.h) will give you a substantially smaller ROM, if you don't <br>
need SAN booting support.<br>
</BLOCKQUOTE>
<P>That managed to create a much smaller ROM, but now is less than 65536 bytes. I'm just going to pad the end with NUL's - shouldn't be any issues with that should there? Is there a way to do this from the build or should I just do it from the shell? </P>
<P>Carl</P><BR></HTML>