Just installed Windows 7 pro 64 bit clean, full version on a brand spanking new WD SATA drive.
It seems to have lots of problems with hard drives though.
First it wouldn't instal unless I disconnected all hard drives except the destination and the DVD. Gave me format errors.
Odd thing was that I formated it on my old XP OS drive then nothing, then the big disconnect and voila.
I use a lot of music recording software, and have always used a leaner OS drive (100-250 GB) and a secondary for storage and back up (1 TB atm)
At first windows seven didn't see the other drives although bios recognized them, but the 1 TB SATA drive showed up under device manager.
After updates and who knows what, after a new start, it gave me an error message that it found a new HD, but it needed to be formatted in order to use it. This is the 1 TB SATA drive.
I also have my old IDE drives, one, an another back up and the old OS XP pro drive, that I thought I might be able to run and import emails and passwords and such from, but they only show up in Bios.
1st question, can windows 7 read and xp drive, like u used to be able to with xp, if it were a slave drive? I used to when upgrading to a bigger drive, do that and import old emails and passwords and bookmarks and so.
2nd, since I formatted the new drive with XP and installed win 7 on it with no problems, why won't it recognize my back up drive that was formatted with XP?
It may be a SATA issue? With old IDE drives you could always set master and slave and the PC knew which to run as a boot drive with OS and the other which was only data. I don't know, there is no such jumper settings.
I really hope to save some time sending everything on my big drive to an online back up service, reformat and then re-download 150G of data.
Any know if that's my only option?
I have installed xp compatibilty. Shouldn't the drive also work in XP compatibilty mode? It's just a dump drive for stuff to big for my main drive. It has no programs on it. It did however seem to be where xp chose for my recycle bin for some reason. Maybe that's something.
Would dual boot help in this situation (never tried it)
Maybe it's a raid controller issue? (also I have no idea about, or ever monkey'd with)
Thanks in advance.