| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2939.1 | Did anything else change? | LODGE::LEN | David M. Len | Wed Sep 20 1989 13:59 | 6 |
| When I have seen it, it was from a RESIDENT command. It was a warning,
indicating that the program I was making resident did not have the
pure bit set on its directory entry. If you make a program resident
that is not "pure" (i.e. re-entrant) severe error can result. As to
why you would get this message as a result of going to 1.3 roms, I have
no idea.
|
| 2939.2 | Oops!! | SHARE::DOYLE | | Wed Sep 20 1989 14:54 | 6 |
| Well, I also used Powerpacker on my boot disk, maybe I paccked a prg.
that my startup sequence is trying to make resident...........
Now that I think of it..... this is the only disk that does this.
Thanks for the Explanation
Ed
|
| 2939.3 | Pure Bit Not Set | DICKNS::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Wed Sep 20 1989 16:56 | 4 |
| Yeah ... just look at the protection on any commands you are making
resident from within your startup sequence. Do a PROTECT +P on any that
aren't. Do remember that the pure bit cannot be set on some to make them
resident
|
| 2939.4 | | WJG::GUINEAU | Impossible Concentration | Wed Sep 20 1989 17:23 | 7 |
| > aren't. Do remember that the pure bit cannot be set on some to make them
> resident
And just cause you force the pure bit, it doesn't make the code pure!
John
|
| 2939.5 | Listen to .4 | TLE::RMEYERS | Randy Meyers | Wed Sep 20 1989 21:16 | 3 |
| >And just cause you force the pure bit, it doesn't make the code pure!
Yep, like, for example, "PowerPacked" files aren't pure code anymore!
|
| 2939.6 | Nothings 100% Compatible | SHARE::DOYLE | | Thu Sep 21 1989 09:15 | 9 |
| I've both ARPed and Packed my boot disk, so I could squeeze more disk, and
File Utilities on it. (If I ever get my hard drive working, I won't have
to worry about this)
Both of these foul up some of the Virus Checkers I use......
Ed
|
| 2939.7 | Pure or not pure? | LODGE::LEN | David M. Len | Thu Sep 21 1989 09:45 | 10 |
| Prior to this note I was also wondering about the interaction between
powerpacker and the resident command. Once powerpacker does its job on
unpacking the image, what is in memory should be bit for bit identical
to the non-powerpacked disk file(at least this is what I would
expect). My concern was the difference between invoking an image and
making an image resident not allowing powerpacker to do it's unpacking
correctly. Does the powerpacker documentation make any reference to
using the resident command on powerpacked files? (Inquiring minds want
to know but not take the time to download and read the documentation
:-).
|