The errors/warnings are probably related to the absolute PC paths.  Poser allows both Windows and MacOS file specifiers (N:xx and Nx).

The reason that absolute paths were stored in the file was probably because the referenced files were not in Poser's Runtime somewhere (so Poser saves the entire path rather than a relative one).  To fix this, you must make sure that the files are within the Poser Runtime  If they are (during construction of the product for instance), then you need to edit the problem paths so as to be something like (examples):

:Runtime:textures:MyTextures:mytexturemap.jpg

or

:Runtime:Geometries:MyObjects:myobject.obj

or

:Runtime:libraries:character:MyCharacter:whatever.extension

For distributed Poser content, things like:

F:MyPoserProductsProduct1RuntimeTexturesMyTexturesmytexturemap.jpg

aren't going to work on anyone else's system since it is an absolute and unique path.

There are probably ways to fix this without text editing your Poser files (CR2 or PP2), but I can't think of any off the top of my head.  Does the Merchants Utility have some form of path reference correction option?

Robert

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone