Comments on: BCDboot and BCDedit

By: Pride

Pride — Fri, 18 Sep 2009 15:31:47 +0000

…to put that long post very short.

Just RESTART before applying the: bcdboot d:\windows /s c: -command

By: Pride

Pride — Thu, 17 Sep 2009 06:29:59 +0000

I’ve found out something really weird myself.

After starting WinPE, diskparting your HDD to two partitions (one 200mb for bitlocker, will be assigned C-letter, and second for D – Windows) and applying .wim -image with ImageX, bcdboot doesn’t do ANYTHING. Yes, it says “bootfiles succesfully created”, but indeed that’s not the case. Still claims boot manager is missing, BUT…

…after you re-run WinPE and run simply bcdboot again, everything works fine. Only reason I’ve came up with is that after diskpart + image apply, bcdboot cannot do some of the changes it should do, which require a restart first. So, don’t lose your hope if you get “bootmgr is missing!” at the first time, instantly after dropping your image! Try it twice!

Notice that the syntax is: bcdboot d:\windows /s c:
(D:\Windows -being the path of Windows on the drive where you applied your imageX) and C: the small “system” named partition for Win7/Bitlocker.

By: Harald Kraft

Harald Kraft — Thu, 23 Jul 2009 04:35:46 +0000

The purpose of four operating systems is of various nature:
On the one hand, I wanted this to be a coding machine on which I wanted to be able to program under Linux and Windows. And on the other hand, it’s supposed to be an experimental computer, so I wanted to test Windows 7 and OpenSolaris

By: Franse

Franse — Wed, 22 Jul 2009 23:10:46 +0000

Hey Harry,
Du machst Sachen =) Haben 4 BS auf einem Rechner dann auch n bestimmten Zweck? Software-Tests a la “selbe Komponenten, verschiedene BS”? Oder einfach zur Gaudi?

Und schreib mal wieder was neues – die Leserschaft will bei Laune gehalten werden