Icon for script on main Workbench window?

[malko]

Originally Posted by Daedalus

It also talks about the H bit meaning "hidden" and the A bit only working under 1.3, so it's probably not the best source of information.[...]

Don't forget that at that time, they were comparing with older version of the OS, meaning AOS1.2. Therefore, we can say that the source is quite good

Originally Posted by AMIGASYSTEM

The bit "E" it is not necessary to run a script or Icon, The bit "E" it is instead necessary on the real executables otherwise they do not start.

From "AmigaDOS Inside and Out ©1987,1988 Data Becker GmbH & ©1988 Abacus"

[...]
Workbench 1.3 implementation:
  Syntax: Protect FILE/A,FLAGS,ADD/S,SUB/S
  Workbench 1.3 adds four new protection bits to the Protect command:
     h (Hidden)   - controls visibility of certain file entries
     s (Script)   - controls starting script files w/o Execute
     p (Pure)     - controls program loading using Resident 
     a (Archived) - controls file copying (Kickstart 1.3)
  When using Workbench 1.3/Kickstart 1.2 to start your Amiga you 
  must pay particular attention to the p and s flags.
h (hidden)
  The hidden protection bit suppresses the entry of the respective files 
  in the directory. For example, the .info files responsible for the icon 
  on the Workbench disk can be made invisible in the directory list. 
  Larger directories can be made more readable using this method.
s (script)
  The script protection bit deals with script files. When the script flag 
  is positive (set), the script file can be started from a shell. It is not 
  necessary to enter the Execute command to invoke a script file any
  more. A set script flag automatically calls an Execute command.
p (pure)
  The pure protection bit allows the associated program to be loaded 
  using the Resident command. By doing this it is always ready for 
  the user and it also doesn’t have to be loaded from the drive anymore.
  The pure protection bit is necessary because not every program has 
  the qualities needed for using the Resident command. More 
  information about the Resident command can be found in Chapter 4.
a (archive)
  The archive protection bit controls die option of copying files under 
  Kickstart 1.3. The Copy command only copies files that have negative 
  (unset) archive protection bits. A file with a positive (set) 
  archive protection bit is said to be archived. The archive protec
  tion bit goes negative when you write to the file. A new archive 
  protection bit must be set.
[...]

Edit: misprint are due to bad OCR on the pages

[kolla]

H flag is not hidden, and for anyone saying it is - if H means hidden, when and from what is it hidden? Where is "show hidden files"?

[daxb]

Make a poll about H flag. What do you think is H flag for? Then give several answers to choose. Could give interesting results.

[kolla]

Lol, I would be surprised if the correct answer would win such a poll

I use the H flag quite actively on my systems, it's a nice way to speed up the boot process while keeping startup-sequence tidy. Frequently used CLI programs also get it, to avoid disk access over and over.

[Daedalus]

Originally Posted by malko

Don't forget that at that time, they were comparing with older version of the OS, meaning AOS1.2. Therefore, we can say that the source is quite good

Hmmm, perhaps. The reference to 2.0 in your quote threw me off that pattern of thought:

V2.0 ALL/S,QUITE/S
ALL Multiple files may now be protected.
QUIET No messages are displayed.

I'm less familiar with the much older versions of AmigaDOS, so it could well be that the flags were only implemented from 1.3 on, in which case it looks like the text wasn't updated to account for 2.0 (assuming the 2.0 reference is talking about the new at the time KS 2.0). Still, it's not unheard of for 3rd party publications to contain errors or misunderstandings, especially if 1st party documentation wasn't easy to find at the time.

[PeterK]

I use the H flag quite actively on my systems, it's a nice way to speed up the boot process while keeping startup-sequence tidy. Frequently used CLI programs also get it, to avoid disk access over and over.

Interesting! Do you want to say that the H flag is something for caching programs, like an S flag for loading resident?

The OS 3.9 protect command does not know it, although list shows the H flag and it can be set or removed with DOpus 4, but indeed nothing is ever hiding on OS 3.9.

[AMIGASYSTEM]

Peter Flag H he does not hide anything either OS 1.0, 1.1, 1.2 and 1.3

[PeterK]

I'm never playing with OS 1.0 - 2.1 anymore and who knows how WinUAE is handling a H flag?

[gulliver]

I can confirm you that the H flag is for "Hold". It holds the program into ram (without requiring the "resident" command to be used, just by running the affected program once) for faster access next time.

That is why it doesnt hide anything, and is the reason why kolla gets a speed up on his system.

[AMIGASYSTEM]

For confirmation that H does not hide anything i protected all the files on the WB floppy with the H flag 1.0, then i started the floppy with emulation A1000 and the files remain visible, i enclose a small exhaustive video.

[kolla]

Originally Posted by PeterK

like an S flag for loading resident?

Correct, that's exactly what it is.

Funny that you mention DOpus, because there was quite a turmoil with the DOpus developers (Jonathan Potter, and Greg Perry) over this back in the days, as they had started using the H as hidden, for no other good reason that it was broken in OS3.0.

[kolla]

Originally Posted by PeterK

I'm never playing with OS 1.0 - 2.1 anymore and who knows how WinUAE is handling a H flag?

You mean when accessing windows filesystems directly? Doesn't WinUAE use metafiles for holding Amiga filesystem flags?
I know FS-UAE does, files get a companion file, with extension .uaem.