HELP: Can't See Other HD

setotitan

New Member
Firstly, this is a great little bit of freeware programming. I'm always amazed when I see someones actually taken the time to solve a problem that would have taken hours and reduce it to minutes. That being said I'm having an issue. I have 2 SATA HDs that were originally set up in a RAID configuration, however as of late I've just been using one for my OS and one as storage. Then I read some article about Win7 64 bit being faster than Win7 32 bit, I had a spare HD figured why not try it out. Long story short I have x32 on drive 1 and x64 on drive 2. The only way I could get to drive 2 was in BIOS to disable drive 1 from even loading, before BCD. The main issue with that is I have a lot of files I still needed to access on drive 1, that's why I installed BCD in the first place, however it has not fixed the problem.

When I log into Win7 x32 on drive 1 I can see drive 2 as well. But if I boot Win7 x64 on drive 2 I can't see drive 1. Below are my details, please let me know what I need to do to remedy my issue.

Code:
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=C:
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {ba29a000-fe75-11de-a22f-c897e6b1bc84}
resumeobject            {ba299fff-fe75-11de-a22f-c897e6b1bc84}
displayorder            {ba29a000-fe75-11de-a22f-c897e6b1bc84}
                        {ba29a004-fe75-11de-a22f-c897e6b1bc84}
                        {ba29a003-fe75-11de-a22f-c897e6b1bc84}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30
displaybootmenu         Yes

Windows Boot Loader
-------------------
identifier              {ba29a000-fe75-11de-a22f-c897e6b1bc84}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 - 32BIT
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {ba29a001-fe75-11de-a22f-c897e6b1bc84}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {ba299fff-fe75-11de-a22f-c897e6b1bc84}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {ba29a004-fe75-11de-a22f-c897e6b1bc84}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Windows 7 - 64BIT
locale                  en-US
osdevice                partition=D:
systemroot              \Windows
resumeobject            {7a4a2614-f8ab-11df-86a5-806e6f6e6963}

Real-mode Boot Sector
---------------------
identifier              {ba29a003-fe75-11de-a22f-c897e6b1bc84}
device                  boot
path                    \ubnldr.mbr
description             Auto Super Grub Disk
 

JustinW

Super Moderator
Staff member
Because its an internal drive and was not originally attached you may need to go into disk management to assign it a drive letter before it can be used.
 

setotitan

New Member
In the words of Ed McMahon, "you are correct sir!". I assigned the drive a letter, and boom I could see it. Thanks!
 
Top