<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://etherboot.org/wiki/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="http://etherboot.org/wiki/feed.php">
        <title>Etherboot/gPXE Wiki</title>
        <description></description>
        <link>http://etherboot.org/wiki/</link>
        <image rdf:resource="http://etherboot.org/wiki/lib/images/favicon.ico" />
       <dc:date>2010-09-08T12:03:16-04:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/wiki/about?rev=1247996261&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/acknowledgements?rev=1233622370&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/andytim_todo?rev=1250119064&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/aoe?rev=1173992226&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/aoeboot?rev=1191151645&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/aoebootprepdebianetch?rev=1191151301&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes?rev=1271086279&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/biosmodule?rev=1208396518&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/bochs?rev=1151342607&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/bootingmemdisk?rev=1151245654&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/burningroms?rev=1240173077&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/commandline?rev=1266337448&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/commerciallinks?rev=1194469607&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/concepts?rev=1231387381&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/consultancy?rev=1158584079&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/contact?rev=1231705594&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/contributing?rev=1258637636&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/debian_aoe_migrate?rev=1191168135&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dhcpd?rev=1234920088&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dnsmasq?rev=1272494725&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/dnsresolver?rev=1150291427&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/doc?rev=1276117735&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/download?rev=1249165390&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/edd-utils?rev=1157832594&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/editing_permission?rev=1250713881&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/eeepc?rev=1266135854&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/etherboot-software?rev=1155741232&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/filename_specification?rev=1150290975&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/freebsd?rev=1153069574&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/gpxe_imagetypes?rev=1276118139&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/hardwareissues?rev=1281581755&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/howtos?rev=1283624874&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/httpboot?rev=1264965182&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/ibft?rev=1258847660&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/iscsibootprepw2k3?rev=1187032590&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/isolinux?rev=1283787663&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/lilowithetherboot?rev=1153069785&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/logos?rev=1216862220&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/macbuild?rev=1276625824&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/mailinglists?rev=1265049026&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/msdhcp?rev=1268696052&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/multicast?rev=1150288504&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/old_news?rev=1265833098&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/oldwiki?rev=1150280174&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/pcmcia_support?rev=1150280141&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/playground?rev=1149714855&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/proxydhcp?rev=1273992710&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/pxe?rev=1153064054&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/pxe2ndstage?rev=1150285175&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/pxechaining?rev=1279137718&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/realtek8139roms?rev=1151240577&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/relatedlinks?rev=1259468612&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/removable?rev=1271878501&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/romburning?rev=1283031042&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/romdumping?rev=1250838236&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanboot?rev=1264266742&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/sanbootconf?rev=1235870486&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/scenario?rev=1151318298&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/screenshots?rev=1186935757&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/scripting?rev=1248355506&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc?rev=1217561004&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/socideas?rev=1146655696&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soctools?rev=1147415128&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/staging?rev=1263589214&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/start?rev=1277846009&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/syslinux?rev=1283471158&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/talks?rev=1278633750&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/tftp_backslash?rev=1204560266&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/twodhcpservers?rev=1151246755&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/unity-patch?rev=1259176806&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/usbwithstorage?rev=1253815550&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/usermanual?rev=1153346293&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/vmware?rev=1151396923&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/winbootibft?rev=1158758251&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/windowsntloader?rev=1151247633&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/winpe_memdisk?rev=1242335602&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/zeroconf_design?rev=1258067923&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://etherboot.org/wiki/lib/images/favicon.ico">
        <title>Etherboot/gPXE Wiki</title>
        <link>http://etherboot.org/wiki/</link>
        <url>http://etherboot.org/wiki/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://etherboot.org/wiki/about?rev=1247996261&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-19T05:37:41-04:00</dc:date>
        <title>about</title>
        <link>http://etherboot.org/wiki/about?rev=1247996261&amp;do=diff</link>
        <description>We, the Etherboot Project, create network booting code that allows computers to load their operating system from a network.  Our code can be stored in a number of places, including BIOS Flash, EPROMs, floppy, CD, HD, or other bootable media.  

The Etherboot project has been active since about 1995.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/acknowledgements?rev=1233622370&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-02T19:52:50-04:00</dc:date>
        <title>acknowledgements</title>
        <link>http://etherboot.org/wiki/acknowledgements?rev=1233622370&amp;do=diff</link>
        <description>Many people have contributed substantially to Etherboot. We are grateful for all the assistance over the years. 

This page lists major contributors who identified themselves when submitting code to the project. We do our best to keep this up to date, but if you feel your name has been accidentally left out, please contact me.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-07T17:44:37-04:00</dc:date>
        <title>amibios</title>
        <link>http://etherboot.org/wiki/amibios?rev=1254951877&amp;do=diff</link>
        <description>In systems with a motherboard-integrated NIC, the NIC's ROM generally does not exist as a separate entity. Instead, it is read as a sort of “option ROM module” out of the overall BIOS flash. This page contains instructions for replacing the vendor PXE image with gPXE in the flash image of an AMIBIOS-based machine.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/andytim_todo?rev=1250119064&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-12T19:17:44-04:00</dc:date>
        <title>andytim_todo</title>
        <link>http://etherboot.org/wiki/andytim_todo?rev=1250119064&amp;do=diff</link>
        <description>*  Work 9 hours per day every week-day
	*  NASM NSIS script
	*  XP-via-SMB AppNote
	*  XP Pivot_Root Driver/“Native” .EXE
	*  XP “Fall-through” filesystem filter
	*  Port Ubuntu initrd for HTTPFS FUSE connection to public filesystem.squashfs (GSoC project, not mine)
	*  memdisk mapping
	*  memdisk El Torito (.ISO-boot)
	*  gPXE iSCSI &amp; AoE code for floppy and ODD media
	*  gPXE (or maybe general) compact scripting language system (GSoC project, not mine)
	*  Finish gPXE cmdline+initrd code (Mayb…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/aoe?rev=1173992226&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-15T16:57:06-04:00</dc:date>
        <title>aoe</title>
        <link>http://etherboot.org/wiki/aoe?rev=1173992226&amp;do=diff</link>
        <description>Classic/“normal” Operating systems, like:

	*  many Linux releases
	*  DOS
	*  Windows 1.0 - 3.11
	*  Windows 9x


...just need the Interrupt 13 to run and to do file operations, such as:

	*  loading Operating system components and booting the Operating System itself
	*  writing log files
	*  reading settings
	*  loading drivers
	*  ...</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/aoeboot?rev=1191151645&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-30T07:27:25-04:00</dc:date>
        <title>aoeboot</title>
        <link>http://etherboot.org/wiki/aoeboot?rev=1191151645&amp;do=diff</link>
        <description>This page has been moved to sanboot</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/aoebootprepdebianetch?rev=1191151301&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-30T07:21:41-04:00</dc:date>
        <title>aoebootprepdebianetch</title>
        <link>http://etherboot.org/wiki/aoebootprepdebianetch?rev=1191151301&amp;do=diff</link>
        <description>This page has been moved to debian_and_ubuntu</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-22T13:28:51-04:00</dc:date>
        <title>appnoted</title>
        <link>http://etherboot.org/wiki/appnoted?rev=1240421331&amp;do=diff</link>
        <description>Introduction

gPXE is a new version of the well know Etherboot project.
 
The project created network booting code that allows computers to load their operating system from a network.
 
The code can be stored in a number of places, including BIOS Flash, EPROMs, floppy, CD, HD, or other bootable media.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes?rev=1271086279&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-12T11:31:19-04:00</dc:date>
        <title>appnotes</title>
        <link>http://etherboot.org/wiki/appnotes?rev=1271086279&amp;do=diff</link>
        <description>This section contains examples of specific tasks that people have accomplished using gPXE and related software.  You may find some of these examples helpful.


	*  iSCSI Enterprise Target on Fedora 8 - steps to install the iSCSI Enterprise Target (&lt;http://iscsitarget.sourceforge.net&gt;) on Fedora 8</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-19T04:20:55-04:00</dc:date>
        <title>biosext</title>
        <link>http://etherboot.org/wiki/biosext?rev=1227086455&amp;do=diff</link>
        <description>Add gPXE to the BIOS of the Jetway J7F2WE family of motherboards (replacing the Intel UNDI PXE code)


Jeff Campbell, Turks &amp; Caicos Islands, February 27, 2008

 Note:  This is completely without warranty.  It worked for me.  It may not work for you.  It may wreck your system.  If you don't know what you're doing, don't do it.  You have no recourse but to blame yourself and sit in the dark rocking in the fetal position if this fails.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/biosmodule?rev=1208396518&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-16T21:41:58-04:00</dc:date>
        <title>biosmodule</title>
        <link>http://etherboot.org/wiki/biosmodule?rev=1208396518&amp;do=diff</link>
        <description>DISCLAIMER first:

I did do this. It worked for me perfectly. This might not be the case with you. If you don't find a Bios flashing tool for your mainboard, if you are not fluent with creating dos boot disks for Bios flashing, if you fear to loose your mainboard when flashing fails - this page is not for you. No guarantees.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/bochs?rev=1151342607&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-26T13:23:27-04:00</dc:date>
        <title>bochs</title>
        <link>http://etherboot.org/wiki/bochs?rev=1151342607&amp;do=diff</link>
        <description>Running Etherboot within Bochs

Orginal documentation by Michael Brown mbrown@fensystems.co.uk 
Based on an idea suggested by H. Peter Anvin hpa@zytor.com 
Wikified By Tim Fletcher tim@parrswood.manchester.sch.uk 
Reformatted by Anselm M. Hoffmeister</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/bootingmemdisk?rev=1151245654&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T10:27:34-04:00</dc:date>
        <title>bootingmemdisk</title>
        <link>http://etherboot.org/wiki/bootingmemdisk?rev=1151245654&amp;do=diff</link>
        <description>Disclaimer / Warning

This wiki page documents the author's recent experience in making an etherbootable image (nbi) of memdisk. At its best, it is only a temporary reference for those who want to boot memdisk from etherboot directly. It is temporary because the etherboot project team are reviewing some of the features in the current release 1.4.3 of mknbi. Depending on the results of their review, some bugs might have been fixed and new features might have been added to the next and/or future r…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/burningroms?rev=1240173077&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-19T16:31:17-04:00</dc:date>
        <title>burningroms</title>
        <link>http://etherboot.org/wiki/burningroms?rev=1240173077&amp;do=diff</link>
        <description>Burning ROM chips

Questions about burning ROM chips came up on the mailing list, so some information was written up to be put here for reference.



has anyone tried burning etherboot onto a bootrom
instead of booting from a floppy drive to get connected?</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/commandline?rev=1266337448&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-16T11:24:08-04:00</dc:date>
        <title>commandline</title>
        <link>http://etherboot.org/wiki/commandline?rev=1266337448&amp;do=diff</link>
        <description>Etherboot command-line

Network Interfaces

Etherboot names interfaces following the pattern “net#”.  The special network interface alias “netX” refers to the last opened network interface.

ifstat [interfaces...] Displays information and statistics about the specified interface.  If no interface is specified, displays information about all detected interfaces.  Information includes MAC address, PCI bus/slot/function identiers, and packet counts.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/commerciallinks?rev=1194469607&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-11-07T16:06:47-04:00</dc:date>
        <title>commerciallinks</title>
        <link>http://etherboot.org/wiki/commerciallinks?rev=1194469607&amp;do=diff</link>
        <description>This listing is provided only as a service to help users locate providers and does not constitute endorsement of the services or products by the Etherboot project. 

If you wish to be listed on this page, please contact me. 

Licensing and Distribution


Remember that Etherboot is under the GNU Public License (GPL). This means that if you distribute binaries, e.g. in the form of ROMs, you are required to provide the source to the recipient on request. Please read the file COPYING for the full li…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/concepts?rev=1231387381&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-07T23:03:01-04:00</dc:date>
        <title>concepts</title>
        <link>http://etherboot.org/wiki/concepts?rev=1231387381&amp;do=diff</link>
        <description>gPXE is a boot-loader: a program that allows your computer to load either another boot-loader or your Operating System.  gPXE, however, is a very special kind of boot-loader that allows the computer to boot via a network, rather than a disk.  gPXE is the direct descendant of Etherboot; both are part of the Etherboot project, though Etherboot is no longer maintained.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/consultancy?rev=1158584079&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-18T08:54:39-04:00</dc:date>
        <title>consultancy</title>
        <link>http://etherboot.org/wiki/consultancy?rev=1158584079&amp;do=diff</link>
        <description>For urgent queries, you may wish to contact one of the Etherboot developers directly on a consultancy basis.

Michael Brown, Fen Systems Ltd.


Lead developer of the Etherboot project, author of many components including iSCSI and AoE boot.  Contact via &lt;mbrown@fensystems.co.uk&gt;.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/contact?rev=1231705594&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-01-11T15:26:34-04:00</dc:date>
        <title>contact</title>
        <link>http://etherboot.org/wiki/contact?rev=1231705594&amp;do=diff</link>
        <description>As of the time of writing (2007-07-13), most development discussions take place in the project IRC channel: #etherboot on FreeNode.  Support discussions might also be possible in #etherboot for FOSS environment support and in #etherboot-win for closed-source proprietary environment support.  There are also project mailing lists hosted by SourceForge. See Mailing Lists for more details.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/contributing?rev=1258637636&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-19T08:33:56-04:00</dc:date>
        <title>contributing</title>
        <link>http://etherboot.org/wiki/contributing?rev=1258637636&amp;do=diff</link>
        <description>Etherboot is a volunteer project. Many kind people have contributed in various ways, see the acknowledgements. You can help in various ways:


	*  Improve the documentation. Edit the wiki or send us changes if you feel something is missing or can be improved.
	*  Try different variations on configurations and software. Send us the documentation or a link to your Web page when you have succeeded, of course.
	*  Spread the word about network booting wherever you see a situation which could use the…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/debian_aoe_migrate?rev=1191168135&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-09-30T12:02:15-04:00</dc:date>
        <title>debian_aoe_migrate</title>
        <link>http://etherboot.org/wiki/debian_aoe_migrate?rev=1191168135&amp;do=diff</link>
        <description>This page has been moved to debian_and_ubuntu</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-10T03:49:58-04:00</dc:date>
        <title>debug</title>
        <link>http://etherboot.org/wiki/debug?rev=1149925798&amp;do=diff</link>
        <description>Sat Jun 10 07:40:52 UTC 2006


I've started to work on getting more drivers working in gPXE 0.5, and have come across an interesting problem.

I am not sure what is causing the problem, so I need to debug it.  It occurred to me that this is a perfect opportunity to show how the process works, and get more people involved.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dhcpd?rev=1234920088&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-17T20:21:28-04:00</dc:date>
        <title>dhcpd</title>
        <link>http://etherboot.org/wiki/dhcpd?rev=1234920088&amp;do=diff</link>
        <description>Defining the gPXE-specific options


Add the following block to the top of your /etc/dhcpd.conf file:

  # gPXE-specific encapsulated options
  #
  option space gpxe;
  option gpxe-encap-opts code 175 = encapsulate gpxe;
  option gpxe.priority code 1 = signed integer 8;
  option gpxe.keep-san code 8 = unsigned integer 8;
  option gpxe.no-pxedhcp code 176 = unsigned integer 8;
  option gpxe.bus-id code 177 = string;
  option gpxe.bios-drive code 189 = unsigned integer 8;
  option gpxe.username co…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T10:33:54-04:00</dc:date>
        <title>disklessdos</title>
        <link>http://etherboot.org/wiki/disklessdos?rev=1151246034&amp;do=diff</link>
        <description>Using MEMDISK to etherboot a diskless DOS

Please, read also the general memdisk introduction.

This page is about using memdisk to run DOS, plus a virtual harddrive in RAM.


Diskless DOS (big ram disk)

Cloning a harddisk, in its simplest form, is just like cloning a floppy. Assumptions:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T10:41:33-04:00</dc:date>
        <title>disklesswin98</title>
        <link>http://etherboot.org/wiki/disklesswin98?rev=1151246493&amp;do=diff</link>
        <description>Diskless win98

Please, also read the page about generally using memdisk.

Here, we are talking about converting an existing win98 workstation on harddisk into its RAM disk equivalent. We assume the readers had gone through the exercises elaborated in Quick Start and Diskless DOS (big ram disk). A lot of tasks, terms, names, etc. will be reused here. Theoretically, assuming our DC, i.e. xterm, was a working win98 workstation before we took away its harddisk, we only need to dump the contents of …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dnsmasq?rev=1272494725&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-28T18:45:25-04:00</dc:date>
        <title>dnsmasq</title>
        <link>http://etherboot.org/wiki/dnsmasq?rev=1272494725&amp;do=diff</link>
        <description>[A network card]

Why DNSMasq

	*  It is small and lightweight
	*  Easy to setup (includes its own tftp server)
	*  It may already be running on your linux-based router :-)

Defining the gPXE-specific options


Add the following settings to your /etc/dnsmasq.conf file:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/dnsresolver?rev=1150291427&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T09:23:47-04:00</dc:date>
        <title>dnsresolver</title>
        <link>http://etherboot.org/wiki/dnsresolver?rev=1150291427&amp;do=diff</link>
        <description>The DNS resolver code (optionally to be compiled into Etherboot) allows for filenames to contain hostnames. Thus,


http://www.memtest86.com/memtest.nbi


might in theory be a valid file to be downloaded (you will have to compile-in HTTP support as well).</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/doc?rev=1276117735&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-09T17:08:55-04:00</dc:date>
        <title>doc</title>
        <link>http://etherboot.org/wiki/doc?rev=1276117735&amp;do=diff</link>
        <description>General Documentation

	*  gPXE Image types: explanation on types of images cranked out by make or r-o-m

Source Code Documentation


Many parts of the gPXE code-base include commenting for use with the Doxygen system.  To build this documentation for browsing, go into gPXE src/ directory and do</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/download?rev=1249165390&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-01T18:23:10-04:00</dc:date>
        <title>download</title>
        <link>http://etherboot.org/wiki/download?rev=1249165390&amp;do=diff</link>
        <description>Prebuilt binaries


Prebuilt gPXE images are available from &lt;http://rom-o-matic.net/&gt;.  Images can be generated from official gPXE releases or from the current development tree.  This is probably the easiest way to get started with gPXE.

Source code (git)


You can browse the current development tree at &lt;http://git.etherboot.org/?p=gpxe.git&gt;, or check out a copy using:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-04-07T07:00:12-04:00</dc:date>
        <title>eb_imagetypes</title>
        <link>http://etherboot.org/wiki/eb_imagetypes?rev=1175943612&amp;do=diff</link>
        <description>Using rom-o-matic, or compiling Etherboot yourself, you will be able to generate different file types, depending on your needs.

Those file types shall be explained here:

Floppy bootable ROM image (.zdsk)

These files are meant to be used on floppy disks. If you obtained such a file, copy it to a floppy: Under Linux,</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/edd-utils?rev=1157832594&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-09T16:09:54-04:00</dc:date>
        <title>edd-utils</title>
        <link>http://etherboot.org/wiki/edd-utils?rev=1157832594&amp;do=diff</link>
        <description>Overview


mkeddlinks is a simple utility which creates symlinks for the BIOS INT
13 devices present at the time the system booted.  For example:

[root@dolphin /]# mkeddlinks
[root@dolphin /]# ls -l /dev/bd*
lrwxrwxrwx  1 root root 3 Sep  7 04:07 /dev/bda -&gt; hda
lrwxrwxrwx  1 root root 4 Sep  7 04:07 /dev/bda1 -&gt; hda1
lrwxrwxrwx  1 root root 4 Sep  7 04:07 /dev/bda2 -&gt; hda2
lrwxrwxrwx  1 root root 4 Sep  7 04:07 /dev/bda5 -&gt; hda5
lrwxrwxrwx  1 root root 4 Sep  7 04:07 /dev/bda6 -&gt; hda6
lrwxrwxr…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/editing_permission?rev=1250713881&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-19T16:31:21-04:00</dc:date>
        <title>editing_permission</title>
        <link>http://etherboot.org/wiki/editing_permission?rev=1250713881&amp;do=diff</link>
        <description>Editing or Adding Wiki Content


This wiki has access control enabled because spammers now use wikis as channel for their content.  

This means that you have to get a user account if you want to add or edit content.  

Here's how to get an account:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/eeepc?rev=1266135854&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-14T03:24:14-04:00</dc:date>
        <title>eeepc</title>
        <link>http://etherboot.org/wiki/eeepc?rev=1266135854&amp;do=diff</link>
        <description>Note: this howto is made in mind that you don't have access to a TFTP server on your LAN, that you are too lazy to setup one, or that your sysadmins forbids it


	*  Compile undi.usb:
 cd gpxe.git/src; make bin/undi.usb 

Or if you are lazy download a binary version here.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/etherboot-software?rev=1155741232&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-16T11:13:52-04:00</dc:date>
        <title>etherboot-software</title>
        <link>http://etherboot.org/wiki/etherboot-software?rev=1155741232&amp;do=diff</link>
        <description>Etherboot is a software package for creating ROM images that can download code over an Ethernet network to be executed on an x86 computer. Many network adapters have a socket where a ROM chip can be installed. Etherboot is code that can be put in such a ROM.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/filename_specification?rev=1150290975&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T09:16:15-04:00</dc:date>
        <title>filename_specification</title>
        <link>http://etherboot.org/wiki/filename_specification?rev=1150290975&amp;do=diff</link>
        <description>Depending of its version, Etherboot supports several file transfer protocols.

By default, etherboot will download by tftp, but this can be altered by

	*  specifying a full URI, including the protocol prefix
	*  change default to NFS at compile time: There is an appropriate option available.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/freebsd?rev=1153069574&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T13:06:14-04:00</dc:date>
        <title>freebsd</title>
        <link>http://etherboot.org/wiki/freebsd?rev=1153069574&amp;do=diff</link>
        <description>Freebsd network booting

Doug Ambrisko (?) -- 16 October 1999
 Jason Andresen -- April 4, 2005 

These are some notes on Freebsd network booting with Etherboot.

Add kernel configuration via bootp to kernel. You can see more options in LINT, these are a good set</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/gpxe_imagetypes?rev=1276118139&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-09T17:15:39-04:00</dc:date>
        <title>gpxe_imagetypes</title>
        <link>http://etherboot.org/wiki/gpxe_imagetypes?rev=1276118139&amp;do=diff</link>
        <description>.pxe/.kpxe/.kkpxe

	*  .pxe is an image designed to be chain loaded
	*  .kpxe 
	*  .kkpxe is a PXE image that keeps PXE+UNDI loaded and return to PXE (instead of int 18h). From here</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/hardwareissues?rev=1281581755&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-11T22:55:55-04:00</dc:date>
        <title>hardwareissues</title>
        <link>http://etherboot.org/wiki/hardwareissues?rev=1281581755&amp;do=diff</link>
        <description>This page contains some issues that people had while using gpxe.

3Com 3C905-TX Card

This card is known to not support gpxe while using the MBA v4.0.

Symptoms


gPXE loads, negociate the link speed but the DHCP doesn't grab any valid adress even if the DHCP server make an offer.
This is due to a buggy PXE rom, this usually happens on the MBA (Master Boot Agent) v4.0.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/howtos?rev=1283624874&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-04T14:27:54-04:00</dc:date>
        <title>howtos</title>
        <link>http://etherboot.org/wiki/howtos?rev=1283624874&amp;do=diff</link>
        <description>This section contains tutorials that will guide you through performing a variety of network booting tasks for the first time.  You'll need to download and build gPXE before trying most of them.


How to deploy gPXE


There are three typical deployment scenarios for gPXE.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/httpboot?rev=1264965182&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-31T14:13:02-04:00</dc:date>
        <title>httpboot</title>
        <link>http://etherboot.org/wiki/httpboot?rev=1264965182&amp;do=diff</link>
        <description>Booting from HTTP with gPXE is as simple as replacing the DHCP filename field with an http:// URL.  For example, if you currently have /etc/dhcpd.conf containing

  next-server my.tftp.server;
  filename &quot;/pxe.0&quot;;

then you can just copy pxe.0 to your web server and edit /etc/dhcpd.conf to contain</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/ibft?rev=1258847660&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-21T18:54:20-04:00</dc:date>
        <title>ibft</title>
        <link>http://etherboot.org/wiki/ibft?rev=1258847660&amp;do=diff</link>
        <description>Overview


This package provides utilities for parsing and utilising the
information in an iSCSI Boot Firmware Table (iBFT).  The iBFT is a
table created by iSCSI boot firmware (such as Etherboot), in order to
pass parameters about the iSCSI boot device to the booted operating
system.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-11T09:47:03-04:00</dc:date>
        <title>iscsiboot</title>
        <link>http://etherboot.org/wiki/iscsiboot?rev=1165848423&amp;do=diff</link>
        <description>This tutorial describes a simple three-step process for getting your first iSCSI-booting operating system up and running.  The three stages are:


	*  
	*  
	*  


[Fedora Core 5 booting via iSCSI]

Preparing the operating system image


The first stage is to prepare the operating system image for iSCSI boot.  This generally involves installing an iSCSI initiator and adjusting a few configuration parameters.  Instructions are available for:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-18T15:03:21-04:00</dc:date>
        <title>iscsibootprepfc5</title>
        <link>http://etherboot.org/wiki/iscsibootprepfc5?rev=1158606201&amp;do=diff</link>
        <description>These instructions assume that you have an installation of Fedora Core 5 on a local hard disk.  We will make this installation iSCSI-boot-capable, then copy it to a remote iSCSI target and boot from it.

Start by installing the gcc, kernel-devel, sysfsutils, and dkms packages:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/iscsibootprepw2k3?rev=1187032590&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-13T15:16:30-04:00</dc:date>
        <title>iscsibootprepw2k3</title>
        <link>http://etherboot.org/wiki/iscsibootprepw2k3?rev=1187032590&amp;do=diff</link>
        <description>These instructions assume that you have an installation of Windows Server 2003 on a local hard disk.  We will make this installation iSCSI-boot-capable, then copy it to a remote iSCSI target and boot from it.

[Microsoft Connect download page]

You will need to install the Microsoft iSCSI Software Initiator Boot Version.  You must obtain this from &lt;http://connect.microsoft.com&gt; by signing up with the invitation code ms-8RR8-6K43.  This is not the standard Microsoft iSCSI Initiator; you do need t…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/isolinux?rev=1283787663&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-06T11:41:03-04:00</dc:date>
        <title>isolinux</title>
        <link>http://etherboot.org/wiki/isolinux?rev=1283787663&amp;do=diff</link>
        <description>Making a gPXE-bootable CD/DVD using ISOLINUX

gPXE already offers an option to make a bootable iso image via make bin/gpxe.iso, but what if you also want to store files on the disc? Once you've written the &lt;1MB image to the CD, you still have 701MB left, so you might as well put it to good use.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/lilowithetherboot?rev=1153069785&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T13:09:45-04:00</dc:date>
        <title>lilowithetherboot</title>
        <link>http://etherboot.org/wiki/lilowithetherboot?rev=1153069785&amp;do=diff</link>
        <description>LILO with Etherboot

Ken Yap, &lt;ken_yap AT users PERIOD sourceforge PERIOD net&gt;
 10 May 2002 

This HOWTO explains how to install LILO on disks that do not have any Linux filesystems to boot DOS as well as Etherboot .(z)lilo images. 

Motivation

LILO is perhaps the best known Linux boot loader and many people use it to single or multiple boot OSes?. What is less well known is that LILO can also boot from disks that do not have any Linux partitions at all. This follows from the design of LILO. Th…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/logos?rev=1216862220&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-23T21:17:00-04:00</dc:date>
        <title>logos</title>
        <link>http://etherboot.org/wiki/logos?rev=1216862220&amp;do=diff</link>
        <description>Etherboot Project








gPXE








Rom-o-matic.net</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/macbuild?rev=1276625824&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-15T14:17:04-04:00</dc:date>
        <title>macbuild</title>
        <link>http://etherboot.org/wiki/macbuild?rev=1276625824&amp;do=diff</link>
        <description>You can build gPXE on a Mac running OS X, either targeting the Mac's EFI interface or the normal PC BIOS interface. The Mac's EFI interface is generally trickier to set up, since the restrictions of running under EFI prevent us from providing real-mode interfaces like that required by PXELINUX; you can only load EFI images like elilo.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/mailinglists?rev=1265049026&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-01T13:30:26-04:00</dc:date>
        <title>mailinglists</title>
        <link>http://etherboot.org/wiki/mailinglists?rev=1265049026&amp;do=diff</link>
        <description>Current Etherboot Project mailing lists can be found here:

&lt;http://etherboot.org/mailman/listinfo&gt;


----------

In addition we have some legacy mailing lists:

Etherboot-Discuss is for general discussion of Etherboot and associated network booting topics.  
 This list will be obsolete soon, so please join the gPXE mailing list instead!</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-20T10:59:53-04:00</dc:date>
        <title>mknbi</title>
        <link>http://etherboot.org/wiki/mknbi?rev=1153407593&amp;do=diff</link>
        <description>Name

mknbi - make network bootable image


Synopsis


mknbi --version
mknbi --format=format --target=target [--output=outputfile] target-specific-arguments
mkelf-linux [--output=outputfile] kernelimage [ramdisk]
mknbi-linux [--output=outputfile] kernelimage [ramdisk]
mknbi-rom [--output=outputfile] ROM-image
mkelf-menu [--output=outputfile] [dataimage]
mknbi-menu [--output=outputfile] [dataimage]
mkelf-nfl [--output=outputfile] [dataimage]
mknbi-nfl [--output=outputfile] [dataimage]
mkelf-lua […</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/msdhcp?rev=1268696052&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-03-15T19:34:12-04:00</dc:date>
        <title>msdhcp</title>
        <link>http://etherboot.org/wiki/msdhcp?rev=1268696052&amp;do=diff</link>
        <description>How to configure Microsoft DHCP Server for gPXE

	*  This section is about defining DHCP options for your gPXE clients.  
		*  If you need to set up your Microsoft DHCP Server to chainload gPXE to existing PXE clients, follow the guide here first.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-26T14:03:15-04:00</dc:date>
        <title>msris</title>
        <link>http://etherboot.org/wiki/msris?rev=1151344995&amp;do=diff</link>
        <description>What is RIS?

RIS stands for Remote Installation Services, it is a Microsoft technology that is used to install Windows 2000 and above from a remote server to a PXE enabled client machine. It is different from drive imaging technologies such as Symantec Ghost because it actually boots an installer off a network server and then installs Windows from scratch.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/multicast?rev=1150288504&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T08:35:04-04:00</dc:date>
        <title>multicast</title>
        <link>http://etherboot.org/wiki/multicast?rev=1150288504&amp;do=diff</link>
        <description>What is multicast, anyway?


In IP based networks, there are basically three types of IP packets: unicase, broadcast, and multicast.

Unicast packets are sent from one host, with a valid sender IP address (except for very special things like DHCP discovery), to exactly one other host, specified by another valid IP address.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/old_news?rev=1265833098&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-10T15:18:18-04:00</dc:date>
        <title>old_news</title>
        <link>http://etherboot.org/wiki/old_news?rev=1265833098&amp;do=diff</link>
        <description>[LinuxWorld logo]

LinuxWorld Expo 2008, San Francisco


The Etherboot project will be exhibiting once again at LinuxWorld Expo in San Francisco from August 5-7.  We will also be presenting a tutorial on the morning of Monday August 4th, on the topic of “Virtualization of the Boot Process Using Open Source Software”.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/oldwiki?rev=1150280174&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T06:16:14-04:00</dc:date>
        <title>oldwiki</title>
        <link>http://etherboot.org/wiki/oldwiki?rev=1150280174&amp;do=diff</link>
        <description>Here is content from the old &lt;http://wiki.etherboot.org/&gt; site:


	*  PCMCIA Support</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-10-13T08:56:18-04:00</dc:date>
        <title>openwrt</title>
        <link>http://etherboot.org/wiki/openwrt?rev=1223902578&amp;do=diff</link>
        <description>Edit the file /etc/init.d/dnsmasq to add the right location and arguments:

start() {
  include /lib/network
  scan_interfaces
  config_load /var/state/network
  config_load dhcp
#      args=&quot;&quot;
  args=&quot; --enable-tftp --tftp-root=/mnt/usbdrive --dhcp-boot=/mnt/usbdrive/pxelinux.0&quot;

Then type the following commands on the command line:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/pcmcia_support?rev=1150280141&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T06:15:41-04:00</dc:date>
        <title>pcmcia_support</title>
        <link>http://etherboot.org/wiki/pcmcia_support?rev=1150280141&amp;do=diff</link>
        <description>therboot does not (yet) offer support for PCMCIA cards. 

The tricky part is to initialize the PCMCIA controller.
Before a PCMCIA Network Interface Card can be configured,
has that device be setup.

Source code for how to talk to @@yenta@@ chips is available in the Linux kernel.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/playground?rev=1149714855&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-07T17:14:15-04:00</dc:date>
        <title>playground</title>
        <link>http://etherboot.org/wiki/playground?rev=1149714855&amp;do=diff</link>
        <description>Let's test this playground page.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/proxydhcp?rev=1273992710&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-16T02:51:50-04:00</dc:date>
        <title>proxydhcp</title>
        <link>http://etherboot.org/wiki/proxydhcp?rev=1273992710&amp;do=diff</link>
        <description>Simply put proxydhcp is using a separate dhcp from the regular dhcp server to hand out boot parameters. An existing dhcp server isn't modified. Very handy for setting up a PXE environment without access to the existing dhcp infrastructure. Ubuntu community docs mention that dnsmasq 2.48 or newer supports being a proxydhcp server and that gpxe newer than may 2009 is also needed (gPXE version 0.9.8?). Those docs also mention that proprietary bootroms can also support proxydhcp, so chainloaders are…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/pxe?rev=1153064054&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T11:34:14-04:00</dc:date>
        <title>pxe</title>
        <link>http://etherboot.org/wiki/pxe?rev=1153064054&amp;do=diff</link>
        <description>Using EtherBoot as a PXE boot rom


EtherBoot is a multi-functional boot loader tool. It can either be used as a PXE boot ROM, or as a 2nd stage loader comparable to PXElinux.

Anyway, if you want to have an open source boot rom in your system BIOS, on your network card ROM socket, on a floppy or a cdrom, then EtherBoot is right for you.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/pxe2ndstage?rev=1150285175&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-14T07:39:35-04:00</dc:date>
        <title>pxe2ndstage</title>
        <link>http://etherboot.org/wiki/pxe2ndstage?rev=1150285175&amp;do=diff</link>
        <description>Using Etherboot as a PXE 2nd-stage loader


Several NICS on the market have a firmware on them, containing PXE code.

So, what is PXE anyway?


PXE stands for Preboot Execution Environment. It has been designed by Intel(?, others too?) and specifies how a system should behave on boot as part of Intel's “Wired For Management” initiative.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/pxechaining?rev=1279137718&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-14T16:01:58-04:00</dc:date>
        <title>pxechaining</title>
        <link>http://etherboot.org/wiki/pxechaining?rev=1279137718&amp;do=diff</link>
        <description>If you have a large number of machines which already have a legacy PXE implementation (e.g. network cards containing an Intel PXE ROM), then you may want to avoid having to reflash each machine's network card.  You can achieve this by placing gPXE on your TFTP server.  The PXE-capable machines will download gPXE via TFTP, and instantly become gPXE-capable machines.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-15T22:55:44-04:00</dc:date>
        <title>qemu</title>
        <link>http://etherboot.org/wiki/qemu?rev=1239850544&amp;do=diff</link>
        <description>Step by step

	*  Install Qemu
	*  Compile or download gpxe.pdsk.
	*  Type on the command line: 
 qemu -fda gpxe.pdsk -net nic -net user -bootp http://etherboot.org/gtest/gtest.gpxe 


Quick start

First make sure you have gpxe.pdsk or ns8390.pdsk.  You can download them from ROM-o-matic.net or build them yourself.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/realtek8139roms?rev=1151240577&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T09:02:57-04:00</dc:date>
        <title>realtek8139roms</title>
        <link>http://etherboot.org/wiki/realtek8139roms?rev=1151240577&amp;do=diff</link>
        <description>ROM chips for Realtek 8139 NICs

The 8139 is probably the most cloned NIC in the world.

The design of the ethernet controller chip accomodates ROMs up to 128 kB (1024 kilobit) which require a 32-pin socket.

Some OEMs however use a 28 pin socket because that can hold a 27C512 (and smaller), which can hold up to 64kB (512 kilobit) of code, more than enough for most cases. Those 28-pin-sockets are often soldered in where also 32-pin sockets would have matched - the two sizes are backwards compati…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/relatedlinks?rev=1259468612&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-28T23:23:32-04:00</dc:date>
        <title>relatedlinks</title>
        <link>http://etherboot.org/wiki/relatedlinks?rev=1259468612&amp;do=diff</link>
        <description>If you wish to be listed on this page, please contact me


	*   Rate Etherboot @ O'Reilly's OSDir.com

	*  Linux Terminal Server Project is an open source project to create the administration tools that will make setting up a diskless workstation easier.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/removable?rev=1271878501&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-21T15:35:01-04:00</dc:date>
        <title>removable</title>
        <link>http://etherboot.org/wiki/removable?rev=1271878501&amp;do=diff</link>
        <description>You can place gPXE onto a removable medium such as a floppy disk, CD-ROM, or USB key.  This will contain drivers for all supported network cards, and lets you quickly and easily try out gPXE.

Creating Images Using Prebuilt Binaries


Probably the quickest way to get started using gPXE in a Windows environment is by using the ROM-o-Matic page and downloading some prebuilt images.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/romburning?rev=1283031042&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-08-28T17:30:42-04:00</dc:date>
        <title>romburning</title>
        <link>http://etherboot.org/wiki/romburning?rev=1283031042&amp;do=diff</link>
        <description>For a permanent deployment of gPXE, you can burn it into your network card's expansion ROM, as a replacement for the card's legacy PXE ROM.  Most modern network cards store their expansion ROMs in flash memory, and most manufacturers will provide a utility to allow you to update the expansion ROM.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/romdumping?rev=1250838236&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-21T03:03:56-04:00</dc:date>
        <title>romdumping</title>
        <link>http://etherboot.org/wiki/romdumping?rev=1250838236&amp;do=diff</link>
        <description>Sometimes it can be useful to dump PCI expansion ROMs for debugging and troubleshooting purposes.  This page shows how to extract PCI expansion ROM contents.

ROM Dumping on Linux


Sysfs provides access to all PCI devices on a system (sysfs-pci.txt documentation).  It is possible to map in expansion ROMs in order to dump their contents.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-03-10T21:39:58-04:00</dc:date>
        <title>rplchaining</title>
        <link>http://etherboot.org/wiki/rplchaining?rev=1205199598&amp;do=diff</link>
        <description>If you have a large number of machines which already have a legacy RPL implementation (e.g. network cards containing a Novell RPL ROM), then you may want to avoid having to reflash each machine's network card.  You can achieve this by placing gPXE on your RPL server.  The RPL-capable machines will download gPXE via RPL, and instantly become gPXE-capable machines.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T09:46:24-04:00</dc:date>
        <title>safebootmode</title>
        <link>http://etherboot.org/wiki/safebootmode?rev=1151243184&amp;do=diff</link>
        <description>SafeBootMode

Trust and Security in network booting

On regular PC systems, the aspect of which operating system is booted, where the kernel will be loaded from etc. can be controlled (more or less) reliably. For example, with a proper setup GRUB bootloader, in combination with an operating system like GNU/Linux, users will not be able to change the boot options without opening the PC case and (for example) resetting the BIOS or attach additional drivers - which is rather unlikely in most office…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanboot?rev=1264266742&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-23T12:12:22-04:00</dc:date>
        <title>sanboot</title>
        <link>http://etherboot.org/wiki/sanboot?rev=1264266742&amp;do=diff</link>
        <description>[Windows Server 2003]

gPXE allows you to boot an operating system directly from a Storage Area Network, using a protocol such as iSCSI or AoE.  In this setup, you do not need a TFTP server or any other boot-time-only server.  The operating system is loaded directly from the network-attached disk.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/sanbootconf?rev=1235870486&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-28T20:21:26-04:00</dc:date>
        <title>sanbootconf</title>
        <link>http://etherboot.org/wiki/sanbootconf?rev=1235870486&amp;do=diff</link>
        <description>Introduction


sanbootconf is the Windows SAN Boot Configurator.  It allows you to boot Windows XP over the network using iSCSI.

sanbootconf is implemented as a boot-time driver that configures your NIC and instructs the boot-capable Microsoft iSCSI Initiator to perform an iSCSI boot.  It is designed to be a drop-in replacement for Microsoft's iscsibp.sys.  If you are trying to boot Windows XP via iSCSI, then you will need to use sanbootconf, since iscsibp.sys requires Windows Server 2003 or la…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/scenario?rev=1151318298&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-26T06:38:18-04:00</dc:date>
        <title>scenario</title>
        <link>http://etherboot.org/wiki/scenario?rev=1151318298&amp;do=diff</link>
        <description>A typical network boot scenario

This page shall explain how to setup a simple network boot scenario.

Physical setup

For network booting, you will need two machines:

	*  The (preferrably diskless) “client”
	*  The server


The client will not need any disks, so it can be built noiseless. Most “thin clients” on the market do not have any moving parts. If your network adaptor does not have a network boot ROM though, you will need either a floppy drive or a CD-ROM to load the network boot code (…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/screenshots?rev=1186935757&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-12T12:22:37-04:00</dc:date>
        <title>screenshots</title>
        <link>http://etherboot.org/wiki/screenshots?rev=1186935757&amp;do=diff</link>
        <description>HTTP booting and initramfs assembly


You can boot a Linux kernel directly from a web server using gPXE.  The kernel, initial ramdisk and other boot-time files (e.g. kernel modules for the network card) can also be loaded from the same web server.  There is no need to create dedicated ramdisk images containing drivers for each network card you want to be able to boot from.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/scripting?rev=1248355506&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-07-23T09:25:06-04:00</dc:date>
        <title>scripting</title>
        <link>http://etherboot.org/wiki/scripting?rev=1248355506&amp;do=diff</link>
        <description>You can use any of the commands found in the gPXE command line reference as instructions in a script file to boot your OS.
 
For example, &lt;http://etherboot.org/gtest/gtest.gpxe&gt; contains the following gPXE commands:

  #!gpxe   
  kernel http://etherboot.org/gtest/bz2bzImage root=100   
  initrd http://etherboot.org/gtest/initrd.bz2   
  boot   

or using the 'chain' command, this would be equivalent to:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc?rev=1217561004&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-07-31T23:23:24-04:00</dc:date>
        <title>soc</title>
        <link>http://etherboot.org/wiki/soc?rev=1217561004&amp;do=diff</link>
        <description>GSoC Page


Our GSoC wiki start page is here.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/socideas?rev=1146655696&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-05-03T07:28:16-04:00</dc:date>
        <title>socideas</title>
        <link>http://etherboot.org/wiki/socideas?rev=1146655696&amp;do=diff</link>
        <description>This page has been moved to soc</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-04-21T20:13:20-04:00</dc:date>
        <title>socint</title>
        <link>http://etherboot.org/wiki/socint?rev=1208823200&amp;do=diff</link>
        <description>Preparation


Coding will formally start on Monday 26th May (though you're welcome to start earlier, if you're ready).  You'll need to make sure that your build and test environment is up and running before this date.  Here's a rough checklist:


	*  On your main development machine, make sure you have gcc and all relevant build tools (binutils, make, etc.) installed.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soctools?rev=1147415128&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-05-12T02:25:28-04:00</dc:date>
        <title>soctools</title>
        <link>http://etherboot.org/wiki/soctools?rev=1147415128&amp;do=diff</link>
        <description>Script to extract data from SoC open applications
#!/bin/sh
# A very simple shell script to extract essential data from Google SoC
#  Application list pages
#  M. Connor Fri May 12 03:05:08 GMT 2006
#  Outputs name, email, project_title, score, has_mentor?

# First we Delete blank lines
sed -e &quot;/^$/d&quot; |

while read xx
do
   lineclass=`echo $xx | sed -e &quot;s@^.*class=@@&quot; -e &quot;s@\&quot;@@g&quot; -e &quot;s@\&gt;.*@@&quot;`
#  echo &quot;lineclass: $lineclass&quot;
   case &quot;$lineclass&quot; in
        &quot;listrequestapp&quot; )
            read x…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/staging?rev=1263589214&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-01-15T16:00:14-04:00</dc:date>
        <title>staging</title>
        <link>http://etherboot.org/wiki/staging?rev=1263589214&amp;do=diff</link>
        <description>[A boot ROM]

The staging tree is used to hold branches waiting for potential merging into the main gPXE tree.  It provides a central location for collecting patches submitted via the mailing list, IRC, and other methods.

Most branches in the staging tree hold individual features, such as a new driver, and are referred to as “feature branches”.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/start?rev=1277846009&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-29T17:13:29-04:00</dc:date>
        <title>start</title>
        <link>http://etherboot.org/wiki/start?rev=1277846009&amp;do=diff</link>
        <description>[A network card]

gPXE is an open source (GPL) network bootloader.  It provides a direct replacement for proprietary PXE ROMs, with many extra features such as DNS, HTTP, iSCSI, etc.  Take a look at our Screenshots page and the HowTo Guides for some ideas of what we can do, and grab the code from our Download page.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/syslinux?rev=1283471158&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-09-02T19:45:58-04:00</dc:date>
        <title>syslinux</title>
        <link>http://etherboot.org/wiki/syslinux?rev=1283471158&amp;do=diff</link>
        <description>Much like the howto usbwithstorage, this will guide you through installing gPXE on your flash drive (or any other FAT/ext234/btrfs partition for that matter) without losing ability to store files on it. In fact, using EXTLINUX or SYSLINUX, it's possible to use this method to make almost any medium gPXE-bootable.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/talks?rev=1278633750&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-08T20:02:30-04:00</dc:date>
        <title>talks</title>
        <link>http://etherboot.org/wiki/talks?rev=1278633750&amp;do=diff</link>
        <description>Members of the Etherboot Project have made regular appearances at various conferences and trade shows, given talks, and submitted papers.  This page links to some of those events and papers.  They provide an overview of our project and our software.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/tftp_backslash?rev=1204560266&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-03-03T11:04:26-04:00</dc:date>
        <title>tftp_backslash</title>
        <link>http://etherboot.org/wiki/tftp_backslash?rev=1204560266&amp;do=diff</link>
        <description>Several TFTP clients (notably those from Microsoft) require the TFTP server to accept a backslash (\) as a path separator, rather than the more usual forward slash (/).  It is often possible to configure your TFTP server to work around these broken clients.  The workaround will depend on the TFTP server that you are using.  Instructions are available for:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-10T15:44:31-04:00</dc:date>
        <title>todo</title>
        <link>http://etherboot.org/wiki/todo?rev=1249933471&amp;do=diff</link>
        <description>You probably want todo/start</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-08-08T08:11:20-04:00</dc:date>
        <title>troubleshooting</title>
        <link>http://etherboot.org/wiki/troubleshooting?rev=1218197480&amp;do=diff</link>
        <description>Troubleshooting FAQ

&quot;No IP address&quot;

Problem:
 You have setup a DHCP server, boot EtherBoot, but it will fail to accept an IP address from the server.

Solution:
 As of version 3.0.3 of the ISC DHCP server, the value of “next-server” does not have a reasonable default any more (it used to contain the IP address of the DHCP server, which would act as TFTP server then). You will have to set it to the IP address of the TFTP server (in most cases, the same machine as the DHCP server):</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/twodhcpservers?rev=1151246755&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T10:45:55-04:00</dc:date>
        <title>twodhcpservers</title>
        <link>http://etherboot.org/wiki/twodhcpservers?rev=1151246755&amp;do=diff</link>
        <description>Having more than one DHCP server on a network

It seems to be a common setup to have a DSL-router or similar device that has an integrated dhcp-server (which for one or another reason may not be turned off). For setting up a second dhcp server (e.g. for LTSP, handing out filenames, root-path's etc per gusto), it is reasonable to make it “not authoritative” and only hand out offers to several, hand-configured thin clients. Read the mail below, from LTSP mailing list:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/unity-patch?rev=1259176806&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-25T14:20:06-04:00</dc:date>
        <title>unity-patch</title>
        <link>http://etherboot.org/wiki/unity-patch?rev=1259176806&amp;do=diff</link>
        <description>I (rwcr) have been working on a rather extensive modification of gPXE, to allow images and SAN devices (and eventually files on filesystems) to be treated with more unity. This resolves a great many “ugly hack” comments, makes SAN booting less architecture-dependent, and allows one to SAN-boot ISO images (to name a few possibilities). The cost is a tiny size increase in image type codesize due to an additional layer of indirection, and a more significant size increase in block device codesize fo…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/usbwithstorage?rev=1253815550&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-24T14:05:50-04:00</dc:date>
        <title>usbwithstorage</title>
        <link>http://etherboot.org/wiki/usbwithstorage?rev=1253815550&amp;do=diff</link>
        <description>As stated  here you can place gPXE on a USB drive, unfortunately, the standard procedure will render your USB device unusable for any other purpose. The intention of this guide is to walk you through the process of deploying gPXE to a USB device and be able to still use it as storage media.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/usermanual?rev=1153346293&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-19T17:58:13-04:00</dc:date>
        <title>usermanual</title>
        <link>http://etherboot.org/wiki/usermanual?rev=1153346293&amp;do=diff</link>
        <description>Ken Yap - Markus Gutschke - Version 5.2.2

Copyright (C) 2001,2002,2003 Ken Yap and Markus Gutschke

2003-09-30

Revision History

	*  Revision 5.2.2   2003-09-30   Revised by: KY
	*  Revision 5.2.0   2003-08-11   Revised by: KY


This User Manual explains how to install, configure and compile the Etherboot package. The instructions here apply to version 5.2 of Etherboot.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/vmware?rev=1151396923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-27T04:28:43-04:00</dc:date>
        <title>vmware</title>
        <link>http://etherboot.org/wiki/vmware?rev=1151396923&amp;do=diff</link>
        <description>Making VMware boot Etherboot

You might have wondered wether VMware can run Etherboot. And yes indeed, that is possible.

VMware is known to emulate a /lance/-chipset ethernet PCI card. This emulation seems to do well enough to work with all those supported guest systems' drivers, but unfortunately, because of code relocation issues, the etherboot /lance/ driver will not work in a virtual machine. To overcome this reason, the /pcnet32/ driver has been written - with that driver, Etherboot 5.2 sh…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-13T09:10:09-04:00</dc:date>
        <title>vmwarebios</title>
        <link>http://etherboot.org/wiki/vmwarebios?rev=1236949809&amp;do=diff</link>
        <description>Using Etherboot inside the VMware BIOS

The following mail has been posted on June 26, 2006 by Borg Number One in the EtherBoot mailing list.

EtherBoot ROM in VMware and Bochs - The tutorial

(updated on 07.07.2006)

Declarations

	*  Expansion ROM / ExpansionROM , Extension ROM / ExtensionROM , Option ROM / OptionROM , Extension BIOS / ExtensionBIOS</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/winbootibft?rev=1158758251&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-20T09:17:31-04:00</dc:date>
        <title>winbootibft</title>
        <link>http://etherboot.org/wiki/winbootibft?rev=1158758251&amp;do=diff</link>
        <description>Representatives of Microsoft have recently raised objections to the publication of information describing the iSCSI Boot Firmware Table (iBFT).  The iBFT is a data structure used when Windows is booted from an iSCSI disk hosted on a remote computer, or on an iSCSI network-attached storage (NAS) box; a high-level overview is published by Microsoft at &lt;http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/STO026_WH06.ppt&gt;.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/windowsntloader?rev=1151247633&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2006-06-25T11:00:33-04:00</dc:date>
        <title>windowsntloader</title>
        <link>http://etherboot.org/wiki/windowsntloader?rev=1151247633&amp;do=diff</link>
        <description>Load Etherboot from a Windows 2000/XP NT loader

This page describes a possibility to add Etherboot to a Windows 2000/Windows XP only machine. 

Standard disclaimer:

Make a backup. Following the steps described on this page might very well destroy your operating system, data or mp3 files on your hard drive, or even worse things. I tried this at home, and it worked fine. I recommend you to try this on a non-production system before deploying a solution based on the methods described below.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-05T10:34:57-04:00</dc:date>
        <title>winpe</title>
        <link>http://etherboot.org/wiki/winpe?rev=1275748497&amp;do=diff</link>
        <description>[Windows AIK installation screen]

Overview


Windows Preinstallation Environment (WinPE) is a network-bootable version of Windows designed for installation, troubleshooting or system recovery.  It is not a general-purpose Windows system; it can be used only for these specific tasks.  If you want to boot a fully functional version of Windows, you need to Boot from SAN instead.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/winpe_memdisk?rev=1242335602&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-14T17:13:22-04:00</dc:date>
        <title>winpe_memdisk</title>
        <link>http://etherboot.org/wiki/winpe_memdisk?rev=1242335602&amp;do=diff</link>
        <description>This method of booting WinPE uses Memdisk to boot a hard disk image containing a WinPE WIM file and the support files necessary to load and boot the WIM. This is done in order to bypass the traditional (read: Microsoft) way of network booting WinPE over TFTP, and all the inherent problems with using TFTP, specifically, scaling to any significant number of clients on cheap hardware.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-29T15:30:55-04:00</dc:date>
        <title>wirelessboot</title>
        <link>http://etherboot.org/wiki/wirelessboot?rev=1259526655&amp;do=diff</link>
        <description>Thanks to some work done during Summer of Code 2009, gPXE supports the 802.11 protocol for accessing Wi-Fi wireless networks.

Note: the contents of this page rely on some features that are not yet present in mainline gPXE, but hopefully they should be there soon.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/zeroconf_design?rev=1258067923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-12T18:18:43-04:00</dc:date>
        <title>zeroconf_design</title>
        <link>http://etherboot.org/wiki/zeroconf_design?rev=1258067923&amp;do=diff</link>
        <description>Zeroconf is a set of tools used to create a local network in the absence of DHCP and DNS servers.  Using multicast DNS, IPv4 Link-Local Addressing, and DNS Service discovery (dns-sd) a local network can be full featured with out the need for a Wide Area Network (WAN).  There is a good video of zeroconf from a google talk: November 2, 2005 Dr. Stuart</description>
    </item>
</rdf:RDF>
