For some reason, my responses to the last group of questions got lost in
cyberspace, so let's start from scratch. Below I've included my original
message, the response from Daave, my response to him, the response from Ed Y,
my response to him, Daave's second response, and my response to him. No
offense Rock, but you basically asked the same questions as Daave did on his
second message.
ORIGINAL MESSAGE:
Back when I purchased my first computer with Windows 98 SE, 3 or 4
times a week I would get an error message when I tried to move, rename,
or delete a file that informed me that I could not do the above
function because someone else was using the file. No one else had ever
touched that computer but the people who built it and shipped it to me.
So no one else could have been using those files.
Now with my new computer and the installed XP Home Edition, I get the
same error message, but now it is 6 or more times A DAY. Once again,
no one else has touched this computer but the people that built it and
shipped it to me. So once again, no one else could possibly be using
those files. But XP has added a new glitch, namely that when moving a
file, it sometimes leaves a ghost file behind in the old location. The
only cure in any of these circumstances is to restart the computer.
So, to save on restarting too often, I keep a paper off to the side
where I record all the files I couldn't rename, all the files I
couldn't delete, all the files that I couldn't move, and all the files
that I was able to move only to have a ghost file left behind. And at
the end of the day, I restart the computer and go down that list to do
the tasks that XP wouldn't let me do earlier in the day. Sometimes I
have to restart a second time because some files will still block my
desired actions. And once I've gotten all the files taken care of, I
go to the Recycle bin, only to find that XP has ANOTHER glitch Windows
98 SE didn't have, namely that some files can't be removed from the
Recycle bin because "file is not empty". So I have to restart the
computer AGAIN to get rid of those files.
I have three questions here:
1. Why has this problem been allowed to continue for so many
reincarnations of Windows (Windows 98SE thru to XP)?
2. Is there a fix for this problem?
3. Has anyone made an effort to remove that problem in Windows Vista,
or am I going to have to deal with more of the same?
DAAVE'S RESPONSE:
Please post the complete text of this repeating "error message."
MY RESPONSE:
I might have a file I haven't touched in months and decide I no longer
need. When I try to delete it, the below error message pops up on the
screen.
"Cannot remove folder (name of the folder): It is being used by
another person or program.
Close any programs that might be using the file and try again."
Similar versions of the above message pop up from time to time when I
decide to rename or move a file. And occasionally, even when I
successfully move a file, an empty folder is left behind looking
ghostly, like a folder that has been cut for cut and paste, and when
you try to delete that empty ghost folder you receive a variation of
the above error message. And then there are the folders that have
subfolders in them and that I try to move, only to find out that I
can't move all the subfolders because of a variation of the message
above. And then there are those folders I can't delete because of the below
error message:
"Cannot delete (file name): Access is denied.
Make sure the disk is not full or write-protected and that the file is
not currently in use."
Checking the file thru Properties there is no indication it is
write-protected, I have plenty of space on my hard drive, and as I have
already indicated, the only other people that have ever touched my
computer are the people who built it and packed it for shipping to me,
so no one else has access or would be using those files. The only cure
to the above problems is to restart my computer. Consequently, to keep
from restarting over and over all day long, I keep a piece of paper on
my desk and record the names of all the folders I was blocked from
doing anything with that day, and at the end of the day, I restart the
computer and go back to those folders to delete, move, or rename them.
And if I succeed in removing the folders I wanted to remove, I
sometimes run into another error message when I try to dump them from
the Recycle bin. I can't replicate that message right now, but it
refers to the file and tells me it cannot be deleted because "file is
not empty". This is a new one that wasn't in Windows 98 SE. Since
when do you need to empty a file before sending it to the Recycle
bin in order to be able to delete it permanently???
As I've also already indicated, this was a minor and occasional problem
with my previous computer and Windows 98 SE. But with the purchase of
my new computer and the XP Home that came with it, the frequency of
these error messages went from the 3 or 4 times a week with Windows 98 SE to
6 or more times a day with the XP. I would have expected an improvement with
the newer version of Windows. Instead matters have gotten worse. Which
leaves me wondering whether I dare even consider purchasing Windows Vista. I
would go back to Windows 98 SE and install it on my new computer if it were
compatible with all my other non-Windows software. Unfortunately it isn't.
Suggestions???
ED Y'S RESPONSE:
Without seeing the message, I'd wager to guess that it's telling you
that another application or piece of software on your machine is using
the file. Until you ID what that is, you'll never solve your problem.
MY RESPONSE:
Well, I downloaded a program called WhoLockMe, which when used on the
file I get the error message on is supposed to indicate who is locking
me out of that file. That program gave me Windows Explorer as the
culprit. I reloaded my Windows 98 SE to resolve this issue, to no
avail. I've been reluctant to reload Windows XP, but if you think it
will work with this version of Windows when it wouldn't with 98 SE,
I'll give it a try. What do you think?
DAAVE'S RESPONSE:
You say you are trying to delete a file you "haven't touched in
months." And these "ghostly"-looking folders sound like hidden folders
you have chosen deliberately to unhide. If you are trying to delete
system files, Windows (rightly) won't let you do it.
Again, *be specific*. Which files are you trying to delete? And why?
What are the names of the folders you have written down?
Do you perform regular maintenance on your PC? See:
www3.telus.net/dandemar/slowcom.htm
MY RESPONSE: (This response I am paraphrasing, since the original
transmission seems to have been lost in cyberspace)
The only reason I specified problems deleting files I "haven't touched
in months", is because I noticed this error message occurs more often
with files I've visited during the course of that very day. Whether
that has any relevance to the problem, I don't know. But I wanted it
clear that files I haven't visited in months are also affected.
As for the ghost files, none of those files, I repeat, none of those
files are system or program files. They are files of my own creation
with titles such as Genealogy (containing census forms and pictures of
ancestors), Angelina Jolie (containing pictures of Angelina Jolie),
Arthur's files (containing letters from a dead cousin), Avatars (containing
avatars for membership sites I belong to), etc. etc.
Nothing in any of the files is of a software nature. When I transfer a
file from one location to another, even though the folder transfers
successfully, a file is sometimes left in the old location. But the
file is not a clearly definable folder, but looks indeed like the
hidden folder you referred to or like a folder after you've clicked Cut
and before you've Pasted it elsewhere. And this ghost folder cannot be
deleted without a restart. Any attempt to delete it will lead to the
previously mentioned error message about someone else using it.
As for the regular maintenance question, I performed two defrags of the
hard drive prior to 4 months ago, when I purchased Windows Live
OneCare, at which time I set it up to do a full tune-up once a month,
which it has been doing ever since (the last time on 28 January).
Those tune-ups over the last four months have had no effect on the
problem. More questions? Any suggestions?
