- Windows XP with SP2 does not detect my Hard drive
- Posted by Pokemon on October 21st, 2005
I have an 80G seagate hard drive partitioned into c: and d: with 40 G each. I
have a 1.7G seagate and assigned a drive e:. When I power up my machine, the
bios detects that there are 2 hard drives connected. But when I open up the
Window explorer, I can only see C: and D: My E: drive is not being detected.
I have to either do a 'Add hardware' or in device manager to scan the
hardware before it shows up in my Wondow explorer.
Any reason why? and how to fix it up.
Thanks.
- Posted by Jerry on October 21st, 2005
A 1.7Gb harddrive? Really?
"Pokemon" <Pokemon@discussions.microsoft.com> wrote in message
news:80340125-6BDF-40FE-851D-477733693189@microsoft.com...
>I have an 80G seagate hard drive partitioned into c: and d: with 40 G each.
>I
> have a 1.7G seagate and assigned a drive e:. When I power up my machine,
> the
> bios detects that there are 2 hard drives connected. But when I open up
> the
> Window explorer, I can only see C: and D: My E: drive is not being
> detected.
> I have to either do a 'Add hardware' or in device manager to scan the
> hardware before it shows up in my Wondow explorer.
>
> Any reason why? and how to fix it up.
>
> Thanks.
>
- Posted by Triffid on October 21st, 2005
Jerry wrote:
> A 1.7Gb harddrive? Really?
Sure.
The smallest HD I have in my collection is 340MB. It still works - even
on a modern motherboard IDE interface.
Triffid
> "Pokemon" <Pokemon@discussions.microsoft.com> wrote in message
> news:80340125-6BDF-40FE-851D-477733693189@microsoft.com...
>
>>I have an 80G seagate hard drive partitioned into c: and d: with 40 G each.
>>I
>>have a 1.7G seagate and assigned a drive e:. When I power up my machine,
>>the
>>bios detects that there are 2 hard drives connected. But when I open up
>>the
>>Window explorer, I can only see C: and D: My E: drive is not being
>>detected.
>>I have to either do a 'Add hardware' or in device manager to scan the
>>hardware before it shows up in my Wondow explorer.
>>
>>Any reason why? and how to fix it up.
>>
>>Thanks.
>>
>
>
>