J
John F. Davis
Hello
I am trying to get wndows xp embedded to network boot. I am fairly ms
illiterate so bear with me.
Here is my setup. I have three machines. One is a windows 2k
professional running the windows xp embedded tools. A second is a
win2k/win xp embedded dual boot machine. A third is a linux server.
I can build xp embedded images which i can boot from hard disk. I
used this image to create a ramdisk.sdi file. I used the Saad Syed
information from this newsgroup to create the ramdisk. ie.
create a sdi file that is 128 MB, copy the contents of my already
FBA'd XP embedded bootable hard disk partition to this sdi file
excluding boot.ini, ntdetect.com, and ntldr.exe per the same document,
running the three cscript cmmands to create the second and final
ramdisk.sdi file. Then I put the .sdi file on the tftp directory of
my win2k pro (not server) box which is running the tftp service.
Then, I configure the linux dhcp server to tell the target machine to
tftp one of two images.
Try #1.
I use this setting in dhcpd.conf
option PXE.mtftp-ip "ip address of my win2k pro machine"
filename "ramdisk.sdi"
next-server "ip address of my win2k pro machine"
This results in the target machine trying to boot. It fails with this
message:
PXE-E34 TFTP to many packages.
I did a search on google and I found that its possibly a problem in
that I am trying to tftp the 128MB ramdisk.sdi file when I need to
tftp a pxe loader file first. This lead me to try #2.
Try #2.
I changed the settings on my DHCP server to be:
filename "startrom.n12"
This time when I boot the target machine it fails with the message:
NTLDR:Fatal Error 21 reading BOOT.INI.
You got me what the problem is. I did not put BOOT.INI in the
ramdisk.sdi file. I don't know if its actually trying to get the
ramdisk.sdi file.
Here is how I have the remote boot manager setup:
Client Mac Address - my mac addr
Description - my descript
Action - boot
Boot Server -192.168.0.6 "The ip address of my win2k pro box running
remote boot manager."
Boot Program - startrom.n12 "picked because it sounded like what I am
tryinto do."
Boot Image ramdisk.sdi
Boot Parms blank
None of the check boxes are checked inthe Global settings pane.
The defaul settings say boot server is 0.0.0.0, boot program is
abortpxe.com, bootimage and boot parms are blank.
Please advise.
I am trying to get wndows xp embedded to network boot. I am fairly ms
illiterate so bear with me.
Here is my setup. I have three machines. One is a windows 2k
professional running the windows xp embedded tools. A second is a
win2k/win xp embedded dual boot machine. A third is a linux server.
I can build xp embedded images which i can boot from hard disk. I
used this image to create a ramdisk.sdi file. I used the Saad Syed
information from this newsgroup to create the ramdisk. ie.
create a sdi file that is 128 MB, copy the contents of my already
FBA'd XP embedded bootable hard disk partition to this sdi file
excluding boot.ini, ntdetect.com, and ntldr.exe per the same document,
running the three cscript cmmands to create the second and final
ramdisk.sdi file. Then I put the .sdi file on the tftp directory of
my win2k pro (not server) box which is running the tftp service.
Then, I configure the linux dhcp server to tell the target machine to
tftp one of two images.
Try #1.
I use this setting in dhcpd.conf
option PXE.mtftp-ip "ip address of my win2k pro machine"
filename "ramdisk.sdi"
next-server "ip address of my win2k pro machine"
This results in the target machine trying to boot. It fails with this
message:
PXE-E34 TFTP to many packages.
I did a search on google and I found that its possibly a problem in
that I am trying to tftp the 128MB ramdisk.sdi file when I need to
tftp a pxe loader file first. This lead me to try #2.
Try #2.
I changed the settings on my DHCP server to be:
filename "startrom.n12"
This time when I boot the target machine it fails with the message:
NTLDR:Fatal Error 21 reading BOOT.INI.
You got me what the problem is. I did not put BOOT.INI in the
ramdisk.sdi file. I don't know if its actually trying to get the
ramdisk.sdi file.
Here is how I have the remote boot manager setup:
Client Mac Address - my mac addr
Description - my descript
Action - boot
Boot Server -192.168.0.6 "The ip address of my win2k pro box running
remote boot manager."
Boot Program - startrom.n12 "picked because it sounded like what I am
tryinto do."
Boot Image ramdisk.sdi
Boot Parms blank
None of the check boxes are checked inthe Global settings pane.
The defaul settings say boot server is 0.0.0.0, boot program is
abortpxe.com, bootimage and boot parms are blank.
Please advise.