Jump to content











Photo

PXE LAN BOOT GRUB4DOS over TFTPD32 WINPE and over

pxe pxe boot tftpd32 lan boot grub4dos winpe lan boot pe lan pe lan boot tutorial guide

  • Please log in to reply
5 replies to this topic

#1 rushyn

rushyn
  • Members
  • 5 posts
  • Location:Brisbane
  •  
    Australia

Posted 14 November 2011 - 07:55 AM

Hello All

I origenaly posted this in reboot.pro→ Groups→ Project forge→ Tftpd32 but was advised to move it.

I was PMed by one of reboot.pro members asking me how to setup a PXE boot server. I did compose a responses to that member then I was done I decided it was a good idea to start a new thread for this. This is not exactly the same I have made some changes.



Some basic disclaimers first.



1. There is more than one way to Skin a Cat. You can set it up on Windows or Linux or Even Over operating system platforms.

2. You can set it up Using the proper Microsoft but I strongly recommend you avoid it. For one you can only do it on a Windows Server and you need to set it up as a domain controller and if you’re not wondering what the hell was Microsoft was finking. Wall......

There also a number of over ways to do this.

3. I recommend that you read the whole guide before attempting it that way you can download every fing first before you start playing with NIC IP address




Ok so the goal is to setup a PXE boot on a windows platform on any windows 2000 or later platform.

Here is a list of tools you will need.

1. TFTP32 http://tftpd32.jouni...2_download.html "Download the 32bit tftpd32 standard edition (zip) version unless you have good reason to use the 64bit one I have had some problems with the 64bit."

2. You will need http://grub4dos-chen...b-2011-10-30.7z now DO NOT just Google it as it will give you links to a 4 year old version and it has problems with current AHCI and EFI/EFI hybrid mainboards.

3. This one is optional depending on there you intend to make your own WINPE. Windows OPK here.
http://www.microsoft...dows_7_opk.aspx
http://oem.microsoft...opk_english.img (English Version) (you may need a login)

4. If you have no understanding of the basics of network theory hear is how to setup your Network Interface Card (NOT WLAN (LAN, Ethernet 802.1). To people hum know what they are doing feel free to modify this instructions.
Assuming windows 7

4a. Go to Start -> Control Panel.

In the right top hand corner change the option to Large Icons.

Go to Network and Sharing Centre -> Then click Chang Adapter Settings

Assuming you only have one NIC(network interface card) and you have not renamed it there will be “Local Area Connection” right click then go properties.

In the “Local Area Connection Properties” select “Internet Protocol Version 4 (TCP/IPv4) then click “Properties”

Place the dot in “Use the following IP address”

IP Address: 192.168.1.250

Subnet Mask: 255.255.255.0

Default Gateway: Blank if uncertain

Preferred DNS server: Blank if uncertain

Alternate DNS Server: Blank if uncertain

Click Ok then Ok again.

Also if you have a router that give out IP address on your network or an over DHCP server running make shire to unplug it or it WILL cause you problems (Just unplug it that way you can just plug it back in. (If you are setting up on the server (windows server) just stop the DHCP service)




Ok hear is how to set it up (Now you do not have to set it up this way but it’s the way I have it setup.)

1. Create a directory called "TFTP32" in "C:\" (C:\TFTP32)

2. Extract the contents of "tftpd32.400.zip" in to "C:\TFTP32" "If you do not have a program that can extract ZIP files I recommend WINRAR http://www.rarlab.com/download.htm but it’s not the only program you can use"

3. In "C:\TFTP32\" create directory called "root" (C:\TFTP32\root\)

4. In grub4dos-0.4.5b-2011-10-30.7z archive there will be a directory called "grub4dos-0.4.5b" extract the contents of that directory not the directory itself in to "C:\TFTP32\root\"

5. Create a boot directory in "C:\TFTP32\root\" so it looks like these "C:\TFTP32\root\boot\" the boot directory is there you place boot images I.E. "ISO,
IMG overs."

6. Now we need to edit the menu.lst in "C:\TFTP32\root\menu.lst" you can use notepad but I recommend notepad++ http://notepad-plus-...d/v5.9.6.1.html

7. Ones you have menu.lst opened delete every fink below line 9. (you may want to hold on to a copy of the file it has a good examples of how to do stuff) Delete line 7 if you do not want it to time out.

9. Now we are going to setup 2 boot entrees as examples one for a floppy disk image and one for ISO

9a. First an ISO this one is for booting PE. Copy paste the could in to the menu file


title TEST PE
map --mem /boot/testpe.iso (0xff)
map --hook
chainloader (0xff)
boot

So what douse this mine?


title TEST PE (the title serves to function first it indicates the begging of the script second whatever you type after will be what you see in the GRUB4DOS menu.)
map --mem /boot/testpe.iso (0xff) (this indicates that file testpe.iso needs to be loaded in to RAM from TFTP server not to be confused with FTP {(0xff)} indicates it’s an ISO)
map --hook (I do not know what this douse but it doesn’t work without.)
chainloader (0xff) (This indicates that CD/DVD drive emulation needs to be applied.)
boot (I fink this one is self-expiatory)

9b. Here is an example of how to boot from a floppy image.


title DOS TEST
map --mem /boot/dostest.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

Its pretty march the same as ISO the deferens is (fd0) and "rootnoverify"

(fd0) is floppy drive emulation.
"rootnoverify" is essentially boot but works differently.

You can download some dos boot IMG fines from hear http://www.allbootdi...wnload/dos.html there will work for testing you want the *.IMG not *.EXE

You can also download a WINPE image that is good for testing http://www.4shared.c...npe_30_x86.html

One you have edited the menu.lst and pleased the images in the proper directory’s and fixed names.

10. Run TFTP32 C:\TFTP32\tftpd32.exe

11. Now it’s time to configure TFTP32

11a. Go to settings in the "TFTPD32:Settings" go to GLOBAL windows make sheer that

TFTP Server

DHCP Server

Are ticked

11b. Go to settings in the "TFTPD32:Settings" go to TFTP windows make sheer that

TFTP Security is set to NONE

PXE Compatibility
Translate Unix File names
Allow "\' as virtual Root

I also recommend that you binned the TFTP server to a specific Network address using IP the options is "Bind TFTP to this address”

Are ticked the rest are un-ticket "you can have over options turned on especially "anticipation window of" and set I recommend to 4096 to improve transfer speeds but play with this options after you have it working."

11c. Go to settings in the "TFTPD32:Settings" go to DHCP windows make sheer that

I'll live the options hear to your discretion except for 2 (if you need help setting the DHCP server PM me and I’ll give you some pointers)

"Boot File" needs to be "grldr"

"Bind DHCP to this address"

12. Click ok then KILL TFTP32 sometimes you need to reboot the application in order the settings to apply the start it again.

13. You will need a second computer that is PXE capable. (Now all most all mainboards have PXE capability but you will probably need to enable the function in BIOS/EFI

14. If every fing works then you will be able to boot over PXE.

Have Fun.

#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 5,319 posts
  • Location:UK
  • Interests:computers (!), programming (masm,vb6,C,vbs), OSes, photography,TV,films,guitars
  •  
    United Kingdom

Posted 14 November 2011 - 11:15 AM

You may also find this tutorial useful http://www.rmprepusb.com/tutorials/pxe

#3 sambul61

sambul61

    Gold Member

  • Advanced user
  • 1,568 posts
  •  
    American Samoa

Posted 14 November 2011 - 12:51 PM

Thank you both guys! Very useful... :thumbsup:

#4 Tripredacus

Tripredacus

    Frequent Member

  • Expert
  • 183 posts
  • Interests:K-Mart-ian Legend
  •  
    United States

Posted 14 November 2011 - 02:28 PM

Honestly, there's nothing special about using the OPK over the WAIK. The only real difference is that the help files have extra information regarding licensing.

#5 rushyn

rushyn
  • Members
  • 5 posts
  • Location:Brisbane
  •  
    Australia

Posted 14 November 2011 - 10:10 PM

Honestly, there's nothing special about using the OPK over the WAIK. The only real difference is that the help files have extra information regarding licensing.


So just use the WAIK I am not stooping you.

#6 komori

komori
  • Members
  • 1 posts
  •  
    Romania

Posted 14 June 2012 - 04:45 PM

Hi, guys,

I think I'm coming up with a little bit of a challenge.

I want to do something a bit out of the ordinary. I've set up a VM with a 2008 R2 with WDS.
following the stuff from HERE and HERE, I've managed to set up my own personalized menu in WDS.
I've tested it only with an acronis rescue media and of course the win7 x86 and x64 boot images and it works without a hitch, be it with other VMs or direct network bridging and physical PCs.

However, due to practical reasons, I want to make the whole thing above work with a tftpd solution. I have a low-resource PC which I want to use with a blank windoze / linux system and a tftpd util to be able to roll out various disk images created via WDS
So, is there any way to make this work, using the boot, capture and install images with the respective appended drivers with the tftpd solution?
I'm very happy with the image capturing, driver appending and deployment from WDS, but I don't want to depend on the VM to deploy stuff.

Thanks!





Also tagged with one or more of these keywords: pxe, pxe boot, tftpd32, lan boot, grub4dos, winpe lan boot, pe lan, pe lan boot, tutorial, guide

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users