Differences

This shows you the differences between two versions of the page.

--- embed [2011/12/02 21:42]
mcb30
+++ embed [2012/03/15 10:41]
mcb30
@@ Line 53: / Line 53: @@
     initrd myscript.ipxe
-This uses a standard version of the iPXE binary ''ipxe.lkrn''.  You can change the embedded script by editing the ''myscript.ipxe'' file, with no need to rebuild the iPXE binary.  The ''myscript.ipxe'' file is a plain iPXE script file; there is no need to use a tool such as ''mkinitrd''.
+This uses a standard version of the iPXE binary ''ipxe.lkrn''.  The ''myscript.ipxe'' file is a plain iPXE script file; there is no need to use a tool such as ''mkinitrd''.
+You can change the embedded script by editing the ''myscript.ipxe'' file, with no need to rebuild the iPXE binary.
 This method works only with iPXE binary formats that support an initrd, such as ''.lkrn''.
@@ Line 59: / Line 61: @@
 ===== The "Press Ctrl-B" prompt =====
-When you embed a script, you will no longer see the "Press Ctrl-B for the iPXE command line" prompt at startup or if booting fails.
+When you embed a script, you will no longer see the "Press Ctrl-B for the iPXE command line" prompt at startup or if booting fails.((If you are using an iPXE ROM, then you will still see the initial "Press Ctrl-B to configure iPXE" prompt that appears during the power-on self-tests (POST).  If you want to disable this initial prompt, you can do so by editing the file ''config/general.h'' to include the line:<code>    #define BANNER_TIMEOUT 0</code>))
 If you would like to provide the user an opportunity to access the iPXE command line, then you can provide your own replacement prompt using the ''[[:cmd:prompt]]'' command.  For example: