Sat, Jan 11, 11:31 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)



Subject: Render problem after conversion to NTFS


dariop ( ) posted Sun, 06 April 2003 at 12:00 PM ยท edited Sat, 11 January 2025 at 11:14 PM

Hi Bit of a long shot but someone might know ! I converted my file system from FAT32 to NTFS and now I cannot do large renders. I get a weird error message which says "Disk is full cannot render at this resolution" - yet my disk has 24GB of free space. I am running Windows XP Pro and Pro Pack. Obviously there is some kind of block on creating files above a certain size but I can't figure out where it is. It isn't Quota Management because I've turned that off. Anyone got an idea what the problem might be ? Thanks in advance dariop


BeatYourSoul ( ) posted Sun, 06 April 2003 at 12:23 PM

Well, I find that to be strange since FAT32 only supports files up to 4GB and NTFS supports files much, much, much larger than that (the size is ridiculous). FAT32 is the one with the file size limitations. (???) Curious Labs Support FAQ: Poser can't render high resolution images. Error appears "Insufficient disk space to render". After some intense investigation we believe we have a work around. It turns out that Windows NT 4, 2000 and Windows XP must be using some space for the pagefile.sys file on the same partition that Poser is installed, to render large images. The pagefile.sys is the virtual memory or temp space for Windows. An approximate minimum would 10 MB. This amount might have to be increased for more complex scenes and animations. The maximum should be 10 MB or greater. To modify the Virtual Memory: Windows NT 4 = Right Click my computer. Click the performance tab. Click change. Click the drive Poser is installed on. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Windows 2000 = Right click My computer. Select the Advanced tab. Click Performance option. Click Change. Select the drive Poser is installed on. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Windows XP = Click Start. Right Click My Computer in the menu. Select Properties. Select the Advanced tab. Click Settings, next to Performance. Select the advanced tab. Click Change. Select the drive Poser is installed on. Click the Custom size button. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Poser will now be able to render up to its maximum size of 4090 pixels x 4090 pixels @ any resolution BYS


dariop ( ) posted Sun, 06 April 2003 at 1:49 PM

Hi BYS Thanks for that. Sadly it didn't work :-( Still getting the same "Insufficient disk space......." error message.


judith ( ) posted Sun, 06 April 2003 at 2:09 PM

Have you tried moving your paging file to another partition or physical hard drive? That did the trick for me.

What we do in life, echoes in eternity.

E-mail | Renderosity Homepage | Renderosity Store | RDNA Store


RealitysPoison ( ) posted Sun, 06 April 2003 at 2:40 PM

Try entering higher initial size. Ten wouldn't do it for me. So I jacked mine WAY up and then things were fine.


PeterWahoo ( ) posted Sun, 06 April 2003 at 4:05 PM

You could try installing Poser on a different hard drive than where Windows is installed. In addition you could try cleaning out your temporary files. I never mess with swap files. According to many experts, Windows 2000 and XP do a more than sufficient job on their own. Also, don't forget to defrag your hard drive.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.