It seems to me that any school would have an established set of rules concerning such problems. You just follow the proper procedure.

My first response echos Curious Lab's recommendation. However, I was not offended at all by your response: "Windows XP (virtual memory) and Poser are competing for space. My easy fix was to put Poser on a different disk than Windows XP> I still get that error, but only rarely. The fix then is to defrag the hard drive. You can try resetting your virtual memory. I am too shy to fiddle with that."

Current versions of Steffy Staxx and Voluptuous Vicky are not meshes. They are MOR pose files that change the original characters. Voluptuous Vicky is related to Victoria, while Steffy Staxx is related to Stephanie.

If you use Restore on a figure, you will get that Pose. It is the default pose for any human figure. What are you trying to accomplish by using the Restore command? It might be best just to save a pz3 file of the scene in case you want to go back to a particular point. If you want to go back, just hit "new," to unload the current scene, then load the one you'd previously saved.

I have an educated guess. So many fine Poser sites have fallen victim to the costs of the Internet. The sad fact is that many people can't afford to pay the hosting costs involved in a web site that gives stuff away. That includes tutorials and freebies. If a site is really popular, bandwidth and hosting costs increase, and you lose another fine site.

CorrectReference won't convert the jpg bump files to bum. What I do is find the folder in question. Then I load a prop (I usually use the ball from Poser Prop Types), and apply a bump map to the prop. Poser offers to convert the jpg file to bum. Do this till all the jpg bump maps are converted. Then run CorrectReference and ensure that all texture references are correct. Then load the actual product, and everything works fine.

If you read the other responses, we've already mentioned that fix. Of course, the thing that I can't get past is this sentence: "After some intense investigation we believe we have a work around." When will they actually KNOW if this is a good fix?! Or at least rewrite their response. Again, my fix(es) work. And they don't involve nearly as much hassle.

It is a problem if people think we're getting the final version for free, or if people don't want to be beta testers. But then that should be obvious.

There is no indication that LanceB has Norton Utilities or Norton SystemWorks. Heck, we don't even know how much free space is on the hard drive in question, or whether LanceB defrags the hard drives, etc.

Maybe it's me, but I don't see DAZ saying DAZ Studio, or a part of it, will be free. They are saying the beta version of the base program will be free. This implies that the final version will cost us money. "Prior to the release of version 1.0, the base version of DAZ|Studio will be publicly available as a free beta for an undetermined period of time until it is solid."

I really wish you'd told us that you had Poser and Windows XP on different drives. It doesn't feel good jumping in to provide advice when all the facts are not known. I stand by my own recommendations. I have been getting by just fine with only 512MB of memory. I won't touch any of those memory utilities. How often do you defrag your hard drive?!

Windows XP (virtual memory) and Poser are competing for space. My easy fix was to put Poser on a different disk than Windows XP> I still get that error, but only rarely. The fix then is to defrag the hard drive. You can try resetting your virtual memory. I am too shy to fiddle with that.

What kills me is that DAZ owes its very livelihood to Poser and Curious Labs. They sell Poser content, after all. DAZ Studio doesn't truly exist as a product to sell just yet. But DAZ spent the last few months driving nails into Curious Labs, and yes, I think they're helping to kill Poser. To make things worse, people support DAZ's strategy by continuing to buy DAZ products.

You have a relatively new computer. I'm surprised since you were previously running Windows ME. In fact, your computer is more powerful than mine. You are a bit light on the memory. You might want to increase the memory to at least 512MB. I have 512MB, and Poser bogs down on me sometimes. I have no crashes at all.