<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">GES on Windows 7</title><subtitle type="html">Focusing on Enterprise and OEM Deployment and App Compat Issues</subtitle><id>http://blogs.msdn.com/b/7/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/7/atom.aspx" /><generator uri="http://telligent.com" version="5.6.583.19431">Telligent Community 5.6.583.19431 (Build: 5.6.583.19431)</generator><updated>2009-10-07T02:47:00Z</updated><entry><title>Allowing Standard Users to Install Network Printers on Windows 7 without Prompting for Administrative Credentials</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2011/07/11/allowing-standard-users-to-install-network-printers-on-windows-7-without-prompting-for-administrative-credentials.aspx" /><id>http://blogs.msdn.com/b/7/archive/2011/07/11/allowing-standard-users-to-install-network-printers-on-windows-7-without-prompting-for-administrative-credentials.aspx</id><published>2011-07-11T18:07:00Z</published><updated>2011-07-11T18:07:00Z</updated><content type="html">Have you ever wondered if there is a way to allow a Standard Domain User to install network printers on their Windows 7 client computer without being prompted for administrative credentials? The following Blog Post which I have created provides you with the necessary information to guide you through the process and steps to enable this ability. 
 &amp;bull; This document Applies to Windows 7 Professional, Enterprise, and Ultimate x86 and x64 &amp;bull; This document contains information with regards to...(&lt;a href="http://blogs.msdn.com/b/7/archive/2011/07/11/allowing-standard-users-to-install-network-printers-on-windows-7-without-prompting-for-administrative-credentials.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10185264" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="Point and Print" scheme="http://blogs.msdn.com/b/7/archive/tags/Point+and+Print/" /><category term="robkier" scheme="http://blogs.msdn.com/b/7/archive/tags/robkier/" /></entry><entry><title>Enabling Printing for DOS Applications within Windows XP Mode VM on Windows 7</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/11/30/enabling-printing-for-dos-applications-within-windows-xp-mode-vm-on-windows-7.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/11/30/enabling-printing-for-dos-applications-within-windows-xp-mode-vm-on-windows-7.aspx</id><published>2010-11-30T18:32:00Z</published><updated>2010-11-30T18:32:00Z</updated><content type="html">You may find that your older DOS Applications will not work when installed on Windows 7. This can be due to a known problem on 32 bit Windows 7 according to Microsoft article 2408903 or you may be running a 64 bit edition of Windows 7. 
 2408903 An MS-DOS-based program that uses the MS-DOS protected mode interface crashes on a computer that is running Windows 7 
 http://support.microsoft.com/default.aspx?scid=kb;en-US;2408903 
 On Windows 7 64 bit edition, the NTVDM is not available. If you have...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/11/30/enabling-printing-for-dos-applications-within-windows-xp-mode-vm-on-windows-7.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10098521" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="XP Mode" scheme="http://blogs.msdn.com/b/7/archive/tags/XP+Mode/" /><category term="DOS" scheme="http://blogs.msdn.com/b/7/archive/tags/DOS/" /></entry><entry><title>Debugger Extensions Tips</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/06/08/debugger-extensions-tips.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/06/08/debugger-extensions-tips.aspx</id><published>2010-06-08T01:49:00Z</published><updated>2010-06-08T01:49:00Z</updated><content type="html">Windows Debugger Extension Tips. 
 Windows debugger is a powerful tool for diagnosing and examining drivers and applications in Windows. There is support for developers to create their own extensions within the debugger to assist them with common or even highly detailed analysis. The purpose of this blog is to show you how to get started and manage these extensions within Windows. The Windows debugger help file is your main resource but the three commands below are your starting point and should...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/06/08/debugger-extensions-tips.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10021331" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>The space bar is the new F8 when it comes to WinPE, Vista and Windows 7.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/06/02/the-space-bar-is-the-new-f8-when-it-comes-to-winpe-vista-and-windows-7.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/06/02/the-space-bar-is-the-new-f8-when-it-comes-to-winpe-vista-and-windows-7.aspx</id><published>2010-06-02T18:49:28Z</published><updated>2010-06-02T18:49:28Z</updated><content type="html">In Windows operating systems starting at Vista or greater and including WinPE you now have an alternative with more flexible options than just pressing F8 while booting. Next time you restart your system, right after the BIOS POST screen and just before you see the Windows boot screen, try pressing the space bar. If you timed it right or hit the space bar enough you'll now be at the Windows Boot Manager. 
 You can select which OS you'd like to boot, or you can hit F8 for the normal recovery options...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/06/02/the-space-bar-is-the-new-f8-when-it-comes-to-winpe-vista-and-windows-7.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10019034" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>System Image Recovery – When I have identical drives, how do I know which one to restore to?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/06/02/system-image-recovery-when-i-have-identical-drives-how-do-i-know-which-one-to-restore-to.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/06/02/system-image-recovery-when-i-have-identical-drives-how-do-i-know-which-one-to-restore-to.aspx</id><published>2010-06-02T18:29:43Z</published><updated>2010-06-02T18:29:43Z</updated><content type="html">The other day we ran into an interesting customer issue.&amp;#160; The customer had 4 identical drives on the system and had previously used Windows 7 Backup to create a system image of his system and boot partitions. He then ran into a problem where Windows was no longer bootable and he needed to restore from an image.&amp;#160; We had him boot into Windows Recovery Environment (WinRE) using his system repair disc (the original Win7 media could also have been used). Once in WinRE, we chose System Image...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/06/02/system-image-recovery-when-i-have-identical-drives-how-do-i-know-which-one-to-restore-to.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10019024" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Two Escalation Engineer positions available. Apply now!</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/06/01/two-escalation-engineer-positions-available-apply-now.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/06/01/two-escalation-engineer-positions-available-apply-now.aspx</id><published>2010-06-01T21:18:43Z</published><updated>2010-06-01T21:18:43Z</updated><content type="html">We Are Hiring System Center Escalation Engineer Want to debug the most difficult problems against the largest, most complex piece of software ever written? Are you proficient with ‘Managed Code’ and System Center Products: Configuration Manager, Operations Manager, Data Protection Manager, Virtual Machine Manager or Opalis Integration Server? Are you fluent with debugging &amp;amp; programming? Can you represent Microsoft in critical, time sensitive solution delivery? Writing code is easy, finding bugs...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/06/01/two-escalation-engineer-positions-available-apply-now.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10018519" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="News" scheme="http://blogs.msdn.com/b/7/archive/tags/News/" /><category term="Corey" scheme="http://blogs.msdn.com/b/7/archive/tags/Corey/" /><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /></entry><entry><title>Windows 7 introduces a new KMDF 1394 driver.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/05/12/windows-7-introduces-a-new-kmdf-1394-driver.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/05/12/windows-7-introduces-a-new-kmdf-1394-driver.aspx</id><published>2010-05-12T22:44:00Z</published><updated>2010-05-12T22:44:00Z</updated><content type="html">The Windows 7 1394 has a new default driver. The default binary is 1394OHCI.sys (KMDF) driver. Windows 7 also comes with, but not loaded, the Legacy Window OHCI1394.sys and 1394bus.sys drivers. Below is a listing of some of the key enhancements to be aware of from the new driver. 
 * 1394OHCI.sys is now the default Windows 7 2008/r2 driver. 
 ** Requires 1394A PHY or 1394b cards. 
 ** Offers Gap Count Optimization which provides a big improvement in performance. 
 As the legacy drivers are included...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/05/12/windows-7-introduces-a-new-kmdf-1394-driver.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10012093" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="davidwin" scheme="http://blogs.msdn.com/b/7/archive/tags/davidwin/" /><category term="1394ohci" scheme="http://blogs.msdn.com/b/7/archive/tags/1394ohci/" /></entry><entry><title>Enable Debugging in WinPE3.0 when booting from a Windows Deployment Services (WDS) Server</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/05/11/enable-debugging-in-winpe3-0-when-booting-from-a-windows-deployment-services-wds-server.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/05/11/enable-debugging-in-winpe3-0-when-booting-from-a-windows-deployment-services-wds-server.aspx</id><published>2010-05-11T16:34:00Z</published><updated>2010-05-11T16:34:00Z</updated><content type="html">Steps to enable debugging in WinPE 3.0 when booted from WDS. 
 You will need access to the folder structure on the WDS server. 
 If you need to enable boot debugging, modify RemoteInstall\boot\{arch}\default.bcd. Here is an example: 
 
 “bcdedit /store c:\RemoteInstall\boot\x64\ default.bcd /set {bootmgr} bootdebug on” 
 If you need to enable kernel debugging, modify RemoteInstall\boot\{arch}\Images\{WIM}.bcd. Here is an example: 
 REM to get the {GUID} look at “bcdedit /store c:\remoteinstall...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/05/11/enable-debugging-in-winpe3-0-when-booting-from-a-windows-deployment-services-wds-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10011067" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Micander" scheme="http://blogs.msdn.com/b/7/archive/tags/Micander/" /><category term="WDS" scheme="http://blogs.msdn.com/b/7/archive/tags/WDS/" /><category term="WinPE" scheme="http://blogs.msdn.com/b/7/archive/tags/WinPE/" /><category term="Debugger" scheme="http://blogs.msdn.com/b/7/archive/tags/Debugger/" /><category term="Debug" scheme="http://blogs.msdn.com/b/7/archive/tags/Debug/" /><category term="Windows Deployment Services" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+Deployment+Services/" /></entry><entry><title>Year 2038 problem</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/03/15/year-2038-problem.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/03/15/year-2038-problem.aspx</id><published>2010-03-15T11:43:00Z</published><updated>2010-03-15T11:43:00Z</updated><content type="html">This is a short blog aimed at bringing together a lot of great content already published by many individuals. The issue is the year 2038 issue, also known as Unix Millennium bug, “Y2K38” and many others. The issue is encountered when a user sets their system date to a year past 2038 (actually it seems the date has to be past January 19, 2038) weird things happen as a result of the date calculation that is performed by the OS. You see, most Unix-like computers calculate system time as the number of...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/03/15/year-2038-problem.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9978983" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Farhad" scheme="http://blogs.msdn.com/b/7/archive/tags/Farhad/" /><category term="Date" scheme="http://blogs.msdn.com/b/7/archive/tags/Date/" /><category term="2038" scheme="http://blogs.msdn.com/b/7/archive/tags/2038/" /></entry><entry><title>Creating an Application Compatibility Shim</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2010/01/22/creating-an-application-compatibility-shim.aspx" /><id>http://blogs.msdn.com/b/7/archive/2010/01/22/creating-an-application-compatibility-shim.aspx</id><published>2010-01-22T22:48:00Z</published><updated>2010-01-22T22:48:00Z</updated><content type="html">If you are trying to run an application that was created for XP or Vista and had problems running in Windows 7, you could always turn on compatibility mode for the executable on your machine. However if you are trying to create a shim that could be used on other machines as well, you could use the following instructions to create the shim and send it. It is a very small size and once executed, will always be associated with that executable on that machine. The example used here is for creating a...(&lt;a href="http://blogs.msdn.com/b/7/archive/2010/01/22/creating-an-application-compatibility-shim.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9952226" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="App Compat" scheme="http://blogs.msdn.com/b/7/archive/tags/App+Compat/" /><category term="Farhad" scheme="http://blogs.msdn.com/b/7/archive/tags/Farhad/" /><category term="Shim" scheme="http://blogs.msdn.com/b/7/archive/tags/Shim/" /><category term="ACT" scheme="http://blogs.msdn.com/b/7/archive/tags/ACT/" /></entry><entry><title>Set Network Location automation during Windows 7 Audit mode.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2009/12/03/set-network-location-automation-during-windows-7-audit-mode.aspx" /><id>http://blogs.msdn.com/b/7/archive/2009/12/03/set-network-location-automation-during-windows-7-audit-mode.aspx</id><published>2009-12-03T02:24:39Z</published><updated>2009-12-03T02:24:39Z</updated><content type="html">When automating installation of Windows 7 and booting to Audit mode you may see the “Set Network Location” prompting you to set Home, Public, or Work Network. If this is an issue for you and you would like to close this window. The following sample script worked for me to close the windows as part of automated installation. Copy the following to a text file and save as: Closewin.vbs: Set WshShell = Wscript.CreateObject(&amp;quot;WScript.Shell&amp;quot;) Do While Not Wshshell.AppActivate (&amp;quot;Set Network...(&lt;a href="http://blogs.msdn.com/b/7/archive/2009/12/03/set-network-location-automation-during-windows-7-audit-mode.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9931753" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="OPK" scheme="http://blogs.msdn.com/b/7/archive/tags/OPK/" /><category term="Micander" scheme="http://blogs.msdn.com/b/7/archive/tags/Micander/" /></entry><entry><title>Why won't my notebook resume from sleep for a scheduled task or event?</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2009/10/22/why-won-t-my-notebook-resume-from-sleep-for-a-scheduled-task-or-event.aspx" /><id>http://blogs.msdn.com/b/7/archive/2009/10/22/why-won-t-my-notebook-resume-from-sleep-for-a-scheduled-task-or-event.aspx</id><published>2009-10-22T20:59:00Z</published><updated>2009-10-22T20:59:00Z</updated><content type="html">You may have noticed that after installing Windows 7 on your portable computer, it will no longer automatically wake from sleep for scheduled events such as: Windows Updates A scheduled TV recording in Media Center Scheduled backups, defrag, etc. This is because starting with Windows 7, the default power management behavior for notebooks is to not automatically wake up the system for an scheduled event or task.&amp;#160; This was done to preserve battery life by not having the notebook wake up during...(&lt;a href="http://blogs.msdn.com/b/7/archive/2009/10/22/why-won-t-my-notebook-resume-from-sleep-for-a-scheduled-task-or-event.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9911685" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Alan" scheme="http://blogs.msdn.com/b/7/archive/tags/Alan/" /><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="netbook" scheme="http://blogs.msdn.com/b/7/archive/tags/netbook/" /><category term="notebook" scheme="http://blogs.msdn.com/b/7/archive/tags/notebook/" /><category term="Allow Wake Timers" scheme="http://blogs.msdn.com/b/7/archive/tags/Allow+Wake+Timers/" /><category term="Power Management" scheme="http://blogs.msdn.com/b/7/archive/tags/Power+Management/" /></entry><entry><title>ReadyBoost Changes in Windows 7</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2009/10/09/readyboost-changes-in-windows-7.aspx" /><id>http://blogs.msdn.com/b/7/archive/2009/10/09/readyboost-changes-in-windows-7.aspx</id><published>2009-10-10T01:27:00Z</published><updated>2009-10-10T01:27:00Z</updated><content type="html">ReadyBoost is a feature that was introduced in Windows Vista, allowing a flash memory device (such as a USB flash drive or SD card) to act as a memory cache. This assisted with increasing a PC's performance, especially when physical memory was limited or not upgradable. Windows 7 has improved the capabilities of ReadyBoost over Windows Vista, including: 
 
 Maximum cache size has been increased from 4GB to 32GB. Note that to utilize a memory cache of greater than 4GB, the flash drive needs to be...(&lt;a href="http://blogs.msdn.com/b/7/archive/2009/10/09/readyboost-changes-in-windows-7.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9905634" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Alan" scheme="http://blogs.msdn.com/b/7/archive/tags/Alan/" /><category term="Windows 7" scheme="http://blogs.msdn.com/b/7/archive/tags/Windows+7/" /><category term="ReadyBoost" scheme="http://blogs.msdn.com/b/7/archive/tags/ReadyBoost/" /><category term="netbook" scheme="http://blogs.msdn.com/b/7/archive/tags/netbook/" /></entry><entry><title>DiskPart.exe and managing Virtual Hard Disks (VHDs) in Windows 7</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2009/10/08/diskpart-exe-and-managing-virtual-hard-disks-vhds-in-windows-7.aspx" /><id>http://blogs.msdn.com/b/7/archive/2009/10/08/diskpart-exe-and-managing-virtual-hard-disks-vhds-in-windows-7.aspx</id><published>2009-10-08T03:20:00Z</published><updated>2009-10-08T03:20:00Z</updated><content type="html">In Windows 7, new commands have been added in DiskPart to allow for the creation and management of Virtual Hard Disks (.vhd files).&amp;#160; The DiskPart VHD management commands have been provided below in 2 sections – commonly used commands with examples and other commands.&amp;#160; It is assumed in each of the examples that DiskPart.exe has already been launched in an elevated command prompt. Creating a VHD The example below creates a 20GB dynamically expanding VHD called &amp;quot;test.vhd&amp;quot; and places...(&lt;a href="http://blogs.msdn.com/b/7/archive/2009/10/08/diskpart-exe-and-managing-virtual-hard-disks-vhds-in-windows-7.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9904659" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author><category term="Alan" scheme="http://blogs.msdn.com/b/7/archive/tags/Alan/" /><category term="DiskPart" scheme="http://blogs.msdn.com/b/7/archive/tags/DiskPart/" /><category term="Virtual Hard Disk" scheme="http://blogs.msdn.com/b/7/archive/tags/Virtual+Hard+Disk/" /><category term="VHD" scheme="http://blogs.msdn.com/b/7/archive/tags/VHD/" /></entry><entry><title>Windows 7 to say Hello World! on October 22nd.</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/7/archive/2009/10/07/windows-7-to-say-hello-world-on-october-22nd.aspx" /><id>http://blogs.msdn.com/b/7/archive/2009/10/07/windows-7-to-say-hello-world-on-october-22nd.aspx</id><published>2009-10-07T01:47:00Z</published><updated>2009-10-07T01:47:00Z</updated><content type="html">In preparation for the general availability of Windows 7, the OEM team has been preparing a new blog which will continue where Windows Vista Now left off. Unfortunately that means an end to the old blog, content there will no longer be updated and will remain live to serve as an archive. Starting today and moving into the future, look to this blog to continue on with Windows 7. We're also now on Twitter so follow us @MicrosoftGES , we'll be posting much more frequently from various sources with information...(&lt;a href="http://blogs.msdn.com/b/7/archive/2009/10/07/windows-7-to-say-hello-world-on-october-22nd.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9904070" width="1" height="1"&gt;</content><author><name>EPSOEMFT</name><uri>http://blogs.msdn.com/EPSOEMFT/ProfileUrlRedirect.ashx</uri></author></entry></feed>