| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
I am sure I've read of this problem here before, but no luck with
DIR/TITLE=
I am starting a nice collection on my hard disc of files that I
can't delete. Any attempt gives me an "Unable to delete - object
in use" message. At the moment I've collected three, of various
sorts. I am able to rename them, so I keep them in my special directory
/what_do_I-do_with_these.
Any ideas as to why they occur and how I can put them out of their
misery. (I had considered backing up and restoring my entire disc,
but there must be a more humane and painless way)
Colin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3335.1 | Re Misery in deletion | WELMTS::FINNIS | Mon Jan 15 1990 08:49 | 7 | |
Hi Colin,
I had quite a problem like this trying to delete files and they
would not go away, then I realised that there was white-space in
the name i.e a space at the end.
Pete
| |||||
| 3335.2 | Here are the ones I know of: | MSVAX::BARRETT | Who is Steve Dahl? | Mon Jan 15 1990 09:43 | 24 |
This will also happen if one or more of the following is true:
1) There is an ASSIGN statement referencing the file or directory.
The fix is to remove it.
2) There is an open ICON or window for that file or directory. The fix is
to de-select the icon or close the window.
3) Your current directory (the one that shows up when you do just
a "DIR") is the directory you're trying to delete. The fix is to
"cd" yourself elsewhere.
4) I'd also make sure that the file(s) in that directory are not
resident (do a RESIDENT command to see).
5) Lastly, make sure no background task uses the file/directory.
The bottom line is that you can usually believe the error message
-- SOMETHING somewhere is referencing it. The most common is the
ASSIGN statement.
{kgb}
| |||||
| 3335.3 | TALLIS::MCAFEE | Steve McAfee | Mon Jan 15 1990 10:16 | 5 | |
Although it is obvious and you've probably done it already...
You can try rebooting. Sometimes a poorly written program
will fail to release a lock on a file.
- steve
| |||||