no boot option screen

[gregrocker]

I've never heard of the booted DVD connecting to MS to complete any kind of repairs in the Repair console.

Are you sure you are booting the Win7 DVD, choosing Repair My computer on second screen, then clicking through to Recovery Tools list to choose Startup Repair at least three separate times with reboots? http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S

If Partition Wizard shows Win7 is marked active when it wasn't before it may mean Startup Repair was on path to fixing the MBR but you didn't go back for enough repeat fixes so that it could finish the job.

 

[graveller39]

I've never heard of the booted DVD connecting to MS to complete any kind of repairs in the Repair console.

All I know is it's done this to me twice now -- I suppose I should say, the repair console gave me the option to connect.

Are you sure you are booting the Win7 DVD, choosing Repair My computer on second screen, then clicking through to Recovery Tools list to choose Startup Repair at least three separate times with reboots? http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S

yes, that's exactly what I did.

If Partition Wizard shows Win7 is marked active when it wasn't before it may mean Startup Repair was on path to fixing the MBR but you didn't go back for enough repeat fixes so that it could finish the job.

No, it was the XP partition I had set to Inactive (before the Startup Repair) and now it's Active again.
The Win7 partition I previously set to Active, as you suggested, and it's still Active.
At this point, I don't know where the MBR is, as I'm unable to boot into Win7.

 

[Saltgrass]

Anytime changes are made, perhaps you could just go ahead an post another Disk Management picture. That is the only way I can see what is going on. You have made so many changes, gregrocker might be able to follow, but the original picture is completely out of date.

Also, indicate which drive you show first priority in the bios and please put OS labels on the partitions. You might also use the view options to show hidden and system files. Then look at the partitions to see where bootmgr and ntldr files are located (probably 2 or even 3 different partitions).

The Maxtor partition does not have a drive letter, just like the Win 7 system reserved partition doesn't. If you look at if from XP, it will.

Could the connection mentioned be the install trying to access the net to activate?

Please remember, if you disconnect a drive and then reboot, you have possibly changed the drive order.

 

[gregrocker]

There has to be something else wrong, so agree we need to see the full Disk Mgmt or Partition Wizard drive map screenshot.

http://www.sevenforums.com/tutorials/9733-how-post-screenshot-seven-forums.html

 

[graveller39]

Here's the latest screenshot from PartitionWizard.
The Maxtor drive is disconnected as it appears it was likely part of the original problem.

The HDD with Windows 7 is selected as first boot in the BIOS.

I could not find any ntldr files, but I found these:

I found this file in C:\boot -

;
;Warning: Boot.ini is used on Windows XP and earlier operating systems.
;Warning: Use BCDEDIT.exe to modify Windows Vista boot options.
;
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT /USEPMTIMER

I found bootmgr here –
E:\Windows\Boot\PCAT\bootmgr

I'm not sure what else to look for.

Could the connection mentioned be the install trying to access the net to activate?

I don't think so, the Repair console specifically said it was connecting to microsoft to automatically fix.

 

[gregrocker]

Download and install EasyBCD 2.0 beta to XP, after doing the quick registration to use the beta.

You'll also need to install Net Framework 2.0 to use EasyBCD in XP.

On the Add/Remove tab, add Win7 by Name, type and correct drive letter. Then highlight new Win7 listing above and Save.

 

[graveller39]

thanks gregrocker,
I ran EasyBCD and this what it shows -- do I still need to add Windows 7?
It looks like its already there...

 

[Saltgrass]

graveller39 do not worry about this post, these are observations for gregrocker only.

If the E: partition is active and primary drive, why is there no boot error? I could understand the C: partition being the system partition if there were no active partitions prior to it, but if the Win 7 drive is the primary drive, it should have hit that and caused an error if no boot system was encountered.

I don't think he was checking hidden system files since he did not see bootmgr or ntldr in the root directories.

Just an observation, no response expected.

 

[graveller39]

you're right Saltgrass - I didn't have the "hide protected operating system files" box unchecked.
I do have ntldr and bootmgr in the C:\ drive.
sorry about that...

 

[gregrocker]

is boot.ini in C: root also?

Try removing Win7 in Easy Add/Remove tab, then Add it again.

See if you can boot into Win7 then.

We may need SIW2 to look at this.

 

[graveller39]

hi gregrocker,
yes, boot.ini is also in C:\
I tried removing Win7 in the Add/Remove tab, then added it again;
still won't boot into Win7 - it gets to the "Starting Windows" screen and then shuts down.
Booting to XP is not a problem.

 

[gregrocker]

I'm not sure why Win7 HD is set first HD to boot in BIOS since XP holds the System Active MBR.

Try entering BIOS setup to set XP HD first HD to boot (after DVD) and report back what happens with dual boot.

See if you get the same drive listings by booting Partition Wizard CD. That Disk0 HD might still hold the MBR and isn't showing it now.

How much trouble would it be for you to plug XP into Disk0 slot and Win7 into Disk1 slot, then set XP as first HD to boot without the data drive plugged in. Next try Win7 as first HD to boot w/o data drive.

 

[graveller39]

I can set the XP drive to be first boot and see what happens, although I thought the Win7 bootmgr was the one that controlled things once Win7 has been installed? - I don't fully understand the boot process though.

I was thinking another fresh install of Win7 might fix things up, so I tried that, but I'm still in the same spot - Win7 can't/won't boot. I'm wondering if the install itself isn't quite finishing as I'm running into this problem at the very end of the Win7 install process - it may never have quite finished as it couldn't boot back into Win7, although it did at least once during the install.

The remaining data drive (Disk 1 according to PartitionWizard) is connected to a SATA card - not directly to the motherboard. Could this drive also be interfering with the install as I believe the PATA drive was? I could disconnect this one too and try the install once more. I'll have to try that tomorrow though as its getting late...

oh, I forgot mention - after trying to reinstall Win7 again, I noticed my E: drive (Win7 ) is no longer active. Is this to be expected?

thanks for your patience and help.

 

[Saltgrass]

I think if I were gregrocker, I would suggest you take out all the drives except the win 7 drive. Get Win 7 running and worry about the rest later.

 

[gregrocker]

I agree with Saltgrass. If you unplug all of the other drives and install Win7 by itself, then you can plug back in the XP drive, set one as default to boot first in BIOS, or choose the other by using the BIOS shortcut key given on first bootup screen for Boot Menu.

This keeps the HD's independent and can come and go as you please.

If you're set on having a Windows-managed Dual Boot, you can try adding XP from Win7 using Easy BCD or try another Win7 install with only the 7/XP HD's plugged in.

If you are pre-formatting the Win7 drive to set it Active, this is not necessary - use the Win7 DVD Custom Drive Tools to format.

 

[woebetide]

A maximum of four primary partitions can be placed on any hard disk. The limitation of four is one that is imposed on the system by the way that the master boot record is structured. Only one partition may be designated, at any given time, as active. That partition will be used for booting the system.

So only 1 ACTIVE partition !!!!

And bootmgr , boot folder with BCD and ntldr should be on that partition as far as I know.

BCD should be something like this:

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=D:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {e183bfc2-0b9a-11df-8e0a-c37636dd1cce}
displayorder            {ntldr}
                        {current}
toolsdisplayorder       {memdiag}
timeout                 5

Windows Legacy OS Loader
------------------------
identifier              {ntldr}
device                  partition=D:
path                    \ntldr
description             Earlier Version of Windows

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {e183bfc4-0b9a-11df-8e0a-c37636dd1cce}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {e183bfc2-0b9a-11df-8e0a-c37636dd1cce}
nx                      OptIn

 

[graveller39]

I tried installing Win7 once more with only the two physical drives connected.
SATA 1: XP
SATA 2: Win7
Exactly the same thing happened - dual-boot was setup fine, but I can't boot into Win7 - in fact, the install never really finishes...

I'm not sure why Win7 HD is set first HD to boot in BIOS since XP holds the System Active MBR.

I can set either HD to boot first, it doesn't seem to make any difference. What I don't get is why my XP drive holds the System Active MBR... shouldn't this be on the Win7 drive and should I not have only one active drive and maybe that is why Win7 won't boot? Maybe there's something I'm missing about how the MBR works.

If I unplug the XP drive and install Win7 with just the one drive connected, will I run into problems booting into XP once its connected again? You can understand my concern - I really don't want to be stuck without XP as my experience with Win7 so far is pretty poor...as in I'm very close to giving up and writing it off as another MS dud.

 

[gregrocker]

What you're experiencing is very unusual. For some reason, Win7 won't install correctly or configure the dual boot with XP.

It is correct for XP to be System Active as the MBR remains there and is updated for dual boot during 7 install. But Win7 partition is supposed to hold the Boot and it is not.

In this case, it is best to disconnect all other drives and install Win7 to its own drive with its own System Active Boot. Then I would set Win7 HD first HD to boot in BIOS, after DVD drive. If you decide to boot XP, use the key given on first bootup screen for Boot Menu to intervene and boot XP instead of 7.

This is actually a better way to dual boot in the eyes of many of us here since it keeps the HD's independent so they can come and go as you please.

However, if you want a Windows-managed Dual Boot, then install EasyBCD in Windows 7 and add XP on the Add/Remove tab.

 

[graveller39]

Disconnected all drives except the one SATA for Win7. It created the 100MB partition this time - I thought maybe its working... but no - it still quits near the end of the install and won't boot into Win7.

Strange though, as soon as I reconnected the 2nd SATA drive (with XP), the dual-boot option was there.
Is it stored on the XP drive then...?

Anyway, I'm right back to where I was - with an extra 100MB system partition...

I'm thinking its definitely an install problem - checking several other forums, I see many others have had the same problem.
Seems MS really messed up with this one - and its supposed to be better than Vista ???

right...

 

[gregrocker]

If you boot the Win7 DVD Repair console, does it find an installation to repair? If so, run Startup Repair repeatedly to see if it will start.

If not, try clearing the CMOS in your BIOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS

What is the SATA controller setting in BIOS?

Try installing from flash drive: http://www.sevenforums.com/tutorials/2432-usb-windows-7-installation-key-drive-create.html

Lastly, try running HD Diagnostics and memtest86.