Trouble migrating an IDE drive to SATA mobo

I was trying to figure out the best way to move files from my old PIII XP PRO desktop to my new Quad 7 box but then decided why not just move the drive over. (didn't remember that I might have used Windows Easy Transfer!)

The new Windows 7 64bit sata machine already had a 300gb sata drive as primary so I thought the 120 coming from the old computer might make a good storage partner/backup. (It might be better if they were the other way around....with the 300 as the 'backup'....but, so be it.

I bought an IDE to SATA adaptor to connect the old IDE drive to the sata mobo.
It seemed to work initially, although somewhat "sketchily"; the computer was slow to boot but I did eventually have both drives running OK and was able to access all files on both and see them both on my workgroup.

After a couple of shutdowns and restarts, though, the machine got increasingly slow/difficult to boot (sometimes only coming to life if I hit the spacebar on my keyboard (weird!)......then after three or four of these wonky boots, it wouldn't boot at all. I removed the added drive and after many shutdowns and restarts, the box finally started windows 7, but I swear it played the XP sign-on/splash screen music! At that point I realized/remembered that the XP Pro OS was still on the old drive....and now I see in another thread, that IDE drives somehow "overrule" sata drives. Ooops.

I think my Master Boot Record is botched up. (Booting takes longer than it did before.....and I swear the "login music" is wrong!) I don't even see a BIOS prompt when booting now; the computer goes from blackscreen to windows splash screen....no "F12 or F2" visible anywhere.

So, here are the questions:
1. Should I keep this drive? (I've invested in the adaptor and I'd hate to scrap both)
2. Can I hot-mount the old drive (connect it while the pc is running) so I don't risk another 'spooky' boot?
3. Is there a special setting for the jumpers on this 2nd drive...or are they different depending on the brand?
4. How do I get my BIOS prompt back...and what do I do once I get into it? (assuming I can.)

Complicating any rescue efforts is the fact that my Windows 7 disk is one of the popular (read: CHEAP) OEM versions that I don't believe provides all the REPAIR utilities that come with the full-blown copies. Any suggestions for fixing up my boot process OTHER than a full re-install? (I'm lazy...like most humans...and HATE the thought of all that backing up and reloading!)

Thanks a bunch for any and all tips/tricks/suggestions.

Ivan the SoSo said:

hit f8 during boot up....go to advanced boot options....repair your computer...press "enter"...startup repair

Thanks for getting back, Ivan.

I'm familiar with the process....unfortunately, I don't get a BIOS prompt on my screen, so I don't know when to hit F8. If I do it at the "wrong" time (which apparently is any time I do it...before, during or after the lights coming on/going off etc)....the computer just sits there with a black screen and never boots.

Here's what happens.....(and it does pretty much the same thing, whether starting from OFF or RESTART)
I hit the start button (or click on restart)
Everything is black
After about 10 seconds the NumLok light on my keyboard comes on and stays on
The drives/fans continue to run for about 30 seconds (screen black all this time)
Then the other two lights on the keyboard (Caps Lock & Scroll Lock) come on for 1 sec.
Then ALL lights go off for about ten seconds
Then the NumLok light comes back on briefly then goes off, and right after that, Windows 7 splash screen comes up and the program launches.

At no time is there a prompt or any text on screen referring to BIOS or any F keys.

Is there any way of knowing EXACTLY when to hit F8?

Or is this not likely a procedure that's going to work for me, given my description of the visual clues I'm (not) getting? (Is there any OTHER way to get into BIOS besides the "boot interruption" technique?

Thanks again to ANYONE who has any tips.

Mike

I'm not questioning your approach, but I'm also not sure I understand what you're getting at with that process? (AND I don't have any other video cards!)

In the meantime, I attempted to create a partition on my drive using Easeus (apparently the new alternative for Partition Magic) so that I could possibly reinstall Win 7 from scratch onto the new partition, without trashing my data files.

Seems I've really screwed things up now; now I'm not able to boot AT ALL; neither from the hard drive nor the CD with my disk in it. I was not able to boot from the CD previously anyway, but now the hard drive is equally non-responsive. This is not looking good.

Hellllllllppppppppppppp!

Ah......now that makes sense.

Unfortunately, as I mentioned above......I seem to have bigger/different problems now: after trying that partitioning exercise, I don't hear anything coming from the drive other than a steady hum. (No thudding and whining as you usually would during bootup.)

Any thoughts as to where I go from here? (Please don't say the computer shop......I HATE the thought that I wouldn't be able to get outta this jam with your help!)

Thanks,
Mike

Ivan the SoSo said:

Monitors and video cards have two modes....alphanumeric for the BIOS, and graphic for windows...the on screen monitor menu is alphanumeric, so if it works its not the monitor.....

Your spec show dual video cards if one can show the BIOS screen then one card is bad....possibly cable if neither shows video....

If the motherboard has built in graphics but can't show the BIOS screen....possible cable/bad motherboard/power supply issues

I'm virtually positive it isn't anything wrong with the monitor or it's cable. The monitor does display the Digital/Analog square that comes up in the corner of the screen....just as it always does......and if I push the menu buttons on the monitor's control panel I do get the message floating across the screen advising me to check the cable because it's getting no signal.

(I feel) It has to be something related to the BIOS, boot sector or the drive. The drive just isn't "bumping and grinding" the way a drive does when it boots.....and IT'S the only thing I've really messed around with by doing the partitioning thing. I very much doubt that anything has coincidentally gone 'wrong' with the video cards or motherboard at the same time.

Plus, I have no way of checking these things if my drive isn't reading properly.

How about just putting in a new, virgin drive? I don't have one on hand, but I'm thinking about buying one anyway (a 500).....and if that would get this thing booting....I'll do it.