I think that you've identified exactly why it becomes necessary to 'pause for thought' prior to rushing into any impromptu organisation of runtimes. When I first started to consolidate runtimes, one of my chief aims was to arrive at a situation where each of my integrated runtime libraries would be as near as possible self-contained. I wanted (and am slowly achieving) the ability to keep 'working backups' of these runtimes on CD (now DVD). The 'hair issue' is an excellent example to use in order to illustrate this dilemma. My own hair runtime is about exactly 2 gigabytes. Almost half of this content is contained within Textures and Geometries (most of which are universally applicable. I could indeed have opted to locate the relevant hair types within each of my characters libraries. However, I really do believe that such a strategy would only have added to the chaos that I was attempting to eliminate. Had I have followed such a strategy, then unless I was prepared to allow duplicate textures and geometries, I would have been introducing an essential inter-dependence in the gestalt scheme of things. The result that follows is that Very few of my hair items would be functional in Poser without a crucial component being loaded in some other (more or less) distant runtime. I can certainly empathise with your comments about finding it frustrating having to move runtimes - that too was an early concern which I shared. However, you'll probably be surprised to hear that I now (honestly) prefer 'getting lost in' my self-contained hair runtime library. Somewhat paradoxically, what I've learnt to value too is the empty hair library folder in my various runtime libraries. However deeply I'm nested within a particular character's own library, I always know that I can gain access to the root list of my runtime libraries by using this "short cut". As I keep my (most frequently visited) hair library at the top of my runtime list in Poser, I really don't find it much of an inconvenience to access whatsoever. When I return to other runtimes, I'm also assured that the subsequent opening of library folders will still be reflective of when I last visited. On a few rare occasions (e.g. relatively small MAT pose files) I'm happy to permit duplication in runtimes. I've also made several arbitrary decisions so that (for example) all the millennium uni-textures get located in my V3 runtime library. At the end of the day there really is no hard and fast solution to what is essentially a task of personal structuring, and I'm sure other users will adopt radically different - but equally effective - planning,