XP Dual Boot across two physical HDD - Help Please

[Galen Somerville]

At least that wasn't a bold faced font.

Galen

"db" <databaseben.discussions.microsoft.com> wrote in message not interested .

Mr. (e-mail address removed)

however, unlike yourself I am not accountable
to anyone here except those i choose
to help.

Please spare the world your "help" as it it much better
off without it. You don't even know enough to post in
plain text, much less to actually help anyone with your
textual flatuses. As for being "not accountable", your
postings are not accountable because they account for
nothing.

*TimDaniels*

 

[Rock]

"db" <databaseben.discussions.microsoft.com> wrote

Don't offer me any deals in the future.
Don't mention me in your sacastic postings.

<more nonsensical ranting snipped>

Oh my, LOL, that nerve hit went deep.

 

[db]

Mr. Rock, MVP

based on your response
it seems that you are still
exhibiting sarcasms and
antagonistic behaviors.

you simply cannot understand
that your actions are unprofessional.

be advised that due to your continue use of discourteous
and disrespectful remarks, I believe this information
should be provided to the MVP administrators.

keep in mind that you have created all of the information
that is available for me to provide to them. your
postings will provide accuracy in my dissertation.

as i had mentioned sometime ago, i think that biting the
hand that feeds your ego is disloyal.

unfortunately i have reason to believe that your disloyalty
also reflects poorly on the other Microsoft mvp's as well.

For those Microsoft MVP's who are inherently
professional are likely hoping that you simply
shut up because the postings you have provided
to me reflect poorly to the public and
Microsoft customers.

i do not want to hear from you again.

and do not invite a response from me via
your sarcasms or references in your future
responses.


-------------------------------------

http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RulesofConduct :
Rules of conduct
Expectations of service
Microsoft MVPs: Microsoft MVPs (Most Valuable Professionals) volunteer technical answers and expertise in many Microsoft Community Web sites. Microsoft MVPs come from a wide range of backgrounds and professions. All share a willingness to give their time, expertise, and advice to enhance the technical skills of others. MVPs are not Microsoft employees and Microsoft has no expectations of MVPs beyond the expectations of courtesy, professionalism, and adherence to the Community rules that we ask of all Microsoft community members. For more information on the MVP program and how you can become an MVP, see .


"db" <databaseben.discussions.microsoft.com> wrote

Don't offer me any deals in the future.
Don't mention me in your sacastic postings.

<more nonsensical ranting snipped>

Oh my, LOL, that nerve hit went deep.

 

[Rock]

"db" <databaseben.discussions.microsoft.com>

and do not invite a response from me via
your sarcasms or references in your future
responses.

<snip>

It not only hit a nerve, it went right to the bone, eh?

 

[mikeyhsd]

as he said and I have said repeatedly, RUDE and DISCOURTEOUS behavior.
like it or not one more person dares to say so.,




(e-mail address removed)



"db" <databaseben.discussions.microsoft.com>

and do not invite a response from me via
your sarcasms or references in your future
responses.

<snip>

It not only hit a nerve, it went right to the bone, eh?

 

[Jethro]

Hi all -

I found this thread dealing with dual booting which I have been
wanting to do simpler. I have two hard drives (Primary Master and
Primary Slave), both containing XP OS, but with different data and
apps.

Without going into why I want to boot a drive of choice, when I do it
I always make the choice in the BIOS, and except for the careful
choosing of the BIOS changes I have to make, it has done the job for
me.

I saw that Mr Daniels suggested:

2) Boot.ini menu - Your boot.ini file (at C:\boot.ini - which you may have to
unhide to view). [clip]
Using Notepad, add another entry under "[boot loader]" with the
argument to rdisk being "1" instead of "0", and change the number of
seconds for the timeout to be something like 10 seconds. Thus, the
boot.ini for dual-boot would look like:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP1" /noexecute=optin
/fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="WinXP2" /noexecute=optin
/fastdetect

With this form of the boot.ini file on both HD's "active" partitions, it doesn't
matter
which HD is at the head of the HD Boot Order list - either one will have a
dual-boot
menu for you to choose one or the other OS to boot. Just remember that
"rdisk(0)"
designates the HD at the head of the list, and "rdisk(1)" designates the 2nd HD
in
the list.

I tried what Mr Daniels suggests, but I cannot boot up from drive two,
Boot from drive one remains okay. I get to choose which drive at
boot-up. but drive two produces this error message right off:

Windows could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.
Please check the Windows documentation [clip].

I had changed my BIOS.INI file thus:
[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

This surprised me since drive two will boot up okay if selected via
the BIOS.

So what do you guys think? Did I miss something?

I would appreciate some help here.

Thanks

Jethro

 

[John John]

Hi all -

I found this thread dealing with dual booting which I have been
wanting to do simpler. I have two hard drives (Primary Master and
Primary Slave), both containing XP OS, but with different data and
apps.

Without going into why I want to boot a drive of choice, when I do it
I always make the choice in the BIOS, and except for the careful
choosing of the BIOS changes I have to make, it has done the job for
me.

I saw that Mr Daniels suggested:

2) Boot.ini menu - Your boot.ini file (at C:\boot.ini - which you may have to
unhide to view).
[clip]

Using Notepad, add another entry under "[boot loader]" with the
argument to rdisk being "1" instead of "0", and change the number of
seconds for the timeout to be something like 10 seconds. Thus, the
boot.ini for dual-boot would look like:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP1" /noexecute=optin
/fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="WinXP2" /noexecute=optin
/fastdetect

With this form of the boot.ini file on both HD's "active" partitions, it doesn't
matter
which HD is at the head of the HD Boot Order list - either one will have a
dual-boot
menu for you to choose one or the other OS to boot. Just remember that
"rdisk(0)"
designates the HD at the head of the list, and "rdisk(1)" designates the 2nd HD
in
the list.

I tried what Mr Daniels suggests, but I cannot boot up from drive two,
Boot from drive one remains okay. I get to choose which drive at
boot-up. but drive two produces this error message right off:

Windows could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.
Please check the Windows documentation [clip].

I had changed my BIOS.INI file thus:
[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

This surprised me since drive two will boot up okay if selected via
the BIOS.

So what do you guys think? Did I miss something?

I would appreciate some help here.

Try this:

[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

John

 

[Jethro]

Hi all -

I found this thread dealing with dual booting which I have been
wanting to do simpler. I have two hard drives (Primary Master and
Primary Slave), both containing XP OS, but with different data and
apps.

Without going into why I want to boot a drive of choice, when I do it
I always make the choice in the BIOS, and except for the careful
choosing of the BIOS changes I have to make, it has done the job for
me.

I saw that Mr Daniels suggested:

2) Boot.ini menu - Your boot.ini file (at C:\boot.ini - which you may have to
unhide to view).
[clip]

Using Notepad, add another entry under "[boot loader]" with the
argument to rdisk being "1" instead of "0", and change the number of
seconds for the timeout to be something like 10 seconds. Thus, the
boot.ini for dual-boot would look like:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP1" /noexecute=optin
/fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="WinXP2" /noexecute=optin
/fastdetect

With this form of the boot.ini file on both HD's "active" partitions, it doesn't
matter
which HD is at the head of the HD Boot Order list - either one will have a
dual-boot
menu for you to choose one or the other OS to boot. Just remember that
"rdisk(0)"
designates the HD at the head of the list, and "rdisk(1)" designates the 2nd HD
in
the list.

I tried what Mr Daniels suggests, but I cannot boot up from drive two,
Boot from drive one remains okay. I get to choose which drive at
boot-up. but drive two produces this error message right off:

Windows could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.
Please check the Windows documentation [clip].

I had changed my BIOS.INI file thus:
[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

This surprised me since drive two will boot up okay if selected via
the BIOS.

So what do you guys think? Did I miss something?

I would appreciate some help here.

Try this:

[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

John

Aw jeeze! I got the (1) in the wrong place, and didn't see the
error. Remind me to shop for a new brain.

Thanks

Jethro

 

[John John]

Jethro wrote:

Hi all -

I found this thread dealing with dual booting which I have been
wanting to do simpler. I have two hard drives (Primary Master and
Primary Slave), both containing XP OS, but with different data and
apps.

Without going into why I want to boot a drive of choice, when I do it
I always make the choice in the BIOS, and except for the careful
choosing of the BIOS changes I have to make, it has done the job for
me.

I saw that Mr Daniels suggested:



2) Boot.ini menu - Your boot.ini file (at C:\boot.ini - which you may have to
unhide to view).

[clip]


Using Notepad, add another entry under "[boot loader]" with the
argument to rdisk being "1" instead of "0", and change the number of
seconds for the timeout to be something like 10 seconds. Thus, the
boot.ini for dual-boot would look like:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="WinXP1" /noexecute=optin
/fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="WinXP2" /noexecute=optin
/fastdetect

With this form of the boot.ini file on both HD's "active" partitions, it doesn't
matter
which HD is at the head of the HD Boot Order list - either one will have a
dual-boot
menu for you to choose one or the other OS to boot. Just remember that
"rdisk(0)"
designates the HD at the head of the list, and "rdisk(1)" designates the 2nd HD
in
the list.


I tried what Mr Daniels suggests, but I cannot boot up from drive two,
Boot from drive one remains okay. I get to choose which drive at
boot-up. but drive two produces this error message right off:

Windows could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.
Please check the Windows documentation [clip].

I had changed my BIOS.INI file thus:
[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

This surprised me since drive two will boot up okay if selected via
the BIOS.

So what do you guys think? Did I miss something?

I would appreciate some help here.

Try this:

[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="Microsoft Windows XP
Professional DISK 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Professional DISK 2" /noexecute=optin /fastdetect

John

Aw jeeze! I got the (1) in the wrong place, and didn't see the
error. Remind me to shop for a new brain.

No problem, we all have our off days.

John

 

[Timothy Daniels]

Aw jeeze! I got the (1) in the wrong place, and didn't see the
error.

Does the change from rdisk(0) to rdisk(1) load OS from the
2nd HD for you now?

*TimDaniels*