Hi every buddy.
i got a headache problem for weeks.
basically i try to xpe boot from a remote linux box
Here is my situation
i have been able to pxe boot from startrom.n12
TFTP and DHCP are running in windows. such as Tftp32 or
HaneWin DHCP Server .
what i do xpe boot from remote TFTP and DHCP server
1. config the TFTP and DHCP server and provide startrom.n12
as boot file.
2. place all necessary file in the tftp root
include
win2k3.img
boot.ini
NTLDR
startrom.n12
ntdect.com
boot.ini contents shows below
[boot loader]
timeout=60
[operating systems]
ramdisk(0)minicmd="win2k/" /fastdetect /minint /rdpath=net(0)win2k.img
so all above setting will make me xpe boot sucessfully
My question is how to xpe boot from startrom.n12
and all TFTP and DHCP server run on linux???
i did many tests.
here is what i do
i setup atftp and DNSMasq
i add a line in DNSMasq config file
dhcp-boot=startrom.n12,DD-WRT,192.168.11.100
then i place all files in atftp root
win2k3.img
boot.ini
NTLDR
startrom.n12
ntdect.com
now it comes a triger part
when i do a pxe booting. i found out
atftp and DNSMasq are functional
and i do see a booting menu which means
startrom.n12 and boot.ini are all been downloaded
but. when i enter the keyboard try to load win2k3.img
i was immediately shown a error stated that system could
not load img file.
i am sure win2k3.img sits in the right place.
as it works in win based system. but the error seems remind
me that i set path wrongly. so booting process has stopped.
boot.ini contents shows below
[boot loader]
timeout=60
[operating systems]
ramdisk(0)minicmd="win2k/" /fastdetect /minint /rdpath=net(0)win2k.img
boot.ini will tell ntldr where to find the win2k.img
i did not find anything wrong with it
i also tried
ramdisk(0)minicmd="win2k/" /fastdetect /minint /rdpath=win2k.img
ramdisk(0)minicmd="win2k/" /fastdetect /minint /rdpath=win2k.img
but all tries were failed.
Could anyone could sheld light to me?
any clue ?
Thanks in advance
austin
2 replies to this topic
#1
Posted 07 April 2012 - 05:00 AM
#2
Posted 07 April 2012 - 05:11 AM
i know a lot of people set pxelinux. 0 as xpe boot file instead of startrom.n12
something like this
dhcp-boot= pxelinux.0,DD-WRT,192.168.11.100
i wonder if anyone ever try to set
dhcp-boot=startrom.n12,DD-WRT,192.168.11.100
basically startrom.n12 serve same function as pxelinux.0. right???
Cheer
something like this
dhcp-boot= pxelinux.0,DD-WRT,192.168.11.100
i wonder if anyone ever try to set
dhcp-boot=startrom.n12,DD-WRT,192.168.11.100
basically startrom.n12 serve same function as pxelinux.0. right???
Cheer
#3
Posted 07 April 2012 - 05:19 AM
something need to mention
when boot from linux box NTLDR must be rename to capital letter
or you even can not see the boot.ini load manager when do a xpe boot
when boot from linux box NTLDR must be rename to capital letter
or you even can not see the boot.ini load manager when do a xpe boot
Also tagged with one or more of these keywords: pxe
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users