As I said, placing a swapfile on a different harddisk only helps if the program is doing a lot of work on the harddisk AND at the same time is swapping to the disk. In that case you distribute disk usage over two disks and see a performance increase. But that doesn't apply to Poser, and therefore you won't see a performance increase. BTW I would never set the min/max size the same. There is simply no logical reason to do that. By setting the min size you can indeed prevent fragmentation of your swapfile and windows doesn't spend time changing the size of the swapfile. Therefore a good minimum size is the maximum amount of virtual memory you normally use, plus a bit extra. (25% for example). There is no harm in setting a high max size. Windows will only use it when it needs more swapspace, and when it doesn't need it anymore, it releases that diskspace again. But when your max space is not large enough, your application will crash. So I don't take a risk and set a high max setting. My max setting is 3GB. (Normal application cannot use more than 3GB, so higher then that isn't needed IMHO) BTW just placing swapfiles on a seperate partition but not on a seperate disk doesn't increase speed. (Because it is still the same harddisk that had to do the work) The only thing you can accomplish that way is to prevent fragmentation of the swapfile. (But you can also do that with a good min size)