Chris123NT's Blog

So yeah, I’ve moved this site to a new server.  More precisely, MY OWN server.  I have done this to better control reliability and uptime, and no longer have to worry about outside factors causing unnecessary downtime of this site.

So If you can see this, welcome!

If you see any issues, please do not hesitate to contact me, and I will get them fixed.  New server so there might be a few little hiccups here and there.

So I’ve actually been meaning to write this for a while because it’s been annoying the hell out of me.  I have seen people saying that 7105 and 7106 of Windows 7 are RC builds and the RC will be > 7100.  Well all I can say to those people is that you’re wrong, you fail, and you need to learn how the development process works inside Redmond before you go spouting about a build being an RC ESCROW or now.

There’s also the other camp that seems to think that Microsoft is strictly working on RC and have not let winmain continue building towards RTM.  Again, learn how the process works before you talk.

Ok so now I will attempt to explain all of this so you guys can walk away from reading this post knowing how it works in Sinofsky’s lair.

Basically, after build 7076 the tree was split.  7077 was compiled as an RC ESCROW build (winmain_win7rc) and the winmain lab bumped its build number up to 7105.  7077 and on are code frozen, meaning no feature changes will occur in that branch (the RC branch.  This allows them to work out the bugs to deliver a high quality RC release.

Any code changes internally are checked into winmain (7105 and higher at this point).  So from that standpoint you could say that codewise future 71xx.winmain builds are newer than the RC will be as those builds are still receiving new check-ins from the various fbl labs.

So for those who are wondering I will answer the question.  7105 or higher are NOT RC builds, but rather winmain builds pushing towards RTM.  7077, 7078, 7079, 7080 etc… are all RC ESCROW builds.  When the RC has passed testing, they will compile the final RC build as 7100.

Hope this clears up some of the confusion.  As usual if you have any questions feel free to ask!

UPDATE: The current situation has been clarified a bit to me. (Thanks to Tom W for this).  Build 7106, which leaked the other day in chinese, is in fact 7076 with a revved up build number.  So currently 7077 is the newest from a code perspective as 7106 does not contain the new visual style elements (updated taskbar buttons etc…) that are in 7077.  So for all of you who have 7077, stick with it and don’t bother with 7106, it’s not worth the hassle of attempting to translate it.  I really only did it myself to see if it was even possible.  7077 is re-installing on my laptop as I write this.

Well folks, here we are again, another leak of Windows 7.  This time we have build 7057.winmain.090305-2000.  This build is a mere 6 days old as of this writing and brings forth a few changes since build 7048.  I will outline these changes here as well as over a few other things.

UAC Issue

As you all know, previous builds of Windows 7 allowed you to change the level of UAC without ever receiving a prompt from the system.  This could potentially allow a piece of malware to turn off UAC on your system and open it up to a much more lethal attack.  This issue was not fixed in 7048 which surprised me, but it IS fixed in 7057.  Hooray!

New Logon Screen

Upon first boot of this build you will notice the most obvious change over 7048.  The logon screen is new.  At first when I saw the screenshot I didn’t think I liked it, but after seeing it running it is pretty nice, although it might be a little too bright in some areas.  See the screenshot below to have a look at the logon screen:

New Wallpapers

This build contains some new wallpapers over 7048.  They seem to be centered around the “Characters” theme which is clearly geared towards little kids.  Can’t say I’ll be using these but I’m sure they will make the 4 year old from the Windows Live commercials very happy.  See screenshot below to see new wallpapers:

New User Pictures

This build features all new user pictures to be used for your account on the system.  Some of these are quite nice and there are more than double the number that were present in Vista and previous builds of Windows 7.  See the screenshot below:

Expiration Date Change

This build, in preparation for the RC, has an expiration date which is set to March 1, 2010.  I have already seen people reading into this WAY too much stating that this must mean Microsoft won’t release Windows 7 until early 2010.  I can assure you all that this expiration date is merely there to give people ample time to get retail bits before their RC  build expires.

Startup Bug, Desktop.ini Opens in Notepad on Every Boot – FIX

This is an odd bug, mostly due to the fact that some instances of desktop.ini are visible and not set to system and hidden.  Fortunately the fix for this is quite easy:

1. Navigate to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
2. Delete desktop.ini
3. Navigate to C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
4. Delete desktop.ini if present.

That pretty much covers it, a small overview of the changes in 7057.  Any questions or comments feel free to ask or discuss it in the comments.

So I came across THIS article today that pretty much states that Opera’s CEO is not happy with Microsoft making Internet Explorer 8 a removable component in Windows 7.  So that got me to thinking, what exactly DOES this guy want?  And then it hit me.  He wants to see Microsoft integrate his browser, and possibly others into Windows.

I can say right now that the above would NEVER happen.  Microsoft would rather withdraw from the EU market then include competitor’s products in Windows.  And there are many valid reasons for this, a couple of which I will outline below:

Support Issues

This is perhaps the single biggest issue.  The fact is, Microsoft has a responsibility to support everything that they include in box with Windows.  If Microsoft were to box Opera or any other browser with Windows, and said browser causes crashes or other unforseen issues, users will hold MICROSOFT responsible because it “came with Windows, so it must be Microsoft’s fault”.  The only way around this would be to sub out the support to the browser developers, but that is complex and puts an unfair burden on Microsoft because they will still have to field calls from users who don’t know any better.

Confusion

This point could be argued but I believe that if the OS were to come pre-boxed with multiple web browsers, users would become confused.  In my experiences in the field most users access the internet with “the blue e”.  No, I’m not making that up, people actually have said that to me.  If there are more choices one of two things could happen.  Either people will continue to use IE, or some may become confused and ask why there is more than one Internet on their computer (yes they will probably ask it like that too).

The bottom line though, is that the reasons for not integrating competing browsers into Internet explorer are plentiful and range the whole spectrum, from technical issues right down to legality and support issues.  I would recommend that competing browser companies bide their time and accept that IE is removable as a good thing.  Most users will switch away from IE once they see how bad IE8 is and just how badly it breaks the web.  This will be a good thing for people like Mozilla, Google, and hey, maybe some people will use Opera too.

Anyway just wanted to write a little blurb about this.  Feel free to comment with your opinions and/or questions.

I couldn’t believe this when I saw it, but it’s true.  Internet Explorer 8 is fully removable in Windows 7 build 7048.  I believe this fully squashes the case that the EU has against Microsoft?

As you can see in the above screenshot there is a new entry for Internet Explorer 8, if you uncheck it, IE8 will be removed from the operating system.  Want proof?  Try it for yourself:

Here are some instructions courtesy of Bryant

1. Enter the Control Panel and look at “All Control Panel Options”
2. Click “Programs and Features”
3. In the left sidebar, click “Turn Windows Features On or Off” (you will be thrown a UAC prompt if you elevated UAC)
4. Wait for the list to load.
5. Look for Internet Explorer 8 in the list and uncheck it.
6. Click OK. You will see a prompt notifying you of a reboot.
7. The machine will reboot once, configure things, and reboot again.

As you can see above, currently it just deletes iexplore.exe, which I hope will be revised in future builds, but all references to IE are removed from the OS (see second shot), so my bet is that deleting these files would not harm anything, but then again I could be wrong.

So there you have it, step in the right direction for Microsoft?  And a quick solution to the EU’s argument against them?  Time will tell.

Yesterday, I posted a quick and dirty article entitled “Apple Tax: Stealing your Benjamins, one wallet at a time“, with the purpose of illustrating the difference in cost between a Dell Studio XPS 16 notebook which was fully loaded, and a base model MacBook Pro with memory upgraded to match that of the Dell (so that the configuration was similar).

One of the comments on that article made me wonder if the Reality Distortion Field turns a persons perception of life into pure gold in fields of roses…

gremme had this comment:

You should not buy it if you aren’t willing to pay a premium for good service and construction and a sleek look. Not only that, but you also are buying into the mac experience and lifestyle. If you don’t have the money then buy your dell, you get what you pay for.

A premium for good service? AppleCare in many countries (including Canada) doesn’t even offer mail-in service for MacBooks, which is pretty bad considering Dell, HP, Gateway, Lenovo, and Acer have been doing this for years (some even go above that by offering next business day on-site repair service and accidental damage coverage). Having to drive for an hour to drop a $2,000+ notebook off at an Apple Service Provider isn’t exactly the best solution.

Good construction? Need I mention the many issues with the Mini DisplayPort adapter and external monitors not working? I mean, using an external display with a notebook has only been possible for years… no reason for this not to work. How about those with scratches on the aluminum enclosure straight from the factory… dust under the glass screen covering… glass screen covering coming loose from the display unit… uneven lids… issues waking up from sleep…

As for “buying into the Mac experience and lifestyle”, this statement makes me believe even more that there’s some sort of cult surrounding Apple. Did I miss the memo where spending $2,700 on a notebook, leaving it on your desk and admiring it in all of its “premium design glory” was classified as normal?

As I wrap this post up, I just wanted to also point out a comment left by stephen which just made my day:

“Yes because we buy a laptop to stare at it all day and think about how good-looking it is. Macs are economically just as much as a lifestyle as Starbucks, and you can see where they’re going. Yeesh.”

For the purpose of full disclosure, I was a Mac user for the past year. I never have, and never will, agree with the Reality Distortion Field.

Editors note: This is a guest post by Kristan Kenney.

Here are two notebooks which are very similar in configuration and features:

Apple MacBook Pro:

• 2.4GHz Intel Core 2 Duo
• 4GB 1066MHz DDR3 SDRAM – 2×2GB
• 320GB Serial ATA @ 7200
• SuperDrive 8x (DVD±R DL/DVD±RW/CD-RW)
• NVIDIA GeForce 9600M GT 256MB
• Backlit Keyboard (English) / User’s Guide
• Apple Mini DisplayPort to DVI Adapter
• Mini DisplayPort to VGA Adapter
• AppleCare Protection Plan for MacBook Pro (w/or w/o Display) – Auto-enroll

Price: $2,706.00

Dell Studio XPS 16:

• Intel® Core™ 2 Duo P8600 (3MB cache/2.4GHz/1066Mhz FSB)
• Genuine Windows Vista® Home Premium Edition SP1, 64-bit
• 3Yr Ltd Hardware Warranty, InHome Service after Remote Diagnosis
• Edge-to-Edge HD Widescreen 16.0 inch WLED LCD (1366×768) W/2.0 MP
• 4GB Dual Channel DDR3 SDRAM at 1067MHz (2 Dimms)
• 320GB 7200 RPM SATA Hard Drive
• 8X DVD+/- RW(DVD/CD read/write) Slot Load Drive
• ATI Mobility RADEON® HD 3670 – 512MB
• Intel® 5100 WLAN Wireless-N (1×2) Half Mini Card
• High Definition Audio 2.0

Price: $1,518
Difference (also known as the “Apple Tax”): $1,188.00

What the hell? Even if you deduct the retail price of iLife ‘09 and Mac OS X Leopard, you’re still paying an extra $980, and for what? A “multi-touch glass trackpad” which for the most part is useless as you can’t configure the gestures, and an aluminum enclosure (which can be attributed to beer cans and Faraday cages the world over). Having used a MacBook Pro, I can tell you this – there are better things that you could spend that $1,188 on. Like useful software. Or groceries.

Editors note: This is a guest post by Kristan Kenney

News has come down the grapevine that Microsoft have already branched off winmain and started compiling RC1 branch builds, no doubt preparing for the public release of Windows 7 RC.  This tells me that Microsoft is far ahead of schedule with Windows 7 development and are going full speed ahead to get this release polished up and done.

This news has come to us in the form of a build tag which sports the typical naming scheme for milestone branch builds.  7048.winmain_win7rc1.090211-1625 is the tag.  As you can see, this build was compiled on February 11th 2009 at 4:25 PM.  On one hand it is good to see Microsoft moving this quickly with the development of Windows 7, but on the other it is a little concerning.  Microsoft have only officially released one build (7000) which went to beta testers and the public alike.  One build is not enough to gather enough feedback to move ahead this quickly IMO.  Windows is a far more complex piece of software than Office and I hope Mr. Sinofsky can learn that before this beta cycle is over.

Beta testers (and the public) will likely see RC1 within the next month or two and then likely will not see anything until Microsoft declare Windows 7 to be RTM, thus making the technical beta utterly USELESS.  I am a part of the Windows 7 beta and I am not pleased with what I am seeing.  There is no incentive to testing anymore, anything we get the public gets, so can someone remind me why I’m on the techbeta?  We have gotten no new builds, our feedback is not being taken seriously, etc…  Granted they have the public testing and they are getting BOATLOADS of SQM data, but that simply isn’t enough.  That won’t fix rogue usability issues, or odd app incompatibility issues, or driver issues etc…  So if anyone from the beta team reads this, please rethink your strategy and think about releasing some more builds for testing.  It can’t hurt, it can only help the end product.

So anyway, I know I drifted off into a bit of a rant but I feel the above needed to be said, and hopefully this feedback is taken seriously by the Windows team (hey there’s a chance, it’s not like we’re dealing with the Windows Live team, those people don’t know the meaning of the word feedback).

Source: Geeksmack

Discuss: Geeksmack Forums

So as you all know by now, Windows 7 build 7022 has made it’s way onto the internet yesterday.  Unfortunately this build only leaked in the 32 bit flavor but it still gives us some insight into the direction that Windows 7 is going.  The next official build from Microsoft will likely be RC1, so thankfully we have these “unofficial” builds to show us the progress in between.  I have to say I am impressed with what I see in 7022.  The changes may be small, but I think they are little details that just make the overall experience a whole lot better.

The first thing you will notice about 7022 is the speed of the install process.  The build installed about 5 minutes faster than 7000 did (15 minutes on 7022, 20 on 7000).  Upon first boot you will also notice that Windows does not ask you to create a Homegroup.  This is because it actually creates one for you, and you can go in and tweak the settings on your own later.

Read the full overview after the jump…

Read the rest of this entry »

Well it looks like the screams over the past week or so have finally been heard, and more importantly, LISTENED TO.  Steven Sinofsky has made a post on the E7 blog outlining that they plan to address the concerns with 7’s UAC and make changes to make the system much more secure.  Changing the UAC level will now prompt you no matter what level you have UAC on.

I definitely applaud the Windows 7 team for finally listening, although I have a funny feeling the driving force behind this change was Steven himself along with the backlash that John received when he posted this morning that they weren’t going to change the system.

Here is the whole post from the E7 blog quoted for your reading pleasure:

When we started the “E7” blog we were both excited and also a bit uneasy. The excitement is obvious. The unease is because at some point we knew we would mess up. We weren’t sure if we would mess up because we were blogging about a poorly designed feature or mess up because we were blogging poorly about a well-designed feature. To some it appears as though with the topic of UAC we’ve managed to do both. Our dialog is at that point where many do not feel listened to and also many feel various viewpoints are not well-informed. That’s not the dialog we set out to have and we’re going to do our best to improve.

This post is an attempt to get both the blog right and the feature right. We don’t like where we are in terms of how folks are feeling and we don’t feel good – Windows 7 is too much fun and folks are having too much fun for us to be having the dialog we’re having. We hope this post allows us to get back to having fun!

To start we’ll just show representative comments from the spectrum of feedback. We’ll then talk about the changes we’re making and also make sure we’re all on the same page regarding how we move forward. In terms of comments we’ve heard the following:

@sroussey says:

You have 95% of the people out there think you got it wrong, even if they are the ones that got it wrong. The problem is that they are the one’s that buy and recommend your product. So do you give them a false sense of increased security by implementing the change (not unlike security by obscurity) and making them happy, or do you just fortify the real security boundaries?

And @Thack says:

Jon,

Thanks for sharing your thoughts.  I understand your points.

Now, I want add my voice to the call for one very simple change:

Treat the UAC prompting level as a special case, such that ANY change to it, whether from the user or a program, generates a UAC prompt, regardless of the type of account the user has, and regardless of the current prompting level.

That is all we are asking.  No other changes.  Leave the default level as it is, and keep UAC as it is.  We’re just talking about the very specific case of CHANGES to the UAC prompting level.

It will NOT be a big nuisance – most people only ever change the UAC level once (if at all).

Despite your assurances, I REALLY WANT TO KNOW if anything tries to alter the UAC prompting level.

The fact that nobody has yet demonstrated how the putative malware can get into your machine is NO argument.  Somebody WILL get past those other boundaries eventually.

Even if you aren’t convinced by my argument, then the PR argument must be a no-brainer for Microsoft.

PLEASE, Jon, it’s just a small change that will gain a LOT of user confidence and a LOT of good PR.

Thack

With this feedback and a lot more we are going to deliver two changes to the Release Candidate that we’ll all see. First, the UAC control panel will run in a high integrityprocess, which requires elevation. That was already in the works before this discussion and doing this prevents all the mechanics around SendKeys and the like from working. Second, changing the level of the UAC will also prompt for confirmation.

@mdaria510 says:

Sometimes, inconsistency with your own ideals is a good thing. Make an exception, if only to put people’s fears to rest.

That sums up where we are heading. The first change was a bug fix and we actually have a couple of others similar to that—this is a beta still, even if many of us are running it full time. The second change is due directly to the feedback we’re seeing. This “inconsistency” in the model is exactly the path we’re taking. The way we‘re going to think about this that the UAC setting is something like a password, and to change your password you need to enter your old password.

The feedback is that UAC is special, because it can be used to disable silently future warnings if that change is not elevated and so to change the UAC setting an elevation will be required.  To the points in the comments, we also don’t want to create a sense or expectation of security that is not there—you should still not download code and run it unless you trust the source. HTML, EXE, VBS, BAT, CMD and more are all code and all have the potential to alter the environment (user settings, user files) running as a standard user or an administrator. We’re focused on helping people make sure that code doesn’t get on the machine without consent and many third party tools can help more as well. We want people to be comfortable with the new UAC control and the new default setting, so we’ll make the changes outlined above as the feedback has been clear.

While we’re discussing this we want to make sure we’re all on the same page going forward in terms of how we will evaluate the security of Windows 7. Aside from the UAC setting, the discussion of the vulnerability aspects of the Windows 7 Beta  have each started with getting code on the machine, which the mechanisms of Windows have prevented in the cases shown. We have also heard of security concerns that involve multiple steps to demonstrate a potential exploit. It is important to look at the first step—if the first step is “first get code running on the machine” then nothing after that is material, whether it is changing settings or anything else.  We will treat very seriously the ability to get code on a machine and run without consent. As Jon’s post highlighted briefly, the work in Windows 7 is about the increased protections in place to secure your PC from acquiring and running code without your consent, and of course we continue to make sure Windows code is secure from both tampering or circumventing the protections in the system.

We want to reiterate the security of the system overall. Windows 7 is SD3+C and is designed to be more secure that Vista—that’s our priority. None of us want to have Windows 7 be perceived as being less secure than Vista in any way, because our design point is to make sure it is more secure that Windows Vista, by default.

We said we thought we were bound to make a mistake in the process of designing and blogging about Windows 7. We want to continue the dialog and hopefully everyone recognizes that engineering, perhaps especially engineering Windows 7, is sometimes going to be a lively discussion with a broad spectrum of viewpoints expressed. We don’t want the discussion to stop being so lively or the viewpoints to stop being expressed, but we do want the chance to learn and to be honest about what we learned and hope for the same in return. This blog has almost been like building an extra product for us, and we’re having a fantastic experience. Let’s all get back to work and to the dialog about Engineering Windows 7. And of course most importantly, we will continue to hear all points of view and share our point of view and work together to deliver a Windows 7 product that we can all feel good about.

–Jon and Steven

 

Source: E7 Blog