5 replies to this topic

[dw5304]

I have a working version of our current boot env under linux. Im trying to move to windows cause of bosses needs...
i copied all my boot files and i get a ip fragment error while loading the pe init... that is being set by my router.
if i set the tftp server to pxe compatibility mode i can get syslinux to boot. but when i select my windows installers it gives me a bcd error. even though it works fine under linux.
any ideas as to what i can try so i can fix this issue..

pxe comp mode:


option nogation:


it dose the same thing on another computer even with all vm's software removed.


current tftpd32 settings.

thanks in advance.


fixed it by going to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\guid for my network card
and setting MTU to 1492 and rebooting the system with option nogation: checked.

Edited by dw5304, 02 September 2011 - 07:02 AM.

[madmax69]

I had similar problems with TFTP protocol errors. Although non-intuitive in a PXE environment it needed PXE compatibility changing to Option Negotiation instead. I didn't need to edit the registry

[Wonko the Sane]

Yep, it is not at all intuitive , but is documented in most of the available guides, listed in the sticky here:
http://reboot.pro/1961/

As an example last one currently posted there leads you to:
https://sites.google...b/tutorials/pxe
where you can find:

Note: set Option negotiation, Bind TFTP to the PCs IP address and Allow \ as virtual root.
These settings are important! Do not tick PXE Compatibility (except as a last resort!).
The Tftp port MUST be 69.

Wonko

[madmax69]

Great links Wonko. Thanks! I've printed the Unattended XP guide out and it even inspired me to write another quick util I was planning for a while. One to patch the loader (binary) files from the command line instead of faffing about with a HEX editor! (e.g. when patching startrom.n1 and setupldr.exe as per the guide above).

I've already been looking at potential ways of multibooting via PXE/GRUB/startrom.X etc. and this has given me some useful clues

http://software.kerys.co.uk/binpatch/ (binary-file find/replace: alpha version, only just finished it, basic testing only so far)

[Wonko the Sane]

Great links Wonko. Thanks! I've printed the Unattended XP guide out and it even inspired me to write another quick util I was planning for a while. One to patch the loader (binary) files from the command line instead of faffing about with a HEX editor! (e.g. when patching startrom.n1 and setupldr.exe as per the guide above).

Which one?

With all due respect, and though a new utility tool is always welcome , there are already ways to NOT use a hex editor to replace a few bytes, namely what is commonly used is gsar:
http://home.online.no/~tjaberg/

A small quote for you :
http://reboot.pro/15298/page__st__9

BTW the link you posted is not working .


Wonko

[madmax69]

Ah, right. Dammit LOL. I'd not come across that one. Still it's always good to have an excuse to do a bit of coding. I'll have a look, thanks, I'm sure it will be better than mine.

The tutorial I found interesting was:
http://reboot.pro/1961/ -> http://reboot.pro/in...&attach_id=3390
(Guide_From_Base_Install_for_Fully_Unattended_Windows_Installs_Using_TFTPD32.doc)

I just checked the site and http://isthatsitedown.com showed it up at 13:00 GMT. It may be my ISP being awkward. (I could also access OK using Opera Tor (via Germany). The anti-bot tarpit software may have picked up your subnet perhaps.