XP doesn't start

Why dual boot problem

please note Computer Guru.
Reasoning for dual boot problem is:
When MBR on drive is set to a Win nt MBR Windows XP boots
As soon as Win 7 MBR is installed XP fails to load.
Also when legacy(ntldr) section removed and added by EasyBCD beta 2 it still fails.
When starting XP in safe mode the files are loaded
rdrive(0)partition(2) .......until mup.dll.
Then splash screen sits for ever (+ an Hour)


Addendum:


where can XP boot.ini configuration now be found?
I wanted to turn of splash and use sos mode. but can not find these under win7 Legacy boot paramaters have tried editbcd. but no reference to XP boot.ini type options..
I feel a grub .97 or 1.97 comming on.
But this notebook is for a non-linux person.
 
Last edited:
Your XP partition is "system". That's where all the boot files are, XP's and W7's. The boot.ini in use is in the root of XP's partition.
That "recovered W7" entry is wrong. Remove it. (add/remove).
You talk about "removing the NTLDR legacy section"
You did use "add/remove", not "tools/edit legacy entries"
Can you check that E:\NTLDR E:\ntdetect.com and E:\boot.ini are all present and post the contents of boot.ini.
You don't alter the "active" flag at any time, do you. ?
 
>.Your XP partition is "system".
Yes it is
>-That's where all the boot files are, XP's and W7's. The boot.ini in use is in the root of XP's >partition.
Yes but the W7 Bootmanager comes up with
Microsof Windows XP -->
"Windows XP on on E:\
But boot.ini has
"Windows XP (1,2) "
"Windows XP (1,2) SOS no splash"
>That "recovered W7" entry is wrong. Remove it. (add/remove).
Yes me slack ...should have deleted
>You talk about "removing the NTLDR legacy section"
>You did use "add/remove", not "tools/edit legacy entries"
Yes Remove- > Add -> automatically edit entry
>Can you check that E:\NTLDR E:\ntdetect.com and E:\boot.ini are all present and post the >contents of boot.ini.
have checked numerous times
>You don't alter the "active" flag at any time, do you. ?
Have tried both primarys as active
with many repairs of XP and Win 7.
Installed win 7 3 times as well

Addendum:

;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=15
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP (0,2)" /NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP (0,2) SOS no Splash" /NOEXECUTE=OPTIN /FASTDETECT /SOS /NoSplash


Ok found boot.ini modified hence "Mirosoft Windows XP on E:"
restored boot.bak to boot.ini.
now I can get to splash screen on Windows XP (0,1)
or i can get to Windows XP Service pack 3 screen. drive C;D;E
quickscan no errors detected but it Sits on this screen for 10 mins. no sign of booting
will try 20 mins

Addendum:

Still waiting .
P.S is NeoGrub based on Grub legacy 0.97
or grub 2 (1.97) ????? cheers
 
Last edited:
That isn't the boot.ini created by EasyBCD2.
The one that says "Windows XP on on E:\" is created by Easy2
Why are you replacing it with one that doesn't work ?
 
Splash still showing after 27 mins.
Time to restart PC..
about to Get a ghost image of XP and 7.
will then zap mbr with XP's to once again prove XP boots with XP's bootloader .

Addendum:

Neither work. If one worked I would be thanking you for all the help by now.

by the way thanks for all the prompt help so far.
You have been a good sounding board.
 
Last edited:
What's in the one that Easy2 created ? and what's the nature of the failure to boot ?
 
Last edited:
;Warning: EasyBCDs warning......
;
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Mirosoft Windows XP on E:" /NOEXECUTE=OPTIN /FASTDETECT

problem with boot ...sits on Splash screen for over an hour.

Save multi line up until = only Description string changed ...
hence same boot problem yes the splash screen is bueatiful... But not very usefull:brows:

Addendum:

I would think the partition table is unchanged. If it has been changed then that may explain the probem
I would think Partition 1 is partition 1.....2 is 2 ....3 is empty....4 is Extended...5 ..is my logical data partition... I expect Dos/XP/W7/Linux ...Partition Magic ....Gpart all to agree.
The only thing changing should only be the drive letters... according to all the research I have done ?????

Addendum:

still ghosting by the way. currenly in a Win PE shell

Addendum:

?Do you code?? If so whats your favorite language.
P.S. Yes killing time Oh yes I do have 2 pcs . Hence I can still work.
While my 2nd PC is in the middle of being backed up

Addendum:

Finished ghost image.
any sugestions.
 
Last edited:
Have you noticed any problems with the site ?
I replied ages ago, and the post has never appeared.
I wanted to know how you changed the PBR ? EasyBCD uninstall/reinstall Vista bootloader or some other method ?
I ask, because as CG pointed out earlier, the problem isn't with EasyBCD. It correctly configures the route to XP, hence the splash screen.
The mystery is why a broken OS is "cured" by just altering the PBR, which precedes the point of failure.
It should make no difference, the boot route is either MBR IPL PBR Bootmgr NTLDR, or MBR IPL PBR NTLDR. The bit that actually boots XP doesn't change.
 
changed to XP mbr by fdisk /mbr with XP
Changed to W7 mbr by running W7 Repair .X 3 times.
also used Repair console to do use the W7 Partion editor.
To view partition information
I have gone Win XP mbr <-> W7 mbr 3 separate times. so may have not done it exactly the same each time. Will do the Add/remove/automatic edit in easyBCD to get the exact boot.ini edited/created by easyBCD beta for you
 
No need to do it again, it's obviously finding it OK or you wouldn't get the splash.

Addendum:

Use EasyBCD /Diagnostics/ Change boot drive to put the system files in the W7 partition.
Boot W7 again, check that W7 is now "boot" "system" and "active", delete the XP entry and add it again letting it auto-configure again.
 
Last edited:
; This boot.ini was automatically generated by NeoSmart Technologies' BootGrabber.exe
; Use EasyBCD from http://neosmart.net/dl.php?id=1 to manage your bootloader
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP on E:\" /fastdetect

Addendum:

Done 7 starting confirming boot Part 1.. Yes Part 1 active

Addendum:

crossing fingers,,,,tring win XP.....Will give it 3 mins

Addendum:

it beeped....does not look promising

Addendum:

I may try bootrec next ?
3.00 am I do not believe I am still awake
 
Last edited:
under tools/msdos...
even fdisk /mbr from 98 and ME works
I only use me disk for fdisk /mbr and changing active partion in a scrap.
Yes of course XP Diskmanager and Partition Magic and Gpart etc will all do the same thing.
ie change active partition for you

Addendum:

About to go to bed.
ON my pc
when XP mbr and part 1 active fails to boot
when xp mbr and part 2 active ........Boots.
so if i fixboot ...fix mbr while part 1 active.
replace Xp mbr with Win 7 then xp should dual boot..
Hopefully but I will not do it now ...that would be insane

Addendum:

About to go to bed.
ON my pc
when XP mbr and part 1 active fails to boot
when xp mbr and part 2 active ........Boots.
so if i fixboot ...fix mbr while part 1 active.
replace Xp mbr with Win 7 then xp should dual boot..
Hopefully but I will not do it now ...that would be insane

Addendum:

Well doing the XP boot repair while partition 1 is active fixed problem Dual boot now works perfectly.
Thankyou very much for your help. Still not sure why having partition 2 active has caused problem
 
Last edited:
im having the exact same problem, but having trouble finding out exactly how you solved it...
any chance you can summarize your fix?
 
There are at least 3 problems in this thread. Can you describe your own with a bit more detail, and attach Disk Management and display settings information as described in the sticky thread.
Are you using EasyBCD 2.0 latest build ? (1.7 contains no W7 support and no automation features. It requires you to know what additional tasks are needed and how to do them)
 
Back
Top