> > ever write to system directories. Another thought that came up > > that > > was what I thought, a good idea - use attributes on the shared > > library > > files to "register" programs using them. Then you could have an > > app > > (such as an installer/uninstaller) search the file attributes of > > installed shared libraries and remove any that had no applications > > assigned to them. This, of course, requires that all application > > developers "registered" their programs with shared libs by adding > > to > > the attributes of the libs. Food for thought. > > Deej > > Not being a programmer this may be a stupid idea... > Would it be possible to have "intelligent" shared libraries that add > the > calling application to its attribute if it's not registered there > already. Or > does this add a major overhead? This is next to impossible, I'm afraid. It *can* be done, but it would add enormous overhead. -Nathan -- Fortune Cookie Says: Q: How many IBM cpu's does it take to do a logical right shift? A: 33. 1 to hold the bits and 32 to push the register.