Dont forget that you can make a complex subdirectory structure with any modern filesystem.
You should create at least 48 subfolders named like "! ! !" or "+!+".
Further you should avoid short filenames the closer you come to root.
Never let a path be shorter than 240 characters.
Store only a single file per directory.

Going for redundancy is always a good thing...
What should reside somewhere inside the Poser installation can be spread throughout the whole system. ReadMe's included. This way the large capacity of nowadays harddrives will be used in an excellent manner while at the same time it prevents the user from doing what he's best at: conserving digital crap.

Offer formats that are of no use to most of the target group. Offer textures in resolutions that can not be handled by the target app or that are much to low to yield good results.
Provide the ReadMe in at least 20 different variants. Including backward compatible ones.

Create an installer to reproduce your files on every drive and of course into the "system32", "drivercache" and "System Volume Information" directories.
Use the OS-tools to remove user and admin ownership of these redundant file and any possible other rights. For NTFS the effort to screw the FS shadowcopy will surely pay off.

If you create an compressed archive that contains rel. filepaths you should at least try to overwrite as many important files of the target Poser installation as possible. But not the obvious ones like Poser.exe...
Oh, and one thing: never name a file in a way that could let the user know what it contains.

Optional: Offer technical help regarding the installation process and make the user pay for this service.