there are enough software incompatabilities with 64bit that no one will use it, so no one cares.

“..Because Microsoft did not want to scare VMWare into thinking they had competition, and will release a public statement apologising to VMWare for ever stepping on their toes.”
Have a great day,
David

“you really don’t need to test 64-bit server and client products anyway.”

or

“we just didn’t want to make the Virtual Server team feel bad.”

“SBS Premium proved that you really CAN run more than one infrastructure application per Windows server image. So who really NEEDS to virtualize?”

By the way, is “customer virtualization” somehow “cloud” related? As in “my customers are virtually disappearing into the cloud?”

To paraphrase Ken Olson’s infamous speech back in 1977, “There is no reason anyone would want a 64bit Virtual Machine in their home.”

we didn’t want to release something that worked the first (or second) time around, as marketed.

they were unable to meet the driver certification requirements!

Microsofts monopoly is quickly turning into a crapopoly. They could pretty much release an OS that took 2 hours to boot and we would still be using it…

Sad but true!

it’s not a v 3.0 product yet…

Hah! I like Andy’s reply!

- because the team is still shooting for a Hyper-V RTM this year.

- because there’s still no decent consumer motherboards with >8GB of RAM.

- because it would be out of character with current release decisions.

- because we forgot we had a client-side VM product. Go buy Win2008 you cheapskates!

- because we’ve lost our passion since Bill dumped us. Sob.

- because. Just because! Besides, it’s only supposed to be an internal tool for retro games! Keep quiet and let us finish Prince of Persia! Shhh!

…because that would just be silly! And, besides, we would just have to pull that feature later due to intability and lack of support from us…

…64bit guest operating system support is a work in progress and we have a lot of things we need to learn from, so it shall be released when it is perfected.

Expect that around the same time that Windows 10 with SP7 (Super Duper Online Business Edition) is released….as well as WHS Powerpack 2 still missing a database backup feature.

I can’t win another SM shirt but

“we were busy trying to purchase other companies instead of finishing our products…then the dead line came for the release and we decided it was better to release it next time”

“…my milkshake brings all the boys to the yard. Damn right its better than yours. I’d teach you, but I’d have to charge.”

sorry about that…

they are focusing their development on Hyper-V, which will be included in Windows 7. An anonymous Microsoft source cited Gartner’s 64 bit market data as the main reason for the decision, pointing out that only gamers and hobbyists run 64 bit OSes and that both groups prefer native hardware virtualization versus the overhead of Virtual PC.

Microsoft is still focused on sticking with their tried and true methodology of luring their competitor, in this case VMware, into a Netscape-esque lull. Once phase one is complete phase two will commence with a release cycle that will offer minor iterative enhancements. Phase three consists of using WSUS to deploy the full version as an “Update” (e.g. KB917013), thus leveraging their desktop monopoly to increase their install base. Phase four consists of planned damage control and justifying the product as “good enough”, thus freeing the userbase from having to look for alternatives. Phase five is optional; pressure partners to exclusively push the Microsoft solution.

Just like it’s 2nd cousin ISA, the folks who use it are only a rounding error compared to our mainline product.

….because if we gave folks the features they want in a new product, there’d be no need for Software Assurance and no need for the next generation product.