Pay attention to camera's FOV, too.. Portraits zoomed from 30 feet away look nothing like the wide-angle "hold the camera at arms lenght" type of photo people post to their forum profiles / facebooks / etc.  It's the same in poser. Try a picture with the pose cam and then the face cam to see what I mean.

VSS 's default skin shader, tweaked as you like, is also a great equalizer for using characters from different artisans. Keeps the texture maps, most of them anyway, but distributes its shader, which gives a semblance of cohesion to groups of characters who'd sometimes look like they came from different extra-terrestrial species, so different they are - in skin complexion - from each other. :D

 Ran some simulations on the ol' calculator (we're not running ludite variation, are we?) and game theory pretty much decided for me : I'll be looping all over King's Cross waiting for the best contract (And then I'll overbid, but we'll see to that when you guys finish the current round).

 Just like Laurie said, it is neither a Microsoft (Winblows) nor a Smith Micro (PoserPro) problem. It is a DAZ installer problem. :)

 Old DAZ installer...

Just make a copy of poserpro.exe and rename it poser.exe..  I think even an empty text file renamed poser.exe will do.  --  Actually, now that I think of it, I must have such a text file in each and every one of my external runtimes, to cope with the installer's request.

What he means is that, if you set render dimensions to a bigger pixel size than what your preview/render window is set to, then only parts of the render will appear  --  the rest is drawn, but "off screen".

So your image, once rendered, would give you something like what's at the top here. If that's what happens, then you're rendering fine : you can use the 'hand' icon to move the image around the window, or save it to file as it is complete.

If your render screen comes out as the image below, with blacked-out (or whited out?) parts, then there's indeed a problem.

I most certainly support this petition.