I dont think more freedom in organizing the runtime will be hard to users. Anyone who uses a computer is familiar with organizing stuff in folders (or at least should be). The additional restrictions Poser puts on the user are what it makes hard. While I think my suggestion would not make it harder for beginners, I would focus more on optimal workflow for experienced users anyway. One is a experienced user for longer than a beginner. I rather have a bit stepper learning curve than an annoyance forever. I think the installer should work with any existing zip file, because all required Path information is included in the library files. These Daz installers are a pain anyway and for me, progress is more important than backward compatibly in the most cases. It should install the content in a default folder and make it easy for the user to move it around. Poser itself should manage all file dependencies while moving the content, including between runtimes and drives. But that may be a wish to big for P6. I have no problem with shifting the content database to a later release, but I think eventually it will the way to go. I was thinking about putting the comments in the library files, not in the thumbnails. Then the size would be no problem. On a right click on a thumbnail, poser should read it from the file and display it in a help window. But maybe your idea is easier to implement. Stefan