Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!unido!rwthinf!cip-s02!wolfram From: wolfram@cip-s02.informatik.rwth-aachen.de (Wolfram Roesler) Newsgroups: comp.sys.atari.st.tech Subject: Re: Hidden folders (was Hidden Files) Message-ID: Date: 1 Feb 91 10:42:20 GMT References: <1991Jan16.163558.26338@arc.ab.ca> <1991Jan21.053855.1449@mailer.cc.fsu.edu> <8800@star.cs.vu.nl> <15861@sdcc6.ucsd.edu> <2814@atari.UUCP> Sender: news@rwthinf.UUCP Lines: 14 apratt@atari.UUCP (Allan Pratt) writes: >TOS versions 1.4 and greater do not allow this. They return "access >denied" if you try to change the folder bit to make a file into a folder. >You also can't set the volume-label bit or any of the undefined bits. Now that we are talking about the undefined flags, what exactly do they do? I remember setting them on a ramdisk file with the result of making that file disappear, so I didnt do much more experiments about that. Is it possible for applications to use these flags in a 'self defined' way? BTW: why is it not possible to hide a folder? Just to keep people from turning files to folders by changing a flag? How about making a folder readonly, which would affect all of its files?