OK, thanks..I'll get back on to that tomorrow...
I have the HDD out back at the workshop now and i am at home.
This particular machine is a HP4530s that I run 'Dual Boot' ...via removing the HDD and sticking another SSD HDD in to run OS-X. Got it here with me now , but with the OS-X HDD in place.
I'll get back on to it tomorrow
Many thanks
Use the letter you see from winpe, it is an alias.
You also need to point at boot.sdi.
Example:
1. Create {ramdisktoptions} object in the bcd store:
bcdedit /create {ramdiskoptions} /d "Ramdisk options"
bcdedit /set {ramdiskoptions} ramdisksdidevice partition=Drive:
2. Add sdipath:
bcdedit /set {ramdiskoptions} ramdisksdipath \Recovery\WindowsRE\boot.sdi
3. Create boot application entry:
for /f "tokens=1-3" %%a in ('Bcdedit /create /d "Boot from Wim" /application osloader') do set PE_GUID=%%c
bcdedit /set %PE_GUID% device ramdisk=[Drive:]\Recovery\WindowsRE\winre.wim,{ramdiskoptions}
bcdedit /set %PE_GUID% osdevice ramdisk=[Drive:]\Recovery\WindowsRE\winre.wim,{ramdiskoptions}
bcdedit /set %PE_GUID% path \windows\system32\winload.exe
(note - use winload.efi for efi boot )
bcdedit /set %PE_GUID% systemroot \windows
3. Specify winpe:
bcdedit /set %PE_GUID% winpe yes
bcdedit /set %PE_GUID% detecthal yes
4. Add new entry to display order:
bcdedit /displayorder %PE_GUID% /addlast
Last edited by SIW2; 27 Dec 2013 at 14:58.
Here are a few examples: Johan Arwidmark - Booting WinPE 2.0 from a third party PXE Server
for /f "tokens=1-3"
Works in english version. In some foreign languages it is: for /f "tokens=1-2"
Here are the BCD files I currently have on the now removed HDD.
This is a working system.
I am not going to touch this system.
Will need to find another HDD to try a recovery too, as I wan't to avoid screwing with this now I have got it working..but want the knowledge to do it again when necessary...as I am sure that will occur. The only thing that is going to stop me is if it turns out not to be possible to get Win7 to see the network and FreeBSD CIFS SMB and Mac AFP shares. If Win7 cant be set up to do that then it is not going to be worth the effort to use Win7
HP_Recovery PARTITION BCD
System PARTITION BCD'sCode:Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device boot path \bootmgr description Windows Boot Manager locale en-US default {572bcd55-ffa7-11d9-aae0-0007e994107d} displayorder {572bcd55-ffa7-11d9-aae0-0007e994107d} timeout 30 Windows Boot Loader ------------------- identifier {572bcd55-ffa7-11d9-aae0-0007e994107d} A device attached to the system is not functioning.
Code:Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device unknown description Windows Boot Manager locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} extendedinput Yes default {c0e849d1-6e89-11e3-aa17-c4df00072efd} resumeobject {c0e849d0-6e89-11e3-aa17-c4df00072efd} displayorder {c0e849d1-6e89-11e3-aa17-c4df00072efd} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 30 customactions 0x1000085000001 0x5400000f custom:5400000f {c0e849d4-6e89-11e3-aa17-c4df00072efd} Windows Boot Loader ------------------- identifier {c0e849d1-6e89-11e3-aa17-c4df00072efd} device unknown path \windows\system32\winload.exe description Windows 7 locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence {c0e849d4-6e89-11e3-aa17-c4df00072efd} recoveryenabled Yes osdevice unknown systemroot \windows resumeobject {c0e849d0-6e89-11e3-aa17-c4df00072efd} nx OptIn
FROM WORKING C:\
Code:Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device locate=custom:12000002 description Windows Boot Manager locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {b5c086aa-359d-11e0-ae5e-82634f96898b} resumeobject {b5c086a9-359d-11e0-ae5e-82634f96898b} displayorder {b5c086aa-359d-11e0-ae5e-82634f96898b} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 30 Windows Boot Loader ------------------- identifier {b5c086aa-359d-11e0-ae5e-82634f96898b} device unknown path \windows\system32\winload.exe description Windows 7 locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} truncatememory 0x100000000 recoveryenabled No osdevice unknown systemroot \windows resumeobject {b5c086a9-359d-11e0-ae5e-82634f96898b} nx OptIn
HP_Recovery PARTITION BCD: Is that really the bcd located on that partition?
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
A device attached to the system is not functioning.
--is that realy end of output??
System PARTITION BCD's: Where is that bcd located?
FROM WORKING C:\: That bcd is on C?
Post bcdedit/enum all output.
Yes, that is it..
it is located
HP_RECOVERY\boot\bcd
maybe because that is created initially at the point where there is no data on the c:\..it is just a blank partition
in a boot folder on the SYSTEM drive..the 300mb 1st partition
System\Boot\bcd
Yes on c:
c:\boot\bcd
have mounted the drive on an external USB adapter and pulled the BCD's off it from there and viewed the output via EasyBCD running on a VM machine.
Will booting the real machine from this HDD and running bcdedit/enum all give a different output? If so , i'll get on with it.
From Elevated Command Prompt
Replace C with actual drive letter of HP_RECOVERY, C drive, SYSTEM RESERVED.Code:bcdedit /store C:\boot\bcd /enum all
Post output.
Which of the 3 partitions has been marked as ACTIVE btw?
Should I do this from within elevated cmd prompt of the running system? or boot from Win PE USB or Win7 Install disk Repair console?
OK, well I have it running now from within win7...
just having issues with exporting to text.
reading this now
BCDedit output to text ?
It is the 300mb System partition that is the active one
Quote
