| 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 |
PROTECT
I seem to have a problem changing the protection on some files.
For example, when I type
PROTECT #? +a
I often receive a "Protect failed" error message. I even try the
same command on the offended file like this
PROTECT libs +a
but with the same result. Any idea why some files cannot have their
archive bit modified? I would like a simple way of modifying the
archive bit on every file on my hard disk.
Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1831.1 | BAGELS::BRANNON | Dave Brannon | Sat Oct 29 1988 00:22 | 9 | |
how about "object in use"?
I was using PROTECT #?.bat +s to set the script file bit on a bunch
of files, forgot that was editing one of them. That was the only
file that wasn't changed. And I did get that PROTECT failed error
message.
-dave
| |||||
| 1831.2 | MTWAIN::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Mon Oct 31 1988 12:38 | 2 | |
From what I understand, an file or directory that is locked, like
libs: or devs:, is impervious to protection mods.
| |||||
| 1831.3 | More switches needed | FSDEV1::JBERNARD | Mon Oct 31 1988 13:50 | 4 | |
PROTECT dev:path/#? -a ADD works fine for me.... I haven't been
able to do a full device... a command like
PROTECT DHn:#?.abc -a ADD ALL would be nice
| |||||