Page 3 of 4

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 8:58 am
by TeraByte Support(PP)
The syntax was wrong in both of the robocopy commands you ran. Please try them again. In the "bootmgr" copy you didn't have a space between "c:\" and "bootmgr" and in the second one you use "bootb" instead of "boot" and used "\\" instead of "\".

Also, if you use TBIView, you would be wanting to copy (or extract) them to the C: partition, not the F: partition.

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 9:32 am
by thenoo
TeraByte Support(PP) wrote:
> The syntax was wrong in both of the robocopy commands you ran. Please try
> them again. In the "bootmgr" copy you didn't have a space between
> "c:\" and "bootmgr" and in the second one you use
> "bootb" instead of "boot" and used "\\"
> instead of "\".

Apologies ! Must be getting tired - as I'm sure you are !

Here it is again:-
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>robocopy f:\Boot c:\Boot /s /r:0 /b

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Mon Aug 13 17:27:00 2012

Source : f:\Boot\
Dest : c:\Boot\

Files : *.*

Options : *.* /S /COPY:DAT /B /R:0 /W:30

------------------------------------------------------------------------------

7 f:\Boot\
1 f:\Boot\cs-CZ\
1 f:\Boot\da-DK\
1 f:\Boot\de-DE\
1 f:\Boot\el-GR\
2 f:\Boot\en-US\
1 f:\Boot\es-ES\
1 f:\Boot\fi-FI\
5 f:\Boot\Fonts\
1 f:\Boot\fr-FR\
1 f:\Boot\hu-HU\
1 f:\Boot\it-IT\
1 f:\Boot\ja-JP\
1 f:\Boot\ko-KR\
1 f:\Boot\nb-NO\
1 f:\Boot\nl-NL\
1 f:\Boot\pl-PL\
1 f:\Boot\pt-BR\
1 f:\Boot\pt-PT\
1 f:\Boot\ru-RU\
1 f:\Boot\sv-SE\
1 f:\Boot\tr-TR\
1 f:\Boot\zh-CN\
1 f:\Boot\zh-HK\
1 f:\Boot\zh-TW\

------------------------------------------------------------------------------

Total Copied Skipped Mismatch FAILED Extras
Dirs : 25 0 25 0 0 0
Files : 36 0 36 0 0 0
Bytes : 14.01 m 0 14.01 m 0 0 0
Times : 0:00:00 0:00:00 0:00:00 0:00:00

Ended : Mon Aug 13 17:27:00 2012

C:\Windows\system32>

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 9:40 am
by thenoo
Sorry forgot the "bootmgr" command - here it is


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>robocopy f:\ c:\ bootmgr /r:0 /b

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Mon Aug 13 17:37:44 2012

Source : f:\
Dest : c:\

Files : bootmgr

Options : /COPY:DAT /B /R:0 /W:30

------------------------------------------------------------------------------

1 f:\

------------------------------------------------------------------------------

Total Copied Skipped Mismatch FAILED Extras
Dirs : 1 0 1 0 0 0
Files : 1 0 1 0 0 0
Bytes : 374.7 k 0 374.7 k 0 0 0
Times : 0:00:00 0:00:00 0:00:00 0:00:00

Ended : Mon Aug 13 17:37:44 2012

C:\Windows\system32>

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 10:03 am
by TeraByte Support(PP)
Please post the output from this command:
bcdedit /store c:\boot\bcd /enum all

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 12:47 pm
by thenoo
TeraByte Support(PP) wrote:
> Please post the output from this command:
> bcdedit /store c:\boot\bcd /enum all

OK. Here it is:-

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /store c:\boot\bcd /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=F:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
displayorder {default}
{0048fdd6-cf74-11df-ae5a-f34a80ad44b1}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {0048fdc8-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0048fdcc-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0048fdcf-cf74-11df-ae5a-f34a80ad44b1}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {0048fdd0-cf74-11df-ae5a-f34a80ad44b1}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {0048fdce-cf74-11df-ae5a-f34a80ad44b1}
nx OptIn

Windows Boot Loader
-------------------
identifier {0048fdd0-cf74-11df-ae5a-f34a80ad44b1}

Windows Boot Loader
-------------------
identifier {default}
device partition=F:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {0048fdd4-cf74-11df-ae5a-f34a80ad44b1}
recoveryenabled Yes
osdevice partition=F:
systemroot \Windows
resumeobject {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
nx OptIn

Windows Boot Loader
-------------------
identifier {0048fdd4-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0048fdd6-cf74-11df-ae5a-f34a80ad44b1}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {d0f70ad9-adad-11e1-8278-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {0048fdd7-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[C:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {0048fdce-cf74-11df-ae5a-f34a80ad44b1}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
device partition=F:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=F:
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {d0f70ad9-adad-11e1-8278-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=F:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd1-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\0048fdd0-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

C:\Windows\system32>

Re: Problems removing a second Windows Folder

PostPosted: Mon Aug 13, 2012 5:44 pm
by TeraByte Support(PP)
The file looks correct. Go ahead and run the Step #11 command:
bcdedit /store c:\boot\bcd /set {bootmgr} device partition=C:

If the operation completes successfully, next boot into BIBM and edit the menu item for Windows 7 . Change the booting partition to the "C:" partition (Disk 1, partition 1) instead of the "F:" partition (Disk 0, partition 1) -- change it to boot the Windows 7 partition.

Then return to the BIBM Boot Menu and try booting the Windows 7 item. You should get the same Windows 7 boot menu and should be able to boot into Windows 7 normally. Assuming this works, you can clean up the BCD a bit and get rid of the Windows 7 boot menu so it boots directly into Windows 7 from BIBM.

Re: Problems removing a second Windows Folder

PostPosted: Tue Aug 14, 2012 3:07 am
by thenoo
TeraByte Support(PP) wrote:
> The file looks correct. Go ahead and run the Step #11 command:
> bcdedit /store c:\boot\bcd /set {bootmgr} device partition=C:

OK . I'll run the above command now . Depending on the result , I'll almost certainly need help with your 2nd and 3rd paragraphs as I'm not familiar with the process you mention there.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32> bcdedit /store c:\boot\bcd /set {bootmgr} device part
ition=C:
The operation completed successfully.

C:\Windows\system32>

------------------------------------------------------------------------------------------
OK - As that was a success I'll attempt your paragraphs 2 and 3. Standby


>
> If the operation completes successfully, next boot into BIBM and edit the
> menu item for Windows 7 . Change the booting partition to the
> "C:" partition (Disk 1, partition 1) instead of the
> "F:" partition (Disk 0, partition 1) -- change it to boot the
> Windows 7 partition.
>
> Then return to the BIBM Boot Menu and try booting the Windows 7 item. You
> should get the same Windows 7 boot menu and should be able to boot into
> Windows 7 normally. Assuming this works, you can clean up the BCD a bit and
> get rid of the Windows 7 boot menu so it boots directly into Windows 7 from
> BIBM.

Re: Problems removing a second Windows Folder

PostPosted: Tue Aug 14, 2012 4:53 am
by thenoo
I navigated BIBM>MAINTAINANCE>BOOT EDIT>EDIT thus arriving at "EDIR MENU ITEM"

#1 Is this correct ?

#2 What do I do now ? This page has a LEFT SIDE and a RIGHT SIDE . Do I change both ?

#3 If so - how ?

#4 Is it possible to print out these BIBM pages ?

Re: Problems removing a second Windows Folder

PostPosted: Tue Aug 14, 2012 11:47 am
by TeraByte Support(PP)
#1 - Yes, that's correct.

#2 - Make sure the "HD" item is set to the correct drive. In this case, it should be set to the drive with the Windows 7 partition on it (probably 1 on your system). The partitions loaded for each drive are displayed on the right side in MBR Details. In your screenshot (post #1) it doesn't show any labels for either C: or F:. If you label them it's easier to tell which is which.

Then use the "Boot" drop-down and select the Windows 7 partition as the booting partition. Then click OK to save the changes. An example is shown in the screenshot below (it has the Windows 7 partition selected for HD 0).

#4 - On a physical machine, it's usually easiest to just take a picture of the screen (digital camera, phone, etc.).

Re: Problems removing a second Windows Folder

PostPosted: Wed Aug 15, 2012 5:17 am
by thenoo
TeraByte Support(PP) wrote:
> #1 - Yes, that's correct.
>
> #2 - Make sure the "HD" item is set to the correct drive. In this
> case, it should be set to the drive with the Windows 7 partition on it
> (probably 1 on your system). The partitions loaded for each drive are
> displayed on the right side in MBR Details. In your screenshot (post #1) it
> doesn't show any labels for either C: or F:. If you label them it's easier
> to tell which is which.
>
> Then use the "Boot" drop-down and select the Windows 7 partition
> as the booting partition. Then click OK to save the changes. An example is
> shown in the screenshot below (it has the Windows 7 partition selected for
> HD 0).

It looks like I've changed the C:Partition (Disk1) to be "Boot,Active" as oposed to the F:Partition (Disk0)
See attached Disk Management picture
>
>
> #4 - On a physical machine, it's usually easiest to just take a picture of
> the screen (digital camera, phone, etc.).