Problem booting to Windows 7

Terry60

Knows where his towel is.
Staff member
#21
I notice you're using the RC not the Beta, so I'm not going to be much further use. I'm still having big problems getting a stable install. 7000 went on like a dream without leaving a ripple on the smoothness of the pre-existing dual-boot, but 7100 has managed to lose the drivers for my graphics card, monitor and TV card, and I have a distorted desktop with a predisposition to BSODing at the moment and I'm still trying to find the time to sort it all out. It wouldn't surprise me to find that something in the boot process is also not working the same as in 7000, but I can't confirm or deny that because I use grub to control my boot, though I have seen a comment in another thread that someone else couldn't get Vista to boot 7100 the way they did it with 7000, and they had to workaround by getting 7100 to boot Vista instead.
 

JustinW

Super Moderator
Staff member
#22
I think i'll be .vhding the RC. It looks like I should be testing it on my desktop rather than my laptop since I got a usb TV tuner here too...
 

Terry60

Knows where his towel is.
Staff member
#23
I'm still having problems. I haven't started again with the TV card removed yet, as I promised in the other thread. I thought I'd try the pre-7000 windows install routine of individually locating and installing the drivers first to see if the crippled install is fixable, but unfortunately the ATi site doesn't have drivers for my Graphics card for W7, which is all very weird because 7000 supported all my hardware straight out of the box.
I've a suspicion that even removing the TV card won't fix the install but I'm hoping that it might at least remove the BSOD and get a clean finish that I can use as a base.
I'm going to try reinstalling 7000 and updating it to 7100 after that to see if that's a better route, but I'll report what I actually do do in the other thread and what the effects were.
 

JustinW

Super Moderator
Staff member
#24
I don't believe you can upgrade from 7000 to 7100 directly unless you've found a guide somewhere for manually doing it. MS says you need to do a clean install. Also most OEMs won't have Windows 7 drivers yet. Windows 7 has been designed to work with Windows Vista drivers as well, or at least its supposed to.

Good luck and keep us posted. I havent had time to play around with the rc let alone the beta lately but when I do hopefully I have a good review of it to report.
 

Terry60

Knows where his towel is.
Staff member
#25
Ati listed W7 drivers for some cards, just not mine. I'll give it a whirl as an upgrade. If it doesn't work I've lost nothing more than a few hours (and I've given it enough of those already). I don't use it for anything. I'm just beta testing it out of the goodness of my heart. Vista is still my workhorse with XP as my legacy app backstop, and I'm just playing with Linux for the experience at the moment.
 
#26
I've still been trying to figure this out. I don't know if it's a fix or not but at the moment, its working now. What i did was that i unplugged my data hard drive and only kept in my OS hard drive. I then reinstalled Win7. After the reinstall it gave me my list and everything is now working fine with no errors. I haven't yet plug in my other HD.

What i noticed every once in a while my boot drive on the Display page in EasyBCD was one of the drives on my data HD (Drives J or L). So my theory was that some how boot files were put on other drives other than the OS and then upon boot up, the files weren't with the OS, computer gets confused and therefore no startup and an error. It's just a theory.

Here is my Debug view as i put in my other HD and hope for a nice clean start up

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 {e41d11d8-44c4-11de-9d54-001a926bf344}
resumeobject {e41d11d7-44c4-11de-9d54-001a926bf344}
displayorder {466f5a88-0af2-4f76-9038-095b170dc21c}
{e41d11d8-44c4-11de-9d54-001a926bf344}
{e8709fb6-fa5f-11db-be4d-e219ece5282e}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader
-------------------
identifier {e41d11d8-44c4-11de-9d54-001a926bf344}
device partition=H:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {e41d11d9-44c4-11de-9d54-001a926bf344}
recoveryenabled Yes
osdevice partition=H:
systemroot \Windows
resumeobject {e41d11d7-44c4-11de-9d54-001a926bf344}
nx OptIn

Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device partition=C:
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=C:
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
 
#27
Hi Chris,
Just wondered if you figured out the problem with windows 7 only booting with disk in drive via the boot manager, I'm having the same problem and can't seem to figure the cause of it?

Benn
 

Terry60

Knows where his towel is.
Staff member
#28
Hi Benn, welcome to NST.
Can you post a screenshot of your Disk Management and we'll take a look at why it's not booting unaided.