FYI

These are the steps I used to successfully install XP after Vista RTM.

Disk was clean (no partritions)
Boot via Vista DVD
Create C:
Install Vista into C:
Boot into Vista, create E: via Disk Mgr
(D: is the CD/DVD drive)

Boot via XP CD
Select E: as target
Install XP into E:

When XP install is finished, computer will only boot into XP
Copy ntldr file from Vista vol into root of XP vol

Boot via Vista DVD
Select Repair Your Computer
Select Vistal vol
Select Startup Repair
(no notice of finding an error)
Reboot per prompt

Boot into Vista
Install VistaBootPro v3.1 beta
Do the BCD backup
Select "Manage OS Entries"
Select "Add new op system entry"
Select "Windows Legacy"
Enter a name (to show in the Vista boot mgr menu)
Select drive letter E:
Select Apply

Reboot
Select XP op system from the Vista boot mgr menu

boy do you believe in doing things the hard way.
so much easier to boot xp first and prep the hard drive. create partitions format and such.

install XP, then install vista.

proper dual boot set up for you during the vista install.



[email]mikeyhsd@sport.rr.com[/email]



"CZ" <CZ@no99spam.com> wrote in message news:eTBWC3nRHHA.1860@TK2MSFTNGP06.phx.gbl...
FYI

These are the steps I used to successfully install XP after Vista RTM.

Disk was clean (no partritions)
Boot via Vista DVD
Create C:
Install Vista into C:
Boot into Vista, create E: via Disk Mgr
(D: is the CD/DVD drive)

Boot via XP CD
Select E: as target
Install XP into E:

When XP install is finished, computer will only boot into XP
Copy ntldr file from Vista vol into root of XP vol

Boot via Vista DVD
Select Repair Your Computer
Select Vistal vol
Select Startup Repair
(no notice of finding an error)
Reboot per prompt

Boot into Vista
Install VistaBootPro v3.1 beta
Do the BCD backup
Select "Manage OS Entries"
Select "Add new op system entry"
Select "Windows Legacy"
Enter a name (to show in the Vista boot mgr menu)
Select drive letter E:
Select Apply

Reboot
Select XP op system from the Vista boot mgr menu

>> boy do you believe in doing things the hard way.
so much easier to boot xp first and prep the hard drive. create partitions
format and such.
install XP, then install vista.
proper dual boot set up for you during the vista install.


Mike:

There have been posts suggesting that it could not be done, so I tried it as
a test.

Also, some people who purchase a new computer with Vista installed may want
to install XP.

installing xp after vista is installed damages the vista boot loader.
requiring almost as much jumping through hoops as you have done to repair it.

there are 2 3rd party programs that can assist in restoring the vista boot loader.

VistaBootPro and EasyBCD.



[email]mikeyhsd@sport.rr.com[/email]



"CZ" <CZ@no99spam.com> wrote in message news:O7dd$ltRHHA.488@TK2MSFTNGP06.phx.gbl...[color=blue][color=green]
>> boy do you believe in doing things the hard way.[/color][/color]
so much easier to boot xp first and prep the hard drive. create partitions
format and such.
install XP, then install vista.
proper dual boot set up for you during the vista install.


Mike:

There have been posts suggesting that it could not be done, so I tried it as
a test.

Also, some people who purchase a new computer with Vista installed may want
to install XP.

just to clarify for anyone who may be confused, the ntldr.exe file comes from the /i386 folder on your xp install disk, not the vista volume (or at least I don't think so...)

Thanks a lot for the guide!

It is by no means pointless, as people like me who already have Vista installed don't want to reinstall it in order to get XP running.

I needed XP because some of my Apps didn't work in Vista x64

On Tue, 13 Feb 2007 18:04:52 -0800, luketc <luke.cori******.com>
[color=blue]
>just to clarify for anyone who may be confused, the ntldr.exe file comes
>from the /i386 folder on your xp install disk, not the vista volume (or
>at least I don't think so...)[/color]

NTLDR or NTLDR.EXE?

The first code file of the NT boot process has no file extension, i.e.
is C:\NTLDR rather than C:\NTLDR.EXE, is why I ask.

I wish .EXT were on by duhhfault, so we wouldn't have all this
confusion, as well as less opportunity for malware spoofing
(README.TXT.SCR and all that, plus companion infectors).

I think the Vista "just guess the name and we'll find it for you"
approach is going to create new problems of this sort, especially when
combined with the "haven't they learned by now?" Win95-era blunder of
hiding file name .ext by duuuuhfault.


[color=blue]
>--------------- ---- --- -- - - - -[/color]
Saws are too hard to use.
Be easier to use![color=blue]
>--------------- ---- --- -- - - - -[/color]