CompuServe Thread

#Help with pure bit

5 messages in this thread
#47669From: Al BenglenJan 30, 1992 6:02 AM
I need a little assistance please. Recently I had to reconstruct my Whap disk which I use to boot my system (A500 with 1 meg and 2 floppies). Everything *seems* to work fine–system boots and Whap functions as it should (as far as I can tell). However, during the booting of the system, the message "Pure bit not set" displays on the screen. Exactly what es this message mean, and what should I do to correct the situation? via Whap! Al Benglen 74615,500
#47684From: Edward SwatschekJan 30, 1992 1:15 PM
"Pure bit not set" means that a command is being made resident that does not have it's pure bit set (the 'p' in '–p-rwed' shown by the list command). If a program is 'pure', it is safe to make resident; if not, it may have or cause problems when running from a resident state, but then, may not – no guarantees. When you make a non-pure command resident ( ie RESIDENT C:IconX PURE ), the Operating System returns the 'pure bit…' message as a reminder. To get rid of the message, insert a '>NIL:' immediately after RESIDENT ( ie RESIDENT >NIL: C:IconX ). hope this helps, Edjs Edward_Swatschek@mindlink.bc.ca – via Whap!
#47816From: Al BenglenFeb 1, 1992 6:42 AM
Thanks very much for the help and the explanation. via Whap! Al Benglen 74615,500
#47953From: ShraddhanFeb 2, 1992 6:16 PM
You say you had to reconstruct your Whap disk. Do you mean you used DiskDoctor or DiskSalv to repair it? If so, my guess is that the P status flag of one of the programs run during startup is now missing. If you can find out which one it is, you can set this flag again using: protect <filename> add p where of course <filename> is the name of the file. Shraddhan – via Whap! from Hertfordshire in the UK
#48017From: Al BenglenFeb 3, 1992 5:58 AM
Thanks for your help. via Whap! Al Benglen 74615,500