Jump to content

lollan

Member
  • Posts

    1
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About lollan

lollan's Achievements

0

Reputation

  1. Hello all, I am using a PXELINUX implementation to load WinPE and boot Windows OSes over the network. Windows 2008, 2003 and XP specifically. However, I have been unable to find the correct BCD settings to load separate instances of WinPE for different architectures. For instance: needing to load Windows PE x86 for 32 bit OSes. I can successfully boot Windows PE if my BCD file is in my root tftp directory, however if I move it to a sub directory, ie: \Boot\w2k8x86\, I get a blue screen each time referencing the "Boot\BCD". I read that it is necessary to hexedit bootmgr.exe to reference the correct BCD location if loading multiple versions of PE, but have been unable to find that entry in the executable. Has anyone done such a thing? Would it be easier to just keep at slipstreaming the 32 bit source files into the 64 bit image and using one WinPE image? I would REALLY appreciate some guidance here as it is driving me mad! Thanks in advance, all! *** Update 5/4/9 *** I have successfully edited my one BCD file where I can load separate .WIM files from Bootmgr, however this is not what I want to achieve. I want to be able to boot x86 or x86-64 architectures from my syslinux boot menu and load the installer from one user intervention there. I know it sounds picky, but I am trying to keep my setup as automated and unattended as possible. I have seen this done before, unfortunately I do not know how it was achieved. *** Update 5/6/9 *** Frustrated, I'm inspecting the previous administrator's configuration and I'm making small bits of headway. In the root tftpboot directory, he has 2 BCD files, neither of which named "BCD" which I thought was hardcoded and required? Regardless, if I import these files with bcdedit, I see it's doing exactly what I expected: Neither is there a "bootmgr.exe", each version of Windows being booted seems to have it's own as well. "osdevice ramdisk=[boot]\boot\w2k8x64\w2k8x64.wim,{ramdiskoptions}" I imagine you'd have to hex edit pxeboot.0 to look for files other than "BCD" in the root directory? I've not been able to find any information on how to do this after days of endless google searching. Any help is GREATLY appreciated! *** Solved 5/6/9 *** I used a different hex editor in Windows, "FlexHex" and was able to view the hex entries that I wasn't able to previously. I must have had an odd encoding option set or something, because I was seeing completely different characters before. All is good well with the world now, however. Created BCD and Bootmgr entries for each individual version of PE I wanted to boot from pxelinux and the rest was a breeze once I used FlexHex. Ecstatic to have it working!
×
×
  • Create New...