Dave-So opened this issue on Feb 12, 2007 · 12 posts
cherokee69 posted Mon, 12 February 2007 at 10:39 PM
Attached Link: http://poserpros.daz3d.com/forums/viewtopic.php?t=15989&postdays=0&postorder=asc&highlight=posershell&start=20
There is a post about this at the link above...last post on page 2 but here it is...it's for Poser 5 but works for Poser 6 as well....Quote - "layingback"]OK, for BadCo and others wanting more detailed instructions:
NB: Usual warnings, not responsible for damage done to your system, your Poser or your sanity if you follow these instructions - your mileage may vary, etc.
I can only give instructions for one of the very slow Poser 5 setups - 'cos that's the one I have, but some additional notes at end for others...
First copy posershell.xml as a backup. It's in Poser 5Runtimeui. Using Windows Explorer, right click the file and select Copy. Right click on any white space in Win Explorer and select Paste to save a copy.
OK, open posershell.xml in an editor - WordPad will do.
Find the first occurrence of: contentRoom
This should be of the form: <Widget name="contentRoomTab" ...
Delete everything through to the next > character, ie. leave the section for the clothesRoom alone. And don't leave any blank lines.Find the next occurrence of: contentRoom
This should be of the form: <Tab width="65" textWidget="contentRoomTab" />
Delete this whole line. Again don't leave any blank lines.Find the third and last occurrence of: contentRoom
This should be of the form:
. i.e. leave the faceRoom alone. Again, leave no blank lines.
Delet that line, and every line up to an including the first one containingDouble check to see that there aren't any more instances of contentRoom.
Save the file, and give it a shot. If you have no Content Room, and Poser 5 loaded faster than before, then you're set. And if you had a Poser 5 dog before like I did, you'll now discover that moving the parameter dials is just a little slower than in Poser 4, like it is when Poser 4 is getting tighter on memory - whereas before it was was more like a roulette wheel with a mind of it's own
Now on my version of the posershell.xml file those were all the changes necessary and applicable. But in c1rcle2's original post above there were instructions to remove a line containing <PSDFile name="./runtime/ui/"1701_ContentStuff.psd />. You'll see where these are, up near the top of the file, but mine had 10 of these types of lines, for loading all the other rooms, but not one for the contentRoom - go figure! But if you find one, you might want to delete it too.
FYI, in the description above the first delete removes the room selection from the ui, the second delete removes the image of the tab from the ui, and the last removes the actual page, all the palettes, etc.