Thank you 3dcheapskate.

after your comments i do now remember installing PP11 'several times' because of making the mistake of choosing the wrong directory for the content on start up and installing the whole RT into the AppData directory.

In my part it was confusion over the location and of the difference between required software system files and of the content runtime library files. And most notably, not reading the installation procedure correctly. On the positive, by painstakingly moving files individually to where i want them it has given me ground knowledge of where files should be, and work correctly.

Unfortunately there seems to be a complication with regards to DazPeople M4 which doesn't follow the same directory structure as Poser Characters/Actors whereby it installs them into its own IDAZ directory. The installation of M4 is permitted to be only loaded to the runtime location of where the Poser.exe is. It is on bringing M4 into Poser that the software is unable to find the path to the groups and channels of M4 so i have to manually show Poser where they are. I save M4 as a new figure 'M4a' and can bring the complete model into Poser there after. (Apart from morphs for the fingers) I believe this is due to Poser asking for groups & Channels that are differently named than to what they are originally called in the IDAZ directory? This is the guessing part i mentioned in my last thread.

Today after reading your reply i copied the IDAZ directory into a different runtime and onto another drive and it works, complete with requirement to find the unmapped groups and channel files and unusable finger morphs. I can work with that, again by saving a new M4 Character. But it does bring into question the initial need for M4 to be installed into a runtime directory under the poser executable on the C: drive? My mind is looking more to the installation of M4 for cause that i may be doing it incorrectly, or missing something.

However now that i know that M4 can be moved and works within a fashion, the 11.2 update will not be responsible for its failure, unless the update causes a more catastrophic termination.

Regards. Pat :)