I have 127+GB of Poser content.  My previous strategy was:

1.  Use Semidieu's Shaderworks to add poser runtimes directly to the Poser libraries XML file under my user profile in Windows XO.

2.  Use Dizzi's Advance Library to provide visual reference of content.

3.  Inside of Poser, run the python PRCPD daemon to allow direct loading from Advance Library, so long as the  content item being loaded has its runtime included by Shaderworks in Poser libraries XML (otherwise, Poser keeps asking for texture andmesh file locations.)

4.  Check problematic references using 3PDOExplorer and if necessary, open uncompressed content file in Metapad to visually read text lines to trouble-shoot.

With content being added nearly daily ( so call me a download maven), I have had to switch my strategy.  Also, I find that running PRPCD leads to some instability with Poser 7SR2.1.  It (Poser) may shut down unexpectedly while I'm in the middle of a project.  (Heck, it does that sometimes even without PRPCD running !)

Therefore, I have found this to be a more effective method:

1.  Just load Poser quickly with minimal runtimes in library - Poser 7's and the Download runtimes is fine, loads fast.

2.  Same as item 2 above.

3.  Using Advance Library to identify item I want to use for current scene creation project, right-click and scroll to bottom of pop-up menu, choose to open windows explorer. 

4.  Once Windows Explorer is open, note the location of the item from the Windows Explorer address blank.  In particular, note which runtime of my hundreds of runtimes, that item is to be found in.

5.  Inside of Poser, add that runtime to the library menu tag.

6.  Now I can load the item I want into my scene.

The new method allows me to:

A) Avoid adding everything with Shaderworks upfront, which thereby decreases my poser launching time (eliminates the need for Poser to scan 127++GB of runtimes before settling down). 

B) I avoid losing runtimes in my Poser library when I shift runtimes around or remove external media which contain runtimes.  (note added: I had been working on the premise of a static set of Poser libraries in my previous method)

C) I only add the runtimes I need to work with.  (Note added: Previously, I had all my runtimes added to poser - unwieldy.)

D) I am not constrained by too much advance planning, because I can still browse the content using Advance Library, and pick and choose what I feel is appropriate for my creative purpose at a moment in time.

(note added: I have also blogged this into my Rendo blog for my own reference.)

Eternal Hobbyist