The new Vengeance M60 is geared for FPS players with an innovative "Sniper" button while the M90 targets MMO players who'll use as many configurable buttons as they can find. Do they work out in practice, though? Read on for our thoughts on these two new mice.

So how does the ASUS P1 fare in our short look? While we don't have the necessary equipment to test many aspects of the projector, for the intended purpose it delivers what ASUS has promised. Read on for our thoughts on the device.

The timing is impeccable as we're fully expecting to start seeing MSM8960 based phones next week at MWC, and we've been telling you to hold off on any smartphone purchases until the 8960's arrival. Today we're finally able to give you an indication of just how fast Qualcomm's next-generation Snapdragon S4 will be. Read on!

Lian Li aims to offer a lighter, more austere shell for high performance systems in the PC-90, and we can tell you they've been very successful. The PC-90 is also better than our prior experiences with Lian Li in that it performs right about where you'd expect. Read on for the full details.

Today we have Corsair's Vengeance K60 and K90 gaming keyboards in house. Corsair opts to use Cherry MX Red switches in an effort to find a more suitable balance between typing and gaming needs, and they bring a little more style and class than we're used to seeing in gaming peripherals. Read on for our impressions of the K60 and K90 keyboards.

Was Alienware able to cram a fully-powered machine in this tiny chassis, or were too many sacrifices made? Just what exactly can you fit into this console-esque chassis? Read on for our full analysis!

It’s very similar to the CoreHT we reviewed before, even sharing nearly the same specs. The one major difference: there’s two 500GB HDDs in the place of one, configured in RAID 0. Other than that, there’s the same mobile Sandy Bridge internals, headlined by the HM67 chipset and Core i5-2410M processor. Read on to find out if this update addresses our earlier concerns of if we're still left wanting more.

Today AMD will be launching two cards based on the Cape Verde GPU: the Radeon HD 7750, and the Radeon HD 7770 GHz Edition. As the Juniper based 5700 series never got a proper Northern Islands successor, this is the first real update for the x700 series since the launch of the 5700 series in October of 2009. Given the success of the 5700 expectations are going to be high, and to fulfill those expectations AMD will be bringing to bear their new GCN architecture along with a full node jump with TSMC’s 28nm process. But will this be enough to enable the 7700 series to replicate the success of the 5700 series? Let’s find out.

Droid RAZR MAXX (left), Droid RAZR (right)

The Droid RAZR MAXX is quite simply a Droid RAZR with a larger internal battery, 1.8 times the size of the original, to be exact. The result is a device that does internal batteries the right way - if it's going to be sealed inside, it should at least be huge. Read on for our full RAZR MAXX review.

The VAIO Z2 has a lot going for it, but is it worth the heavy price tag? Outside of the specs on paper—which admittedly look quite good—what's the build quality like on the Z2, how does it fare in day to day use, and are there any concerns or benefits that might not immediately stand out? We'll cover that and more as we put this laptop to the test.

Those looking for maximum efficiency can now set their sights on 80 Plus Platinum PSUs, which will be new halo market for high-end—and high cost—power supplies. To reach the necessary efficiency levels, some improvements are necessary that can change some of the core characteristics of a power. Improved resonant topologies, new MOSFETs for synchronous rectifying, higher switching frequencies, better drivers, and low-resistance conduction paths are just some of the things we'll see with 80 Plus Platinum. We're naturally eager to see what the new models can bring to the table, and Enermax sent us their Platimax 750W model, which uses an optimized Modu87+ design. Read on to find out if Enermax is the new efficiency king, and how it performs in other metrics.

A few weeks ago OCZ released a firmware update for its Octane drives that promised a significant increase in 4KB random write performance. Read on for our analysis of the firmware update!

Up until now, we've operated under the assumption that a new version of Windows called Windows 8 would be released this year, and that it would run on both x86 (32-bit and 64-bit - throughout this article I'll use x86 to refer to both architectures) and ARM processors - Sinofsky's post makes it clear that the ARM version of Windows, officially referred to as Windows on ARM (WOA), is considered to be a separate product from Windows 8, the same way that products like Windows Server and Windows Embedded share a foundation with but are distinct from Windows 7. Windows on ARM has a "high degree of commonality" and "very significant shared code" with Windows 8 - much of the user's interaction with the OS will be the same on either platform, and much of the underlying technology we've seen in our Windows 8 coverage so far will be present in both versions, but they're distinct products that will be treated differently by Microsoft.

This post is quite lengthy and represents what is likely to be our best look at WOA for at least a little while - we'll get to see some of its features in the Windows 8 Consumer Preview when it is released at the end of the month, but for now Windows on ARM is only being tested internally, and on customized hardware that will be sent to some developers and hardware partners at about the same time. It will be a little while before we see anything remotely similar to shipping hardware.

The Windows Desktop, Office, and x86 Apps

One of the biggest recurring questions I've seen about Windows on ARM is whether the standard Windows desktop would be available for use on those devices as it will be on Windows 8 machines - the answer is yes, it definitely will be. The desktop can be invoked from the Start screen, and once there users can perform standard Windows Explorer operations, launch the desktop version of Internet Explorer, and other tasks either via touch (for which Explorer has apparently been optimized) or via keyboard and mouse input. The desktop will only consume resources when it is launched, meaning that there are no performance or battery life implications for users who stick with the Metro interface for everything - the desktop is there if you want it, but one of Microsoft's stated goals with the Metro interface is to make it so that you don't need to use the desktop as a fallback.

Microsoft will also be bundling versions of Microsoft Word, Excel, PowerPoint, and OneNote with Windows on ARM systems. These Office apps will be a part of the new Office 15 family of products (suggesting, but not guaranteeing, that we may see a full x86 version of that suite before the end of the year as well), but will be touch-optimized versions of the applications rather than ports of the standard suite. The Windows on ARM products will "maintain fidelity" with their x86 counterparts (meaning that a file created in Word or Powerpoint on an x86 machine will look the same on an ARM machine), but will otherwise be redesigned to fit the platform - an early version of Excel is shown above.

That said, Microsoft is firm in its insistence that it will not support running, emulating, or porting existing x86 apps on the Windows on ARM desktop - apps can only be downloaded and installed through the Windows Store, and only apps written to target the new WinRT APIs can be distributed through the store (however, the store will be able to distribute and update both ARM and x86 versions of apps in the event that the app uses any code native to either architecture). Microsoft suggests that current Windows developers should be able to take significant bits of their existing code and wrap them in a Metro layer, but acknowledges that bringing over existing apps will require a bit of work - WinRT is clearly the wave of the future where Windows is concerned, but it'll be up to individual developers to decide how, when, and if to bring their programs over.

Supported Devices and Release Date

Windows on ARM is being written to run on ARM SoCs from NVIDIA, Qualcomm, and Texas Instruments, and it will only be available on devices designed to run it - you won't be able to buy a license for Windows on ARM and install it on an existing tablet, or a tablet designed to run Android. Microsoft is working with partners to deliver compatible hardware, and the company's goal is to start shipping devices running Windows on ARM at the same time as x86 devices running Windows 8 (currently slated for late this year).

In addition to SoC type, Microsoft will have a set of broad guidelines for Windows on ARM tablets that are similar to those for current Windows phones (the "chassis specification," in Microsoft parlance) - likely a set of supported screen resolutions and a list of required hardware devices designed to provide a middle ground between the uniformity of the iPad and the diversity-to-the-point-of-insanity of Android tablets. On Windows phones, these requirements are in place to give consumers some choice while also limiting developer headaches and ensuring a standardized look and feel across different devices from different manufacturers - the requirements for Windows on ARM will have the same aims, and we'll talk a little bit more about some of the hardware that will be common to WOA devices later on in this post.

In treating Windows on ARM as a separate product, Microsoft has left itself some wiggle room to let its release date slip without holding up Windows 8 (wiggle room is very important to the post-Vista Windows team, and they generally don't give hard dates unless they expect to be able to hit them). Microsoft obviously wants to ship before the end of the year because, let's face it, they don't want to give Apple, Google, Amazon, and the rest another holiday season all to themselves, but at this point in the game a botched or half-baked release in time for Christmas could actually be worse for Microsoft's market and mindshare than a well-executed release a few months later. Expect a concurrent release with Windows 8, but know that Microsoft hasn't yet completely committed to it.

When it is shipped, Windows on ARM should come as a single edition of Windows from a feature standpoint (though the company notes that no decisions regarding new Windows product editions have been finalized) - Microsoft promises to "adjust the features ... such that [WOA] is competitive in the marketplace and offers a compelling value proposition to customers of all types." That doesn't tell us much, but I think we should expect the consumer-oriented features that you'd find in a Home Premium version of Windows along with business-minded features (like domain joining and device encryption) thrown in to increase WOA's appeal to enterprises. Whether the decision to ship a single Windows on ARM SKU will have any effect on the x86 version's army of different editions remains to be seen.

Drivers, Updates, and Hardware

So, since Windows on ARM will only be available on devices designed specifically for it, Microsoft can actually keep track of what hardware WOA devices are guaranteed to be using. This means that all software, from OS patches to device firmware to specific drivers, can and will be distributed using Windows Update. Apple has achieved something similar in OS X - Macs are many and subtly varied, especially when you take multiple model years into consideration, but ultimately there is a finite set of hardware in the field, and Apple can keep every Mac in use up-to-date with drivers, firmware, and OS updates through Software Update, rather than the broad array of different first and third-party updaters required to patch those separate elements on an x86 Windows box (and I promise that I'm just comparing the two to give you a frame of reference, not because I consider one system to be inherently superior to the other).

To reduce the number of drivers it will have to keep up to date, Microsoft is relying heavily on "class drivers" to support hardware in both WOA and Windows 8 - for those of you just tuning in, a class driver is designed to support all hardware manufactured to certain standards, rather than targeting specific devices. They're why you can freely plug in different USB keyboards and flash drives to a Windows computer and have them recognized by the machine without needing to pop in a driver disk first.

A lot of the work Microsoft is putting into class drivers is also applicable to Windows 8 - we've already looked at new class drivers for USB 3.0 controllers, mobile broadband chips, and motion sensors, and we should also see class drivers for printers, Bluetooth, Embedded MultiMediaCard (eMMC) storage, and drivers for different busses and input devices (like the Windows, power, and volume buttons).

Where Microsoft can't create class drivers, it's trying to enforce some common specifications - WOA devices will all have DirectX-capable GPUs and drivers, which will power Metro apps, the Windows UI, and GPU acceleration in Internet Explorer among other things. This baseline has enabled Microsoft to improve on the fallback software GPU driver to enable a nicer-looking display on devices without a specific driver (and also for system diagnostic and information screens). This new soft GPU driver will also be available in Windows 8, where it will replace the standard VGA driver that has been a part of Windows for just about as long as Windows has been around.

WOA systems will also require UEFI firmware and Trusted Platform Module (TPM) hardware across the board to support its secure boot and data encyption features, both of which will also be available to Windows 8 devices with the correct hardware (TPMs have been used to encrypt hard drives with BitLocker since Windows Vista and UEFI is slowly replacing BIOS in OEM PCs, but Windows 8 should push the adoption of both in a wider range of computers).

Conclusions

To see what Microsoft is trying to do with Windows on ARM, the most applicable template to examine is the one the company followed with Windows Phone 7. In both cases, Microsoft is entering an established market where competitors have established footholds through very different strategies (in each case, Apple and its tighty-controlled iOS on one end, Google with its infinitely malleable Android on the other, and a few other competitors fighting for scraps in between) and has tried to forge a middle path. Windows Phone 7 has been a bit of a slow starter because of Microsoft's low profile in the smartphone field and because of some lackluster handsets, but the platform has some very vocal fans - if the company can achieve a similar balance in Windows on ARM and get it to market on competitive hardware by the end of the year, that (combined with Android's relative weakness in the tablet market so far) might just be enough to establish Windows as a major player in the tablet space.

As usual with these Building Windows post summaries, I've relayed and distilled the most pertinent information for Windows users and enthusiasts here. If you'd like to read the full post, which also includes some details about how Microsoft is testing Windows on ARM in its labs and some of the more technical details involved in "porting" Windows from x86 to ARM, it is linked below for your convenience.

Source: Building Windows 8 blog

Back in 2008, however, we discussed the elements of a thorough server review. Our list of important areas to test included ERP, OLTP, OLAP, Web, and Collaborative/E-mail applications. Looking at our initial Interlagos review, several of these are missing in action, but much has changed since 2008. The exploding core counts have made other bottlenecks (memory, I/O) much harder to overcome, the web application that we used back in 2009 stopped scaling beyond 12 cores due to lock contention problems, the Exchange benchmark turned out to be an absolute nightmare to scale beyond 8 threads, and the only manageable OLTP test—Swingbench Calling Circle—needed an increasing number of SSDs to scale.

The ballooning core counts have steadily made it harder and even next to impossible to benchmark applications on native Linux or Windows. Thus, we reacted the same way most companies have reacted: we virtualized our benchmark applications. It's only with a hypervisor that these multi-core monsters make sense in most enterprises, but there are always exceptions. Since quite a few of our readers still like seeing "native" Linux and Windows benchmarks, not to mention quite a few ERP, OLTP, and OLAP servers are still running without any form of virtualization, we took the time to complete our previous review and give the Opteron Interlagos another chance.

When I first started covering SSDs four years ago I became obsessed with the idea of migrating nearly every system over to something SSD based. The first to make the switch were our CPU testbeds. Moving away from mechanical drives ensured better benchmark consistency between runs as any variation in IO load was easily absorbed by the tremendous amount of headroom that an SSD offered. The holy grail of course was migrating all of the AnandTech servers over to SSDs. Over the years our servers seem to die in the following order: hard drives, power supplies, motherboards. We tend to stay on a hardware platform until the systems start showing the signs of their age (e.g. motherboards start dying), but that's usually long enough that we encounter an annoying number of hard drive failures. A well validated SSD should have a predictable failure rate, making it an ideal candidate for an enterprise environment where downtime is quite costly and in the case of a small business, very annoying.

Our most recent server move is a long story for a separate article but to summarize the move, we recently switched hosting providers and data centers. Our hardware was formerly on the east coast and the new datacenter is in the middle of the country. At our old host we were trying out a new cloud platform while our new home would be a mixture of a traditional back-end with a virtualized front-end. With a tight timetable for the move and no desire to deploy an easily portable solution at our old home before making the move we were faced with a difficult task: how do we physically move our servers half way across the country with minimal downtime?

Thankfully our new host had temporary hardware very similar in capabilities to our new infrastructure that they were willing to put the site on as we moved our hardware. The only exception was, as you might guess, a relative lack of SSDs. Our new hardware uses a combination of consumer and enterprise SSDs but our new host only had mechanical drives or consumer grade SSDs on tap (Intel SSD 320s).

In preparing for this move I realized we hadn't publicly discussed the performance and endurance issues associated with using consumer SSDs in an enterprise environment. What follows is a discussion of just that. Read on...

Codenamed Cherryville, Intel's SSD 520 would go through a full year of validation before Intel would sign off on the drive for release. In fact, it was some unresolved issues that cropped up during Intel's validation that pushed Cherryville back from the late 2011 release to today.

Intel's strenuous validation will eventually make SandForce's drives better for everyone, but for now the Cherryville firmware remains exclusive. Intel wouldn't go on record with details of its arrangement with SandForce, but from what I've managed to piece together the Intel Cherryville firmware is exclusive for a limited period of time. That exclusivity agreement likely expires sometime after the SF-2281 is replaced by a 3rd generation controller. There are some loopholes that allow SandForce to port bug fixes to general partner firmware but the specific terms aren't public information. The important takeaway is anything fixed in Intel's firmware isn't necessarily going to be fixed in other SF-2281 based drives in the near term. This is an important distinction because although Cherryville performs very similarly to other SF-2281 drives, it should be more reliable.

Read on for our full review of Intel's SSD 520.

AMD's Rory Read Outlines AMD's Future Strategy
AMD Outlines HSA Roadmap: Unified Memory for CPU/GPU in 2013, HSA GPUs in 2014 
AMD is Open to Integrating 3rd Party IP in Future SoCs
AMD's Financial Analyst Day 2012 - Mark Papermaster, SVP & CTO Presentation 
AMD: Flexible Around ISA
AMD Nods at Shorter Design Cycles, More Synthesized Designs
What AMD Views as Important: Tablets, Servers, Notebooks & GPUs
AMD & Compal Show Off 18mm Trinity Notebook 
AMD's 2012 - 2013 Client CPU/GPU/APU Roadmap Revealed 
AMD's 2012 - 2013 Server Roadmap: Abu Dhabi, Seoul & Delhi CPUs
AMD is Ambidextrous, Not Married to Any One Architecture, ARM in the Datacenter? 
AMD's Tablet Architectures: Hondo at 4.5W, Future Sub-2W SoC

Read on for our summary and analysis of AMD's new strategy.

Of course AMD has always produced multiple video cards from their high-end GPUs, and with Tahiti this was no different. The second Tahiti card has been waiting in the wings for its own launch, and that launch has finally come. Today AMD is launching the Radeon HD 7950, the cooler, quieter, and cheaper sibling of the Radeon HD 7970. Aimed right at NVIDIA’s GeForce GTX 580, AMD is looking to sew up the high-end market, and as we’ll see the Radeon HD 7950 is exactly the card to accomplish that.

Today, CyberLink is introducing PowerDVD 12 along with an updated Android / iOS app. With the Blu-ray functionality not needing any updates, most of the attention has been focused on the mobile apps and streamlining the user experience with the PC player. How good are the changes? Are they enough to make us change our opinion of PowerDVD? Read on for our review.

Which leads us to today's build, which AVADirect dubs their Silent Gaming PC. Their builders have tried to take a standard powerhouse boutique machine and kill the noise. Did they succeed, or is the Silent Gaming PC merely the sum of its parts?

There was a bit of chatter this past fall when AOC introduced the i2353 display, which is an LED backlit IPS panel with an MSRP under $200. Had the prices of IPS panels and components finally fallen to the point where they would be able to start forcing companies to transition to them away from TN for their affordable monitor lines? To find out if the AOC monitor was still able to offer a good level of performance at this price point we requested a review sample, which they quickly provided.

Next week we’ll be taking a look at CrossFire performance and the performance of AMD’s first driver update. But in the meantime we wanted to examine a few other facets of the 7970: the impact of PCIe bandwidth on performance, overclocking our reference 7970 (and the performance impact thereof), and what AMD is doing for anti-aliasing with the surprise addition of SSAA for DX10+ along with an interesting technical demo implementing MSAA and complex lighting side-by-side. So let’s get started.

A four-module, eight-core Bulldozer

The bigger issue with Bulldozer isn't one of core semantics, but rather how threads get scheduled on those cores. Ideally, threads with shared data sets would get scheduled on the same module, while threads that share no data would be scheduled on separate modules. The former allows more efficient use of a module's L2 cache, while the latter guarantees each thread has access to all of a module's resources when there's no tangible benefit to sharing.

This ideal scenario isn't how threads are scheduled on Bulldozer today. Instead of intelligent core/module scheduling based on the memory addresses touched by a thread, Windows 7 currently just schedules threads on Bulldozer in order. Starting from core 0 and going up to core 7 in an eight-core FX-8150, Windows 7 will schedule two threads on the first module, then move to the next module, etc... If the threads happen to be working on the same data, then Windows 7's scheduling approach makes sense. If the threads scheduled are working on different data sets however, Windows 7's current treatment of Bulldozer is suboptimal.

AMD and Microsoft have been working on a patch to Windows 7 that improves scheduling behavior on Bulldozer. The result are two hotfixes that should both be installed on Bulldozer systems. Read on for our take on what these hotfixes do to Bulldozer's Windows 7 performance.

NZXT is a well known provider of "eye-catching" cases and peripherals, but like many other brands they offer power supplies as well. These include the HALE90 series, their first 80 Plus Gold product to hit the market. While the HALE90 targets the high-end audience, NZXT also wants to cater to midrange users, and for that market they have their new HALE82 series that covers wattages from 650W to 850W. The rated output makes these models good for high-end single GPUs as well as moderate SLI and CrossFire systems. Features such as 80 Plus Bronze certification and modular cables are common these days, but such features say little about how good a PSU really is. Today, we're testing the 650W and 750W models, with our usual results on the following pages.

The USB CEC adapter from Pulse-Eight aims at solving this issue. As long as you have a TV or receiver compatible with HDMI CEC, you can use that remote to control XBMC on your HTPC, or, with software support, also be able to control other applications. What exactly is CEC and how does it work? What is inside the Pulse-Eight's USB CEC adapter, and how does one get it up and running with XBMC Eden? Can the USB CEC adapter be built into future HTPCs? Read on to find out the answers.