Checklist: Windows 8.1 Core/Pro x86 - leaked √ Windows 8.1 Core/Pro x64 - leaked √ Windows 8.1 CoreSingleLanguage x86 - leaked √ Windows 8.1 CoreSingleLanguage x64 - leaked √ Windows 8.1 CoreCountrySpecific x86 - leaked, but only Chinese √ Windows 8.1 CoreCountrySpecific x64 - leaked, but only Chinese √ Windows 8.1 Pro VL x86 - leaked √ Windows 8.1 Pro VL x64 - leaked √ Windows 8.1 Enterprise x86 - leaked √ Windows 8.1 Enterprise x64 - leaked √ Windows RT 8.1 - leaked √ All we need are leaked
Windows 8.1 Professional now available on DreamSpark neowin.net/news/windows-81-professional-now-available-on-dreamspark
True but seems to me that it's just another build number they keep holding the carrot in front of your nose
That's still no proof! There won't be any new build, at GA the RTM build will simply get updates through Windows Update. And maybe there will be an updated ISO, with updates included in the iso, they will simply be installed after installing exactly the same RTM build we all have!
Nah, when they say "final version", it means the sign-off RTM, build 9600.16384, because what MS means is the current release is only available to MSDN/technet guys for testing, on Oct. 18 is public release, anybody with win8 can get it free, and anybody can buy it from stores.
So far I'm so totally pissed at all the sites whom fail to work properly with 8.1 RTM and IE 11- issues all over that i'm sure glad I saved an restorable image to Windows 8.0 IMO - 8.1 Genuine TN release is 1000% SH*T. I'll give it a week just to make sure... If I had to buy this CRAP, i'd really but PISSSSSSSSSSSSssssssssssssssssssssssssssssssssssssssed
Don't blame IE, blame the websites. IE now identifies as Gecko, which breaks the browser targeting scripts a lot of websites use, these scripts are worthless since IE10 already, and with IE11 even more so, IE is fully HTML5 spec compatbile. For developers this is a clear message, create HTML5 sites, not webkit/gecko websites right now we have the same dilemma we had with IE6.. developers should use a standard not special flake implementions. This is Microsofts atempt to drive the HTML5 spec forward as a standard without browser targeting scripts and css code. Though ofc MS has some still some -ms- tags, because not everything is part of the standard yet, especially stuff like their sizing for snap res, and stuff like the new animation boxes to create picture boxes that are smooth and accelerated. While Developers can use this and ms tries to get that into the standard, it's especially there for HTML5 apps on the Store.
Yes, on Web sites I get lots of DEBUG errors now, so much bad coding... then how does one work around it... FF is not so good for me either... never got use to that. but Chrome has done a pretty good job. on the crap sites... so many have pissy Certificates, and bad code.. at least MDL so far I have not had one ERROR here... So Thanks to the Web site here...