Page 1 of 1
winpe - detect architecture
#1
Posted 27 October 2008 - 06:24 AM
i've got dhcp and tftp and dns under unix system. I made that i can boot win pe from pxe server (unix) but only one architecture, for example 32bit, if i want to boot another (64bit) i have to change wim image for 64bit version. Under Windows it happens automatically (it detects), but under unix i have to do it manually. What i have to do? please help
#3
Posted 27 October 2008 - 07:15 AM
http://technet.microsoft.com/en-us/library...351.aspx#enable
if I understand it right, there seems to be server-side and client-side detection mechanisms.
Now the question is, where is the client-side mechanism (either pxeboot.com or bootmgr) and how do you set it up, as server-side is a no-go for your situation.
edit:
some more insight: http://support.micro....com/kb/932447/
from http://technet.micro...y/cc754611.aspx
suppose you have the Boot\x86\Images folder structure, now try creating Boot\x64\Images and place the boot configuration storage (BCD) in the related folder, just that this BCD points to your x64 PE image. Not tested, but maybe worth a try.
if I understand it right, there seems to be server-side and client-side detection mechanisms.
Now the question is, where is the client-side mechanism (either pxeboot.com or bootmgr) and how do you set it up, as server-side is a no-go for your situation.
edit:
some more insight: http://support.micro....com/kb/932447/
from http://technet.micro...y/cc754611.aspx
Quote
The BCD Store Physical Structure
There are four possible classes of client computers, so four BCD stores are created in the \Tmp folder:
* x86-based. This file consists of the Default.bcd file from the \Boot\x86 folder and all boot image BCDs from the \Boot\x86\Images folder.
* Itanium-based. This file consists of the Default.bcd file from the \Boot\ia64 folder and all boot image BCDs from the \Boot\ia64\Images folder.
* x64-based. This file consists of the Default.bcd file from the \Boot\x64 folder and all boot image BCDs from the \Boot\x64\Images folder.
* x86-based and x64-based (this corresponds to if you run WDSUTIL /set-server /DefaultX86X64ImageType:both). This file consists of the Default.bcd file from the boot\x86 folder and all boot image BCDs from both the \Boot\x86\Images and \Boot\x64\Images folders.
There are four possible classes of client computers, so four BCD stores are created in the \Tmp folder:
* x86-based. This file consists of the Default.bcd file from the \Boot\x86 folder and all boot image BCDs from the \Boot\x86\Images folder.
* Itanium-based. This file consists of the Default.bcd file from the \Boot\ia64 folder and all boot image BCDs from the \Boot\ia64\Images folder.
* x64-based. This file consists of the Default.bcd file from the \Boot\x64 folder and all boot image BCDs from the \Boot\x64\Images folder.
* x86-based and x64-based (this corresponds to if you run WDSUTIL /set-server /DefaultX86X64ImageType:both). This file consists of the Default.bcd file from the boot\x86 folder and all boot image BCDs from both the \Boot\x86\Images and \Boot\x64\Images folders.
suppose you have the Boot\x86\Images folder structure, now try creating Boot\x64\Images and place the boot configuration storage (BCD) in the related folder, just that this BCD points to your x64 PE image. Not tested, but maybe worth a try.
This post has been edited by bj-kaiser: 27 October 2008 - 07:25 AM
#4
Posted 27 October 2008 - 08:00 AM
#5
Posted 27 October 2008 - 07:44 PM
mario_s, on Oct 27 2008, 09:00 AM, said:
You can do that from the x86 version of winPE. Doesn't require that you use x64.
EDIT (I looked up the actual command for you):
V:\x86\Std\sources\setup.exe /m:C:\OEM\$oem$ /tempdrive:C: /unattend:C:\unattend.xml /installfrom:V:\x64\Std\sources\install.wim /noreboot
This is the command line I use. You use the x86 version of setup.exe, and use the /installfrom: switch to point to the x64 wim file.
This post has been edited by Jazkal: 27 October 2008 - 07:51 PM
- ← net use failed under winpe 2.0
- Windows PE
- Detect HALs under WinPE (Vista) by running Batch Script →
Share this topic:
Page 1 of 1



Help
Back to top









