Quote:
The only instance where I see it fail here is when the boot has been derailed to a data drive that was not unplugged during install, or is not unplugged while the repair operations are undertaken.
This seems to be my case. I'm derailed to the drive I ran my Windows 7 "expandedSetup" folder's contents (setup.exe) from.
I've tried fixing with the windows7 start up repair utility but it INSISTS that the OS is loading properly. Tis not.
I made things worse with easyBCD then somehow it's all OK again... so long as I have the crappy old IDE drive (H

plugged in I can manage to boot my windows install.
Everything looks good from every angle I look at it from Microsoft utilities and even easyBCD's normal view:
Quote:
Entry #1
Name: Windows 7
BCD ID: {current}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe
Windows Directory: \Windows
but I see a clue when I study the boot.ini(?) in debug mode using easyBCD:
Quote:
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=H:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {032f3278-d091-11de-ad3d-9531cb837b3f}
resumeobject {032f3277-d091-11de-ad3d-9531cb837b3f}
displayorder {032f3278-d091-11de-ad3d-9531cb837b3f}
{1c7c9848-ee92-11db-a26d-9cd8a469f4c4}
{00b2d95a-ee2f-11db-9614-96b4de5879c4}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
That's the bugger I think... H: is the old IDE drive I ran setup from and need plugged in to do a boot to Windows 7 on my D: drive.
I hate relying on that drive for my system. Any ideas for when Windows 7 "bootfix" doesn't fix?