Quote: Originally Posted by gregrocker
As long as you do these repairs on each HD separately with the other one unlugged, you might be able to start both of them and can do no harm. You will also find out more about the condition of the F3 which may have failed.
It is a concern that you cannot boot the Windows 7 installer or Repair CD. Have you tried burning a new one to rule out a bad installer, using USB flash instead of DVD or vice versa? I gave you a link to the latest installer and tool to burn/write.
You may need to read back over the thread a few times to study the resources you've been given more in depth, ask back any further questions to get the steps done.
I tried making a new Windows 7 installer CD, and that failed on the SSD. I also tried booting the Partition Wizard (I used the bootable CD Version) and that also failed. It goes to a black screen with a bunch of white words. The last row says:
NET: Requested protocol family 1
The dash keeps blinking, so I don't know if it's still working. Hitting "Enter" or "ESC" gets me no where, so I guess I'll let it sit for now. I'll repeat these steps for the F3 to see if it works, but not looking too good right now
[UPDATE] So I tried partition wizard on the F3, same exact sequence of events, with it loading to a black screen with a bunch of white words. Also says "NET: Requested protocol family 1". Searching that on google gave me nothing. I tried the new repair disk on the F3 as well, and still stuck on "Starting Windows" no logo. I'm going to let it stay like that overnight, see if maybe it's just taking a super long time to load or something. If it is still stuck like that tomorrow, I'll try using the Seatools utility you gave me.
It looks like my plan to use PW to wipe the hard drives and do a clean install of Windows 7 won't work since PW won't even load. I'm going to see if I can borrow a clean hard drive from a friend and install Windows there, then attempt to use Partition Wizard to see if I can salvage the SSD or the F3.