Why Can't I Copy A File?

[geezer]

This is strange.

I am on WXP PRO.

I have a small (1KB) text file (myfile.txt) I created some time ago
using notepad. It had been readable/changeable/copyable - whatever.
Even when I try to open the file in notepad or wordpad, 'access' is
said to be 'denied'.

I find it is just 'not accessible'. I can't move, read or copy it
or anything. Properties for the file show neither the 'read-only' or
'hidden' box checked. There are other files co-located with this file
(in same sub-directory) that show no trouble in this respect.

What could have happened?

Anyone?

Geezer

 

[Bob Harris]

There are several possibilities, including:

1. XP thinks that you are not the owner. (Why this would happen, I do not
know. It could be a symptom of something worse.) If so, try taking
ownership while logged in as an adminisrator.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308421&sd=tech

2. The file/directory is corrupt. While rare, that does happen some time.
Open a command prompt and run CHKDSK on the partition with the /R option,
reboot when prompted, and wait about an hour for it to check/fix the file
system. If the partition is C:, the format would be:

CHKDSK C: /R

3. The file is locked by some process, possibly one that is hung. Try
rebooting as the simplest way to stop the process. Also consider
downloading and using a free program called UNLOCKER:

http://ccollomb.free.fr/unlocker/

 

[geezer]

There are several possibilities, including:

1. XP thinks that you are not the owner. (Why this would happen, I do not
know. It could be a symptom of something worse.) If so, try taking
ownership while logged in as an adminisrator.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308421&sd=tech

2. The file/directory is corrupt. While rare, that does happen some time.
Open a command prompt and run CHKDSK on the partition with the /R option,
reboot when prompted, and wait about an hour for it to check/fix the file
system. If the partition is C:, the format would be:

CHKDSK C: /R

3. The file is locked by some process, possibly one that is hung. Try
rebooting as the simplest way to stop the process. Also consider
downloading and using a free program called UNLOCKER:

http://ccollomb.free.fr/unlocker/

Thanks

I am running CHKDSK as we speak. While it is running, I'll download
the 'unlock' program. I'll also try dealing with ownership after
CHKDSK.

This is a new WD 160GB (two-weeks old) drive, and it has already
'lost' a different subdirectory about a week ago. I thought it was
due to something I did, but just maybe the drive is bad?

Problems, problems, problems. dang it!

Geezer

 

[geezer]

There are several possibilities, including:

1. XP thinks that you are not the owner. (Why this would happen, I do not
know. It could be a symptom of something worse.) If so, try taking
ownership while logged in as an adminisrator.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308421&sd=tech

2. The file/directory is corrupt. While rare, that does happen some time.
Open a command prompt and run CHKDSK on the partition with the /R option,
reboot when prompted, and wait about an hour for it to check/fix the file
system. If the partition is C:, the format would be:

CHKDSK C: /R

3. The file is locked by some process, possibly one that is hung. Try
rebooting as the simplest way to stop the process. Also consider
downloading and using a free program called UNLOCKER:

http://ccollomb.free.fr/unlocker/

CHKDSK did not fix the problem.
Unlocker said the file was 'not' locked, and it allowed me to change
the filename.

Then I went to
http://support.microsoft.com/default.aspx?scid=kb;en-us;308421&sd=tech
and tried to take ownership of just the file. It did no good. I
tried everything - even disabled the so-called 'inheriting' of
permissions from the 'parent'. So then I tried changing permissions
of the 'parent' which in this case was the sub-directory name. It did
no good for the bad file either UNTIL I rechecked the file to
'inherit' permissions from the 'parent again. Lo, now the text file
is accessible.

Before you say the problem was with the 'parent's' permissions, I need
to add that before I did all this, none of the other files under the
same sub-directory manifested this problem - just the text file.

The bottom-line is - things are working again (at least right now). So
thank you for your helps. Maybe my experience, and what I did, will
help others.

Thanks

Geezer