Windows 8 leaks: 7973, 8056, 8161!

[betaluva]

allrighty then,im off to the BA ftp.

[Intellmac]

What about NX bit requirement? What build has that/what build doesn't?
EDIT: Do they support XPDM drivers?

[ovctvct]

Here's 8161:

[betaluva]

very cool. Thanks for pics.

[yourepicfailure]

8056, different lab

@Lukas what lab is it?

[classiconthebox]

Can someone send me the default crossword puzzle wallpaper from 8056? It looks different than the 7989 one, I like it.

[gus33000]

Can someone send me the default crossword puzzle wallpaper from 8056? It looks different than the 7989 one, I like it.

Here you go:

[classiconthebox]

Can someone send me the default crossword puzzle wallpaper from 8056? It looks different than the 7989 one, I like it.

Here you go:

Thanks! I'm making a version where there is no crossword puzzle on it.

[ovctvct]

Did anybody notice that 8056's bootscreen is actually different from 7989's?
8056:
7989: http://www.thecollectionbook.info/galle ... %20013.png

[betaluva]

Don't forget to share it.

[ovctvct]

Anyone seen this before(8056).?:


That's what I call "Sinofsky"

[gus33000]

Did anybody notice that 8059's bootscreen is actually different from 7989's?

Yep, I noticed that. Also we should never forget this build for the introduction of the much loved sad face BSOD (Black Screen of Death)

Offtopic Comment

Damn, I wish it was a flip table ascii instead of a sad face

[Courage]

Anyone seen this before(8056).?:


That's what I call "Sinofsky"

This was in 8102, IIRC.

@gus33000: 8056's BSOD is a fusion of 7989's (colors) and 8102's (text). I like this combination very much.

[ovctvct]

Anyone seen this before(8056).?:


That's what I call "Sinofsky"

This was in 8102, IIRC.

@gus33000: 8056's BSOD is a fusion of 7989's (colors) and 8102's (text). I like this combination very much.

Offtopic Comment

How do you force a BSOD in 8056?

[gus33000]

Offtopic Comment

How do you force a BSOD in 8056?

Open taskmgr, processes tab, click on show for all users button, kill csrss.exe

[Courage]

Going to install 8161 now. Note that the 8161 compile we have here is actually x64, not x86.

UPDATE: Still one of the most boring color schemes for a clean install:



Same old bootscreen:







OOBE looks cleaner:





Updated logon screen and user account picture:



The RTM-ish charms bar (present but not default in 8102 and 8148) is now enabled by default on this build:





Winver:



Desktop IE:



Metro IE:



Start patterns are now present in this build, but they do not work properly. All of the (two) patterns will look the same:



Shutting down/restarting:

[ovctvct]

*snip*


*snip*

Offtopic Comment

How did you kill activation to allow changing color, etc, since personalisation requires you to activate it? (If its something against the rules, PM me it, I really wanna know...)

[Windows OS]

How did you kill activation to allow changing color, etc, since personalisation requires you to activate it? (If its something against the rules, PM me it, I really wanna know...)

I think I seen something to kill activation for the Developer Preview back in the day, but I cannot remember what it was.

Offtopic Comment

I cannot believe it has been 4 years since the Developer Preview came out... Damn, I'm old.

[MSUser2013]

What about NX bit requirement? What build has that/what build doesn't?
EDIT: Do they support XPDM drivers?

Any build before 8400 doesn't require NX bit, So none of these builds need it, Also, 7973 *might* support XPDM drivers, AFAIK 7989 was the first to drop support for them. So 8056 and 8161 won't work with XP drivers, So you're stuck with the basic video driver with those builds.

[ovctvct]

What about NX bit requirement? What build has that/what build doesn't?
EDIT: Do they support XPDM drivers?

Any build before 8400 doesn't require NX bit, So none of these builds need it, Also, 7973 *might* support XPDM drivers, AFAIK 7989 was the first to drop support for them. So 8056 and 8161 won't work with XP drivers, So you're stuck with the basic video driver with those builds.

7973 is from fbl_core1, while 7989 is winmain, fbl_core1 is more advanced over winmain, so 7973 probably doesn't support XPDM. Anyway, there was a topic around there about bypassing the nx bit: http://www.betaarchive.com/forum/viewto ... 62&t=28824

[Courage]

7973 is from fbl_core1, while 7989 is winmain, fbl_core1 is more advanced over winmain, so 7973 probably doesn't support XPDM. Anyway, there was a topic around there about bypassing the nx bit: http://www.betaarchive.com/forum/viewto ... 62&t=28824

Offtopic Comment

You're forgetting about the other 7973, which is from fbl_core2_sid_data. This (x64 checked) compile may support XPDM.

[classiconthebox]

Did anybody notice that 8059's bootscreen is actually different from 7989's?

Yep, I noticed that. Also we should never forget this build for the introduction of the much loved sad face BSOD (Black Screen of Death)

Offtopic Comment

Damn, I wish it was a flip table ascii instead of a sad face

Now that is a weird BSOD! I find it kinda creepy with the black screen and sad smiley (anybody remembers the PS1 error with the black screen?).

[ovctvct]

Did anybody notice that 8059's bootscreen is actually different from 7989's?

Yep, I noticed that. Also we should never forget this build for the introduction of the much loved sad face BSOD (Black Screen of Death)

Offtopic Comment

Damn, I wish it was a flip table ascii instead of a sad face

Now that is a weird BSOD! I find it kinda creepy with the black screen and sad smiley (anybody remembers the PS1 error with the black screen?).

Weird for you at most. 7955 and earlier have that black BSOD, just no smiley. Here's it in 7973.fbl_core1:


Also, there's a hidden immersive RDP in 8056, but it's present only as a .html file:

[DiskingRound]

Would it be possible to enable metro in the leaked 8056, say by copying the shsxs from 8102 to this build and using RPEnabled/SHSXSWasEnabled/whatever the heck it is registry key to enable it? Or is it impossible?

[ovctvct]

Would it be possible to enable metro in the leaked 8056, say by copying the shsxs from 8102 to this build and using RPEnabled/SHSXSWasEnabled/whatever the heck it is registry key to enable it? Or is it impossible?

Highly doubtful, since there are a lot of changes from 8056 and 8102, plus the Mo Framework is also broken in 8056, that would need fixing.