Restoring image to 2nd partition AFTER installing Vista

G

Guest

I've got Vista Ultimate installed on my laptop just fine. The laptop has two
disks. I've created a 2nd partition on the 2nd disk and successfully restored
a image of another machine (Windows 2003) using an imaging app (Acronis' True
Image). However, I'm having a hard time using BCDEDIT to create another entry
in the boot loader... I can't get a prompt to boot into the Windows 2003
environment.

What I'm trying to do is on boot, get prompted to select the OS to boot into
(for presentations & demos), but to default to Vista after 5 seconds. I know
the boot process is different than pre-Vista, but having a hard time creating
a {legacy} entry in my BCD.

Ideas?
 
M

Michal Kawecki

AC said:
I've got Vista Ultimate installed on my laptop just fine. The laptop
has two
disks. I've created a 2nd partition on the 2nd disk and successfully
restored
a image of another machine (Windows 2003) using an imaging app
(Acronis' True
Image). However, I'm having a hard time using BCDEDIT to create
another entry
in the boot loader... I can't get a prompt to boot into the Windows
2003
environment.

What I'm trying to do is on boot, get prompted to select the OS to
boot into
(for presentations & demos), but to default to Vista after 5 seconds.
I know
the boot process is different than pre-Vista, but having a hard time
creating
a {legacy} entry in my BCD.

Ideas?


EasyBCD http://neosmart.net/dl.php?id=1

P.S. http://www.multibooters.co.uk/
 
G

Guest

Thanks Michal... EasyBCD helped. Although I told it the new OS was on E:\, it
saved it to the BCD data store as C:\, but I was able to edit it to look for
it on E:\. Now when I tell it to boot into my second image, I get an error
saying there's a problem in boot.ini. I think this is expected, as the image
I took was within a virtual machine that had only one disk & partition. I
restored the image to the 2nd partition on the second disk. Always had
problems with the boot.ini file... Here's what it says now:

[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="Windows Server 2003, Standard"
/noexecute=optout /fastdetect

So, guessing that I should change both entries to disk(1) and paritition(2)?
Yes, I'm proceeding very carefully as I really don't want to do anything to
my primary partition.
--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog
 
M

Michal Kawecki

Just add a new line in section [operating systems]:
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="W2k3". It will boot system
from second primary partition on second hdd using BIOS numbering. That
BIOS numbering is sometime not exactly what people think they are, so
test alternate rdisk settings too.
You can find Boot.ini explanation here:
http://mirror.href.com/thestarman/asm/mbr/bootini.htm .

But, you will have more problems:
- first, your W2k3 was probably on C letter and now it will be on D or
some other letter. This problem is explained here:
http://support.microsoft.com/default.aspx?scid=kb;en;249321 . So, before
you first boot your W2k3, set it's system partition as active. It will
force it to assign C letter to this partition. Or edit W2k3 registry
under Vista and set Userinit path to value explained in this KB above,
then - after succesfull booting - change system partition letter in W2k3
using regedit (just delete or modify HKLM\SYSTEM\MountedDevices key).
- second, successfull booting W2k3 - which was installed originally in
virtual machine - is very questionable.
- third, you must know that W2k3 will REMOVE all restore points in
Vista.
http://blogs.technet.com/filecab/ar...rd-party-tools-can-affect-restore-points.aspx
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/


AC said:
Thanks Michal... EasyBCD helped. Although I told it the new OS was on
E:\, it
saved it to the BCD data store as C:\, but I was able to edit it to
look for
it on E:\. Now when I tell it to boot into my second image, I get an
error
saying there's a problem in boot.ini. I think this is expected, as the
image
I took was within a virtual machine that had only one disk &
partition. I
restored the image to the 2nd partition on the second disk. Always had
problems with the boot.ini file... Here's what it says now:

[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="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

So, guessing that I should change both entries to disk(1) and
paritition(2)?
Yes, I'm proceeding very carefully as I really don't want to do
anything to
my primary partition.
--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
 
G

Guest

Thanks again. So I set the second partition to be the active one on the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003, Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's something wrong
in my boot.ini file.. not sure what though... Ideas?

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
Just add a new line in section [operating systems]:
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="W2k3". It will boot system
from second primary partition on second hdd using BIOS numbering. That
BIOS numbering is sometime not exactly what people think they are, so
test alternate rdisk settings too.
You can find Boot.ini explanation here:
http://mirror.href.com/thestarman/asm/mbr/bootini.htm .

But, you will have more problems:
- first, your W2k3 was probably on C letter and now it will be on D or
some other letter. This problem is explained here:
http://support.microsoft.com/default.aspx?scid=kb;en;249321 . So, before
you first boot your W2k3, set it's system partition as active. It will
force it to assign C letter to this partition. Or edit W2k3 registry
under Vista and set Userinit path to value explained in this KB above,
then - after succesfull booting - change system partition letter in W2k3
using regedit (just delete or modify HKLM\SYSTEM\MountedDevices key).
- second, successfull booting W2k3 - which was installed originally in
virtual machine - is very questionable.
- third, you must know that W2k3 will REMOVE all restore points in
Vista.
http://blogs.technet.com/filecab/ar...rd-party-tools-can-affect-restore-points.aspx
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/


AC said:
Thanks Michal... EasyBCD helped. Although I told it the new OS was on
E:\, it
saved it to the BCD data store as C:\, but I was able to edit it to
look for
it on E:\. Now when I tell it to boot into my second image, I get an
error
saying there's a problem in boot.ini. I think this is expected, as the
image
I took was within a virtual machine that had only one disk &
partition. I
restored the image to the 2nd partition on the second disk. Always had
problems with the boot.ini file... Here's what it says now:

[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="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

So, guessing that I should change both entries to disk(1) and
paritition(2)?
Yes, I'm proceeding very carefully as I really don't want to do
anything to
my primary partition.
--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
I've got Vista Ultimate installed on my laptop just fine. The
laptop
has two
disks. I've created a 2nd partition on the 2nd disk and
successfully
restored
a image of another machine (Windows 2003) using an imaging app
(Acronis' True
Image). However, I'm having a hard time using BCDEDIT to create
another entry
in the boot loader... I can't get a prompt to boot into the Windows
2003
environment.

What I'm trying to do is on boot, get prompted to select the OS to
boot into
(for presentations & demos), but to default to Vista after 5
seconds.
I know
the boot process is different than pre-Vista, but having a hard
time
creating
a {legacy} entry in my BCD.

Ideas?


EasyBCD http://neosmart.net/dl.php?id=1

P.S. http://www.multibooters.co.uk/
 
D

Don

AC said:
Thanks again. So I set the second partition to be the active one on the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003, Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's something wrong
in my boot.ini file.. not sure what though... Ideas?

The confusing part is that each version of Windows assigns its own
preference for drive letters (A: to Z:) as it sees fit, with no regard
for what previous versions have assigned.

I got so fed up with being confused by this that I edited my boot.ini
to include one entry for any conceivable partition/disk combination!

I was careful to name each entry in boot.ini so I could tell which one
of them resulted in a successful boot, and then I tried each of them,
one by one, until I found the one entry which worked. Years later, I
still have all of those extraneous entries in boot.ini, just waiting for
the day I might possibly need to try them again, at random ;o)
 
M

Michal Kawecki

"Invalid boot.ini file" - there must be some problem with syntax of your
Boot.ini file. Correct it manually or boot into Recovery Console from
W2k3 installation CD and rebuild this file with command bootcfg
/rebuild.

BTW if you have fdd drive then you can test your W2k3 system without
using bootmanager from Vista. Just format one floppy disk under W2k3 -
this procedure will create a correct bootrecord on it - then copy there
ntldr, ntdetect.com, Boot.ini files from your W2k3 installation and boot
computer from that floppy.
If you do not have fdd then simply change boot order in your BIOS
selecting W2k3 hdd as first boot device. But remember that it will also
change BIOS hdd numbering, so you must correct "rdrive" setting in your
Boot.ini file to 0.

AC said:
Thanks again. So I set the second partition to be the active one on
the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is
E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to
E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's
something wrong
in my boot.ini file.. not sure what though... Ideas?

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
Just add a new line in section [operating systems]:
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="W2k3". It will boot
system
from second primary partition on second hdd using BIOS numbering.
That
BIOS numbering is sometime not exactly what people think they are, so
test alternate rdisk settings too.
You can find Boot.ini explanation here:
http://mirror.href.com/thestarman/asm/mbr/bootini.htm .

But, you will have more problems:
- first, your W2k3 was probably on C letter and now it will be on D
or
some other letter. This problem is explained here:
http://support.microsoft.com/default.aspx?scid=kb;en;249321 . So,
before
you first boot your W2k3, set it's system partition as active. It
will
force it to assign C letter to this partition. Or edit W2k3 registry
under Vista and set Userinit path to value explained in this KB
above,
then - after succesfull booting - change system partition letter in
W2k3
using regedit (just delete or modify HKLM\SYSTEM\MountedDevices key).
- second, successfull booting W2k3 - which was installed originally
in
virtual machine - is very questionable.
- third, you must know that W2k3 will REMOVE all restore points in
Vista.
http://blogs.technet.com/filecab/ar...rd-party-tools-can-affect-restore-points.aspx
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/


AC said:
Thanks Michal... EasyBCD helped. Although I told it the new OS was
on
E:\, it
saved it to the BCD data store as C:\, but I was able to edit it to
look for
it on E:\. Now when I tell it to boot into my second image, I get
an
error
saying there's a problem in boot.ini. I think this is expected, as
the
image
I took was within a virtual machine that had only one disk &
partition. I
restored the image to the 2nd partition on the second disk. Always
had
problems with the boot.ini file... Here's what it says now:

[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="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

So, guessing that I should change both entries to disk(1) and
paritition(2)?
Yes, I'm proceeding very carefully as I really don't want to do
anything to
my primary partition.
--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



:

I've got Vista Ultimate installed on my laptop just fine. The
laptop
has two
disks. I've created a 2nd partition on the 2nd disk and
successfully
restored
a image of another machine (Windows 2003) using an imaging app
(Acronis' True
Image). However, I'm having a hard time using BCDEDIT to create
another entry
in the boot loader... I can't get a prompt to boot into the
Windows
2003
environment.

What I'm trying to do is on boot, get prompted to select the OS
to
boot into
(for presentations & demos), but to default to Vista after 5
seconds.
I know
the boot process is different than pre-Vista, but having a hard
time
creating
a {legacy} entry in my BCD.

Ideas?


EasyBCD http://neosmart.net/dl.php?id=1

P.S. http://www.multibooters.co.uk/
 
M

Michal Kawecki

[...]
When I'm in Vista, the partition with the restored Win2003 image is
E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to
E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's
something wrong
in my boot.ini file.. not sure what though... Ideas?


EasyBCD show drive letters just for easy editing of boot entries. In
fact those entries are remembered and enumerated using it's GUID
numbers. Each operating system store actually used letter assignments in
it's own registry (in HKLM\System\MountedDevices key), but bootmanager
can't use those assignments.
 
G

Guest

Unfortunately that's not an option (booting using Win2003 or using via a
FDD). I'm doing this on a laptop and the 2nd drive (in the modular bay) is
where I'm trying to get Win2003 to run... so no floppy or optical drive
available.

I'll try many combinatinos to see which one works. All I needed was a
confirmation that the Vista booter was correct, and now my problem is within
the boot.ini file.

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
"Invalid boot.ini file" - there must be some problem with syntax of your
Boot.ini file. Correct it manually or boot into Recovery Console from
W2k3 installation CD and rebuild this file with command bootcfg
/rebuild.

BTW if you have fdd drive then you can test your W2k3 system without
using bootmanager from Vista. Just format one floppy disk under W2k3 -
this procedure will create a correct bootrecord on it - then copy there
ntldr, ntdetect.com, Boot.ini files from your W2k3 installation and boot
computer from that floppy.
If you do not have fdd then simply change boot order in your BIOS
selecting W2k3 hdd as first boot device. But remember that it will also
change BIOS hdd numbering, so you must correct "rdrive" setting in your
Boot.ini file to 0.

AC said:
Thanks again. So I set the second partition to be the active one on
the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is
E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to
E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's
something wrong
in my boot.ini file.. not sure what though... Ideas?

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
Just add a new line in section [operating systems]:
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="W2k3". It will boot
system
from second primary partition on second hdd using BIOS numbering.
That
BIOS numbering is sometime not exactly what people think they are, so
test alternate rdisk settings too.
You can find Boot.ini explanation here:
http://mirror.href.com/thestarman/asm/mbr/bootini.htm .

But, you will have more problems:
- first, your W2k3 was probably on C letter and now it will be on D
or
some other letter. This problem is explained here:
http://support.microsoft.com/default.aspx?scid=kb;en;249321 . So,
before
you first boot your W2k3, set it's system partition as active. It
will
force it to assign C letter to this partition. Or edit W2k3 registry
under Vista and set Userinit path to value explained in this KB
above,
then - after succesfull booting - change system partition letter in
W2k3
using regedit (just delete or modify HKLM\SYSTEM\MountedDevices key).
- second, successfull booting W2k3 - which was installed originally
in
virtual machine - is very questionable.
- third, you must know that W2k3 will REMOVE all restore points in
Vista.
http://blogs.technet.com/filecab/ar...rd-party-tools-can-affect-restore-points.aspx
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/


Thanks Michal... EasyBCD helped. Although I told it the new OS was
on
E:\, it
saved it to the BCD data store as C:\, but I was able to edit it to
look for
it on E:\. Now when I tell it to boot into my second image, I get
an
error
saying there's a problem in boot.ini. I think this is expected, as
the
image
I took was within a virtual machine that had only one disk &
partition. I
restored the image to the 2nd partition on the second disk. Always
had
problems with the boot.ini file... Here's what it says now:

[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="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

So, guessing that I should change both entries to disk(1) and
paritition(2)?
Yes, I'm proceeding very carefully as I really don't want to do
anything to
my primary partition.
--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



:

I've got Vista Ultimate installed on my laptop just fine. The
laptop
has two
disks. I've created a 2nd partition on the 2nd disk and
successfully
restored
a image of another machine (Windows 2003) using an imaging app
(Acronis' True
Image). However, I'm having a hard time using BCDEDIT to create
another entry
in the boot loader... I can't get a prompt to boot into the
Windows
2003
environment.

What I'm trying to do is on boot, get prompted to select the OS
to
boot into
(for presentations & demos), but to default to Vista after 5
seconds.
I know
the boot process is different than pre-Vista, but having a hard
time
creating
a {legacy} entry in my BCD.

Ideas?


EasyBCD http://neosmart.net/dl.php?id=1

P.S. http://www.multibooters.co.uk/
 
M

Michal Kawecki

I suggest you yet another solution: copy Boot.ini, ntldr, ntdetect.com
files to C: partition (with Vista) and select it using EasyBCD as W2k3
boot partition. It very probably will correct problems resulting from
starting W2k3 bootmanager from removable disk.

regards,
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/

AC said:
Unfortunately that's not an option (booting using Win2003 or using via
a
FDD). I'm doing this on a laptop and the 2nd drive (in the modular
bay) is
where I'm trying to get Win2003 to run... so no floppy or optical
drive
available.

I'll try many combinatinos to see which one works. All I needed was a
confirmation that the Vista booter was correct, and now my problem is
within
the boot.ini file.

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
"Invalid boot.ini file" - there must be some problem with syntax of
your
Boot.ini file. Correct it manually or boot into Recovery Console from
W2k3 installation CD and rebuild this file with command bootcfg
/rebuild.

BTW if you have fdd drive then you can test your W2k3 system without
using bootmanager from Vista. Just format one floppy disk under
W2k3 -
this procedure will create a correct bootrecord on it - then copy
there
ntldr, ntdetect.com, Boot.ini files from your W2k3 installation and
boot
computer from that floppy.
If you do not have fdd then simply change boot order in your BIOS
selecting W2k3 hdd as first boot device. But remember that it will
also
change BIOS hdd numbering, so you must correct "rdrive" setting in
your
Boot.ini file to 0.

AC said:
Thanks again. So I set the second partition to be the active one on
the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is
E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to
E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's
something wrong
in my boot.ini file.. not sure what though... Ideas?

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog
 
G

Guest

OK... brick wall suffuciently hit.

The only way I was able to get the legacy OS to even show me the list of
items in the boot.ini file was to copy ntldr & ntdetect (and boot.ini) to the
root of c:\ (where Vista is). But every combination either results in a black
screen (after picking (1) the legacy OS and then (2) the OS listed from
within the boot.ini file). The entry in boot.ini that seems to work is the
following:
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows 2003 #5, Standard"
/noexecute=optout /fastdetect

Makes sense as I restored Win2k3 to E:\ which is the 2nd partition on the
2nd disk. But it still won't boot... just goes to a black screen and sits
there (all others reported errors).

When I look at Vista boot info using EasyBCD, I see the legacy OS (pointing
to E:\).

I'm lost... not sure what I'm supposed to do here... arg!

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog




Michal Kawecki said:
I suggest you yet another solution: copy Boot.ini, ntldr, ntdetect.com
files to C: partition (with Vista) and select it using EasyBCD as W2k3
boot partition. It very probably will correct problems resulting from
starting W2k3 bootmanager from removable disk.

regards,
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/

AC said:
Unfortunately that's not an option (booting using Win2003 or using via
a
FDD). I'm doing this on a laptop and the 2nd drive (in the modular
bay) is
where I'm trying to get Win2003 to run... so no floppy or optical
drive
available.

I'll try many combinatinos to see which one works. All I needed was a
confirmation that the Vista booter was correct, and now my problem is
within
the boot.ini file.

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog



Michal Kawecki said:
"Invalid boot.ini file" - there must be some problem with syntax of
your
Boot.ini file. Correct it manually or boot into Recovery Console from
W2k3 installation CD and rebuild this file with command bootcfg
/rebuild.

BTW if you have fdd drive then you can test your W2k3 system without
using bootmanager from Vista. Just format one floppy disk under
W2k3 -
this procedure will create a correct bootrecord on it - then copy
there
ntldr, ntdetect.com, Boot.ini files from your W2k3 installation and
boot
computer from that floppy.
If you do not have fdd then simply change boot order in your BIOS
selecting W2k3 hdd as first boot device. But remember that it will
also
change BIOS hdd numbering, so you must correct "rdrive" setting in
your
Boot.ini file to 0.

Thanks again. So I set the second partition to be the active one on
the 2nd
disk. I also modified my boot.ini to be the following:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003,
Standard"
/noexecute=optout /fastdetect

Still getting an error when I try to boot from this OS:
Invalid boot.ini file
Booting from c:\windows
NTDETECT failed

When I'm in Vista, the partition with the restored Win2003 image is
E:\. I
have verified that the 2nd boot option using EasyBCD is pointing to
E:\. Not
sure if this helps, but I thought I'd mention it. Assume it's
something wrong
in my boot.ini file.. not sure what though... Ideas?

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog
 
M

Michal Kawecki

If I correctly understand what you sad (sorry for my poor english),
then:
a/ you created a new legacy entry in Vista bootmanager using EasyBCD
pointing it to E:\ (why not to C:\?),
b/ this new entry initially not worked correctly, but when you copied
those three files to the root of Vista partition then it started showing
Boot.ini menu.

Correct? If yes, then you have some problem with enumeration of hard
disks by BIOS (probably by BIOS).

IMO when you select now legacy entry from Vista bootmenu then Vista
bootmanager load ntldr file from E (and it's correct), but ntldr
probably search and load Boot.ini file from C, not E. So, I suggest you
making one test: differentiate somehow those two Boot.ini files, then
create yet another legacy entry using EasyBCD pointing it to C:\ and
leave entry pointing to E:\ unchanged. Boot into both entry; one of this
should work and you should see your Boot.ini menu. Just test now, what
Boot.ini is in use; it must be on that same partition where you pointed
your legacy entry. If it is not - then your BIOS incorrectly enumerate
hdd's.

But if both *is* on the same partition as your booted entry, then... you
must have some problem with your W2k3 installation. So, I can't step
further until you test your cloned system booting it directly. Go into
BIOS and select your second drive as boot device. I'm sorry, but until
this I can't help you anymore...

P.S. Here you find a great explanation of Windows NT boot sequence and
Boot.ini syntax:
http://www.mossywell.com/boot-sequence/#NTLDR_with_Windows_NT

P.P.S. Just for sure: you have on that second drive only two primary
partition, FAT or NTFS. No Linux, no extended partition. Your "active"
flag of W2k3 system partition should be hexa 0x80, not 0x81 or 0x82
(check this with Partinfo http://terabyteunlimited.com/utilities.html ).
And your disk geometry should be 255/63.
--
M. [Windows - Shell/User MVP]
/before private reply change px with pl in my e-mail address/


AC said:
OK... brick wall suffuciently hit.

The only way I was able to get the legacy OS to even show me the list
of
items in the boot.ini file was to copy ntldr & ntdetect (and boot.ini)
to the
root of c:\ (where Vista is). But every combination either results in
a black
screen (after picking (1) the legacy OS and then (2) the OS listed
from
within the boot.ini file). The entry in boot.ini that seems to work is
the
following:
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows 2003 #5,
Standard"
/noexecute=optout /fastdetect

Makes sense as I restored Win2k3 to E:\ which is the 2nd partition on
the
2nd disk. But it still won't boot... just goes to a black screen and
sits
there (all others reported errors).

When I look at Vista boot info using EasyBCD, I see the legacy OS
(pointing
to E:\).

I'm lost... not sure what I'm supposed to do here... arg!

--
-AC [MVP MCMS]
http://www.andrewconnell.com
http://www.andrewconnell.com/mvp
http://www.andrewconnell.com/blog
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top