Adding IDE Drive to New System with ATA / SATA Architecture

Finally got a new system, made my buy, no problem with Vista [ Hitachi HDP725
SCSI 160GB HD ], (new drive). Added Maxtor 'OneTouch' USB 500GB external HD
for backup. I attached my Samsung SP1203N 120GB HD using a UDMA connection
cable to the primary IDE connection on the system board. The OS is WinXP Pro
SP2

When I rebooted I went to the BIOS to see the drive was recognized, and it
showed an accurate approximation of used and available space. Exited BIOS,
restarted, and came up to the "start option" for improper OS shut down /
start correctly. Restarted, and the WinXP Pro SP2 I have on the drive will
not start up.

I'm not getting a 'blue' screen. When I connect the 'old' drive with the
'new' drive up and running the Vista, my 'old' drive isn't detected. Back in
BIOS I noticed that my 'old' drive is either in the HD 1 or 2 slot and the
'new' drive is ALWAYS listed in the 3 slot. In short ... if I connect the old
drive and restart the old drive comes up first, and the OS won't start. If I
try to connect the old drive while running, detecting or adding hardware
doesnt work and the drive will not show in "my computer".

Is there a way for me to get around this problem without trying to repair /
recover the XP on the old drive and save the data? I believe a repair or
recover could ruin critical information.

Your old winxp drive is never going to boot up on your new PC - different
hardware -
Connect the old drive as slave then copy the data from it to your new Vists
drive

"Derek King" <u48459@uwe> wrote in message news:8f5bf04f8c1e4@uwe...
> Finally got a new system, made my buy, no problem with Vista [ Hitachi
> HDP725
> SCSI 160GB HD ], (new drive). Added Maxtor 'OneTouch' USB 500GB external
> HD
> for backup. I attached my Samsung SP1203N 120GB HD using a UDMA connection
> cable to the primary IDE connection on the system board. The OS is WinXP
> Pro
> SP2
>
> When I rebooted I went to the BIOS to see the drive was recognized, and it
> showed an accurate approximation of used and available space. Exited BIOS,
> restarted, and came up to the "start option" for improper OS shut down /
> start correctly. Restarted, and the WinXP Pro SP2 I have on the drive will
> not start up.
>
> I'm not getting a 'blue' screen. When I connect the 'old' drive with the
> 'new' drive up and running the Vista, my 'old' drive isn't detected. Back
> in
> BIOS I noticed that my 'old' drive is either in the HD 1 or 2 slot and the
> 'new' drive is ALWAYS listed in the 3 slot. In short ... if I connect the
> old
> drive and restart the old drive comes up first, and the OS won't start. If
> I
> try to connect the old drive while running, detecting or adding hardware
> doesnt work and the drive will not show in "my computer".
>
> Is there a way for me to get around this problem without trying to repair
> /
> recover the XP on the old drive and save the data? I believe a repair or
> recover could ruin critical information.
>

On Sun, 28 Dec 2008 23:34:21 GMT, "Derek King" <u48459@uwe> wrote:

>Finally got a new system, made my buy, no problem with Vista [ Hitachi HDP725
>SCSI 160GB HD ], (new drive). Added Maxtor 'OneTouch' USB 500GB external HD
>for backup. I attached my Samsung SP1203N 120GB HD using a UDMA connection
>cable to the primary IDE connection on the system board. The OS is WinXP Pro
>SP2
>
>When I rebooted I went to the BIOS to see the drive was recognized, and it
>showed an accurate approximation of used and available space. Exited BIOS,
>restarted, and came up to the "start option" for improper OS shut down /
>start correctly. Restarted, and the WinXP Pro SP2 I have on the drive will
>not start up.
>
>I'm not getting a 'blue' screen. When I connect the 'old' drive with the
>'new' drive up and running the Vista, my 'old' drive isn't detected. Back in
>BIOS I noticed that my 'old' drive is either in the HD 1 or 2 slot and the
>'new' drive is ALWAYS listed in the 3 slot. In short ... if I connect the old
>drive and restart the old drive comes up first, and the OS won't start. If I
>try to connect the old drive while running, detecting or adding hardware
>doesnt work and the drive will not show in "my computer".
>
>Is there a way for me to get around this problem without trying to repair /
>recover the XP on the old drive and save the data? I believe a repair or
>recover could ruin critical information.

This is strictly a BIOS problem and not related to the OS. As such,
the question is out of place here.

Ask elsewhere

your and idiot and do not deserve the MVP initials.

Derek have you changed the jumpers to designate the old drive as slave?

"Ken Blake, MVP" wrote:

> On Sun, 28 Dec 2008 23:34:21 GMT, "Derek King" <u48459@uwe> wrote:
>
> >Finally got a new system, made my buy, no problem with Vista [ Hitachi HDP725
> >SCSI 160GB HD ], (new drive). Added Maxtor 'OneTouch' USB 500GB external HD
> >for backup. I attached my Samsung SP1203N 120GB HD using a UDMA connection
> >cable to the primary IDE connection on the system board. The OS is WinXP Pro
> >SP2
> >
> >When I rebooted I went to the BIOS to see the drive was recognized, and it
> >showed an accurate approximation of used and available space. Exited BIOS,
> >restarted, and came up to the "start option" for improper OS shut down /
> >start correctly. Restarted, and the WinXP Pro SP2 I have on the drive will
> >not start up.
> >
> >I'm not getting a 'blue' screen. When I connect the 'old' drive with the
> >'new' drive up and running the Vista, my 'old' drive isn't detected. Back in
> >BIOS I noticed that my 'old' drive is either in the HD 1 or 2 slot and the
> >'new' drive is ALWAYS listed in the 3 slot. In short ... if I connect the old
> >drive and restart the old drive comes up first, and the OS won't start. If I
> >try to connect the old drive while running, detecting or adding hardware
> >doesnt work and the drive will not show in "my computer".
> >
> >Is there a way for me to get around this problem without trying to repair /
> >recover the XP on the old drive and save the data? I believe a repair or
> >recover could ruin critical information.
>
> This is strictly a BIOS problem and not related to the OS. As such,
> the question is out of place here.
>
> Ask elsewhere
>

sgopus wrote:

> your and idiot and do not deserve the MVP initials.

I see the newsgroup troll caught you. That isn't Ken Blake to whom you
responded but rather a mentally ill person who has lately decided to
impersonate Ken. The headers are clear and you've been posting in these
groups long enough to know that Ken would never respond to an OP like that.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ

yep, I see that, thanks

"Malke" wrote:

> sgopus wrote:
>
> > your and idiot and do not deserve the MVP initials.
>
> I see the newsgroup troll caught you. That isn't Ken Blake to whom you
> responded but rather a mentally ill person who has lately decided to
> impersonate Ken. The headers are clear and you've been posting in these
> groups long enough to know that Ken would never respond to an OP like that.
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers - Don't Panic!
> FAQ - http://www.elephantboycomputers.com/#FAQ
>
>

On Tue, 30 Dec 2008 04:54:56 -0800, Malke <malke@invalid.invalid>
wrote:

>sgopus wrote:
>
>> your and idiot and do not deserve the MVP initials.
>
>I see the newsgroup troll caught you. That isn't Ken Blake to whom you
>responded but rather a mentally ill person who has lately decided to
>impersonate Ken. The headers are clear and you've been posting in these
>groups long enough to know that Ken would never respond to an OP like that.
>
>Malke

Yes I would. Malke just didn't get the memo that MVPs are no longer
to coddle questions that are stupid or placed in the incorrect
newsgroups...or both.

This is not Ken Blake MVP posting but an imposter

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Ken Blake, MVP" <Ken@blakeMVP.net> wrote in message
news:lupll453e24ag14ori1j07gfmvt5tc6f3j@4ax.com...
> On Tue, 30 Dec 2008 04:54:56 -0800, Malke <malke@invalid.invalid>
> wrote:
>
>>sgopus wrote:
>>
>>> your and idiot and do not deserve the MVP initials.
>>
>>I see the newsgroup troll caught you. That isn't Ken Blake to whom you
>>responded but rather a mentally ill person who has lately decided to
>>impersonate Ken. The headers are clear and you've been posting in these
>>groups long enough to know that Ken would never respond to an OP like that.
>>
>>Malke
>
> Yes I would. Malke just didn't get the memo that MVPs are no longer
> to coddle questions that are stupid or placed in the incorrect
> newsgroups...or both.

"Ken Blake, MVP" <Ken@blakeMVP.net> wrote in message
news:lupll453e24ag14ori1j07gfmvt5tc6f3j@4ax.com...
> On Tue, 30 Dec 2008 04:54:56 -0800, Malke <malke@invalid.invalid>
> wrote:
>
>>sgopus wrote:
>>
>>> your and idiot and do not deserve the MVP initials.
>>
>>I see the newsgroup troll caught you. That isn't Ken Blake to whom you
>>responded but rather a mentally ill person who has lately decided to
>>impersonate Ken. The headers are clear and you've been posting in these
>>groups long enough to know that Ken would never respond to an OP like
>>that.
>>
>>Malke
>
> Yes I would. Malke just didn't get the memo that MVPs are no longer
> to coddle questions that are stupid or placed in the incorrect
> newsgroups...or both.

You just added to the evidence that you are not an MVP, let alone Ken. MVPs
do not work in a common office where memos are normally passed. They are
independent volunteers that passed testing by MS for the MVP moniker. Ken
also uses a signature, whereas, you did not.

You are entitled to your opinions regarding subject matter. You are not
entitled to masquerade and attempt to impersonate a person or persons that
normally provide valuable input in this and other MS newsgroups.
--
Dave

First, let me apologize to everyone who has been kind enough to reply. I
thought I had gave enough information in the question but it seems I didn't.

So to be clear ... I have tried setting the jumper to slave and cable select
with no change. I also went into the BIOS and ensured the drive was being
noticed, I also "attempted" to change the boot order. I say attempted because
the bios would only list the 'new' vista drive, so I couldn't change the
order.

Something else I tried to explain was that NO MATTER THE BOOT ORDER, my 'old'
XP drive "insists" on being recognized / booted to first. I still believe
this is just due to the architecture. Again, since I'm connecting my old
drive to the "primary IDE" on the motherboard I think it just IS.

Lastly, I wouldn't care about which order or anything IF I could just get the
drive to start, but most opinions here seem to think, 'old drive, new system,
won't work'. The drive I'm working with is less than 2 years old and was XP
SP2. Is eveyone telling me that ATA/SATA is so far above IDE that I can't
simply attach a drive and "GO"?

--
Message posted via WindowsKB.com
http://www.windowskb.com/Uwe/Forums....dware/200901/1

"Derek King" <u48459@uwe> wrote in message news:8f5bf04f8c1e4@uwe...
> Finally got a new system, made my buy, no problem with Vista [ Hitachi
> HDP725
> SCSI 160GB HD ], (new drive). Added Maxtor 'OneTouch' USB 500GB external
> HD
> for backup. I attached my Samsung SP1203N 120GB HD using a UDMA connection
> cable to the primary IDE connection on the system board. The OS is WinXP
> Pro
> SP2
>
> When I rebooted I went to the BIOS to see the drive was recognized, and it
> showed an accurate approximation of used and available space. Exited BIOS,
> restarted, and came up to the "start option" for improper OS shut down /
> start correctly. Restarted, and the WinXP Pro SP2 I have on the drive will
> not start up.
>
> I'm not getting a 'blue' screen. When I connect the 'old' drive with the
> 'new' drive up and running the Vista, my 'old' drive isn't detected. Back
> in
> BIOS I noticed that my 'old' drive is either in the HD 1 or 2 slot and the
> 'new' drive is ALWAYS listed in the 3 slot. In short ... if I connect the
> old
> drive and restart the old drive comes up first, and the OS won't start. If
> I
> try to connect the old drive while running, detecting or adding hardware
> doesnt work and the drive will not show in "my computer".
>
> Is there a way for me to get around this problem without trying to repair
> /
> recover the XP on the old drive and save the data? I believe a repair or
> recover could ruin critical information.


Derek later adds...
> First, let me apologize to everyone who has been kind enough to reply. I
> thought I had gave enough information in the question but it seems I
> didn't.
>
> So to be clear ... I have tried setting the jumper to slave and cable
> select
> with no change. I also went into the BIOS and ensured the drive was being
> noticed, I also "attempted" to change the boot order. I say attempted
> because
> the bios would only list the 'new' vista drive, so I couldn't change the
> order.
>
> Something else I tried to explain was that NO MATTER THE BOOT ORDER, my
> 'old'
> XP drive "insists" on being recognized / booted to first. I still believe
> this is just due to the architecture. Again, since I'm connecting my old
> drive to the "primary IDE" on the motherboard I think it just IS.
>
> Lastly, I wouldn't care about which order or anything IF I could just get
> the
> drive to start, but most opinions here seem to think, 'old drive, new
> system,
> won't work'. The drive I'm working with is less than 2 years old and was
> XP
> SP2. Is eveyone telling me that ATA/SATA is so far above IDE that I can't
> simply attach a drive and "GO"?
>
> --
> Message posted via WindowsKB.com
> http://www.windowskb.com/Uwe/Forums....dware/200901/1


Derek:
It might be because in your original post you referred to the new HDD as a
SCSI HDD, to wit...
"...made my buy, no problem with Vista [ Hitachi HDP725 SCSI 160GB HD ],
(new drive)." And you also made reference to "running the Vista", so that
was a bit confusing in that some might think you were referring to that OS.
But you were actually referring to that Hitachi HDD, right? Apparently it's
been given that label by the manufacturer?

In any event, it's a HDD that I'm not familiar with. But you've clarified
that it's actually a SATA HDD, right?

I'm really not clear on your configuration. Are you indicating that you've
installed the XP OS onto the Hitachi HDD and you want that drive to serve as
your boot disk? So that the Samsung 120 GB PATA HDD will be a secondary HDD
in the system (even though it apparently contains a bootable OS)? Do I have
this right?

If my understanding is correct, if you boot to the Hitachi SATA HDD with the
Samsung PATA HDD disconnected from the system, does the system boot without
incident and properly function?

And conversely, if you boot to the Samsung with the Hitachi disconnected, no
problem there as well?

In your response (if you do respond to this), please do not refer to HDD
connections related to "slots". Tell us precisely how the SATA HDD has been
connected to this or that motherboard's SATA connector and precisely how
your PATA HDD has been connected to an IDE channel. And it would be helpful
if we knew the make/model of your motherboard.

We're also assuming here that your motherboard has built-in support for SATA
controller driver capability (or that you've installed an auxiliary SATA
controller driver if such was necessary) so that there's no issue re SATA
HDD recognition by the BIOS.

And you've checked your BIOS settings - specifically the boot priority
order - as well as any related settings to ensure there's no problem on that
end, right?

In any event, I may be misunderstanding your present configuration let alone
your precise objective(s) so please clarify if need be.
Anna