Dual Boot problems

[Guest]

First let me get some configuration issues out of the way:

1. System has two hard disks and a CD ROM.
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G
2.5 2nd Hard Disk has two primary partitions e: and g: and a free space (I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe? (since I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have tried it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything else to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me that
it ever attempted to do anything with the 2nd hard disk (no fba log for
example), (although the standard win2k rectangles crossed the bottom of the
display momentarily) so i'm guessing it never got there. Changing the
boot.ini on the first hard disk to have rdisk 2 gives some other other
message about no Win 2k found.

Any ideas?

 

[John Coyne \(eMVP\)]

Couple answers here for you...

#1 yes, your boot.ini settings look correct to me. (I'm no rocket scientist,
but they LOOK correct)
Physical Disks start with 0 and Partitions start with 1.

#2 you are correct the required Boot files for Win2K are different from
XP/XPE... take NTDETECT.com, and NTLDR.SYS from your XPE load and replace
the ones on the boot volume (the WIN2K ones) the XP/XPE ones are backward
compatible... (Make backups of the 2K ones, so you don't hose your whole
box... JIC)

#3 Based on your description below, and if all physical drives (optical and
otherwise are present) I would say that you need to tell TD to use Drive E

In Target Designer, settings, I set Boot Drive to D:\ and everything else to
D:\Windows, D:\Program Files, D:\Documents and Settings

where in your original Configuration issues statement, you said:

2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G

Again, that's assuming that the CDROM is present in the XPE build too.

HTH,
JC

--
John Coyne
eMVP
Windows Embedded Black Belt
Arrow Electronics, OCS division



When replying directly to this message remove the NOSPAM_ from the address

First let me get some configuration issues out of the way:

1. System has two hard disks and a CD ROM.
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G
2.5 2nd Hard Disk has two primary partitions e: and g: and a free space
(I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe? (since
I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have tried
it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything else
to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets
read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me
that
it ever attempted to do anything with the 2nd hard disk (no fba log for
example), (although the standard win2k rectangles crossed the bottom of
the
display momentarily) so i'm guessing it never got there. Changing the
boot.ini on the first hard disk to have rdisk 2 gives some other other
message about no Win 2k found.

Any ideas?

 

[Thomas Johansen]

Couple answers here for you...

#1 yes, your boot.ini settings look correct to me. (I'm no rocket scientist,
but they LOOK correct)
Physical Disks start with 0 and Partitions start with 1.

#2 you are correct the required Boot files for Win2K are different from
XP/XPE... take NTDETECT.com, and NTLDR.SYS from your XPE load and replace
the ones on the boot volume (the WIN2K ones) the XP/XPE ones are backward
compatible... (Make backups of the 2K ones, so you don't hose your whole
box... JIC)

Are they.?? Doesn't seems to me here. When I replace the NTDETECT and NTLDR
with those from WinXp (embedded, XP Pro SP1/SP2), my Win2k cannt boot
correctly.
When I try boot from the Win2k files, my XP cannot boot (With the same error
!!)

?????????????????

Not that I need this dual boot feature, but just what I have seen... But
maybe in the future, so any idea what I am missing ?

#3 Based on your description below, and if all physical drives (optical and
otherwise are present) I would say that you need to tell TD to use Drive E

In Target Designer, settings, I set Boot Drive to D:\ and everything else to
D:\Windows, D:\Program Files, D:\Documents and Settings

where in your original Configuration issues statement, you said:

2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and

G
Again, that's assuming that the CDROM is present in the XPE build too.

HTH,
JC

--
John Coyne
eMVP
Windows Embedded Black Belt
Arrow Electronics, OCS division



When replying directly to this message remove the NOSPAM_ from the address

First let me get some configuration issues out of the way:

1. System has two hard disks and a CD ROM.
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G
2.5 2nd Hard Disk has two primary partitions e: and g: and a free space
(I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe? (since
I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have tried
it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything else
to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets
read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me
that
it ever attempted to do anything with the 2nd hard disk (no fba log for
example), (although the standard win2k rectangles crossed the bottom of
the
display momentarily) so i'm guessing it never got there. Changing the
boot.ini on the first hard disk to have rdisk 2 gives some other other
message about no Win 2k found.

Any ideas?

 

[Slobodan Brcin \(eMVP\)]

Yes you need to use latest service pack ntldr. and ntdetect.com files in root of boot partition (AKA C
So the best thing is to use ones from SP2, and yes they are backward compatible with W2K and SP1, and Gold versions of XP.

Regarding C:, D:, E: or letter that you need to use file fba.log will tell you if you choose wrong volume letter and if you need to
change it to something else.

This tip might interest you if you plan to two disks for development:
http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx

Regards,
Slobodan

Couple answers here for you...

#1 yes, your boot.ini settings look correct to me. (I'm no rocket scientist,
but they LOOK correct)
Physical Disks start with 0 and Partitions start with 1.

#2 you are correct the required Boot files for Win2K are different from
XP/XPE... take NTDETECT.com, and NTLDR.SYS from your XPE load and replace
the ones on the boot volume (the WIN2K ones) the XP/XPE ones are backward
compatible... (Make backups of the 2K ones, so you don't hose your whole
box... JIC)

Are they.?? Doesn't seems to me here. When I replace the NTDETECT and NTLDR
with those from WinXp (embedded, XP Pro SP1/SP2), my Win2k cannt boot
correctly.
When I try boot from the Win2k files, my XP cannot boot (With the same error
!!)

?????????????????

Not that I need this dual boot feature, but just what I have seen... But
maybe in the future, so any idea what I am missing ?

#3 Based on your description below, and if all physical drives (optical and
otherwise are present) I would say that you need to tell TD to use Drive E

In Target Designer, settings, I set Boot Drive to D:\ and everything else to
D:\Windows, D:\Program Files, D:\Documents and Settings

where in your original Configuration issues statement, you said:

2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and

G
Again, that's assuming that the CDROM is present in the XPE build too.

HTH,
JC

--
John Coyne
eMVP
Windows Embedded Black Belt
Arrow Electronics, OCS division



When replying directly to this message remove the NOSPAM_ from the address

First let me get some configuration issues out of the way:

1. System has two hard disks and a CD ROM.
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G
2.5 2nd Hard Disk has two primary partitions e: and g: and a free space
(I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe? (since
I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have tried
it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything else
to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets
read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me
that
it ever attempted to do anything with the 2nd hard disk (no fba log for
example), (although the standard win2k rectangles crossed the bottom of
the
display momentarily) so i'm guessing it never got there. Changing the
boot.ini on the first hard disk to have rdisk 2 gives some other other
message about no Win 2k found.

Any ideas?

 

[Thomas Johansen]

Thnaks... So I need those from SP2.. Last time I tried was with XP Pro files

Not that I need this dual boot feature right now, but its nice to now...

Yes you need to use latest service pack ntldr. and ntdetect.com files in

root of boot partition (AKA C

So the best thing is to use ones from SP2, and yes they are backward

compatible with W2K and SP1, and Gold versions of XP.

Regarding C:, D:, E: or letter that you need to use file fba.log will tell

you if you choose wrong volume letter and if you need to

change it to something else.

This tip might interest you if you plan to two disks for development:
http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx

Regards,
Slobodan

Couple answers here for you...

#1 yes, your boot.ini settings look correct to me. (I'm no rocket scientist,
but they LOOK correct)
Physical Disks start with 0 and Partitions start with 1.

#2 you are correct the required Boot files for Win2K are different from
XP/XPE... take NTDETECT.com, and NTLDR.SYS from your XPE load and replace
the ones on the boot volume (the WIN2K ones) the XP/XPE ones are backward
compatible... (Make backups of the 2K ones, so you don't hose your whole
box... JIC)

Are they.?? Doesn't seems to me here. When I replace the NTDETECT and NTLDR
with those from WinXp (embedded, XP Pro SP1/SP2), my Win2k cannt boot
correctly.
When I try boot from the Win2k files, my XP cannot boot (With the same error
!!)

?????????????????

Not that I need this dual boot feature, but just what I have seen... But
maybe in the future, so any idea what I am missing ?

#3 Based on your description below, and if all physical drives

(optical
and

otherwise are present) I would say that you need to tell TD to use Drive E
In Target Designer, settings, I set Boot Drive to D:\ and everything
else to
D:\Windows, D:\Program Files, D:\Documents and Settings
where in your original Configuration issues statement, you said:
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E:

(and
G

Again, that's assuming that the CDROM is present in the XPE build too.

HTH,
JC

--
John Coyne
eMVP
Windows Embedded Black Belt
Arrow Electronics, OCS division



When replying directly to this message remove the NOSPAM_ from the address
First let me get some configuration issues out of the way:

1. System has two hard disks and a CD ROM.
2. First Hard Disk is C:, CD Rom is D: and 2nd Hard disk is E: (and G
2.5 2nd Hard Disk has two primary partitions e: and g: and a free space
(I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe? (since
I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have tried
it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything else
to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets
read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me
that
it ever attempted to do anything with the 2nd hard disk (no fba log for
example), (although the standard win2k rectangles crossed the bottom of
the
display momentarily) so i'm guessing it never got there. Changing the
boot.ini on the first hard disk to have rdisk 2 gives some other other
message about no Win 2k found.

Any ideas?

 

[Thomas Johansen]

Thnaks... So I need those from SP2.. Last time I tried was with XP Pro files

XP Pro SP 1 that is ...

Not that I need this dual boot feature right now, but its nice to now...

Yes you need to use latest service pack ntldr. and ntdetect.com files in

root of boot partition (AKA C

So the best thing is to use ones from SP2, and yes they are backward

compatible with W2K and SP1, and Gold versions of XP.

Regarding C:, D:, E: or letter that you need to use file fba.log will

tell
you if you choose wrong volume letter and if you need to

change it to something else.

This tip might interest you if you plan to two disks for development:

http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx

Regards,
Slobodan

too.

(and

G

2.5 2nd Hard Disk has two primary partitions e: and g: and a free space
(I
eventually want to get EWF working).
3. OS on hard Disk 1 is Win2k (Is that okay for booting to WinXpe?
(since
I
think I read somewhere that the NTLDR is used from Drive 1)
4. Disk 2 E: has WinXPe image copied from result of Target Designer
5. I modified boot.ini on c: to contain:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

I think rdisk should be 1 because it is the 2nd hard disk. (I have
tried
it
as 2 also - see results below)

In Target Designer, settings, I set Boot Drive to D:\ and everything
else
to
D:\Windows, D:\Program Files, D:\Documents and Settings
This was what I read to do in the Liming book.

and Boot Arc Path to
multi(0)disk(0)rdisk(1)partition(1)
(Although I don't believe the boot.ini on the 2nd Hard disk ever gets
read,
correct?)

At any rate, at bootup, I select the Win Xp Embedded partition and get a
blue screen with a BAD_SYSTEM_CONFIG_INFO message. It's not clear to me
that
it ever attempted to do anything with the 2nd hard disk (no fba

log

for

bottom

of

Changing

the