Windows Vista Enters Extended Support
yuhong writes "On April 10, the second Tuesday of April, Windows Vista will exit Mainstream Support and enter Extended Support. This means that no-charge (free) support will end, no further service packs will be created, nor will future IE versions (such as IE10) be available for Vista. Also, no new non-security hotfixes will be created or be available without an Extended Hotfix Support Agreement (EHSA). This will last for 5 years before support for Vista completely ends in 2017."
are the idiot sheeple who use what they do not understand and refuse to learn about. They are the only reason Micro$haft hasn't gone bankrupt.
I'm apparently way behind the times -- being perfectly happy with Windows XP!!!!
No patches == more zombies?
Will be interesting (and possibly annoying) to see if this end of patches is accompanied with a surge in botnet based spam and such.
Dear Laura, I am writing to you to say that I miss you very much and I love you. Every day without you is so sad, please you are the only thing I care about in the whole world. Let's get married and live in Jamaica forever together and I will make pancakes or omelets for you every morning and kiss you and call you cute names. Please call, Bobbbbb.
UNITE with the Campaign for a Free Internet because today, our future begins with tomorrow!
And yet my company, a major Fortune 500 member, lives on with XP
Also, no new non-security hotfixes will be created or be available without an Extended Hotfix Support Agreement (EHSA).
Also, nobody uses Vista anyways. It's either XP or Win7 all the way.
When are they going to put a mercy bullet in XP .. I go to major corporations and find that they are STILL on XP .. living off the Extended Support contracts. The IT departments apparently just cant justify moving to Windows 7 or Vista.
Take XP off Extended Life Support.
disk and installed in on a spare latop not too long ago. Shit that thing flies even compared to lxde distros.
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
I mean, really?
"Eve of Destruction", it's not just for old hippies anymore...
My next operating system choice will not be Microsoft.
I purchased Vista in 2008. This is way too early for extended support.
If MS wants to cut support for Vista - fine, just give vista customers a free bounce to 7 and support is fixed.
7 is what Vista should have been anyway and 7 should have been a free upgrade for Vista users.
This means that no-charge (free) support will end,
Windows support is only ever free if your time has no value.
I am writing this on a laptop (TabletPC) running Windows XP. It's a 5-year-old machine, but aside from the battery life getting low (a $40 fix I'm considering, for convenience) it does everything I need a laptop to do. It runs *office. It runs Chrome. It runs Manga Studio (my main drawing program) with full support for the built-in stylus/digitizer. I have no reason whatsoever to replace it. I'm familiar with Windows 7; I work with it at the office. If I had a desktop PC instead of an iMac, I'd probably use W7 on that. But I cannot think of a single feature of W7 that I would benefit from on this computer, and I can think of several factors (speed, mostly) that argue against upgrading. Windows is just an OS: software that acts as an intermediary between my applications and the hardware. WXP does that job quite adequately. To "put a mercy bullet in WXP" is nothing more than deliberate, willful, unnecessary obsolescence.
http://alternatives.rzero.com/
I've been dreading the day I'd have to leave Vista behind!
And end support for Windows Vista altogether. Let's face it, even "upgrading" from Windows XP to Vista is basically the same thing as "downgrading" to Windows 3.11 For Workgroups. Except Windows 3.11 had far fewer issues that the user had to contend with.
I'm a developer at an ISV. Personally, I am waiting for XP to go. Microsoft has some great technology (WWSAPI, SQL Server 2012 LocalDB) that looks like it will solve some of the problems we need to solve with our application, but it's not available on XP. (Technically WWSAPI is, if you're willing to pay for the support contract.)
As it stands, while XP is still supported (mainstream, extended or otherwise) and we have customers on it we are unable to use these new technologies.
In the context of my job I don't think Vista is any different from 7 in terms of the technology available and the support effort.
At home I find 7 to be superior to XP and Vista. I don't think Vista fills any niche, XP has the 5-year-old-low-powered-device market, but anywhere else really should be using 7.
I'll subscribe to Slashdot when I see a month without a dupe, a typo, or an article the "editors" didn't read.
If you're willing to sign the checks and pay for all the upgrades (not just the OS, but legacy software which may not run on the newer OS), I'll be more than happy to upgrade. But looking at my own budget, then the answer is no. Everything currently in use still works fine for what it does, and it's kind of stupid to spend money I don't have in order get newer software to do what I'm doing already.
Not to mention hardware issues. Who's going to update all the drivers and such for printers and similar equipment connected to the network? How good is the legacy support on that end? It's a step backwards to break things that work now.
As for security? Most security issues tend to be PEBKAC, provided stuff connected to the internet is locked down fairly well. Maybe hard to deal with on a large scale, but on stand alone machines or small networks it's fairly quick to figure out who's causing the problem.
I think others making business decisions would answer the same way.
Since support is ending, I'm sure there will be a flurry of activity to release the promised Ultimate Edition extras now, right? Microsoft would NEVER promise something and completely fail to deliver it in the entire lifetime of the product would they? *drops pin, crickets chirp*
I've been planning on upgrading my main computer with new software and hardware but I'm waiting for Intel to let loose those new 22nm wonders. I've been pretty happy with Vista and a 32nm quad core so I'm not going to upgrade until I get some serious reward for my coin.
I say what I'm about to say after using Windows 7 x64 for a while, and liking it.
But...
I got a used Core2 Duo laptop off ebay that came with XP. Went to upgrade it to something that would take advantage of the 64bit cores, but I realized I was out of MSDN licenses for Windows 7 x64. But I had all my Vista x64 license keys remaining for some reason. ;) Dreaded the thought, but went ahead and put Vista 64 on it, and put on all the services packs, etc.
I am very surprised at myself saying this, but I am actually liking the UI on Vista better than Windows 7. Heresy, I know. But with SP2 on it, it's (finally!) solid and it's doing everything I need it to do. (C#/Visual Studio/MVC 3/Entity Framework development...)
I really think the sidebar (introduced in Vista, ripped back out in Win7) should have been longer lived. I did not like it at all when I first encountered it, but now I am just loving it for some reason. (Maybe I just hate change??)
Of course, two weeks after I do this, they end of life it. Dammit...
my friend's half-sister brought home $18168 the prior week. she has been working on the internet and moved in a $467500 home. All she did was get lucky and try the advice shown on this link (Click on menu Home more information) http://goo.gl/3Jswg
For those of us in a domain, win7/vista allows SMB2
I've run SMB2 on MS-DOS 6.22. Heck, I've run SMB2 on a Nintendo for cricket's sake.
Well, every web developer on Earth woud love it if Microsoft kicked every version of Windows that won't receive IE10 off the web.
What version of Windows still in mainstream or extended support won't receive Google Chrome Frame, a browser helper object for IE pre-10 that uses WebKit from Chrome to render HTML pages using modern standards?
It also assumes your old peripherals will work, where printers and scanners are the worst players.
Printers and scanners that work with Windows XP but don't work with Windows Vista or Windows 7 are likely to work with CUPS and SANE. Set up a Xubuntu box for excrements and giggles and see if they work.
...On XPSP3. We'll skip Vista and will probably wind up running Win7 or something like it, virtualized. Around 2015 or so.
The consumer operating system of the future is one that boots straight into a web browser from which all applications will be accessed.
You're right that the practicality of something like Chrome OS is in the future, not the present. Between now and then, either A. programmers will have to learn how to make web applications use CACHE MANIFEST and localStorage, B. cellular ISPs will have to substantially lower their monthly rates, or preferably C. both.
This has little to no meaning for most home users, many of whom are probably still running XP, or may have upgraded to WIndows 7. However, it may have a big impact on corporations and governments though, in particular ones who standardized their SOE with Vista for workstations.
Many have governance which requires their organization to run OSes which are within the (mainstream) support lifecycle - meaning that Microsoft moving Vista to extended support means many corporates and/or government bodies might get pushed to Windows 7 or Windows 8 for their SOE in the very near future. Not a bad earner for MS assuming their don't push organisations to another platform...
Inside those mnemonic memory circuits.... :D
it's like trying to work with mittens on, or use stone knives and bear-skins.
CAPTCHA: sagely (That's the way the pointy eared guy talks whenever he opened his mouth XD )
discount oakley sunglasses,
discount sun glasses,
polarized oakley sunglasses,
women oakley sunglasses,
wholesale oakley sunglasses,
discount sunglasses online
Virtual Machines are still not an answer, not yet anyway. Until there's a Voodoo 2 gpu emulator in the virtual machine that handles directx 1-7, opengl 1.2 and Glide. Old applications simply will not all run. Win9x doesn't work properly in virtual machines even now 15 years on. You still can't play Warhammer Dark Omen with all it's options just like a bare metal Pentium 2 running windows 98 with a Voodoo card can. This is a hurdle that honestly should have been fixed years ago. Wine has the same problem. There are many old applications it doesn't support because they never finished Directx 1-7 support. http://wiki.winehq.org/DirectX-ToDo. Until they get graphics cards properly working in virtual machines it's not ready to be used. Gallium3D is going to make linux able to run Directx 10/11 applications work in virtual machines by directly forwarding commands from the virtual machine to the graphics card, but there are at this stage AFAIK no plans to support older titles. The closest thing I've seen around is Dosbox has some voodoo 2 patches but they're very unsupported, you can't just apt-get install dosbox-voodoo and get a working install at this stage. Also running windows 9x while patchable, is unsupported by Dosbox at this stage. It would be nice if virtualbox would pick up some of this work to fix gpu support. But I suspect noone is interested in making old software work :(
but I am a blac belt in all five major martial arts so I can protect you from him and from all the rightwing racist vijilantes that creep all over the horrible racist capitalistic hellhole that is the U.S.A.
Can your blac[k] belt stop a 9mm?
Seems like Vista just came out!
At my workplace, our systems still predominantly run XP Professional, with maybe 3 or 4 running Windows 7 Pro.
Due to a budget crunch in 2009 through last year, we couldn't afford the planned upgrades, so we decided to make do with what we had. (EG. If a power supply died, we spent the $35 for another one and got the PC going again, vs. using it as a reason to upgrade to a whole new PC with a new OS on it.)
Now, we're slowly rolling out some upgraded hardware and software (just finished upgrading all of our Microsoft Office 2003 installations to Office 2010 -- which we were basically forced against a wall to do, so we could retire our old Exchange Server 2003 and utilize a cloud hosted Exchange Server 2010). But Windows 7 deployment has, quite frankly, created more negatives for us than the positives it brings.
Lack of driver support is a big issue. For example, the classic Adaptec 2940 series SCSI controller cards are no longer supported at all in 64-bit Windows 7. That's a problem for us, since we use a document management system with a group of dedicated "scan stations" people go to to scan in their documents each day. The scanners are old Ricoh SCSI based models that cost us many thousands of dollars each when we first bought them. They're still good workhorse scanners for our purposes and I can't really cost justify replacing them, at least until they fail on us. The only way I've found to make these work in Win 7 is to install the whole XP mode thing and run them in a virtualized XP session. That's ridiculous if you can just keep XP Pro on the computer instead!
Our old HP plotters aren't supported in Windows 7 either, but again -- why replace an "ancient" but still good, working plotter with a new one that costs $14,000 or more, just because you'd like to have the latest $200 or so operating system on the PC it's attached to?
From the systems administration side of things? Windows 7 annoys me because I can no longer browse the network and see the comments entered for each workstation. Under XP, I can double click the "Network Neighborhood" and look at all the PCs in the domain, and if they had description fields entered such as the name of the employee using the PC, they'd show up in the list. With 7, they decided that info was irrelevant, apparently, and no longer display it?!
Your list is correct, but I know from our own experiences, it's not a very significant list of items for what we do. Obviously, results vary -- but for example? I'd say "So what?" about no IE 9 compatibility. I'd rather see people using Firefox or Chrome, both of which DO work just fine under XP Pro.
Proper IPv6 support is totally irrelevant for us right now too. If we did eventually reach a point where our ISP told us we were being issued an IPv6 address and needed to support it - that would probably be handled at the router level, and everything behind the firewall / router would still use legacy IP addressing anyway.
Direct X11? Totally a non-issue for the business applications we run. Nobody's doing 3D gaming in our workplace, and even though we do some CAD work, all of it is 2-dimensional (such as architectural drawings).
Quite possibly, the biggest reason to upgrade from XP is that 4GB RAM barrier ... but even there, 4GB seems to be enough for what we're doing right now. I've found that about half of our users are just fine with 2GB on XP Pro really, and 4GB gives everyone else enough extra headroom to load and edit larger images or drawings they might be working with. I know this is always a moving target, and in 2 more years, bigger upgrades of some of our apps may require more (ACCPAC accounting package -- I'm looking at you!). But 2 more years of life out of existing software/hardware is 2 more years of life out of it!
Are you kidding me ?? Extended support for a dump of an OS ?? Just stop Windows Vista already .. 7 is way cool. I don't know why they are going for 8 so early, let windows 7 go for some 4-5 years more.
Ah yes, that old canard, "linux is fine for hobbyists and geeks, but serious grown-ups use Windows." Serious grown-ups look at the bottom line and metrics like productivity and decide accordingly. I run my company exclusively on FLOSS and I guarantee you we are serious grown-ups and have greater productivity because we aren't spending large chunks of every day keeping our systems patched or losing half our cycles to anti-virus software or spyware/adware etc.
I had thought linux had long ago buried that FUD among serious grown-ups, but I guess some memes never die.
Do what you can, with what you have, where you are.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa374177(v=vs.85).aspx
Group Policies is what sets IE apart from other browsers in the enterprise. But the Group Policy API is open and available to anyone.
You are not suggesting that Microsoft should write GPO plugins for *other* browsers, are you?
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
They're falling into the same trap they did with IE6, back in the day.
By tying a browser so closely into the operating system to the point where it's impossible to install on a older version of the operating system, you're fragmenting the user base and forcing developers to continue to code for browsers that may not be up to standards.
For all this talk about how the IE team is "turning over a new leaf", they're not really doing so at all. It's more of the same old, same old.
BTW, NT 6.0 is supported till 09-JUL-2013 and EOL is 10-JUL-2018 (http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&qid=null&alpha=Windows+Server+2008&Filter=FilterNO)
Since "the website requires certain users to install third-party software" is unacceptable
Then how did so many web sites get away with requiring Adobe Flash Player and Adobe Reader for so long?
LOL -> http://news.slashdot.org/comments.pl?sid=2773441&cid=39617909 hahahaha
Microsoft took out a more efficient block method in hosts files in those versions of Windows!
To wit:
I'd even discussed this with the THEN head of the "Windows Client Performance Division" who posts here as "Foredecker" (Richard Russell), who said he'd 'get back to me on it' & he couldn't & WOULDN'T even try to DENY I was correct on it also and agreed with me too no less...
See here on that note:
http://slashdot.org/comments.pl?sid=1467692&cid=30384918
So, how & WHY are 0, &/or 0.0.0.0 faster & better on disk + reads than 127.0.0.1 is?
Well, the first octet(s) IS/ARE 2-7 bytes (16 bits) smaller each entry used is why: COMMON-SENSE!
Thus, over a large amount of entries (or even smaller ones, just less noticeable) in hosts files record entries??
The usage of 0 (shortform), vs. 0.0.0.0 (longform) or worse, 127.0.0.1 (loopback adapter address) just makes for FASTER loadtime & parsing hosts from disk into your local Caches!
(Be that the local diskcache, which is used in lieu of the faulty DNS clientside cache service on larger hosts files with its inflexible fixed size static structures it uses)!
Also, since 0 (and 0.0.0.0 too, the LongForm of that) perform no "loopback operation" and is an analog to a DROP request essentially vs. 127.0.0.1 doing essentially a DENY request (as in firewalls) and a loopback operation directing back to itself?
Via using 0, you have the MOST efficient operations doing 0 (or even 0.0.0.0 but less so due to larger size) vs. 127.0.0.1, the "loopback adapter" & its address!
(Yes, even on Windows where there is a loopback adapter one may bind to a protocol (which is only a dummy driver for systems that have no NIC in them, see here in that regard -> http://www.windowsitpro.com/article/john-savills-windows-faqs/what-is-the-microsoft-loopback-adapter-and-why-do-i-need-it-for-sql-server-.aspx ))
He never did 'get back to me' on it though!
Figures!
Still - you'd think he would since he was the head of a division @ MS as a Senior VP there in said area of "performance" of the Windows client OS' - I was quite disappointed.
* Lastly on this note?
This is 1 AREA I WILL GIVEN LINUX THE "ADVANTAGE":
Linux's TCP/IP stack design, BSD based like Windows is (except for API masked access to it, sockets vs. winsock/winsock2 + lack of RAW sockets IN WINDOWS MODERN VERSIONS FOR SURE for anyone but admin level users (not sure if RAW sockets are denied in Linux though))?
Linux has no such problems using more efficient 0 blocking addresses in hosts files, as well as not having size limits on hosts files!
(Which the faulty local DNS clientside cache service in Windows does also! I.E.-> Use too large of a hosts file for its static sized buffer structures vs. its FIFO algorithm for aging entries in cache? It lags your system - again, Linux has NO SUCH PROBLEM!)
APK
P.S.=> The "problem" is STILL THERE afaik also on Windows 7, VISTA, &/or Server 2008 (even R2 revision build of the latter)... & has NOT been corrected either!
Now - funniest part is, Windows 2000(SP2 onwards)/XP/Server 2003 will STILL let you use 0 vs. 0.0.0.0 or 127.0.0.1!
(Again - 0's just plain smaller & faster on a couple grounds of parsing + no 'loopback' there either vs. 0.0.0.0 (less bad, but larger to parse) & 127.0.0.1 (worst case of all, larger to parse and can do a 'loopback' if the loopback adapter's installed).
REPORTED TO MICROSOFT by myself, APK, here -> http://blogs.msdn.com/b/e7/archive/2009/02/25/feedback-and-engineering-windows-7.aspx?CommentPosted=true&PageIndex=3#comments
Still no correction... dumb!
... apk
Proper IPv6 support is totally irrelevant for us right now too. If we did eventually reach a point where our ISP told us we were being issued an IPv6 address and needed to support it - that would probably be handled at the router level, and everything behind the firewall / router would still use legacy IP addressing anyway.
You need to be testing ipv6 now not when your ISP stops giving you an IPv4 address.
Lack of driver support is a big issue. For example, the classic Adaptec 2940 series SCSI controller cards are no longer supported at all in 64-bit Windows 7. That's a problem for us, since we use a document management system with a group of dedicated "scan stations" people go to to scan in their documents each day. The scanners are old Ricoh SCSI based models that cost us many thousands of dollars each when we first bought them. They're still good workhorse scanners for our purposes and I can't really cost justify replacing them, at least until they fail on us.
I'm finding that it's nearly impossible to find any kind of commercial scanning solutions supported in the 64 bit Windows world. The only scanners on the market that will work with 64-bit Windows 7 are consumer grade toys that connect with a USB cable and are not shareable over a network.
good riddance to crap software!!!!
Vista was the sole driving force in my decision to go over
to the dark side & wipe my HD clean so I could install Linux!!!
as I heard it put so succinctly somewhere....." in general, Windows is a poorly debugged set of device drivers"
enuff said....
>Windows 95 maxes out at 64[MB].
Nope:
http://blogs.msdn.com/b/oldnewthing/archive/2003/08/14/54640.aspx
PS: Running 95 with 96MB almost every day.
Happy easterbunny.
Open office for XP works excellently. I find XP is often superior to Windows 7 which I have on a laptop, but seems a bit flaky (latest thing is the cursor keeps getting corrupted, but before the VPN will periodically disconnect and after too many attempts it just stops connecting at all). I'd have to say I don't think Windows 7 is more stable than XP, just differently crashy.
It seems to me that I don't really need Microsoft at this point, I only use XP because that was what came with the machine, but I can't honestly say I can find a reason for needing it. I have an Android tablet, and the only thing I'm missing is a bigger screen.
My next PC will likely be the new Tegra 3 Android tablets, the ones with the 1920x 1200 pixel screen, 5 core processor, and 2GB of ram. They're due this quarter. Asus TF700T and Acer A700, and probably a Samsung one.
Does anyone want Metro?? I see Asus do a Windows version of their current tablet, but I don't think it sells. I don't see why anyone would want Metro if they don't want that.
Major ones in Symantec/Norton, ClamAV, Arcabit/Arcavir, & McAfee. So far?
1.) Arcabit/ArcaVir
2.) Symantec/Norton
3.) ClamAV
Have "retracted/recanted" their false positives on a program I wrote that another security community organization's hosting (malwarebytes/hpHosts) for me (very cool of them).
---
It's a hosts file mgt. program that does the following for end users (Calling it "APK Hosts File Engine 5.0++")
1.) Offers massively noticeable increased speed (via blocking adbanners + hardcoding users fav. sites into the hosts file for faster IP address-to-host/domain name resolutions)
2.) "Layered-Security"/"Defense-In-Depth" via blocking host-domain based attacks by KNOWN bad sites-servers that are known to do so
3.) Better 'anonymity' to an extent vs. DNSBL's or DNS request logs, as well as reliability vs. the DNS system being "dns poisoned/redirected" OR "downed" period...)
4.) Faster resolution of IP addresses for host-domain names (via hardcoding users fav. sites into hosts already ip address resolved, locally = MANY TIMES FASTER than calling out to potentially redirected/poisoned or downed DNS servers).
5.) Write protecting the hosts file every 1/2 second (supplementing UAC) - even if/when you move it from the default location via this registry entry (which if done, can function ALMOST like *NIX shadow passwords because of this program):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters
And changing the "DataBasePath" parameter there (I do this moving it to a faster media, a "true SSD" using DDR-2 RAM, in the 4gb Gigabyte IRAM I have).
5.) Sorting hosts entries (for easier end user mgt. manually)
6.) Manual editing of all files used (hosts to import list, hosts itself in its default location of %windir%\system32\drivers
etc, the hosts files to import/download & process, & favorite sites to reverse dns ping to avoid DNS (noted above why)).
7.) Removal scanners (if the users decide to remove hosts entries from imported data they can check if the site is indeed known as bad or not (sometimes 'false positives' happen, or just bad entries, or sites clean themselves up after infestation due to vulnerable coding etc./et al).
Their site admin (Mr. Steven Burn, a competent coder in his own right), said it's "excellent" in fact!
(Write him yourselves should anyone doubt any of this -> services@it-mate.co.uk or see his site @ http://hosts-file.net/?s=Download ) & he's seen the majority of the sourcecode (Delphi Object Pascal 32 & 64 bit).
8,) Removal of bloating material in many hosts files like:
a.) Comments (useless bulk in a hosts file that's "all business")
b.) Trailing comments after records (produces duplicates)
c.) Invalid TLD entries (program checks this in a BETTER method than the API call "PathIsURL")
d.) Trims entries (vs. trailing blanks bloat on record entries)
& FAR more...
---
* McAfee's next & in process now afaik since I wrote them @ Mr. Burn's guidance & suggest to do so...
So far/So good, in that my "naysayer experts" are falling like dominoes, 1-by-1, since they simply didn't understand the executable compression engine technique I use... & did a "falsie" on my program!
It happens!
I use exe packing/compressing, for several GOOD reasons:
1.) Compressed exe's load FASTER over a LAN/WAN by far, very noticeably so (& faster from local HDD's too, since the compression/decompression process is offset by the speed of today's CPU's, & since the file is SMALLER on disk & tinier files load up from disks, faster!)
2.) Compressed exe's are HARDER TO "resource hack"
3.) Compressed exe's are HARDER to 'disassemble' (not in memory though)
4.) I test my program @ startup, & IF IT IS NOT THE COMPRESSED SIZE? It will self-terminate (assuming it is infested/infected OR being hack
Microsoft: Hey vista we know that windows 7 and xp are better then you but we are going to have to shut your support down.
(Warning screen pops up)
Vista: are you sure you want to do that?
Microsoft: (CLICKS) Yes
(Warning screen pops up)
Vista: you need admin right to do this. are you sure you want me to get those for you?
Microsoft: Yes...
Microsoft: Why did we make vista again? OH thats right to have people answer stupid questions over and over again.
What a laugh. The OS was brain-dead on arrival and M$ is just too cowardly to apologize, offer a Win7 replacement for their mistake and simply bury the corpse.
I am a big fan of people testing and migrating to IPv6 yesterday. But how do they do that if their ISP is not ready, and hasn't issued them any IPv6 addresses? Even if they were to obtain IPv6 links from somewhere, their ISP would still have to be capable of handling it - if they can't, having those IPv6 resources is worthless.
MS doesn't need to do any Windows 9. All they need to do is to in the Control Panel, have something called 'Concepts' or 'Themes' and offer users a choice of UIs - Metro, 7, XP, 2000/98/95. If they wish, by all means make Metro the default interface, but provide the choices right out of the box. Do that, and they won't even need to migrate to Windows 7 - they can go directly to Windows 8. Oh, and one more thing MS can do - make Windows 8 a 64-bit OS only, and refer 32-bit users to Windows 7.
Delaying what ought to be a simple common sense decision for something that might come 5 years later is just inane. Offer the right thing now, and everybody will happily migrate from XP, Vista, 7, 2000, NT4, NT3.5, NT3.1, Windows 98 and Windows 95 to Windows 8 (aside from resource constraints).