I have a P4 3.0GB with 1GB of DDR, ASUS P4P800-E mobo, with W2K Pro with SP4 and all the latest UPDATES, also BIOS up to 1007 from ASUS. This computer has been operating great with a WD 120 GB S-ATA hard drive on S-ATA 0 with 4 partitions since about January of this year. I bought a 200GB S-ATA Western Digital hard drive and installed it on S-ATA 1 with 2 partitions of almost equal size. Upon booting up W2K found the hard drive and made a change to the registry and told me to reboot, which I did. After reboot, I can see the partitions from DISK MANAGEMENT and LOGICAL DRIVES under Computer Management. Both partitions were formatted within disk management and everything appeared to be OK. I created a NEW share for each partition to be seen on my network. Here is the problem(s). I can see both drives, all the partitions, a total of 6, 4 to D1 and 2 to D2, in DISK MANAGEMENT and LOGICAL DRIVES, also with Symantec Systemworks 2005 Disk Doctor, W2K disk defragmenter, in the BIOS on startup, across the network as the "SHARES" I setup and even in "My Network Places" in "Windows Explorer" and "My Computer", but NOT as LOCAL drives and partitions in either of these two environments. I can transfer local and network files to this drive and/or partitions ONLY if I use the designated "SHARES". I am really confused on this one. By the way. the file "atapi.sys" is the correct version for W2K. There are 2 DVD burner/CD burners installed on the 2nd IDE channel. Nothing else is installed on the IDE connections. I have even "booted" to Western Digital's partition copy on a floppy, copied the boot partition from D1 P1 to D2 P1, shutdown and swapped the S-ATA cables, and "BOOTED" to the new 200 GB drive and confirmed that it had booted from it as drive "J", and still could not see it other than described above. All drives are formatted in NTFS and sizes reported accurately, and D1 P1 is reported as SYSTEM and D2 P1 is ACTIVE, all healthy. Other than this the computer is running great, no crashes ever, the registry has the correct entry as MS has described in it's bulletin. Have also tried the 32 bit on and off in the BIOS. Go figure! Any help would be very much appreciated.