why change boot order?

just use boot.ini to create Dual Boot Menu!!
then boot to whichever drive you want!!

"Uncle John" wrote:

> Dartmouth
>
> Timothy Daniels has set it out well. If you look a few days back in this
> news group you will have seen a short summary of how to do it using two
> disks and switching the boot priority to change which OS is used.
>
> BTW it helps to have a large bit map on the desktop of the backup disks desk
> top and to label each disk with clearly different names. if you just have C
> and D Windows swaps them round at boot time and it is easy to not appreciate
> which disk you are using.
>
> --
> Uncle John
> "Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
> news:grqdnSoTau83FgbenZ2dnUVZ_t2dnZ2d@comcast.com. ..
> > "Timothy Daniels" wrote:
> >>
> >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Clone OS" /fastdetect
> >
> >
> > Correction: The entry that points to the "other" HD
> > and its OS should be something like:
> > multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Clone OS" /fastdetect
> >
> > (note that "rdisk(0)" refers to the HD at Relative Position 0
> > in the BIOS's hard drive boot order, and "rdisk(1)" refers to
> > the HD at Relative Position 1 in the BIOS's hard drive boot
> > order - i.e. the Relative Position starts at 0.) If the 1st HD
> > gets control, it will because is was at Relative Position 0
> > ("rdisk(0)"), and it will know the other HD as the one at
> > Relative Position 1 ("rdisk(1)"). And if the 2nd HD gets
> > control, it will be because IT had been PUT at Relative
> > Position 0 in the BIOS's hard drive boot order, and it will
> > know the other HD as the one at Relative Position 1
> > (i.e. "rdisk(1)"). So this means each partition can have
> > the same boot.ini contents.
> >
> > *TimDaniels*
> >
>
>
>

Because the original poster may not know how to
(or doesn't want to) modify his boot.ini file. We're
giving him the option. But... he has apparently lost
interest or any desire to provide more information
about his system.

*TimDaniels*

"Dixonian69" wrote:
> why change boot order?
>
> just use boot.ini to create Dual Boot Menu!!
> then boot to whichever drive you want!!
>
> "Uncle John" wrote:
>
>> Dartmouth
>>
>> Timothy Daniels has set it out well. If you look a few days
>> back in this news group you will have seen a short summary
>> of how to do it using two disks and switching the boot
>> priority to change which OS is used.
>>
>> BTW it helps to have a large bit map on the desktop of
>> the backup disks desk top and to label each disk with
>> clearly different names. if you just have C and D Windows
>> swaps them round at boot time and it is easy to not
>> appreciate which disk you are using.
>>
>> --
>> Uncle John
>> "Timothy Daniels" wrote:
>> > "Timothy Daniels" wrote:
>> >>
>> >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Clone OS" /fastdetect
>> >
>> >
>> > Correction: The entry that points to the "other" HD
>> > and its OS should be something like:
>> > multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Clone OS" /fastdetect
>> >
>> > (note that "rdisk(0)" refers to the HD at Relative Position 0
>> > in the BIOS's hard drive boot order, and "rdisk(1)" refers to
>> > the HD at Relative Position 1 in the BIOS's hard drive boot
>> > order - i.e. the Relative Position starts at 0.) If the 1st HD
>> > gets control, it will because is was at Relative Position 0
>> > ("rdisk(0)"), and it will know the other HD as the one at
>> > Relative Position 1 ("rdisk(1)"). And if the 2nd HD gets
>> > control, it will be because IT had been PUT at Relative
>> > Position 0 in the BIOS's hard drive boot order, and it will
>> > know the other HD as the one at Relative Position 1
>> > (i.e. "rdisk(1)"). So this means each partition can have
>> > the same boot.ini contents.
>> >
>> > *TimDaniels*
>> >
>>
>>
>>