The topic pretty much explains it... I've got WinPE 2.1 PXE booting, but some of my utilities (for setting asset tags, etc) only run on DOS, so I need to come up with a way to boot to my dos images from PXE.

Previously, I could just use 3com's el-junko pxe boot menu tool, but I have no idea how to make it work with WinPE.

If anyone has a tutorial on this, that would help tremendously.

i think you can't use the 3com pxe menu to boot into winpe.


Use the syslinux package. It includes pxelinux. It's freeware and you can make a boot menu
with the ability to boot to winpe and to dos floppy images.

http://syslinux.zytor.com/pxe.php

But i haven't a step by step guide for that. But i am sure if you use the search function
of this board you will get it.

This post has been edited by kyor: May 10 2008, 04:38 AM

OK i have made a small Guide with Step by Step instructions.

Hope you enjoy it

kyor[attachment=22028:How_to_m..._WinPE_2.pdf]

This post has been edited by kyor: May 10 2008, 07:46 AM

You, my friend, are a god among men.


Thanks!

Kyor,

I have been using the 3Com boot services and I have bene able to successfully boot to my custom WinPE image. However, I would also like to add the WinPE image to a menu and add the choice to the meny to boot from hard disk. Since the 3Com services don't support boot WinPE from a menu, I found this thread which sounded like a solution to my issue.

I have followed your step by step guide for PXE boot with pxelinux but without much luck. First, I want to make sure, I can use a windows workstation as my TFTPD server?

Also, if I follow your step by step, what is acting as the PXE server? With 3Com, I have to start both the PXE server and TFTP server, but with your instructions, I would only be running TFTPD32. I am running DHCP on another server so I can't run the DHCP server from TFTPD32 and hence, I am not configuring TFTPD32 as a DHCP server. Do I need to somehow add the "pxelinux.0" boot file to my DHCP server?

Thank you in advance for any additional guidance you can provide

Geemail

Yes thats right. You have to configure dhcp options. If you use Windows Server add optition 66 and 67.
See my example.