Quote Originally Posted by cabbspapp View Post
Edit: Noticed something. Using it right after booting results in a lower problem size. After letting it run for a bit, closing LinX and re-running it again sets it to a higher problem size, which gives me the increase in load temps, higher GFlop count, and higher memory usage.
It's because of W7. It still does some things after boot, but eventually releases 200-250MB more of RAM and settles at 900-950MB (from 6GB).
I don't mean this as a flaw of W7. I'm using W7x64 on my old Opty170/NF4 too and it works great. It drops from 600-700MB to 200-300MB when LinX is ran. I run and stop LinX 2-3 times just for Win to release memory and then run it with desired RAM amount.