for placing the bootloader on a completely random drive in my system that contained no NTFS partitions whatsoever.i wasn't aware of this until i removed said drive to place it into another system and had reformatted it... and, of course, windows won't boot now.bcdedit will be the death of me.how does putting the bootloader on a drive that isn't even associated with the windows install and is on like the 3rd SATA channel make any sense?
7/21/2009 12:02:06 AM
Lemme know when neon gets here, I've been itching to eat some popcorn and watch a drama all night.
7/21/2009 12:07:51 AM
*shrug*This is why I physically unplug all drives except the one I actually want the bootloader on, when I install Windows. MS has managed to screw the pooch on this since the Win95 days.
7/21/2009 12:14:20 AM
you are all a bunch of buttloaders as far as I am concerned
7/21/2009 1:19:28 AM
I had this shit happen to me too. For a while I had to use my BIOS to specify which hard drive to boot to.
7/21/2009 1:19:58 AM
7/21/2009 5:36:22 AM
I haven't run in to this problem, but I have noticed that windows and other software likes to install itself, or portions/files, on my external HDDs, which is very fucking annoying.
7/21/2009 8:55:48 AM
haha, i've had this happen with earlier versions beforei found once that just running through the first part of windows setup for whatever reason fixes it. when it reboots during the install it'll go to the screen where you can pick with OS to boot to.. the old one was on the list so i logged into it like normal then deleted all the setup shit.pretty sure there are other/better ways to do it but that worked for me once upon a time
7/21/2009 9:55:05 AM
i got it working after fighting with bcdedit, i just manually created the damn thing from scratch.
7/21/2009 10:15:00 AM
if you boot off the cd (or the recovery partition if you built one) you can use the recovery tools to recreate the boot loader
7/21/2009 12:06:56 PM