Yeah u have to clean out the unused master objects and shaders. Saving internally should only add to file size on disk. The file has to load all in mem anyway so for mem usage I can't see that mattering. Have I actually tested this? No. Transposer actually stays linked to the original poser file so not sure how it will save them anyway if something happens. There is a link between them. Don't use poser so that's about all I can say there. For native should keep them fine and if it happens alot just keep them in the file. Haven't seen this or had it happen. Also on XP you can save your prefs for hex and c by going to documents and settingsuserapplication dataeovia, I believe. xml and text files w/ prefs and settings. 2GB of ram is really a good amt. Can use more, but won't notice too much difference. In some cases maybe. Can use less, but I wouldn't try poser stuff w/ less than a gig. Very high poly. Can check your commit charge in windows to see how high it is climbing.

No need to think outside the box....
    Just make it invisible.