Stewer -- for a single application, yes. The limitation is inculsive of windows itself, as well, so by allowing a larger swap file, you permit windows to grant Poser the full extent of the swap available to it, while still allowing for overhead within windows itself (necessary in XP when writing files to the drive) as well as other prgrams one might be running at the time. The VM doesn't actually have to be a fixed one, and the number needn't be that high, no. I use it as an example because it presents me with a smoother operation in my system, as windows is not always swift enough to increase it on it's own. Since In my case, I'm liable to have Poser, Acid, and a few utilities such as UVMapper and winamp running all at the same time, I need the larger swap file to ensure that I don't have hiccups and have to wait while windows adjusts for me in the middle of my mutli-tasking. Since the bulk of my programs all feed directly off the memory and VM, it works for me. Photoshop is an exception to this, as it does create it's own swap file for it's personal use, plus it utilizes the system resources. That's why I recommend and use a fixed VM. It sin't because windows does a bad job, it's because I tend to push my system harder than windows expects.

thou and I, my friend, can, in the most flunkey world, make, each of us, one non-flunkey, one hero, if we like: that will be two heroes to begin with. (Carlyle)