PC Review
Forums
Newsgroups
Windows Vista
Windows Vista Performance
Hard Disk problem
Forums
Newsgroups
Windows Vista
Windows Vista Performance
Hard Disk problem
![]() |
Hard Disk problem |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
The last few times I've booted up I have been unable to write to my D drive.
I get the message "this drive may be full or write protected". If I re-boot everything is ok. I've been running this computer for about 6 weeks now and this has only started happening over the last 2 days. I'm running Vista Ultimate 64 bit. Anyone have any idea what is causing this problem? Many thanks. |
|
|
|
#2 |
|
Guest
Posts: n/a
|
What's on D? Is is possible it's one of those small "recovery" partitions that a lot of the big-name manufacturers seem to like to put on machines? How big is D? And is it physically another drive, or is it just a partition? "Andy Webb" <AndyWebb@discussions.microsoft.com> wrote in message news:BDF12F5A-F48A-4963-A391-619D9D1F6BAB@microsoft.com... > The last few times I've booted up I have been unable to write to my D > drive. > > I get the message "this drive may be full or write protected". > > If I re-boot everything is ok. > > I've been running this computer for about 6 weeks now and this has only > started happening over the last 2 days. > > I'm running Vista Ultimate 64 bit. > > Anyone have any idea what is causing this problem? > > Many thanks. |
|
|
|
#3 |
|
Guest
Posts: n/a
|
No, its a physical drive of 160Gb.
Nothing special about it, worked fine for six weeks. I ran RegSupreme Pro registry cleaner yesterday and today it booted fine. So whether that's solved it I'll just have to wait and see. |
|
|
|
#4 |
|
Guest
Posts: n/a
|
"Andy Webb" <AndyWebb@discussions.microsoft.com> wrote
> No, its a physical drive of 160Gb. > > Nothing special about it, worked fine for six weeks. > > I ran RegSupreme Pro registry cleaner yesterday and today it booted fine. > > So whether that's solved it I'll just have to wait and see. Hmm, watch out for unexplained problems cropping up from nowhere. Registry cleaners, though they don't cause a problem every time, generally cause more problems than they fix. Sometimes those problems don't surface right away either. If it removes a needed entry but you don't access that feature until some time down the line, then it won't show up until later when that feature is invoked, and it can be hard to track back to what caused it. In my opinion the only safe way to use a registry cleaner is in the hands of an experienced user, who uses it only for suggestions on what to remove, but does not let it do any automatic cleaning. -- Rock [MS-MVP User/Shell] |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

