mchipser

slow pxeboot.0 with 3rd party tftp

29 posts in this topic

BOOTMGR and BOOTMGR.EXE are actually the "same" file BUT the second has some added code to make it a suitable "pxe" target.

Being a little picky, but it would be more correct to say something like;

"BOOTMGR and BOOTMGR.EXE are actually the same file, but the first has some added code (16-bit) to make it a suitable local boot target"

0

Share this post


Link to post
Share on other sites
BOOTMGR and BOOTMGR.EXE are actually the "same" file BUT the second has some added code to make it a suitable "pxe" target.

Being a little picky, but it would be more correct to say something like;

"BOOTMGR and BOOTMGR.EXE are actually the same file, but the first has some added code (16-bit) to make it a suitable local boot target"

Yep :yes: , my bad I got it the "other way round" :blushing: .

jaclaz

0

Share this post


Link to post
Share on other sites
BOOTMGR and BOOTMGR.EXE are actually the "same" file BUT the second has some added code to make it a suitable "pxe" target.

Being a little picky, but it would be more correct to say something like;

"BOOTMGR and BOOTMGR.EXE are actually the same file, but the first has some added code (16-bit) to make it a suitable local boot target"

I think the .exe version has the extra code, at least it is a bigger sized file..

0

Share this post


Link to post
Share on other sites

I think the problem lies in how bootmgr.exe looks for the BCD, which is confirmed from the post earlier; however why cant i use bootmgr from pxelinux? I think it is an issue with using a *nix tftp server. I thought this would be fixed by using the remap feature of the tftp server, but apparently not..

when booting from isolinux i can boot bootmgr fine with no delay.

When trying to boot bootmgr from pxelinux it can not find the bcd but booting bootmgr.exe it find it with the delay..

BOOTMGR and BOOTMGR.EXE are actually the "same" file BUT the second has some added code to make it a suitable "pxe" target. EDIT: BUT the first has some added code (16 bit) to make it a "local boot" target.

EXACTLY like it was in the good ol'days with SETUPLDR and SETUPLDR.EXE, see:

http://reboot.pro/5900/

http://reboot.pro/4952/#entry40701

It seems to me like you pinned down exactly the problem, i.e. the way BOOTGR.EXE looks for the BCD, and right now it seems to me like there are only the metioned ways out:

  1. use an original WDS server
  2. using the workaround you found http://www.0xf8.org/2012/04/the-30-second-delay-in-booting-windows-pes-pxeboot-com-via-pxelinux/
  3. using an alternate WDS server (suggested but UNtested)
  4. using an alternate loader from pxelinux (suggested but UNtested)

Another possibility (also to be tested) is here:

http://reboot.pro/1656/

http://www.ultimatedeployment.org/win7pxelinux1.html

jaclaz

  1. use an original WDS server
  2. using the workaround you found http://www.0xf8.org/2012/04/the-30-second-delay-in-booting-windows-pes-pxeboot-com-via-pxelinux/
  3. using an alternate WDS server (suggested but UNtested)
  4. using an alternate loader from pxelinux (suggested but UNtested)

I am currently using #2.. What other loaders can i use from pxelinux besides grub4dos / grldr, since that one kept giving me errors.

Edited by mchipser
0

Share this post


Link to post
Share on other sites

I think the .exe version has the extra code, at least it is a bigger sized file..

Trust me, bootmgr has every single byte of bootmgr.exe, plus some more (16-bit). It's just that bootgmr.exe is compressed when residing "inside" bootmgr.

0

Share this post


Link to post
Share on other sites

I am currently using #2.. What other loaders can i use from pxelinux besides grub4dos / grldr, since that one kept giving me errors.

Hmmm. :unsure:

Which errors?

Using grub4dos/grldr how (EXACTLY)?

Using grub4dos/grldr which (EXACT) version?

Why #3 is not an option?

Why not trying the 5th (or maybe 5th and 6th) way?

jaclaz

0

Share this post


Link to post
Share on other sites

I think the .exe version has the extra code, at least it is a bigger sized file..

Trust me, bootmgr has every single byte of bootmgr.exe, plus some more (16-bit). It's just that bootgmr.exe is compressed when residing "inside" bootmgr.

I trust you :thumbup

0

Share this post


Link to post
Share on other sites

I am currently using #2.. What other loaders can i use from pxelinux besides grub4dos / grldr, since that one kept giving me errors.

Hmmm. :unsure:

Which errors?

Using grub4dos/grldr how (EXACTLY)?

Using grub4dos/grldr which (EXACT) version?

Why #3 is not an option?

Why not trying the 5th (or maybe 5th and 6th) way?

jaclaz

well i have been trying to get grub to boot the bootmgr / bootmgr.exe with no luck.. this is using TFTPD32

I keep getting an error..


Error 13: Invalid or unsupported executable format

The menu.lst looks like:

title winpe
pxe keep
chainloader /bootmgr

with this menu.lst i get this error

title winpe
pxe keep
chainloader --raw(pd)/bootmgr

Error 1: Filename must be either an absolute pathname or blocklist

I switched from using our current WDS for the TFTP transfer (it is still the DHCP server) since that server only has 10/100 network cards for two of the VLANs. The NAS which is now running the TFTP server has 10/100/1000. I rather not commit another piece of hardware to this.. If the switches I have supported DHCP relay this would not be a problem, they do have VLAN routing though.. I know i could build a RRAS on each VLAN to get IPs, but again another piece of hardware.

I posted in the netgear forums, with no luck..

http://forum1.netgear.com/showthread.php?t=78601

Edited by mchipser
0

Share this post


Link to post
Share on other sites

I think the problem lies in how bootmgr.exe looks for the BCD, which is confirmed from the post earlier; however why cant i use bootmgr from pxelinux? I think it is an issue with using a *nix tftp server. I thought this would be fixed by using the remap feature of the tftp server, but apparently not..

when booting from isolinux i can boot bootmgr fine with no delay.

When trying to boot bootmgr from pxelinux it can not find the bcd but booting bootmgr.exe it find it with the delay..

I am going to try using a windows based tftp server and see what happens

EDIT:

here is a copy of my remap file.


re ^BCD Boot/BCD
r ^\\Boot\\ Boot/
r ^\\boot\\ Boot/
rg \\ /1

I must admit it is several years since I did this, but I remember noticed strange things about different versions of bootmgr.exe's. Read this thread; http://sanbarrow.com/phpBB2/viewtopic.php?t=1705 (maybe aim at page 2 and 3). My tests where done on Windows XP and tfpd32. Maybe there's some usefull information in there.

0

Share this post


Link to post
Share on other sites

with this menu.lst i get this error

title winpe
pxe keep
chainloader --raw(pd)/bootmgr

Error 1: Filename must be either an absolute pathname or blocklist

Without entering in whether the actual "concept" is correct (last time I checked you hade to load pxeboot.n12 :whistle: ), the error 1 simply means that you have not a space between the --raw switch and the target file path and the grub4dos parser reads "--raw(pd)/bootmgr" as a "single item" (since it is a single item withut the space).

Again, which EXACT version of grub4dos is it?

What device (NAS/whatever) is it?

Can it not trun a BINL server?

As in:

http://reboot.pro/1656/#entry119166

http://www.ultimatedeployment.org/win7pxelinux5.html

jaclaz

0

Share this post


Link to post
Share on other sites

Without entering in whether the actual "concept" is correct (last time I checked you hade to load pxeboot.n12 :whistle: ), the error 1 simply means that you have not a space between the --raw switch and the target file path and the grub4dos parser reads "--raw(pd)/bootmgr" as a "single item" (since it is a single item withut the space).

Shouldn't it be possible to load bootmgr directly? isolinux and syslinux can both do it. Is the environment of pxe not able to load bootmgr directly? I can get it to load, but it is unable to find the BCD.

Again, which EXACT version of grub4dos is it?

Grub.exe 0.4.4 / grldr 0.97

What device (NAS/whatever) is it?

We are currently using a QNAP TS-EC1279U-RP, which runs a version of debian, i think.

Edited by mchipser
0

Share this post


Link to post
Share on other sites

Grub.exe 0.4.4 / grldr 0.97

That is:

  1. NOT a version of grub4dos (grub4dos version after 0.4.3 have a date 0.4.4 2009-10-16 being the ONLY recommended version of the 0.4.4 series
  2. it is SEVERELY outdated

Get LATEST "Featured" from here (NOT any among the TestOnly version):

http://code.google.com/p/grub4dos-chenall/downloads/list

Then follow this gude:

http://diddy.boot-land.net/pxe/

If you want to better understand how grub4dos works, besides the readme.txt, do check the guide:

http://diddy.boot-land.net/grub4dos/Grub4dos.htm

Though many new features were added to grub4dos the "base" is still valid.

Check also on reboot.pro, example:

http://reboot.pro/15821/

On UNrelated news :w00t::ph34r:, fresh of today, iPXE+http boot:

http://reboot.pro/17520/

jaclaz

0

Share this post


Link to post
Share on other sites

Grub.exe 0.4.4 / grldr 0.97

That is:

  1. NOT a version of grub4dos (grub4dos version after 0.4.3 have a date 0.4.4 2009-10-16 being the ONLY recommended version of the 0.4.4 series
  2. it is SEVERELY outdated

looks like mine is 0.4.4 2009-03-31

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.