Ok, last night after i posted the above, I insatlled all the newest drivers I had (on my data drive) to C drive. I am a bit worried about these as They are from 3 different sources I had to track down myself - Leadtek, Asus, and nVidia. I hope they aren't conflicting or double installing some of the drivers. Anyways, they are as follows, and I installed them in this order:
1) Chipset_64
2) nforce_6.39
3) 66.93 (nvidia corp)
4) W2K_ALL_6703 Leadtek
5) nTune 2005 v.20 (application)
At this point my internet connection was recognized, and I was able to update Windows (only a few updates neede as I have MCE 2005). Now somewhere along the line of drivers and updates, the "NTLDR" error disappeared, and all was well. I also updated BIOS from 1003 to 1004 at this point. I had installed NV firewall (I think I have to,tostall the interent drivers) but completely disabled it due to using XP firewall. As usualattempts to install my KAV failed.BIOS always asks for RAID at startup.
Anyway, this mornig I turn it on to write this message to you, and I get the original "Disk read eror" in BIOS startup. After disabling Silicon SATA controller in BIOS, it changes to an "NTLDR" error. I was only able to boot windows by using a boot disk.
Anyways:
-"Removable" was first by default, I cahnged this to CD, then HD a few minitues ago.
-I have some of D backed up on a second PC, and thats about the best I can do right now.
-I rebooted-install, as well as a few other types! I've tryed several complete format/install options!
-This NTLDR error came out of nowhere. I've been up and running for about 6 weeks. I have no partitions on either disk. The only possible causes I can think of are: installing 2 'all in one' codec packs, and then trying to uninstall them. After install, some of my other programs (SoundForge, nTune, etc) required reinstall before I could use them again, due to missing files; I turned off Silicon SATA controler in BIOS to get rid of the RAID options at startup; I had to system restore after Windows update due to disk instability about 2 weeks ago.
That's really all I can think of, besides having 2 sets of drivers installed accidentaly a long time ago, as I mentioned above.
Any idea whats going on?