Bingo. I use P Booost with P5 (and hopefully P6; Hogwarden is good about supporting his products) all the time. Some will say that being able to use external runtimes in P5 makes it superfluous, but it is a handy tool to redefine your libary system as you see fit. Well, as an example: With P-Booost I've added a few layers to my Pose folder. I have one that is nothing but the INJ-REM poses that the morph injection enabled models use; as long as the !FolderName ( like '!DAZ') is in the runtime where the actual P5 executable lives, the pose files can go just about anywhere (and getting all those bloody inj files out of the default pose directory cut it almost in half). There's a folder strictly for the adult oriented poses (not only body poses, but set ups, specialty morph injections, etc), one for esoterica, which is a catch all, science fiction based poses, architectural poses, MAT poses, vehicle poses. etc. Now you can do this to some extent without P-Booost; but by using it, you can create the new categories in the main P-Booost window, and drag and drop content out of the existing locations and place them where you want them. Another neat trick I stumbled over with P5 is to create a null runtime; just an empty folder with nothing in it-- and link it into P5. When P5 starts up, it only reads the selected runtime, so if you switch to the null runtime, Poser will start a =lot= faster....like around 20 seconds on my Athlon 64-3000. Then you change to the runtime that has stuff in it, but Poser won't read a library until you open it for the first time. That part is slow....but you aren't trying to read all the libraries at the same time the program is trying to initialize. This trick also works with P-Booost; just create an empty folder in each library, select them before you start P5, and you get the same effect.