locked
XP/WINPE 2.0 RRS feed

  • Question

  • Hi,

     

    I am trying to get a windows xp and windows pe 2.0 environment working together as a dual boot, but it just dosnt seem to want to work?

     

    I am basically having two partitions one win xp and one winpe2.0

     

    I can get both to happily work seperately, however when i try to get winpe to reference my xp partition, i constantly complains about the ntldr file?

     

    I can get win pe2.0 to happily boot off a partition by the following;

     

    imagex /apply d:\sources\boot.wim 1 c:
      copy d:\bootmgr c:
      md c:\boot

    bcdedit -createstore c:\boot\BCD2
      bcdedit -store c:\boot\BCD2 -create {bootmgr} /d "Boot Manager"
      bcdedit -store c:\boot\BCD2 -set {bootmgr} device boot
      bcdedit -store c:\boot\BCD2 -create /d "WINPE" -application osloader
      Bcdedit -import c:\boot\BCD2

    bcdedit -store c:\boot\BCD -set {GUID} osdevice partition=c:
      bcdedit -store c:\boot\BCD -set {GUID} device partition=c:
      bcdedit -store c:\boot\BCD -set {GUID} path \windows\system32\boot\winload.exe
      bcdedit -store c:\boot\BCD -set {GUID} systemroot \windows
      bcdedit -store c:\boot\BCD -set {GUID} winpe yes
      bcdedit -store c:\boot\BCD -set {GUID} detecthal yes
      bcdedit -store c:\boot\BCD -displayorder {GUID} -addlast

     

    I then try to reference an XP installation;

     

    Bcdedit /create {legacy} /d “Description”
      Bcdedit /set {legacy} device boot
      Bcdedit /set {legacy} path \ntldr
      Bcdedit /displayorder {legacy} /addlast
      Bcdedit /timout 5

     

    However it just dosnt seem happy?

     

    If i set up my XP first then my PE, or vice versa it dosnt change anything? I can repair the PE insall from a windows vista cd to make win pe 'bdc' the bootloader instead of the win xp boot.ini, or if i install xp last i can load to an xp environment. I apreciate if i was setting up an xp/vista environmet i could use a whole host of utilities to refernce my legacy install, but i need the correct command lines as i only have winpe? By searching the web many people seem to have the same problem, but i can find the answer? If i use "bcdedit /enum all", i my bcd file seems fine.... it even looks identicle to a working vista/xp dual boot systems? copying the missing files from the windows cd dosnt help, which tends to be the general sudgestion? Can the two live together happily, or am i fighting a loosing battle?

     

    Oh, and i hve tried adding a "bcdedit /set {legacy} device partition=c:".... which was the original difference between my xp/vista and xp/winpe bcd file. Didnt make any difference?

     

    Thanks in advance, incase anyone has any ideas.

     

    Saturday, June 16, 2007 12:40 PM

Answers

  • be sure to change the windows directory for one or the other if you do this on one partition.

    bcd_create.cmd
    Code Snippet

    bcdedit -createstore c:\boot\bcd

    bcdedit -store c:\boot\bcd -create {bootmgr} /d "Boot Manager"

    bcdedit -store c:\boot\bcd -set {bootmgr} device boot

    for /f "tokens=3" %%a in ('bcdedit -store c:\boot\bcd -create /d "Windows PE" -application osloader') do set guid=%%a

     

    bcdedit -store c:\boot\bcd -set %guid% osdevice partition=c:

    bcdedit -store c:\boot\bcd -set %guid% device partition=c:

    bcdedit -store c:\boot\bcd -set %guid% path \windows\system32\boot\winload.exe

    bcdedit -store c:\boot\bcd -set %guid% systemroot \windows

    bcdedit -store c:\boot\bcd -set %guid% winpe yes

    bcdedit -store c:\boot\bcd -set %guid% detecthal yes

    bcdedit -store c:\boot\bcd -displayorder %guid% -addlast

     

    bcdedit -store c:\boot\bcd -create {legacy} /d "Windows XP"

    bcdedit -store c:\boot\bcd -set {legacy} device boot

    bcdedit -store c:\boot\bcd -set {legacy} path \ntldr

    bcdedit -store c:\boot\bcd -displayorder {legacy} –addlast

    bcdedit -store c:\boot\bcd -default {legacy}

    bcdedit -store c:\boot\bcd -timeout 5

    bootsect /nt52 all
    Monday, August 6, 2007 5:27 PM

All replies

  • Any luck getting this to work?  I've been having the sam e problem.
    Saturday, July 28, 2007 9:49 PM
  • Has any one found a solution to the problem above (dual boot winpe and winxp)? ...or Perhaps a website with more information.

     

    Monday, August 6, 2007 4:23 PM
  • be sure to change the windows directory for one or the other if you do this on one partition.

    bcd_create.cmd
    Code Snippet

    bcdedit -createstore c:\boot\bcd

    bcdedit -store c:\boot\bcd -create {bootmgr} /d "Boot Manager"

    bcdedit -store c:\boot\bcd -set {bootmgr} device boot

    for /f "tokens=3" %%a in ('bcdedit -store c:\boot\bcd -create /d "Windows PE" -application osloader') do set guid=%%a

     

    bcdedit -store c:\boot\bcd -set %guid% osdevice partition=c:

    bcdedit -store c:\boot\bcd -set %guid% device partition=c:

    bcdedit -store c:\boot\bcd -set %guid% path \windows\system32\boot\winload.exe

    bcdedit -store c:\boot\bcd -set %guid% systemroot \windows

    bcdedit -store c:\boot\bcd -set %guid% winpe yes

    bcdedit -store c:\boot\bcd -set %guid% detecthal yes

    bcdedit -store c:\boot\bcd -displayorder %guid% -addlast

     

    bcdedit -store c:\boot\bcd -create {legacy} /d "Windows XP"

    bcdedit -store c:\boot\bcd -set {legacy} device boot

    bcdedit -store c:\boot\bcd -set {legacy} path \ntldr

    bcdedit -store c:\boot\bcd -displayorder {legacy} –addlast

    bcdedit -store c:\boot\bcd -default {legacy}

    bcdedit -store c:\boot\bcd -timeout 5

    bootsect /nt52 all
    Monday, August 6, 2007 5:27 PM