Quote - that folder structure is typical for a external runtime.

if you extract it to a work folder and then drag and drop the runtime folder on the poser program folder , it will give you a caution message and MERGE the runtimes .

Which folder structure is typical for an external runtime?

Why bother with the additional step is my point. No matter whether you use the basic Poser runtime or externals, you'll still have Runtime at the top, no? I use an external runtime and do NOT want folders in the zip above Runtime. It's useless to me. And from what I'm seeing it's useless to everyone else here. There's no reason in having that extra step or multiple steps just to place the item into the proper structure. Not having a spurious folder above Runtime in the zip doesn't prevent any of the other methods used mentioned in this thread for placement of stuff. Everyone, as far as I can tell, is describing that they eventually do away with that top folder if one exists above Runtime, so why have it in the first place?

Ok, so we have some lazy vendors ;) It's a reason, I can accept that. And I would ask that they try not to be quite so lazy, whether it's a freebie or not. Just a friendly please, that's all. Hey, I'm lazy too! I can relate! Which is why I despise having to go looking for orphaned runtimes and drag and drop folders when I don't need to ;)