Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Well, It's finally happened to me! When my computer boots up it can't detect the c-drive. I've been seeing more and more posts about this bug in XP. What did ya expect ?

What happens is on boot up my computer fails to recognize the c-drive and it says to hit F4 to continue. I shut off my computer and restart and everything is okay. It's like it's not seeing the c-drive. No failures, it just can't detect the c-drive.

Goes into your bios (hit delete on boot up) and see if the bios is detecting the HDD. Since I don't have your system specs, I can't tell you what to check beyond that. Is this a new drive? Are the cables connected properly? Please post your system specs if you want further help! Thanks,
Tony

It's a P3 1Ghz machine. Since this is very sporadic, when I do go into the bios after it
doesn't detect the drive, the bios shows it as being there. After I exit the bios it's ok
and it might not happen again for many days.
Weird.

I usually leave XP running and rarely shut down the computer.. But the times i do shut it down every time i turn it on i get an error.
I see it every day but i cant remember what it is something about insert boot disk or invalid something.
I just hit the power button then back on and XP loads like it should. I thought it might be because i have an ata100 HD and my motherboard only supports ata66. Or because i moved my hardware into a new case with a p4 rated power supply. Tell the truth i have no idea what the problem is here.
Is this similar to the error your having Mr.No Drive?

Same issue here,I chalked it up to the dual boot thing.On a "hard" shutdown it will not find the "D" drive on reboot(where XP is located).A complete restart and all is fine again.
I dunno...
Jimi_l

I believe XP has serious bugs, I have the problem where, my CD drives will throw up a CRC error. When I disable DMA the drives are very slow, but work, XP has a problem, it seems with IDE and DMA. I dual boot with ME and this problem doe's not occur in ME.
I would have thought microsoft tested for these type of bugs, as IDE drives are quite important :)

Jimi, i thought about that too. So i installed XP on a master drive by itself early on. The problem still occurs.
This post got me curious so tonight i installed XP on an formatted ata66 HD and used the correct ide cables. The problem still occurs. Im using a hardware device to seperate 3 master HD's Trios hardrive selector. Nothing is showing up in any of the error logs. Im lost :)The only thing i can think of on my end now is the fact that im running the HD thru this device. Others having the same error kind of rules out the trios device ( i hope ).
Going to search the mskb and see what i can dig up if anything.

i had the same problem try this fix it fixed mine without a problem
Use regedit to remove the keys named UpperFilter and LowerFilter from:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
just make sure it acrually says in the value in registry cd dvd rom drives

all i know is that when i tried to install xp, it would not recognise my drives. the problem i found was lying with my motherboard. it has 2 bios 1 for ide drives and one for the highpoint hpt66 udma. once i bypassed this and just used udma 33 on the normal ide bios hey presto there my drive was. i believe there is an issue with xp that it does not recognise hpt66.

There clearly is a problem, but it is NOT a "bug" in XP. And remember, it's not just Microsoft who checks these things before a product is released. XP (Whistler) has been tested and re-tested and re-tested by countless beta testers all over the world who provided input into the product before it's final release. A problem with reading a drive would not have slipped by.
Good luck.
writerranger

well after fooling around with cables and such last night i havent been able to get it to happen again. Fingers crossed!

Listen here, It's not the beta testers responsibility to verify the code. It's up to Microsoft and whoever is getting paid to validate the code.

Listen Up:
You misunderstood. I was saying that a problem as clear as not seeing the C drive would not have slipped by all the beta testers AND Microsoft. I didn't say it was the beta testers responsibility. They signed up to participate and offer the feedback and I was simply saying something like this would not have slipped by so many beta testers AND M$FT if it was a "bug"....

![]() |
XP removal
|
ie 6.0 text size keeps ch...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |