Recommended Posts

Over the weekend, Windows Vista build 5231 leaked to the Web, offering users a glance at some upcoming features that Microsoft will be adding to future Community Technical Preview (CTP) and beta releases. Build 5231 is highly unstable--barely usable, in fact--but an interesting preview of things to come.

Highly unstable & barely usable :blink: That doesn't sound like progress to me :no: Yes I know it is still beta, but Paul is making sound like it is worse then build 5219.

http://www.windowsitpro.com/Article/Articl...48069.html?Ad=1

Over the weekend, Windows Vista build 5231 leaked to the Web, offering users a glance at some upcoming features that Microsoft will be adding to future Community Technical Preview (CTP) and beta releases. Build 5231 is highly unstable--barely usable, in fact--but an interesting preview of things to come.

Highly unstable & barely usable :blink: That doesn't sound like progress to me :no: Yes I know it is still beta, but Paul is making sound like it is worse then build 5219.

http://www.windowsitpro.com/Article/Articl...48069.html?Ad=1

586651493[/snapback]

Has anyone tried this build? How stable is it really?

Paul Thurrot admitted it!!! :|

586651713[/snapback]

That's true, but Neowin isn't responable for his actions and we've been told:

Reminder:

...  Admitting to downloading it, helping others find it, or asking about how to get it is not allowed.

586651137[/snapback]

I will wait till it appears on connect :)

586651857[/snapback]

While it may carry the same build number of 5231, it's possible that a newer iteration of it will appear on Connect. I don't know if it will or won't be the same build exactly, just pointing out that it doesn't have to be... Much like the pre-PDC build shwon on Neowin was an earlier iteration of 5219.

Is the build unstable because of this?

First of all, let me get a few things straight: THIS BUILD WAS NOT LEAKED BY UX.Evolutions!! We won't ever leak builds on the site or where ever. The history of the leak is as following: on one way or another ChrisNT123 managed to get the 5231 nuked ISO. The ISO was nuked because all file names where truncated during the ISO creation process. ChrisNT123 managed to fix this nuked ISO partly, he just renamed all files which he saw by hand via the file properties. Though the most files still aren't fixed. When he had enough files fixed to make it run, he started to give it out to a selected group of friends.

From http://www.uxevolutions.com/

How the heck did Chris get it though? ..that is what I'm really wondering.

586652525[/snapback]

He got it from me. And i've got it from a friend of my sister's girlfriend who has an uncle that knows someone from microsoft and that guy knows someone at symantec that knows somebody from the asian microsoft department.

Really mr "L33T h3ckers" ... You will never find out, it would be stupid if you would know how he got it.

*Tired of newbies calling theirselve l33t h3ckerz"

He got it from me. And i've got it from a friend of my sister's girlfriend who has an uncle that knows someone from microsoft and that guy knows someone at symantec that knows somebody from the asian microsoft department.

Really mr "L33T h3ckers" ... You will never find out, it would be stupid if you would know how he got it.

*Tired of newbies calling theirselve l33t h3ckerz"

586652603[/snapback]

Well, don't worry, the key used to install it is unique, although the PDC Key can be used I heard, but I don't believe that. So, Microsoft will find out which one of the 10,000 employees leaked it and he or she will be fired. :)

Is the build unstable because of this?

From http://www.uxevolutions.com/

586652406[/snapback]

First of all, let me get a few things straight: THIS BUILD WAS NOT LEAKED BY UX.Evolutions!! We won't ever leak builds on the site or where ever. The history of the leak is as following: on one way or another ChrisNT123 managed to get the 5231 nuked ISO. The ISO was nuked because all file names where truncated during the ISO creation process. ChrisNT123 managed to fix this nuked ISO partly, he just renamed all files which he saw by hand via the file properties. Though the most files still aren't fixed. When he had enough files fixed to make it run, he started to give it out to a selected group of friends.

LOL :laugh: they are kidding its just working fine much better and stable then pre-beta2

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.