This I posted to another member but I think it applies to us all. Seriously, don't take it the wrong way, but, and it's just a suggestion, you might want to find out a little more information about what members are having problems with, and the specifics of the problem, before you offer quick, uninformed answers. I mean, most of these people genuinely want help. They don't want to be made feel stupid when they have a legitimate problem. As I posted in a certain reply that you had answered, I am having the same problem as another member, and it's not due to an inherent problem with the hardware, it's due to SP2. I'm sure you didn't mean to be as short as you were but in the future, if you answer a post, really, try to offer something helpfull. Don't instantly assume that people who post don't know anything or are stupid. The fact is, I've been working with systems since the VIC20, which if you even know what that is, you'll know that's been quite some time. And I'm stumpted with this same problem too. Now, maybe you've encountered this problem and know a work around for it, I can't find one or any usefull info on it but the fact remains that some drives fail to be PROPERLY recognized after installing SP2. In case you don't get the reply from the thread, I'll give you the opportunity to know the details, and they are almost exactly the same as the post left by the person you replied to. The long and short of it is this. BIOS recognizes the drive. Device manager does too. Windows shell, explorer etc, does not. The drive is partitioned, and formatted in NT format. If I pull the drive and put it in a non SP2 system it works just fine. And, it was working just fine before I installed SP2, which I had been holding off on installing for quite some time for the very fact that microsoft service packs often create as many problems as they fix. Anyhow, enough of scolding you. Honestly, if you know something we don't, please, be the bigger geek and let us know in an appropriate manner. Otherwise, consider yourself scolded, and in the future, just try to find out, or at least ask for, a little more information before you insult somebody who has an honest question. Again, I'm not trying to accuse you of anything, just asking that you think about what I've said. And, when you come up with a work around, please do let us know because as of right now, microsoft says they do not know what the problem is, but they recognize that there is one. Take care and keep on keeping on.