running 4 GB Ram in a Win XP - and still having issues with memory and Poser 6.
Thnaks to inform me..probably I'm out of my mind..but was not fix that?
I re-start to use mey Poser 6 and got all the same again...
thnkas
Cris

yeah. They went to Poser 7.  Seriously though what are you trying to render thats giving you problems?  I'm on P6 with 256mb ram and get by ok.  Poser probably isnt utilizing your full 4 gigs of memory.  The one thing that will kill you when it comes to memory is shadows.

Three of the most important things you should do is: Clear your cache of everything then turn off your computer and get some coffee (most important of the three), come back start it up again.  Then try it.  It might be that 512KByte section of your RAM  that Win everything uses for housekeeping, routing, and deciding what does what and when etc.  It needs to be zeroed out, sometimes on an hourly basis or you start getting other weird stuff happening too eg  rendering along singing a song and suddenly you are looking at your nice wallpaper screen with everything closed.  Might just work for you.  Plutom

is there a program for XP that shuts off/cleans up all the memory hogs..the TSR programs, etc ?
I have a ton of things running always in the background...such as right now I have 56 processes running with 672meg of memory commited. That is obviously not a good thing for using Poser.

some of it can be closed from the taskbar, but most are little apps running in the background.

--and I have 58 of those little buggers running in the background and clogging me 512KBytes of RAM memory that is reserved for registery use.  Do the same thing as you start whacking away at the biggies.  Doesn't appear to help much.  I use McAfee QuickClean along with WinXP's cleanmgr to scrub those little buggers.  Those programs plus shutting my computer down after things become sluggish or weird acting has cleared up everything so far.  I have a Gateway 700SE purchased in July of 2002 (with 512Mbytes of PC800 RAM) and a 2.0GHZ single CPU.

By cleaning crap out everyday keeps everything running smoothly.  Like I stated earlier, just one round with the internet can give around 8 MBytes of cache crap not to mention those lousy cookies.  I only have my four important ones on my computer right now-Rendersity is one of them.  Plutom

*512KBytes of RAM memory that is reserved for registery use.

can you post your source on this information? I've been using/supporting  windows for years and I have no idea what your're talking about with this claim you keep making...*

The best thing you can do in my experience is simply monitor your render as it runs by keeping an eye on Task Manager, and minimize Poser when it approaches about 2gb of memory usage.  This forces Poser to shed a very large amount of unnecessary memory that it has claimed, and can help your renders go a lot farther than they will otherwise.  Rebooting daily and cutting things out of registry doesn't have a lot to do with it in my experience, it's that Poser is limited to 3GB of memory use and P6 doesn't do memory management very well.

Quote - *512KBytes of RAM memory that is reserved for registery use.

can you post your source on this information? I've been using/supporting  windows for years and I have no idea what your're talking about with this claim you keep making...*

 

It's information I read about 10 years ago. It's where your BIOS used to be stored, so you got me wondering-- I had to go on the internet Google.com with the statement Windows BIOs Ram Allocation-the information is from the Mini White Paper on HP workstations.  the BIOS takes up about 512KB starting from the very top address and it allocates blocks for IO cards, networking, PCI hubs, bus bridges, PCI express and video/graphics cards with the largest block of address allocated for the Video Card.  To me that means housekeeping.

I could be very wrong since I'm certainly not a computer programmer. 

However I read that sometimes bits and pieces (I call them that) do not flush out of RAM when some software is closed. I was thinking that BIOS may be dynamic within its address block and may have stuff that clogs up too.

One thing I know for sure is that if I'm have weird stuff happening with any of my software programs shutting the computer down and bringing it back up again has always fixed that problem. 

I  might have mentioned registery files.  However they are totally different and I shouldn't have mentioned them even in the same thread sorry.  Forget that you even have registry files, don't even think about cleaning them--one wrong delete and your computer's death will quick.  Plutom

I think your looking at the wrong item, I read in a forum (here at Renderosity) that it's not your memory that Poser uses to render images, but your "CPU".

Last week I was having a heck of a time rendering an image. I would lower the bucketsize to 32 and reduce raytracing,  and still got the memory error.

Finally I went to my graphic program and located all of the textures for everything I used and reduced them in size using "bicubic resampling" to 1024 on the longest side.  I saw that some were 4000 pixels!  Resizing the textures helped immensely. I didn't have any closeups so I didn't need huge detail and 1024 was more than adequate for my needs.

I still had to reduce my bucketsize to 32 though but didn't have to sacrifice raytracing.

I made a copy of the original textures in case I ever want to use them at full size.

Also, check the shadow map size of your lights.  I had trouble once and eventually found that I had one shadow map that was 8000 which was what was hanging up my render and causing memory issues.

*I think your looking at the wrong item, I read in a forum (here at Renderosity) that it's not your memory that Poser uses to render images, but your "CPU".

*It's the CPU that does all the number-crunching, but, provided that the CPU has the basic minimum required processing-power, the CPU isn't going to stall a render.   You may grow old waiting for a render to complete, if the CPU is lacking in muscle, but it IS probably memory (or, to be more precise, lack of it, or the application's inability to exploit it) that is the killer, when a render fails.   For a Firefly render, I have long followed the procedure that pjz99 described above.   It doesn't always work, but it certainly helps.

Poser 6 SR3 cleared up any and all memory problems I ever had with Poser.

And then came Poser 7 SR2.1 -- hopefully SR 3 for P7 is coming soon, because it's driving me crazy again.

-- Jeff

i still have problems with P6..quite often, actually, with memory problems. It actually seems worse for me than it did originally, if that's possible...maybe I have a bad ram stick or something.
6.03.140 is my version. Is that the latest ?

Quote - [It's information I read about 10 years ago. It's where your BIOS used to be stored, so you got me wondering-- I had to go on the internet Google.com with the statement Windows BIOs Ram Allocation-the information is from the Mini White Paper on HP workstations.  the BIOS takes up about 512KB starting from the very top address and it allocates blocks for IO cards, networking, PCI hubs, bus bridges, PCI express and video/graphics cards with the largest block of address allocated for the Video Card.  To me that means housekeeping.

 

That isn't really applicable any more since the transition to 32-bit operating systems - if you still use Windows 95/98 (and some people do!) then it can affect you.  It used to be that the first 1MB of memory was laid out in a very specific way, as you say some of it claimed and locked out by hardware, and users had to work it like a puzzle to get all their drivers and applications to fit.  Certain programs relied on "low memory" (that first 1MB) in order to run, for things like register space.  Since 32-bit operating systems (Windows NT / Advanced Server and later) that's gone by the wayside.  Nowadays the operating system lets your applications grab memory from any block that is free regardless of where it is, up to 3GB.  If low memory still has any real significance I'm not aware of it (and I'm certainly not aware of everything!)

agreed PJZ... plus what you are quoting Pluto is nothing to do with the registry in Windows 9X upwards hence my confusion. what you are refering to I was taught was called the BIOS Stack, (tho maybe named something else, I later found the teacher was not 100% accurate on names lol)

Pjz-you are the first person that made this stuff clear to me and I appreciate it. 

I think I understand what you are saying. 

BIOS still lays out blocks for stuff.  However if. for example, if a graphics card requires more RAM. can it dip into eg  the PCI hub block for more space.

Are there blocks that can't be touched?  The reason why I asked is that you 
mentioned up to 3GB of RAM.  Plutom  

The 3GB limit is the maximum amount of memory that can be addressed under 32-bit operating systems.  It doesn't matter where the blocks are.  32-bit operating systems are also limited to a max of 4GB total, however it is split up.  This is the big advantage of switching to a 64-bit operating system - the limit is very much larger, so large that it's pretty unlikely you will see hardware that approaches that limit for some years to come.
http://msdn.microsoft.com has much information more accurate than I can convey it.  Basically all that stuff about what hardware grabs which memory is no longer a concern

Thanks for your quick answer Pjz--learned a lot and your comments really answered a lot of questions I had.  I don't think I'm alone either.

I try :blushing:

Someone, SVDL I think, has a python script which strips out all unused (zero-value) morph channels from a figure in memory. It seems to work on props attached to the figure as well, and even strips out morphs from non-injection figures. (I haven't tried it on V4.1, but it works on A3 and H3.) This will dramatically reduce the memory used by poser prior to rendering. I've found that my biggest problem is that when I have six or eight figures, each with six or so props, clothes, hair etc., that the regular P7 program is running at about 1.7 MB. Next time this happens, I'll try using the morph stripping script.

well, i wished that thread was helpfull for all of us..unfortunelly, propably my ignorance towards hardware or else...haven't solved my problem with Poser 6 and WinXP 64 bits..while Poser still running slow and 'tight' since Does not allowed a full FireFly render (final step) using V4 and all the props and backgrounds props too. Make it short; a pz3 file of 106 MB wont Render at final step FIREFLY.No help using smaller buket(32..) n help taking off 'shadows' from objectos and also unmarking the 'smooth polygons' etc...nothing helps..wont go ahead.
;((
reason I did buy yet the P7- since I use it has being the same issue...