So I worked until 11:30 last night perfecting my pxe boot scenario. I have it down pat now and have moved beyond the normal ghost image they create for you and have made my own. But first, let me explain the process as I know it:
1.) The NIC starts the PXE boot and broadcasts for a DHCP address. A simple MS DHCP server gives my client an IP.
2.) The DHCP server also has 2 more entries in it. TFTP Server and TFTP Filename (This is the "Bootstrap", <512k file that is so hard to generate). Since I am running the TFTP server on the DHCP server, it makes it easy (no DHCP Proxy necessary). So now the NIC grabs these 2 values from the DHCP server and requests the "Bootstrap" file that you defined earlier.
3.) The NIC downloads the bootstrap file, which is a tiny OS that just tells it what the name of your floppy image (this is the 1.44 - 16Mb file) is and downloads it.
4.) From there, your floppy/boot image is anything you want it to be. At first I started with the generic ghost image disk, and that works well.
That's it. Done. Very easy.
However, the ghost floppy/boot image only supports ghostcast servers and personally I find that 2x the work if I have to visit the server and set it up and then visit the client and set it up. No, a network boot image is where I want to be, yet the ghost pxe image doesn't have any drive mapping functions (cmds.exe/net.exe) and the network drive mapping solution from ghost doesn't allow you to create that version as an image, only a floppy.
So, I used the handy dandy tools that come with 3com's boot assist version 7.0 and edit the image. The tool is horrible, doesn't support copying directories, and barely works. But it does, so enough complaining. So I added the right stuff from the network drive mapping floppy with the ghost image it created, and it was finished.
I can now turn on a new machine, change the nic to boot first, have it boot to the network, download the image, map a drive and run ghost so I can pull/push the images using windows networking instead of using the limited ghostcast solution.
Sweet. Except that I stopped using the ghost network mapping disk years ago since it barely works and there are 0 tools on that disk and since it uses pcdos, you will have trouble finding the tools for it. So I use barts network boot disk (http://www.nu2.nu/bootdisk/network/) instead. It is a GREAT modular solution, very easy once you get the hang of it, and it supports any nic, any network, domains as well as workgroup authentication, retrying of username/passwords, and even saving of common profiles. Good stuff.
The migration of the ghost image and barts disk is very easy. You just HAVE to use the system files from the ghost disk (msdos.sys, io.sys, command.com I believe) and all the rest is from barts boot disk. I found it handy to get the disk working the way I wanted it, and then move it over to the image. Most of the time I spent was modifying barts disk to remove unecessary features, trim down the chattyness, and remove some of the popup configuration dialogs.
Ok, so this is really long, and I should get to my point. My point is, You DON'T need a pxe server, just that one really hard to get bootstrap file. IMHO I think I could just send you the bootstrap file and that is everything you need. Just use pumpkin or any other tftp server and that is it.
If you can get by with the ghost cast server solution that the ghost image gives you then you are finished. If you want to modify the boot image, then you need a pxe image editor, which I got from the 3com boot services.
It really is a pretty simple and easy procedure. They make it sound so tough and charge a TON of money for a tftp server and a bootp server (which a dhcp server works just as well). They know that that little 20k bootstrap file is the hard part.