I would like to respectfully disagree. For the typical single user environment it won't help, and might even hurt. www.silentpcreview.com did some tests on the raptor, and found that it was better to disable NCQ. In the first place, a single user will rarely have enough hdd intensive tasks going at the same time to build up a queue of any length. And, if they do, it is likely because they are doing sequential work where the next read is likely on the same track as the previous. In such a case, with ncq, the cache may not be primed with the remainder of the track. If you have several sequential access type jobs, it will probably be faster to run them sequentially instead of concurrently. All this is theory, and only a test of the actual environment will tell if NCQ has any meaningful effect on performance.