Attached Link: http://nikkisprite.com

 I keep my content organized by main figure. So for instance, I have

libraries/character/v4/clothes
libraries/character/v4/hair
libraries/character/v4/figures
libraries/pose/v4/clothes matts
libraries/pose/v4/skins
libraries/pose/v4/poses
etc...
on so on for A3, V3, M3.

I use ThumbsPlus to make contact sheets of the libraries. Contact sheets are useful if you have a lot of content --much faster to flip through contact sheets of hair styles, background, cothing matts, etc, than to sift through the content via Poser's interface.

Attached Link: http://NikkiSprite.com

 I've been a LW user for years and occassioanlly import Poser material. Recently I did an animation in which I used a Poser head. In Poser I created different expressions which I exported as separate LW objects. I ended up with about 20 different LW objects some with different expressions, some with different mouth morphs, some with eye morphs, etc.  I loaded the base head into layer 1 of Modeler, then loaded each of the other morphed heads into separate layers. Using the Map/Background to Morph tool, I applied all of the morphs onto the base model in layer 1. I could then dial in and mix the morphs using Lightwave's Morph Mixer tool. It worked great!

I've been eyeing the Kurv Studios converter. Supposedly it will convert geometry, riggs and basic matts. This could be a great tool if it performs as advertised...

 I made several changes. I upgraded to 64-bit Vista and 8 gigs. I also moved my runtime to a new internal drive. So far so good. Not only has Poser performed much better, I can also multitask Photoshop and Chrome.

 I'm in the process of upgrading my PC to Vista 64 and 8 gigs of memory to better run Poser. From what I have read, I should consider upgrading to Poser Pro also. Two quick questions: is the interface for Poser Pro the same as Poser 7 -so it is essentially the same program but with a 64-bit engine? Will it handle the Poser 7 runtime libraries fine, importing saved figures etc?

Thanks!

Thanks to everyone who commented here. I decided to go ahead and purchase a new internal hard drive, more memory, and Vista Ultimate 64 bit. I'll report back whether or not this solves, or at least helps, my memory problems in Poser.

Sean, I wan't suggesting that Poser is a high end program. I don't use it for animation at all, only for stills. If fact, my comparison to high end programs was to make the point that expensive, professional programs that might be expected to me resource hogs run fine on a 2gig machine but Poser, which is anything but a high end package, does not. That said, I do love Poser (and the wealth of 3rd part support) for stills.

"...Poser 6 can't use more that 2 gigs, can it?"

Does anyone know if this is true of Poser 7? If so my upgrades to Vista 64-bit and 8 gigs will be pointless...

Santel, I have 4 gig of memory in the machine but only 3 show under 32-bit XP. I have't attempted the hack to show all 4.

Thanks to everyone who has commented. I like Poser and am an avid user, but I am very disappointed that it handles errors so poorly. From what I now understand, there is no real way to pinpoint the problem. It pretty much could be anything.  I would much rather be spending my money at the Renderosity marketplace than on more hardware, but in order to try and stablize Poser I am going to upgrade to Vista 64, add 4 more gigs of memory, and install another internal hard drive. As mentioned before, I do some high end animation and never have this kind of problem with my professional animation packages....

 The external HD is connected directly to the computer. I think I'm going to pick up a new internal drive for my runtime to see if it will solve the problem.

 I have no concept of how the fragmentation of a hard drive could lead to an insufficient memory error. I'm not discounting the suggestion, I just have a hard time understanding the correlation...

My main runtime is on a removable 350 gig Maxtor usb2 hard drive. ...wonder if that could have anything to do with it?...

 I dont think its a texture path problem. I can load a single model and render okay. When I experienced this problem before, I could sometimes get a scene to render okay after multiple attemps and crashes...