Thanks Shadow, I will look at those.
I haven't done actual perf testing on the page file defrag, but one of the utilities said it was in about 3500 fragments. So my reason for wanting it defragges is that it just seems to me that of all files that one would want to be as efficiently read and written, the one that's supposed to mimick RAM would be at the top of my list. And with this thing in 3500 fragments, I just have this vision in my head of the disk head snapping back and forth when it pages, rather than sitting on a track and just sequentially stepping through the next tracks as it reads. Maybe disks these days are that physically predictable--like in the past when one could physically place the pagefile or other files of choice on the outer tracks, but that's just the vision in my head.
Anyway, I'm not as concerned if an .exe requires a couple of seeks to get the whole thing read for a one-time read, but on this particular machine (Dell laptop, core 2 duo 1.8ghz with 2 Gig ram), it hits the pagefile with regularity. I would prefer more RAM, but this is a company-issued one and that's the spec I'm stuck with for the laptop. Thankfully they stoked my desktop with 16 Gig so I don't have any worries on that box
--Jim