VirnetX, a software corporation founded in 2005, has prevailed in a patent-infringement lawsuit accusing Microsoft of willfully infringing on two patents for automatic and secure Virtual Private Network (VPN) technology. The Texas jury recommended an award of $105.75 million, which is less than half of the $242 million that VirtnetX asked for. Still, the verdict was a very positive one for VirtnetX. "Our clients are very happy with today's verdict," said VirnetX counsel Douglas Cawley in a statement. "We hope this decision sends a clear message to patent infringers everywhere that they will be held responsible for wrongly profiting off the hard work of others."

Microsoft is not happy with the decision and plans to fight on. "We are disappointed by the jury's verdict," a Microsoft spokesperson told Ars. "We respect others' intellectual property, and we believe the evidence demonstrated that we do not infringe and the patents are invalid. We believe the award of damages is legally and factually unsupported, so we will ask the court to overturn the verdict." 

The case was tried in the US District Court for the Eastern District of Texas, the favored venue for patent infringement cases.

In its original lawsuit filed in February 2007, VirnetX alleged that Microsoft Office Communicator included technology covered by its patent No. 6,502,135 and that Windows Meeting Space infringed its patent No. 7,188,180. The $105.75 million breaks down as $71.75 million for the former and $34 million for the latter, according to the Scotts Valley, California company. VirnetX acquired the rights to the patents from the government-contracting company Science Applications International in 2006. Microsoft accused VirnetX of being a patent troll during the trial, and it was revealed that the company's business model was based on winning the lawsuit, though it does have a licensing agreement with VeriSign.

Read the comments on this post

Internet Explorer General Manager Dean Hachamovitch all but confirmed today that the next version of Microsoft's Web browser, Internet Explorer 9, will not be supported on Windows XP.

Hachamovitch stopped short of explicitly saying that XP would not be supported, but said that building a "modern browser" required a "modern operating system." IE9 will be heavily dependent on hardware acceleration, courtesy of its use of Direct2D and DirectWrite; neither API is available on Windows XP.

That IE9 would use these features has been known since last year's PDC, and so the lack of XP support should come as a surprise to few. Nonetheless, there are sure to be some who will gripe that the newest browser (not likely to hit until next year at the earliest) won't be available for a decade-old operating system.

Read the comments on this post

Microsoft today released the Windows Internet Explorer Platform Preview to the public. The release is meant to demonstrate the capabilities of Internet Explorer 9 to Web developers while at the same time providing feedback to the IE9 team. Microsoft says it is committed to updating the Platform Preview to keep a more effective rhythm for discussion, and it will be updated every eight weeks or so. Microsoft will share feedback with standards-setting bodies in addition to using it for internal development.

The Platform Preview is a minimal wrapper: it's not a full-fledged browser. It has no tabs. It has no address bar. It has no back button. So what is included? Everything that Web developers need to see: the rendering engine, of course, as well as the new JavaScript engine, hardware acceleration features, and the developer tools. The IE9 team told Ars that each update will use one of the latest internal engineering builds, at which point the feedback loop will start again.

Microsoft has been quite explicit on the matter: Windows Phone 7 Series is being designed first and foremost for the consumer market. The result is the emphasis on a strong, consistent, effective user interface, possibly at the expense of functionality; Microsoft wants to have this thing out in time for the "holiday season" this year, so there's a limited window for further development, at least for the initial release.

That said, the phone does have features aimed at the enterprise market. Obviously, there's Exchange support, with ActiveSync, providing push mail, address book sync, and all those features that we know and love. In common with Outlook 2010, Windows Phone 7 Series also seems to support multiple Exchange servers concurrently. I say "seems" because it didn't quite work when we tried, but that seemed to be due to a bad password rather than any fundamental flaw—the phone was happy to accept the configuration and created two distinct Outlook Tiles on the Start page, so it looked like it was doing the right thing.

The Microsoft Translator team has given up and concluded that "no matter how many machines you throw at translation, it is still impossible to get the correct, error-free, contextually accurate translation every time." Microsoft's solution to this problem is the Collaborative Translations Framework, which supposedly combines the scale and speed of automatic machine translation with the accuracy and context awareness of human translation.

At MIX 2010, Microsoft Translator API version 2 was announced. In addition to the collaborative features, version 2 includes a batch interface to translate large amounts of data, support for communicating with the service securely via SSL, and a "Translate-and-Speak" feature (text-to-speech functionality). The translation APIs are available at no cost to developers and partners in SOAP, HTTP, and AJAX flavors so that developers can choose the one that best fits their requirements. All you need to get started is a Bing Developer AppID.

Since the Microsoft Translator team works closely on Bing, the Translate-and-Speak functionality will be available on the Bing Translator user site after you hit translate (you should notice a speaker icon that you can click on to hear your translation). Currently, this feature is only available in seven of the 30 languages Bing supports: English, German, Spanish, French, Italian, Portuguese, and Russian.

The Microsoft Translator widget, released just under a year ago, offers real-time, in-place translations on your website into the languages your users choose. Built on top of the new translation API, version 2 of the translator widget also adds collaborative features that help tailor the translations of a website. This means website owners can not only offer their site in multiple languages, but they can also ask their community or professional translators to improve those translations of their site's content.

Each MIX10 attendee received an exclusive invite code in their attendee bags to enable Collaborative Translations features in their widget. If you are not attending MIX, you can add yourself to the Collaborative Translations feature invite list after you get the widget.

Microsoft still plans on polishing the translation widget, toolbar, and alternatives UI as well as analytics for site and app owners based on user feedback. There is also more customizability on the way, such as limiting the number of languages site owners can show as part of the widget. In addition, Microsoft is working on making the Silverlight translator control available as part of the Silverlight toolkit release that will ship when Silverlight 4 goes final.

All this new functionality is still considered prerelease, so you'll want to check out the known issues list before diving in. You can submit bugs and suggestions on the MSDN forums or via This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Read the comments on this post

The big theme at Microsoft's MIX10 developer conference today was developing for Windows Phone 7 Series, and key to this was the new Silverlight 4. For the first time, Microsoft showed off third-party applications for the forthcoming phone platform, and talked about how third-party applications integrate with the platform.

Silverlight is becoming increasingly widely available for the browser, with Microsoft claiming 60 percent of all Internet devices now support it (up from 45 percent in October last year). The new version, available as a Release Candidate today with a final version next month, boasts new features to make it more useful for developing both in-browser and standalone applications, including support for microphones and webcams, printing, and the clipboard.

Microsoft confirmed on Tuesday a new flaw affecting version 6 and 7 of its Internet Explorer web browser that could allow remote code execution. The security advisory noted that targeted attacks using the flaw were already in the wild.

This information was confirmed by McAfee, reporting that exploitation of the flaw was originating from the domain topix21century dot com over both HTTP and HTTPS. The drive-by attacks install a backdoor which connects to a command-and-control server.

Analysis by Symantec reveals that the exploit works effectively on IE 6. IE 7 tended to crash instead, and IE 8 is, as stated in the Microsoft advisory, immune. The attack loads some malicious code, and then makes repeated changes to the HTML document eventually provoking execution of the malicious code.

The best solution is to upgrade to IE 8, as one of the many improvements found in this browser also seals off the security hole. Failing that, enabling Data Execution Prevention in IE 7 should provide some level of mitigation, as the current exploits do not circumvent DEP (though they could probably be combined with DEP bypass techniques). Removing access to the file iepeers.dll using either of the mechanisms described in Microsoft's advisory prevents Internet Explorer from loading the flawed code, but may also break print and web folder functionality. Finally, disabling of scripting and ActiveX in the Internet and Local Intranet security zones should also provide protection against exploitation.

Microsoft has still made no indication whether this flaw will receive an out-of-band update, but with exploits in the wild and documented analysis of the exploit, clearly this flaw is something that needs fixing, and soon.

Read the comments on this post

The CodePlex Foundation has announced the arrival of several new board members, including Jim Jagielski, the Chief Open Source Officer of SpringSource. Jagielski, who was one of the original cofounders of the Apache Software Foundation (ASF), brings a lot of credibility and leadership experience to the CodePlex Foundation.

When the CodePlex Foundation was established by Microsoft last year, an interim board of directors was assembled to help get the organization off the ground while permanent board members were being chosen. A number of the interim board members, including Novell's Mono project leader Miguel de Icaza, will be turning their seats over to new representatives. Former Microsoft open source evangelist Sam Ramji, currently VP of strategy at Sonoa, will be remaining on the board, along with Microsoft .NET Framework program manager Davies Boesch.