BPJ0%LEHIGH.BITNET@ibm1.cc.lehigh.edu (Binoy James. Membership has it's privil) (02/08/90)
Here's a weird situation.
I've got several scripts for Vlt that log me into the various mainframes
around here. Since they contain my password I decided to make them
unreadable, undeletable and hidden! However after I set the protection
bits and I issued a list command, the files showed up even though their
bits said:
hs-----
Not only that I can still read and edit them as before. So whatsamatta
here? Does something else have to be done in order to make them
unaccessable?
Help.
Bincs121jj@ux1.cso.uiuc.edu (02/08/90)
I don't think that the hidden filebit is supported yet. I hear that there is some hacked version of LS that supports it, but as of yet, no one else does. Gotta wait for 1.4 on that one.
darrell.grainger@canremote.uucp (DARRELL GRAINGER) (02/09/90)
If the LIST shows the bits hs------ for a file, the file is set for Hidden (a bit that is not supported by AmigaDOS 1.3.2 or lower) and it is a Script file (a file normally used by the EXECUTE but now EXECUTE need not be used). The fact that the --PARWED bits are not set means that the file is not Pure (see the RESIDENT command of 1.3 and 1.3.2), is not Archived (backed up), is not Readable, is not Writable, is not Executable, and is not Deletable. I would recommend you PROTECT <filename> +WED to make the file Writable, Readable, and Executable. Darrell --- * Via ProDoor 3.1R