We've all been there...

You load an item and then Poser goes into deep search mode looking for something, probably because you put it in a custom runtime and the author assumed it would be in the main runtime.

Yes, I know how to make it load... you go find the missing item and point poser to it.

The Question: What is the easiest method to solve this once and for all. I realize the Pz2 is going to have to be edited to show relative paths instead of absolute ones, but what do you edit and where is it in the HUGE* file? Better yet, is there a program that will do this for you? I'm fine with me having to find everything one more time... I just want to tidy all my files up so I never have to do it AGAIN. 

There's a free app in the freebie section called "CorrectReference"

If its only texture references then use Correct Reference from freestuff.

the relative path is the same no matter what runtime its in. It relies on Poser to look in each runtime using the path and then doing a full search if not. Setting a shallower search will pop up the message faster for you to point to the file. Check that the relative path is correct.

I think I have a script that checks everything but doesnt fix it. I will post it if I can find it.

If you have any of D3D's utilities, Runtime Repair will correct references for single items.

 Yes, I finally found Runtime Repair in those directories where I unpack things that I'm "going to use someday."

I ran it on each of my Character, Prop and Pose directories. Worked beautifully.

...and by the way... talk about speeding up the loading process! It's like I just got a new computer! 

I wish I had known about that. 

Instead I copied my texture and geometry files over to the initial runtime from my external runtimes and Poser was happy...but 4 gigs heavier!

Quote - If its only texture references then use Correct Reference from freestuff.

the relative path is the same no matter what runtime its in. It relies on Poser to look in each runtime using the path and then doing a full search if not. Setting a shallower search will pop up the message faster for you to point to the file. Check that the relative path is correct.

I think I have a script that checks everything but doesnt fix it. I will post it if I can find it.

What if your textures are outside of your runtime?  Also , what if you have the same textures on another drive?  Everything was fine until my drive names changed...

@ moogal:

changing drive names shouldn't make any difference (on a PC anyway); changing drive letters will.

That is what has happened to me, and the problem seems to be that most all of my textures are outside of the runtime folder.