Hey, you missed one! Memory bandwidth is one bottleneck; the next bottleneck is the Hard drive access. And that one impacts speed more as you hit the swapfile. William, you -might- want to consider moving from that XP-3200+ over to an Athlon 64 2800 or 3000. The reason is simple; the memory controller is -in- the CPU itself, not in the northbridge. That alone improves the memory access time, as you do not have to step the signal down. The cpu accesses the controller at it's native speed, and the memory is free to run at -its- best speed. The price is not that much higher, and you can run in 32bit native mode, and have a ready to run upgrade path to 64 bits when the OS is finalized and the porting starts. Giga-byte has a nice board, the K8-VNXP, that has dual SATA raid channels, 4 EIDE ports (two are standard, 2 are for RAID...and they all can be used for stand alone drives. I'm running this board now, and have 4 varying Ultra 133 drives on the EIDE, and a 120gig SATA drive that I'm running my hog apps on, like VuePro. Basically seeing how well they perform on a serial drive), lots of USB 2 ports, and a nifty little plugin power regulator that doubles the power smoothing for your system...or in case the motherboard's regulator fails, can take over for it as a backup. One thing that can speed up P5's launching time is by tricking it. Create a runtime called 'null' and get into the habit of setting Poser for that one whenever you shut down, so that it is the runtime you access again at startup...and install =nothing= into it. P5 only reads the runtime active at startup, and this can get the program up and running quickly. Switching still takes time, but the switch is faster, since Poser isn't trying to initialize itself and read and multigig runtime at the same time.