"pure bit" of hell
28-Mar-93 04:14:05
Sb: #33657-"pure bit" of hell
Fm: Ronald B. Romine 70322,1525
To: <David L. Gold> 73177,1161
Each file has 8 bits of info that describes its "status".
The Bits are "ahsprwed". The RWED bits are the most used, signaling the
READ, WRITE, EXECUTABLE, DELETE status of the file. The other four bits
"AHSP" are more specialized for setting the Archived, Hidden, Script, and
Pure settings.
Pure files, are programs that not only can be loaded into memory, but can
be be re-run without having to be reloaded; they do not modify (corrupt)
themselves.
A pure program could be run several time like COPY or ASSIGN during the
startup-sequence from one copy of each program, running at the same time
or one after the other. This saves the time needed to load the file from
disk when executed.
During the startup, the RESIDENT command attempts to load several of the
commands into memory where they would be availible at all times. But
RESIDENT will only load "pure" programs, recognizing them by checking the
pure bit.
While restoring your HD the P bits of some of the commands appear to have
been "unset".
You can use the PROTECT command to restore the bits. Look at the
startup-sequence, and make a note of every file that is made resident.
The enter:
PROTECT c:<filename> +p
This will add the P bit as being set without touching the other bits.
Ron.
– ap'ing with AP. (Eagles may fly, but weasles aren't sucked
into jet engines.)