Actually, neither Vue nor VuePro are HT aware. But they -are- MP aware....which gets into the issue I mentioned about the app making calls for a second processor when there isn't one. It isn't an issue with Vue; hyperthreading was =designed= to appear to give the appearance of a second processor for just about free, when it isn't. Remember the applictation depends on the OS to tell it what resources it has, and there have been a =lot= of sites that posted screencaps that showed both Win2k and WinXP as mis-identifying an HT enabled P4 as a dual processor. Adobe products (at least the latest versions) have all been written to properly use HT; the reason why video people tend to swear by P4's. Turn HT off, and the AMD chips performance either surpasses, or gets awfully close, to the P4 clocking in some cases almost 30% faster (keep in mind that the AMD numbering system doesn't reflect actual clock speed; a 1800+ actually clocks in at 1.53 ghz by the system clock. My Athlon 64 3000+ is actually only clocking at just over 2 ghz. Remember the Athlon series isn't a clone of the P4; AMD snagged a couple of the movers behind the DEC Alpha chip when HP went stupid; Athlons of any stripe have a radically different structure to the registers and the pipeline structure). The big modelling packages that run on X86-32 hardware have the HT optimizations inserted as of the last (or next to last) build. From what I've read, it would be harder to make Vue and VuePro HT aware than it would be to recompile them for iAMD-64....and since AMD is getting ready to drop honest to God dual cores in one package sometime in the 3rd quarter this year...with rumored backwards compatibility with some existing boards...