First, welcome to mydigitallife. Second, as to why would they? My guess would be to increase the number os devices/systems that win8 could run on. Normal 32-bit supports 16-bit but only when the 16-bit app/driver is is able to "look like" a 32-bit. True 16-bit cannot as far as I know. (have not tried using compatibility mode). Another reason may also be that virtual xp was a huge flop for win7? So that may eliminate that nasty ankle biter situation that is 16-bit support. also, as stated above. dosbox=love
The comment was not meant OR designed to act as a political comment, mikedl. The comment was more in regards to the fact that they got arrogant - a lot like how Microsoft got with IE until the loss of both marketshare *and* mindshare came back and bit them rather hard. I don't care what endeavor you are in - once you reach the top, there WILL be someone that wants what you have; therefore, be prepared to defend your hard-won position. It's when you start thinking that your position is the most secure that you can be at your most vulnerable - which is why hubris is something to be avoided. Businessmen get it - politicians, however, often do not. The staidness - if not outright staleness - of the Windows UI to date have left it vulnerable. It may seem like the *death of ten thousand ducks nibbling* - if left uncountered, the corpse will still be a corpse. The invasion of Android and iOS (especially at the low end of the price curve) are showing that Windows is, in fact, vulnerable. Therefore, staying where it is isn't exactly a good option.
It wasn't that XPMode was a flop per se - it was just that it was limited to x32 operating systems (and was originally limited even further by the VT-x requirement). While the VT-x requirement did eventually go away, the x32 OS requirement did not - which in turn left XPMode (and Virtual PC) vulnerable to assault by the free (and less encumbered) VirtualBox. The one area where VirtualPC shines (and VirtualBox still has issues) is support for OS/2 and its progeny (specifically, eComStation) - which is, to put it bluntly, a niche use.
There's probably not anything new to show. Either MS is going to drop a bombshell when beta launches and implement a new Aero theme or what we have seen so far is pretty much the final product. I'm hoping for the former.
The latest build number for Microsoft's Windows 8 operating system, 8184.0.winmain.120113-1850, has been revealed as we get closer to the launch of the beta version in late February. Windows 8 was apparently a big hit at CES 2012, but it looks like Microsoft brought an older build version of the operating system, 8175.0.fbl_dev_dp4.111216-2019, to Las Vegas this week. Now Winunleaked.tk is reporting that the latest version of Windows 8 is in fact at 8184.0.winmain.120113-1850. The numbering means that Microsoft is getting closer and closer to launching the much anticipated beta version of Windows 8 to the masses. As we reported earlier, a leaked road map for Windows 8 claims that from now until January 23, Windows 8 will be considered to be in pre-beta form at Microsoft. On January 23, Windows 8 will go into what is known as Beta Escrow. After that, the leaked road map claims that Microsoft's own testers will then vote on which of the Windows 8 builds will in fact be the final beta build with the decision being made on January 28. The beta build will then be shown at an internal Microsoft preview on January 30. The road map claims the target build number for the final beta will be 8200.winmain_win8b1. If Windows 8 is at build 8184, it's getting very close to the 8200 mark which means the beta should be arriving very soon.