Superbar is in Windows 7 Build 6801

Hi sahitanand,

Welcome to the forums.

I don't have that bit either. I think that it is not in this version. Just a tease of things to come.

Gary

From Raphael

"This day, last month, I released a small utility to patch system files in Windows 7 Build 6801, the build given out at this year’s Professional Developers Conference (PDC), to enable some features that Microsoft intentionally tried to hide from the public.

Chris Holmes and I were scratching our heads over Aero Peek, a feature that we knew worked in some builds, but wasn’t working on Blue Badge’d systems. I initially wrote it off as an unfinished quirk but I took another look…



… and noticed I totally missed a series of checks made in the registry. Each protected feature has a pair of enabling override bits that are checked for, one for those on the Microsoft domain and one for those that aren’t. I’m not sure as to the rationale behind that, but I suspect it was implemented this way to prevent Microsoft employees from leaking working override bits. Overkill in my opinion.

Revision 3 of the tool no longer patches system files, no longer requires administrative permissions, and is no longer locked to any specific build. It inserts all the known protected feature GUIDs as of build 6956 into the current user’s branch of the registry. An anonymous reader confirmed this behavior is similar to the Microsoft-internal win7features.exe utility.

Yes, this will enable Aero Peek in 6801+.


You can download revision 3 for x86 and x64 right now.



To prying eyes: To those that will inevitably reverse engineer the program, please note the creation of the 41579D76-09BA-4ABD-A49A-A2335B9CB706 key, without braces, is not a typo on my part and must remain intact."

Blue Badge rev. 3 adds registry override bits, “Aero Peek” enabled - Within Windows

limneos said:

Nice one man, thumbs up... So now there's no need to go for 6956, if everything works as it does in this version also on 6801, cause at least 6801 doesn't expire!

its still timebombed limneos
even if it is still activated it will timebomb in Jan

In fact, the pre-Beta M3 bits delivered at PDC 2008 and WinHEC 2008 are time-bombed, and set to expire in January 2009. The expiration date remains in place independent of the slmgr method to prolong the initial grace period of Windows 7 Build 6801, or using valid or leaked product keys to activate the bits, or one of the cracks that have started to circulate."

this timebomb is set up in the kernel so if you have x64
you HAVE NO CHANCE of "hacking" it...lol

limneos said:

well the point is to have the chance to test it, work on it, get dissapointed or not by it, and finally decide if u wanna ditch it or not, or wait for the final version.

For all the above, I believe the limited time is acceptable, not to mention the time-hacks that are going to pop up within the next weeks, if not days!

well then again this is the same with 6956 (not arguing im just saying what i know... no offense )

actually this timebomb is the kernel (remember we are not allowed to modify the kernel in x64... patchguard....)

so pretty much modifing the x64 kernel (if you can in OS although this opens up the changes outside the OS (Linux anyone???...lol) it will yield you a unbootable system...


actually there is a way (only for x32) but shhh i cant say here....

DiamondNRG said:

Yeah, Rafael did a good job with Blue Badge rev3. I sent him build 6936 on Friday sometime and he had the rev3 back to me around 7pm Monday night :)

nice...
man i wish i could get my "hands" on it....:)
oh well a guy can only wish...lol