Hello all..... I can't seem to get any large renders done in Win xp Sp1,while using the option of a separate window. Although , i have 1.8 gig of free space ( not including Xp paging 900 megs ) I always have a warning message " not enough disk space to render at current resolution. I could enlarge my current partition, but I wish I could find a simplier solution. any hints ?.... Thanks for your help.

How large are you looking to do? Sharen

I get those occasionally with XP. Defragging the drive with Poser's Runtime plus deleting any left over "poserTemp.1234567890" type files in Poser's root directory clears up the problem for me every time.

Hi..... 900 pixels , to 1000 x ...? I'm just guessing , my problem might be related to Win Xp Virtual mem page size. I did not have this problem with Win 2k. I tried decreasing my virtual mem from 1.5 gig to 900. but maybe , i have it backwards.... Thanks for replying

Attached Link: http://www.outertech.com

Are you sure it's free? I see it listed as shareware.

Attached Link: http://curiouslabs.com/article/articleview/215/1/65/

try saving your scene, closing Poser, then starting Poser, load the scene, and render.

The memory thing....I used to have virtual + real mem equal to about 2gig. Then I bought more memory and have 1 gig hard mem...I let XP assign virtual...but since I upgraded to 1 gig, I have no more trouble...plus my hard drive is never activated during render.

Seems to me there was an issue with P4 leaving a lot of stuff in memory...it kept adding up as you added and deleted textures or changed things in a scene..that's why I said above to close and reopen...clear the memory....that cache program should help...plus the Curious memory patch

1.8 GB of hard drive space is nothing when you're doing graphics work. This is one time, Poser gave you the right error message.

Message edited on: 07/18/2004 23:09

Message edited on: 07/18/2004 23:10

Don't let BB scare you. In this case, its not a lack of system memory resources, but just Poser's poor memory management. Just gotta find the right combo of things to clean out for you to get back to normal.

You know, I tend to agree with Bobbie Boucher. When I used P4PP it always used to cry if I had less than 15 GB space, no matter what my virtual RAM settings were.

uh... actually Sharon, I think that means that you would agree that the problem does NOT lie with memory settings & availablility as BB suggested, but rather something to do with available disk space.

I'm still using 4.03 as loneranger20 is, with the Extended Memory Upgrade and, when watching Poser's use of memory resources during a render I don't recall ever having seen it gobble up much over 1Gb of memory during a render (well under my 1Gb RAM + 2GB fixed-size pagefile).

On the other hand, when it does occasionally still complain of insufficient memory, it happens at different memory usage levels, but often when using just a couple of hundred Mb, nowhere near the 3000 available. All of this with over a hundred gigs of empty disk space. (And remember, P4's "poserTemp" files created during a render were rendered to disk, not to RAM or Virtual memory)

So, while certainly not disputing BB's experiences, when a defrag, with a fixed-size pagefile, makes the problem go away , (for me at least) it tends to indicate the actual source must not lie in a RAM or Virtual memory problem, but rather to disk space, (and, --my wild guess--, perhaps the apps inability to write its poserTemp files to disk in multiple fragments).

I know we've had this thread a zillion times. Can't say what really made me dive into it this time around -- nothin' truly new to add.

From the license agreement: CachemanXP has two types of licenses: Workstation and Site. The Workstation license is a one or multi computer license, the amount being selectable at purchase time. The Site License is a multi-computer license that allows usage of the program in the registered mode by all members of the company (team, group, and etc), which owns it. If you decide not to purchase the full version of CachemanXP you are allowed to use the unregistered shareware version for an unlimited time. Also, according to the help file that came with it there are a couple of added tweaks if you register it along with support, which you don't get unless it's registered. So the "unregistered shareware" version is free to use in an unlimited fashion. I've been using it for ages and it works. :)

Ahem, I said loneranger20 does not have enough hard drive space. Some people forget that hard drive space is not memory. Memory lies in the RAM chips, and is volatile. When you end a program or turn off your computer, the stuff in memory is gone. Hard drive space, or disk storage, is permanent. The computer is turned off, and the data still exists. loneranger20 does not have enough hard drive space.

Thanks for the clarification, brynna.

I'll accept that Ahem! Completely misread original & subsequent posts,-- thought he'd said 1.8gb RAM, not HDD. ... Nance packs up his tirade, checks his glasses, and crawls under rock, avoiding eye contact with BB. :-0

You know, I had the exact same problem on XP home the other day. I had been rendering without fail for a long while, but then all of a sudden I could render anything to a seperate windows, no matter what size. I read the CL posts about this issue, and they suggested setting a fixed size for the swap disk, instead of letting Windows mess with it. I have a relatively large hard drive, but what I did was actually reduce the swap file in size from what Windows had set it, and it totally did the trick. I can render any size now up to the max of 4096X4096, with no other programs needed. I have 3/4 gig of RAM. Jack

OK, at the risk of being repetitive, Poser isn't always very descriptive concerning error messages. In fact, Poser uses "out of memory" for too many error messages. For instance: 1.) If you are missing a geometry file, Poser first says it can't find the geometry file. You proceed, and Poser states you're out of memory. 2.) Insufficient Disk space is not the same as "out of memory." This error can mean: a.) Yes, I am really out of hard drive space (again, 1GB of hard drive space is not much!) b.) Poser is having trouble because it is conflicting with your Windows swap file. Two possible remedies: a.) The techie approach is to fiddle with your swap file settings. Many people agree that Windows XP is very good at managing your swap file and memory. b.) The safer remedy for me was to give Poser its own hard drive. I currently have a 120GB hard drive for Poser 4 and Poser 5. Windows XP and my other software are on the 20GB C drive that sometimes gets full. I rarely get the Insufficient Disk Space error any more. If I do, it's time to defrag the hard drive. The confusing part to me is that some people think they're "savvy" enough to fiddle with the swap file, but still don't see the difference between memory and hard drive space?!

Misread the original (like Nance), my apologies. Yes, I know the difference between "out of disk space" and "out of memory" type errors. 1.5 gb free diskspace is not beginning to be enough to do much of anything these days and is barely enough to hold a swapfile. And yes I know the difference between memory and hard drive space, having been a computer tech for almost a decade. Ron, you can stop "aheming" for now. ;)

Then why do you recommend a memory manager when we know Windows XP doesn't need them?

*** Bobbie ****

Message edited on: 07/20/2004 15:09

LMAO... Hum... I get this message when I do some heavy duty rendering and my system automatically ups my swap file or does what ever is needed before poser crashes.. One thing you might want to consider is when you do your final render, render it right to your HD..

thank you all for tips..... i solved my problems ,let Winxp to allocate swap file on poser's own partition roughly 10 gigs of disk space Ciao...