PC Review


Reply
Thread Tools Rate Thread

A 2 XP system on 2 separate disks -> boot problem

 
 
Igal.Hunter@gmail.com
Guest
Posts: n/a
 
      10th Jul 2006
Hi All!

I got this strange oroblem that kinda caught me offguard.
I used to have 2 HDs on my PC, 1st the boot (Pimary master, let's call
it "Alfa") and 2nd dump (Primary slave let it be "Betta").
At some point my boot HD (Alfa) was being fixed and I got another HD
(call it "Gamma") on which I installed another copy of XP thus having a
configuration of 1 boot HD "Gamma" (SATA 1) and the dump HD
"Betta"(primary slave). Everything worked just fine.
Now my old Alfa HD got back from the fix and offcause I naively
installed it, planning to use the Gamma HD as a primary boot (it's
larger and faster), however, strangely enough now my system recognizes
only my old Alfa HD as a OS and disregards the newer XP install on the
Gamma HD (the drive is there, it's assigned letter H).
What I'd like to have is to run my new Gamma HD (SATA1) as an only OS,
and turn the old Alfa boot (primary master) to another dump drive.

My best guess is that it has something to do with the boot.ini (on
which of the 3 physical dives I wonder...)

Currently I'm running my old OS, and my boot.ini files look like this
(why I say files... wait and see):
The one that is on C:\ (Which corresponds to Alfa when alfa is booted))
looks like 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" /fastdetect /NoExecute=OptIn

And the one I see (when Alfa is booted)) through system->start up
(which is for some reason on drive d:, my Betta dump drive, not the old
boot drive) looks like this:
[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
Professional - SATA" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect

Gamma drive has no boot.ini on it, even though I installed the copy of
XP on it.

You can see the confusion here. 2 separate boot.ini files (kill me if I
know which one the system uses... during the start up the one located
on D "Betta" seems to pop, but it's second option - the one not marked
SATA points to nowhere... nothing's there, and the 1st option still
points to the Alfa boot device.

All this is a bit confusing, so I home that someone can pinpoint the
general idea in here and maybe give me some good advice how to fix all
this.

If any info is missing - please tell.

Thank you.

 
Reply With Quote
 
 
 
 
=?Utf-8?B?SmFzb24=?=
Guest
Posts: n/a
 
      12th Jul 2006
Hi
I think the first place for you to look is going to be the system bios,
press delete on boot(sometimes another key) to access the bios.
depending on the bios you will be looking for the initial boot device menu
and making sure the bios chooses sata over ide as the boot device.

Good luck on this

Jason

"(E-Mail Removed)" wrote:

> Hi All!
>
> I got this strange oroblem that kinda caught me offguard.
> I used to have 2 HDs on my PC, 1st the boot (Pimary master, let's call
> it "Alfa") and 2nd dump (Primary slave let it be "Betta").
> At some point my boot HD (Alfa) was being fixed and I got another HD
> (call it "Gamma") on which I installed another copy of XP thus having a
> configuration of 1 boot HD "Gamma" (SATA 1) and the dump HD
> "Betta"(primary slave). Everything worked just fine.
> Now my old Alfa HD got back from the fix and offcause I naively
> installed it, planning to use the Gamma HD as a primary boot (it's
> larger and faster), however, strangely enough now my system recognizes
> only my old Alfa HD as a OS and disregards the newer XP install on the
> Gamma HD (the drive is there, it's assigned letter H).
> What I'd like to have is to run my new Gamma HD (SATA1) as an only OS,
> and turn the old Alfa boot (primary master) to another dump drive.
>
> My best guess is that it has something to do with the boot.ini (on
> which of the 3 physical dives I wonder...)
>
> Currently I'm running my old OS, and my boot.ini files look like this
> (why I say files... wait and see):
> The one that is on C:\ (Which corresponds to Alfa when alfa is booted))
> looks like 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" /fastdetect /NoExecute=OptIn
>
> And the one I see (when Alfa is booted)) through system->start up
> (which is for some reason on drive d:, my Betta dump drive, not the old
> boot drive) looks like this:
> [boot loader]
> timeout=15
> default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
> Professional - SATA" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
> Professional" /fastdetect
>
> Gamma drive has no boot.ini on it, even though I installed the copy of
> XP on it.
>
> You can see the confusion here. 2 separate boot.ini files (kill me if I
> know which one the system uses... during the start up the one located
> on D "Betta" seems to pop, but it's second option - the one not marked
> SATA points to nowhere... nothing's there, and the 1st option still
> points to the Alfa boot device.
>
> All this is a bit confusing, so I home that someone can pinpoint the
> general idea in here and maybe give me some good advice how to fix all
> this.
>
> If any info is missing - please tell.
>
> Thank you.
>
>

 
Reply With Quote
 
Igal.Hunter@gmail.com
Guest
Posts: n/a
 
      13th Jul 2006
Well in BIOS the SATA is a preferred drive...

 
Reply With Quote
 
Andy
Guest
Posts: n/a
 
      14th Jul 2006
On 10 Jul 2006 13:57:10 -0700, (E-Mail Removed) wrote:

>Hi All!
>
>I got this strange oroblem that kinda caught me offguard.
>I used to have 2 HDs on my PC, 1st the boot (Pimary master, let's call
>it "Alfa") and 2nd dump (Primary slave let it be "Betta").
>At some point my boot HD (Alfa) was being fixed and I got another HD
>(call it "Gamma") on which I installed another copy of XP thus having a
>configuration of 1 boot HD "Gamma" (SATA 1) and the dump HD
>"Betta"(primary slave). Everything worked just fine.
>Now my old Alfa HD got back from the fix and offcause I naively
>installed it, planning to use the Gamma HD as a primary boot (it's
>larger and faster), however, strangely enough now my system recognizes
>only my old Alfa HD as a OS and disregards the newer XP install on the
>Gamma HD (the drive is there, it's assigned letter H).
>What I'd like to have is to run my new Gamma HD (SATA1) as an only OS,
>and turn the old Alfa boot (primary master) to another dump drive.


>
>My best guess is that it has something to do with the boot.ini (on
>which of the 3 physical dives I wonder...)
>
>Currently I'm running my old OS, and my boot.ini files look like this
>(why I say files... wait and see):
>The one that is on C:\ (Which corresponds to Alfa when alfa is booted))
>looks like 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" /fastdetect /NoExecute=OptIn
>
>And the one I see (when Alfa is booted)) through system->start up
>(which is for some reason on drive d:, my Betta dump drive, not the old
>boot drive) looks like this:
>[boot loader]
>timeout=15
>default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
>[operating systems]
>multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP
>Professional - SATA" /fastdetect /NoExecute=OptIn
>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
>Professional" /fastdetect
>
>Gamma drive has no boot.ini on it, even though I installed the copy of
>XP on it.


Windows XP setup places the boot files in the active primary partition
on the disk that the BIOS is set to boot from. Since the boot files
ended up on the IDE disk, either the SATA disk was not set as first
under hard disk boot priority in BIOS setup, or the BIOS is unable to
designate the SATA disk as the first disk if an IDE disk is also
connected.

>
>You can see the confusion here. 2 separate boot.ini files (kill me if I
>know which one the system uses... during the start up the one located
>on D "Betta" seems to pop, but it's second option - the one not marked
>SATA points to nowhere... nothing's there, and the 1st option still
>points to the Alfa boot device.
>
>All this is a bit confusing, so I home that someone can pinpoint the
>general idea in here and maybe give me some good advice how to fix all
>this.
>
>If any info is missing - please tell.


What motherboard are you using?

>
>Thank you.


 
Reply With Quote
 
Igal.Hunter@gmail.com
Guest
Posts: n/a
 
      16th Jul 2006
Gigabyte,
WEll, nm I got it all fixed, just changed the boot.ini manually (added
2 more disks and found out which one boots what the deleted the
dummies). Thanks anyway.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Dual Boot: XP Pro and Win98SE on separate disks FACE Windows XP General 3 27th Sep 2006 06:47 PM
Separate System and Data disks - performance gain? deko Windows XP Hardware 2 12th Sep 2005 12:42 AM
System boot from floppy disks Adriana Windows XP Setup 3 25th Nov 2003 10:48 PM
Need help with Win2k/WinMe dual boot on separate disks Beowulf Microsoft Windows 2000 1 25th Sep 2003 12:30 AM
Need help with Win2k/WinMe dual boot on separate disks Beowulf Microsoft Windows 2000 Setup 0 24th Sep 2003 04:00 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 01:19 PM.