seems the thread is closed so... Dealer wrote- "use your ram as a back up for your ram...hehe...sounds like a real good idea from here doesn't it" heheheheh.. It does sound absurd doesn't it? But MS makes one resort to absurd measures sometimes... Elkinm- if you try the ramdisk pagefile thing, don't make it too small or you will get a popup error message, VM low, and Windows will create one for you on the harddisk. I'm creating a web page that I hope to have done over the xmas break with all my research on it that will explain why. I'll just say right now you need enough VM space to hold all the possible trimmings from your working set. Which could be substantial. To be on the safe side, keep your OS RAM and RAMdisk disk ram equal in size. You can experiment with a smaller RAMdisk pagefile. The worst that will happen is getting the popup error message. I found some very good evidence supporting my gradual slowdown theory caused by internal pagefile fragmentation. I'll have the reference on my web page when it's done. Can anyone tell me if XP slows down if left running 24/7, that a reboot cures? If not, perhaps one of the VM enhancements MS did to XP was to optimize the page placement algorithm to minimize internel pagefile fragmentation. I'm at almost 5 days uptime now with no slowdown whatsoever and stable as can be. Truly amazing. Oh, I loaded Perfmon finally, and am watching Memoryage Reads/sec. The hard page fault counter. MS says they should be under 20 a sec for good performance. Some of the things I do cause it to be in the 200 to 300 range for tens of minutes. I hit 5700 peak and averaged 3000 a sec for 10 seconds closing one of my apps down. When I used to have the pagefile on the harddisk, that app would take about 3 or 4 minutes to close down and slow the system down in the process. And people wonder why I'm excited about this... Dealer, again I have no affiliation with anyone. You are free to contact Cenatek and ask if you'd like.