[toothless420]

ok so the result are in the drive work perfect it was already in my computer no jumper no align no nothing when windows booted just had to format it and i transferred 50g of data back and forth without any problem
back on this windows still cant see it
so alzeimer was right the drive is good , windows is the issue

next up is what make it not work

[Advertisements]

Thanks for the update.
I sugeested the test to see if the OS on the C drive could see the D drive (without any possible complications introduced by another OS)
Going off line for a while, but please supply info for the others to see,
You installed XP (including SP3) to the D drive?
Was the C drive connected or disconnect?
When booting into the C drive, the D drive does not show?
When booting into the D drive, does the C drive show in disk management?

What is the brand and model of your MB and the BIOS version?

In the BOIS, SATA controllers, can the ports be set indiviually?
If C drive is on SATA 1, how is it configured, Auto, IDE, SATA, AHCI?
if D drive is on SATA 2, how is it configured?

[iammykyl]

Thanks for the update.
I sugeested the test to see if the OS on the C drive could see the D drive (without any possible complications introduced by another OS)
Going off line for a while, but please supply info for the others to see,
You installed XP (including SP3) to the D drive?
Was the C drive connected or disconnect?
When booting into the C drive, the D drive does not show?
When booting into the D drive, does the C drive show in disk management?

What is the brand and model of your MB and the BIOS version?

In the BOIS, SATA controllers, can the ports be set indiviually?
If C drive is on SATA 1, how is it configured, Auto, IDE, SATA, AHCI?
if D drive is on SATA 2, how is it configured?

[toothless420]

well a fresh off the cd windows see the new drive when a sp3 cannot
everything else is the same every bios setting even the sata and power wire are the same beside the hdd containing the windows itself and of coarse the window to as its fresh of the cd (first edition no update no nothing )
but the only diference is windows was installed with both hdd pluged as well on the current setup windows is already installed so didnt have to install it
so i doubt the bios or the sata controller can have anything to play in this
but here is the info

mb is msi k9n6pgm2-v2

bios version is american megatrends ic v10.6 smbios 2.6

both sata are on ide both hdd containing windows where put on the sata 1 and the new hdd always been on sata 2

im tempted with formatting and trying to install windows again i guess it would clear up some possible issue il have to make sure to save all the important data and stuff

so if anyone has a suggestion on what to try in the mean time

Edited by toothless420, 28 June 2013 - 11:58 AM.

[toothless420]

well fresh new install and hdd is seen and working like a charm

will see if it still work after windows is all back to sp3 but i dont think it will be an issue

thanks for the help guys

[rshaffer61]

Strange issue but glad everyone was able to help.

[Alzeimer]

well fresh new install and hdd is seen and working like a charm

will see if it still work after windows is all back to sp3 but i dont think it will be an issue

thanks for the help guys

Happy your back on track, good computing

[rshaffer61]

Thanks to everyone who assisted and great teamwork!!!!

[toothless420]

i found the culprit of the problem it is my motherboard nvidia nfore ide/ata driver that replace windows IDE/ata driver by its own i just lost the hdd again after installing the driver so wouldn't even have needed to format at all

now just need to find how to remove it and put the old one back in

Edited by toothless420, 29 June 2013 - 08:31 PM.

[rshaffer61]

I believe if you go to Device Manager and expand the Controllers entry you can then right click on the main controller and then tell it to rollback the driver.

[toothless420]

yep was gonna say i just rolled back the driver and hdd is back in my computer
so that was the culprit all this time!!!

you might want to remember this it could save someone else allot of time!

[rshaffer61]

you might want to remember this it could save someone else allot of time!

This is why we don't close topics in this part of the site. That way if someone has the same problem they can find this topic and see how the issue was finally resolved.

[iammykyl]

Good result.
I would never have suspected a graphics driver causing the problem. One to remember, for sure.