Dual boot problem on 2 different hdd (win7+winxp)

#1
Hello guru, i'm italian and first i'm sorry for my very bad english.
My problem is that i can't boot into windows xp using easybcd.
My disk configuration is the following
SATA0--> hdd500gb > 3 primary partition:

  1. [1]PRIMARY NTFS ACTIVE "OS windows xp" (inside win7 the volume letter is "D")
  2. [2]PRIMARY NTFS "Storage" (inside win7 the volume letter is "G")
  3. [3]PRIMARY NTFS "Storage" (inside win7 the volume letter is "F")

SATA1--> hdd1,5Tb > 1 primary partition:

  1. [1]PRIMARY NTFS "Storage" (inside win7 the volume letter is "E")

SATA2--> hdd1Tb > 3 primary partition 1 logic/extended partition

  1. [1]PRIMARY NTFS SYSTEM ACTIVE "Windows7 Reserved Partition" (inside win7 the volume letter is "R")
  2. [2]PRIMARY NTFS BOOT "OS windows 7" (inside win7 the volume letter is "C")
  3. [3]PRIMARY NTSF "Storage" (inside win7 the volume letter is "X")
  4. [4]LOGIC NTSF "Storage" (inside win7 the volume letter is "Y")

The version of easybcd is 2.1.2.156 (downloaded from softpedia)

The procedure that i used for dual boot is this:

  1. add new entry
  2. select 2k/xp/etc
  3. select (auto first try) manually partition "D" where is contents OS winxp and push "new entry" button
  4. go to advanced setting and verify that the volume letter is "R" "Win7 Reserved" where is located the boot.ini
  5. restart, select the windows xp at boot manager and the error is:


"Windows could not start because the following file is missing or corrupt: <Windows root>\system32\ntoskrnl.exe. Please re-install a copy of the above file"

i try to modify the rdisk value in boot.ini but the problem remains
.
i enclose the bootgrabber log, the boot.ini and the screenshot of my disk manager
i want to clarify that windows xp started from the motherboard boot manager work perfectly
thanks in advance for your help
 

Attachments

Terry60

Knows where his towel is.
Staff member
#2
Can you cut/paste the contents of the "view settings" box (detailed mode).
You might also like to get the latest Beta build which has Italian translation as an option.
 
#3
Yes:

Code:
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=R:
description             Windows Boot Manager
locale                  it-IT
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {0b228fc1-04e0-11e2-b04c-b67ebf608fce}
resumeobject            {0b228fc0-04e0-11e2-b04c-b67ebf608fce}
displayorder            {0b228fc1-04e0-11e2-b04c-b67ebf608fce}
                        {0b228fcd-04e0-11e2-b04c-b67ebf608fce}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 15
displaybootmenu         Yes

Windows Boot Loader
-------------------
identifier              {0b228fc1-04e0-11e2-b04c-b67ebf608fce}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  it-IT
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {0b228fc2-04e0-11e2-b04c-b67ebf608fce}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {0b228fc0-04e0-11e2-b04c-b67ebf608fce}
nx                      OptIn

Real-mode Boot Sector
---------------------
identifier              {0b228fcd-04e0-11e2-b04c-b67ebf608fce}
device                  partition=R:
path                    \NST\ntldr
description             Windows XP
 

Terry60

Knows where his towel is.
Staff member
#4
That all looks fine.
Since I can't remember if there have been any known XP detection bugs fixed in the last 26 builds (I don't think so), and 2.2 is now the official release,
Announcing EasyBCD 2.2: Windows 8 dual-booting and more! | The NeoSmart Files
can you get 2.2 and use it to delete the XP entry then add it again (auto-configure), and confirm whether you still have a problem.
 

Terry60

Knows where his towel is.
Staff member
#6
Over to you CG
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#8
From what I see of the detailed mode output, it is saying that XP is on Drive R:, when you state that it is listed as Drive D: within Windows 7. The Drive R: is listed as the reserve space, I would wager to guess that is the Recovery Partition.

When you are adding the entry for XP are you using the auto configure mode or the manual method? If your using the auto configure try unchecking that option and manually select the XP Partition yourself. See if that fixes the issue.
 
#9
From what I see of the detailed mode output, it is saying that XP is on Drive R:, when you state that it is listed as Drive D: within Windows 7. The Drive R: is listed as the reserve space, I would wager to guess that is the Recovery Partition.

When you are adding the entry for XP are you using the auto configure mode or the manual method? If your using the auto configure try unchecking that option and manually select the XP Partition yourself. See if that fixes the issue.
Yes this is true, on Win7 the letter of partition where is installed WinXP is "D".
"R" is the reserved partition created by Win7 during the installation, and is the boot partition.
If i manualy select the "D" partition, when i save, in detail mode i see that the soft assign however "R" and create the boot.ini in this partition.
If after creation of dual boot (manually/auto, is the same) in advanced mode change the partition from "R" to "D" at the boot when i select "WindowsXP" it said that the file \NST\easyldr1 do not exist.

I don't understand well the mechanisms of this software, but i would to try a thing: to copy the NST partition on WinXP partition and manually reselect drive "D" in advanced mode.
Do you think it will work?

I'm pretty desperate.... :frowning:

Addendum

Do you think it will work?
don't work :frowning: :frowning:
 

Terry60

Knows where his towel is.
Staff member
#10
It should point to R. That's the "system" partition. The BCD doesn't point to XP, it points to the copy of boot.ini on "system", which in turn points to XP.
That's why I referred it to CG.
EasyBCD is setting the BCD up correctly, and the ntoskrnl error normally indicates a problem with the arc paths in boot.ini, but EasyBCD is also setting that up correctly, hence my post #4 that everything should be working.
 

mqudsi

Mostly Harmless
Staff member
#11
Is this an EFI machine?