<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://ipxe.net/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://ipxe.net/feed.php">
        <title>iPXE - open source boot firmware appnote</title>
        <description></description>
        <link>https://ipxe.net/</link>
        <image rdf:resource="https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico" />
       <dc:date>2026-04-28T20:48:00+0000</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://ipxe.net/appnote/acronis?rev=1502053713&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/boot_local_drive_with_grub4dos?rev=1357598990&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/buildtargets?rev=1674551146&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/chainload_wds?rev=1446735488&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/debian_live?rev=1496511346&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/debian_preseed?rev=1450048392&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/efidriverdisconnect?rev=1501156320&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/etoken?rev=1693479484&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/hardware_drivers?rev=1777406401&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/ibft?rev=1452993130&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/interfaces?rev=1557915109&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/iscsi_targets?rev=1414504191&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/memtest?rev=1424826902&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/msdhcp-options?rev=1400263399&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/named_config?rev=1614862042&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/netware_rpl?rev=1613755772&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/premature?rev=1670792586&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/proxydhcp?rev=1628196797&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/scripting?rev=1775544886&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/srp_install?rev=1287770798&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/tftpd-hpa?rev=1446727458&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/third_party_usage_of_ipxe?rev=1425880909&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/ubuntu_live?rev=1461083658&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/uefihttp?rev=1611695706&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/userclass?rev=1300966360&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/wimboot_architecture?rev=1632221578&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/windowsdisklessaoe?rev=1341243489&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/winpe_with_iscsi?rev=1362675258&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/work_around_bios_halting_on_ipxe_exit?rev=1369186286&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/xenserver?rev=1409582219&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.net/appnote/xp_2003_direct_install?rev=1661762965&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico">
        <title>iPXE - open source boot firmware</title>
        <link>https://ipxe.net/</link>
        <url>https://ipxe.net/lib/tpl/doogiestpl/images/favicon.ico</url>
    </image>
    <item rdf:about="https://ipxe.net/appnote/acronis?rev=1502053713&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-08-06T21:08:33+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:acronis</title>
        <link>https://ipxe.net/appnote/acronis?rev=1502053713&amp;do=diff</link>
        <description>Acronis True Image

With regular iPXE, booting Acronis True Image is fairly straightforward. For example: 

sanboot http://1.2.3.4/ti2017.iso

EFI Support

Booting Acronis True Image 2017 with ipxe.efi is also possible. I was not able to boot with an earlier version (2014) as the kernel did not have CONFIG_EFI_STUB enabled.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/boot_local_drive_with_grub4dos?rev=1357598990&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-01-07T22:49:50+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:boot_local_drive_with_grub4dos</title>
        <link>https://ipxe.net/appnote/boot_local_drive_with_grub4dos?rev=1357598990&amp;do=diff</link>
        <description>Work Around BIOS Halting on iPXE Exit

Overview

Often times, iPXE users will need to exit iPXE and continue with the BIOS boot order for any number of reasons.  This is often the case for people who would like to install an OS directly to a SAN device.  Unfortunately, many system BIOSes will not continue their boot order after iPXE exits and hands back control of the boot process.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/buildtargets?rev=1674551146&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-24T09:05:46+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:buildtargets</title>
        <link>https://ipxe.net/appnote/buildtargets?rev=1674551146&amp;do=diff</link>
        <description>Build targets

iPXE is built using a command-line something like this:
  make bin/ipxe.pxe
The first part, bin in this case indicates platform.
ipxe indicates driver,
and .pxe indicates boot type.
  make [platform]/[driver].[extension]
The bin directory is included in git repo, but all platforms will be created automatically as 
part of the build process.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/chainload_wds?rev=1446735488&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-11-05T14:58:08+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:chainload_wds</title>
        <link>https://ipxe.net/appnote/chainload_wds?rev=1446735488&amp;do=diff</link>
        <description>Chainloading Windows Deployment Services

Windows
Deployment Services (WDS) is a set of services and APIs to
facilitate Windows operating system installation by using PXE, DHCP
and TFTP to bootstrap WinPE, the
Windows
Preinstallation Environment. You can think of it as providing
similar functionality to iPXE with server-side scripting, where
clients are served boot configuration and images based on various
criteria, such as hardware architecture.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/debian_live?rev=1496511346&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-06-03T17:35:46+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:debian_live</title>
        <link>https://ipxe.net/appnote/debian_live?rev=1496511346&amp;do=diff</link>
        <description>Pxeboot Debian 8.8 livecd with http.

	*  Download debian-live-8.8.0-amd64-standard.iso from Debian's website
	*  Extract these three files from the iso and upload them to your web server.
		*  vmlinuz
		*  initrd.img
		*  filesystem.squashfs

	*  Use the following ipxe config.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/debian_preseed?rev=1450048392&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-12-13T23:13:12+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:debian_preseed</title>
        <link>https://ipxe.net/appnote/debian_preseed?rev=1450048392&amp;do=diff</link>
        <description>This trick probably has other applications, but I am going to only discuss one use case, specifically adding a preseed file to a debian install for setting values configured before the network, on both pc and efi platforms.

Under the pc platform this is quite easy as long as your initrd is in cpio format (the default these days):</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/efidriverdisconnect?rev=1501156320&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-07-27T11:52:00+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:efidriverdisconnect</title>
        <link>https://ipxe.net/appnote/efidriverdisconnect?rev=1501156320&amp;do=diff</link>
        <description>Disconnecting EFI drivers

This is notes that might help with debugging issues possibly caused by EFI drivers

	*  Create a disk image with a FAT32 filesystem with UEFI full shell, saved as \EFI\Boot\BootX64.efi
	*  And something to test the scenario with, (we will assume</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/etoken?rev=1693479484&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-08-31T10:58:04+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:etoken</title>
        <link>https://ipxe.net/appnote/etoken?rev=1693479484&amp;do=diff</link>
        <description>UEFI Secure Boot signing using a DigiCert eToken

UEFI Secure Boot requires UEFI binaries to be signed by Microsoft.  This page documents the work in progress to obtain signed versions of iPXE and wimboot.

EV Code Signing Certificate

Microsoft requires submitted UEFI binaries to be signed using an EV Code Signing certificate.  These can be obtained from providers such as</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/hardware_drivers?rev=1777406401&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-28T20:00:01+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:hardware_drivers</title>
        <link>https://ipxe.net/appnote/hardware_drivers?rev=1777406401&amp;do=diff</link>
        <description>Hardware expected to work (unconfirmed)

In the table below you can find a list of the hardware that is
expected to work as of commit
8d2ebbf8a.
If you own hardware in the list below we very much welcome test
results confirming that the hardware indeed works. Please go to the</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/ibft?rev=1452993130&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-01-17T01:12:10+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:ibft</title>
        <link>https://ipxe.net/appnote/ibft?rev=1452993130&amp;do=diff</link>
        <description>Howto: Boot from ipxe/iscsi target using ibft with debian and dracut based Linux

Intro

This guide is intended to be a short writeup of what i learned about booting from iscsi using ipxe.

At the time of writing this some time has passed since i implemented these settings on my systems, so a few details might be incorrect or missing, always check documentation yourself.. i'll try to include as many reference links i can remember.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/interfaces?rev=1557915109&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-05-15T10:11:49+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:interfaces</title>
        <link>https://ipxe.net/appnote/interfaces?rev=1557915109&amp;do=diff</link>
        <description>Purpose

iPXE-style interfaces were created to fulfil the need of transmitting
and transforming messages. For example, an http_connection interface would send data delivery messages to a tcp_socket interface, which can send some other data delivery messages in return later on.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/iscsi_targets?rev=1414504191&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-10-28T13:49:51+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:iscsi_targets</title>
        <link>https://ipxe.net/appnote/iscsi_targets?rev=1414504191&amp;do=diff</link>
        <description>iSCSI targets known to work with iPXE

	*  Windows
		*  Microsoft iSCSI Software Target (included in Windows Storage Server) on Microsoft Windows
		*  StarWind Virtual SAN for Windows -- High performance Commercial iSCSI target for Windows. Has free version with limited functionality

	*  Linux
		*  SCST on Linux
		*  iSCSI Enterprise Target on Linux
		*  LIO (linux-iscsi.org) on Linux (see below)</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/memtest?rev=1424826902&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-02-25T01:15:02+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:memtest</title>
        <link>https://ipxe.net/appnote/memtest?rev=1424826902&amp;do=diff</link>
        <description>Booting Memtest

To be able to boot memtest, there are a couple requirements:

	*  The memtest iso
	*  The memdisk kernel from the syslinux library
		*  Syslinux 6.xx versions display issues trying to boot memtest
		*  Syslinux 5.10 has been tested working</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/msdhcp-options?rev=1400263399&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-05-16T18:03:19+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:msdhcp-options</title>
        <link>https://ipxe.net/appnote/msdhcp-options?rev=1400263399&amp;do=diff</link>
        <description>iPXE-specific options

There are several DHCP options that are specific to iPXE and that are not implemented in the Windows DHCP service. To add support for these options, follow theses steps:

	*  Right-click on the server, select Set Predefined Options</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/named_config?rev=1614862042&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-03-04T12:47:22+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:named_config</title>
        <link>https://ipxe.net/appnote/named_config?rev=1614862042&amp;do=diff</link>
        <description>Named configurations

Named configurations can be specified via the CONFIG=... build
parameter.

For headers in config/*.h which support named configurations, the following files are included when building with CONFIG=&lt;name&gt;:

	*  config/defaults/&lt;platform&gt;.h</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/netware_rpl?rev=1613755772&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-19T17:29:32+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:netware_rpl</title>
        <link>https://ipxe.net/appnote/netware_rpl?rev=1613755772&amp;do=diff</link>
        <description>Chainloading iPXE from a NetWare RPL boot ROM

Novell NetWare supports the RPL network boot protocol, which predates the PXE standard.  It is often found as a boot ROM on very old network cards.

You can use your RPL boot ROM to chainload into iPXE, and then use iPXE to boot via</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/premature?rev=1670792586&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-12-11T21:03:06+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:premature</title>
        <link>https://ipxe.net/appnote/premature?rev=1670792586&amp;do=diff</link>
        <description>Premature

About this page

Desired Long term name

Please don't link to this premature page

Using dnsmasq

dnsmasq provides network infrastructure for small networks: DNS, DHCP, router advertisement and network boot.
It can be configured to support iPXE.

Dnsmasq is configured using the file</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/proxydhcp?rev=1628196797&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-08-05T20:53:17+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:proxydhcp</title>
        <link>https://ipxe.net/appnote/proxydhcp?rev=1628196797&amp;do=diff</link>
        <description>dnsmasq

dnsmasq has gained popularity in recent years. It can easily be configured to support iPXE.

DHCP proxy

If you can't modify your existing dhcp then a proxy is the way to go.
It uses option 43 to display a menu and UDP port 4011 for the PXE configuration, while the IP and other information is given by your default</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/scripting?rev=1775544886&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-07T06:54:46+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:scripting</title>
        <link>https://ipxe.net/appnote/scripting?rev=1775544886&amp;do=diff</link>
        <description>Scripting

Overview

You can create a script to automate a sequence of iPXE commands.  Any command that can be typed at the iPXE command line can also be used in a script.  You can find a full list of commands in the iPXE command reference.

An iPXE script is a plain text file starting with the magic line</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/srp_install?rev=1287770798&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-10-22T18:06:38+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:srp_install</title>
        <link>https://ipxe.net/appnote/srp_install?rev=1287770798&amp;do=diff</link>
        <description>SCSI RDMA Protocol (SRP) improves the read performance in terms of throughput which is increased significantly for both random read with good locality and sequential read.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/tftpd-hpa?rev=1446727458&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-11-05T12:44:18+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:tftpd-hpa</title>
        <link>https://ipxe.net/appnote/tftpd-hpa?rev=1446727458&amp;do=diff</link>
        <description>Supporting broken TFTP clients with tftpd-hpa

tftpd-hpa can easily be configured to support broken TFTP clients by using a remap file.  You can verify that your TFTP server supports a remap file by typing
  /usr/sbin/in.tftpd -V
You should see output such as</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/third_party_usage_of_ipxe?rev=1425880909&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-03-09T06:01:49+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:third_party_usage_of_ipxe</title>
        <link>https://ipxe.net/appnote/third_party_usage_of_ipxe?rev=1425880909&amp;do=diff</link>
        <description>Software and service providers using iPXE

All these projects, software solution or service providers use iPXE in some way.

	*  Netcup (used as netboot system on vservers for installations and to manage the rescue system)
	*  Hetzner (used integrated ROM builds in EX* server series for boot into rescue system and for internal deployment of installations like vSphere)</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/ubuntu_live?rev=1461083658&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-04-19T16:34:18+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:ubuntu_live</title>
        <link>https://ipxe.net/appnote/ubuntu_live?rev=1461083658&amp;do=diff</link>
        <description>Booting Ubuntu Live Disc

To be able to boot into the Live Disc of the Ubuntu distribution, there are several requirements:

	*  The Ubuntu iso
	*  An NFS daemon
	*  Typical network booting infrastructure, including but not limited to:
		*  Physical layer</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/uefihttp?rev=1611695706&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-26T21:15:06+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:uefihttp</title>
        <link>https://ipxe.net/appnote/uefihttp?rev=1611695706&amp;do=diff</link>
        <description>UEFI HTTP chainloading

Version 2.5 of the UEFI specification introduces the UEFI HTTP Boot feature.  You can use the basic UEFI HTTP Boot client to chainload iPXE from an HTTP server, eliminating the need for a separate TFTP server in your boot infrastructure.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/userclass?rev=1300966360&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-03-24T11:32:40+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:userclass</title>
        <link>https://ipxe.net/appnote/userclass?rev=1300966360&amp;do=diff</link>
        <description>Changing the DHCP User Class

iPXE uses a DHCP User Class (option 77) value of “iPXE” to identify itself to the DHCP server as an iPXE client.  This allows the DHCP server to customise its response for iPXE clients.  For example, a DHCP server could instruct all iPXE clients to boot from a SAN.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/wimboot_architecture?rev=1632221578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-21T10:52:58+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:wimboot_architecture</title>
        <link>https://ipxe.net/appnote/wimboot_architecture?rev=1632221578&amp;do=diff</link>
        <description>wimboot architecture

wimboot is a boot loader that is roughly analogous to Windows' pxeboot network boot program. It lets you fetch all the relevant files over HTTP or any other supported protocol, and hands over execution to bootmgr.exe, the Windows boot manager. This page details the</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/windowsdisklessaoe?rev=1341243489&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-07-02T15:38:09+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:windowsdisklessaoe</title>
        <link>https://ipxe.net/appnote/windowsdisklessaoe?rev=1341243489&amp;do=diff</link>
        <description>Boot Windows disklessly with AoE (ATA over Ethernet)

HowTo:

https://windowsdisklessaoe.wordpress.com/



1 - Preparing Windows to Boot Diskless with VirtualBox/Virtual PC/Vmware

Install Windows 7/8/2003/2008 on a Virtual Machine ( create a disk type .vhd with fixed size )
open a cmd as administrator and type two commands:</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/winpe_with_iscsi?rev=1362675258&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-03-07T16:54:18+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:winpe_with_iscsi</title>
        <link>https://ipxe.net/appnote/winpe_with_iscsi?rev=1362675258&amp;do=diff</link>
        <description>Integrating the iSCSI Command Line Interface and Control Panel to WinPE 3.0:

Introduction:

WinPE 3.0 contains the iSCSI initiator driver (msiscsi.sys) by default, and it will connect to an iSCSI target if one was 'sanhooked' (assuming it has inbox NIC drivers that matches your hardware, or such drivers were loaded later using drvload.exe).
While this may be enough to start an installation, sometimes you may want to be able to connect to iSCSI targets using the iSCSI command line interface (isc…</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/work_around_bios_halting_on_ipxe_exit?rev=1369186286&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-05-22T01:31:26+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:work_around_bios_halting_on_ipxe_exit</title>
        <link>https://ipxe.net/appnote/work_around_bios_halting_on_ipxe_exit?rev=1369186286&amp;do=diff</link>
        <description>Work Around BIOS Halting on iPXE Exit

Overview

Often times, iPXE users will need to exit iPXE and continue with the BIOS boot order for any number of reasons, such as installing an OS directly to a SAN device.  Unfortunately, many system BIOSes will not continue with their boot order after iPXE exits and hands back control of the boot process.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/xenserver?rev=1409582219&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-09-01T14:36:59+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:xenserver</title>
        <link>https://ipxe.net/appnote/xenserver?rev=1409582219&amp;do=diff</link>
        <description>Installing XenServer via iPXE

[Xen logo]

You can use iPXE to boot into the XenServer installer via HTTP:

	*  Create a directory on your web server to contain the installation files (e.g. /var/www/boot/xenserver).

	*  Copy the contents of the XenServer installation CD-ROM to this directory.</description>
    </item>
    <item rdf:about="https://ipxe.net/appnote/xp_2003_direct_install?rev=1661762965&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-29T08:49:25+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:xp_2003_direct_install</title>
        <link>https://ipxe.net/appnote/xp_2003_direct_install?rev=1661762965&amp;do=diff</link>
        <description>Installing Windows XP \ 2003 directly to an iSCSI target

About IntegrateDrv

IntegrateDrv is a program that lets you integrate Plug and Play drivers into a Windows Installation.

Using this program, you can install Windows 2000 \ XP \ 2003 Directly to an iSCSI target.</description>
    </item>
</rdf:RDF>
