Introducing Windows… 7

posted on October 13, 2008 by Bryant Zadegan

windows7

Slashdot readers, thanks for visiting. Feel free to chime in here or on the forums.

Mike Nash, former Security Guru and current Client Guru over at Microsoft, has just announced on the Windows Vista Blog that the new name for Windows “7” will be:

Windows 6.1 7

…which makes me wonder why it’s going to be NT 6.1.

It also means that Windows Strata will likely be the codename for the new Cloud OS discussed by Ballmer earlier this month. We’ll carry more about all of this from PDC in two weeks.

Update: Brandon followed up with me on twitter saying it’s the 7th release of Windows, which is ridiculous:

  1. Windows
  2. Windows 2
  3. Windows 3.0
  4. Windows NT (NT 4)
  5. Windows 2000 (NT 5)
  6. Windows XP (NT 5.1)
  7. Windows Vista (NT 6)

That’s 7 releases right there, including XP. If XP isn’t counted because it’s Kernel 5.1 (which would bring the total with Windows 7 back down to seven), then why is Windows 7 being counted as the “seventh” release if it’s kernel 6.1? I hope I’m not the only one seeing the naming problem here.

Kernel increments are used mostly for application compatibility purposes, but still, the logic is lost upon us as most people would count XP as a semi-major release in comparison to 2000. I hope the guys at the Blog have an update, because this is weird.

More potential views of how this could have worked (Update 2: as well as Mike’s clarification) after the break.

Read More »

Hypothetical thoughts on what Windows 7 Milestone 3 might have.

posted on September 15, 2008 by Bryant Zadegan

The following post contains only my thoughts about the subject. As such, this posting is provided “as is” with no warranties, and confers no rights. There is absolutely no guarantee that anything you read here is even remotely true. You can interpret it as you wish, or not interpret it at all, but be aware that I could easily be way off the mark or even be lying. Keep a salt shaker handy as you read.

Alright, so I talked about Windows 7’s pillars not so long ago. Paul, along with a member of our forums, recently mentioned build 6780 as Milestone 3. This post serves as my thoughts of what might hypothetically exist in this build based on what I saw in M1. I’ll start with the applications:

Based on the trend we saw in M1, The Sidebar the thing which really shouldn’t be called the sidebar anymore will be embedded into the desktop even further, eventually annihilating the concept of a sidebar in the first place. The gadgets might remain on the side, but for all intents and purposes, the gadgets might just stay on the desktop, ready and willing to be called to the front using a key combination (not different from what you see in Vista now: Win+Space to pull gadgets to the front in Vista). It will likely be more heavily integrated into the shell than we saw in Milestone 1. Besides these changes, I doubt M3 would have anything different for the user who takes a look. The gadgets thus far would most likely be the same, though I personally hope they switch to a better codebase for the gadgets.

Wordpad and Paint will likely have seen major overhauls to their user interfaces by this point. My suspicion is that they will probably have adopted an Office-esque look along with possibly some added tools and features for both, simply for the sake of consistency. Since adding tools to Paint and Wordpad likely isn’t the Windows team’s largest focus, one could expect to see two or three tabs for the ribbon. By this point, there likely won’t be any other major changes, though seeing feature additions in the future would definitely be in line. Update 9-16-08 8:39PM: Looks like I was right. Stephen has a screenshot.

Calculator in Milestone 1 saw a few minor functional and visual tweaks, such as the addition of programming and statistics modes. With this in mind, it’s reasonable to expect the calculator to be much more aesthetically pleasing in order to follow suit with the pattern likely established by Wordpad and Paint. After all, bundled applications will be seeing an overhaul in Windows 7, so expect them to look similar in terms of design. Calculator almost definitely will not carry an Office UI, as it isn’t a productivity application per se.

Windows Media Player likely won’t see much of an overhaul from Milestone 1 besides possibly being more organized and pretty. It will also start to take a shape of its own as it turns into Windows Media Player 12.

Milestone 3 could also carry rough implementations of various technologies which carried merely a footnote’s worth of importance in Milestone 1. Quick examples:

Homegroups might actually work by now! I suspect the Homegroups feature to be much more well integrated into the networking center as well as other functions in Windows 7 Milestone 3. Joining a computer to a Homegroup, for instance, would likely be something which could be done from the Network and Sharing Center as opposed to only being established during the OOBE what used to be called the OOBE as it was in Milestone 1. It might even be possible to join a computer to multiple Homegroups , though if you only have one home, I’m not sure what good this would do.

Windows Live integration will most likely have increased compared to the first milestone. It wouldn’t be a surprise if Internet Explorer 8 accelerators found their way into Windows 7, likely with shortcuts to make things easier (such as Microphone commands and quick access to accelerators via a taskbar toolbar, perhaps). Also, as has been making the rounds recently on sites such as LiveSide and All About Microsoft, certain applications present in Windows Vista will, by now, start being subtracted from Windows and dropped under the Windows Live designation.

Themes probably wouldn’t be such a discombobulated process for the user in Milestone 3 as it was in Windows Vista. As a part of the goal to make simple tasks easier to do in Vista, a number of quick thematic combinations (visual themes. Probably nothing fancy yet) will likely find their homes in the main Personalization page by way of an iconic representation of the final outcome. Customization would still be available to those who wish to choose something less standard, but the default combos would be helpful for selecting a mode on a glance, such as a high contrast mode for those who have difficulties seeing what’s on their screen.

Other minor visual tweaks will almost definitely exist, likely in the start menu and in typical folderview. However, features such as the “superbar” seen at D6 may not be available out of the box, if at all.

That’s it for my speculative extrapolation on what Milestone 3 of Windows 7 hypothetically could contain. Tomorrow, I’ll detail how one feature which I discussed in the first serving of yam dip might work in Windows 7.

Windows 7 6519.1 – The Leak

posted on June 15, 2008 by Chris Holmes

I can give a pretty interesting perspective on the Windows 7 leak, considering said perspective is coming from someone who has had this build for 3+ months as of the writing of this post.

Before I really jump in, I should explain why leaks of this magnitude are bad. Believe it or not, these leaks do hurt Microsoft and the dev process of the operating system, especially this early in the cycle. When a leak happens, Microsoft has to devote time to investigating the leak and trying to pin down a source, ultimately the internal source or OEM who leaked it. Leaks are also bad because there are just some things that aren’t ready to be seen outside of Redmond yet, especially by the average Joe user. Say a build leaks, and average Joe doesn’t like a certain feature, or even more realistic, finds a real nasty bug. He blogs about that and next thing you know everyone is jumping on the slingfest bandwagon and presto, bad image before the product is even out of the gate.

The main thing about the 6519 leak that gets me is the fact that it leaked after so much time. I can only assume that it came from someone in the group that got the build about a month ago, and for some reason was looking for a “15 minutes of fame” moment. There is, however, a silver lining to all of this. The build is hard coded to expire on June 6th, after which date the activation system will lock you out of the system. Why someone would leak after expiration, you ask? Well it’s actually a pretty simple answer. They get their little moment of fame and (they think) cause little damage to Microsoft since Joe user can’t use it on a daily basis. The fact is though, the beta community is rather unique, we take builds of OS’s and actually use them on our machines to tinker with and see the direction that Microsoft is going with the future of Windows. With 6519, running on the current date is now impossible, but the OS can be used if you set the date back before expiration, which some will probably be willing to do, just for bragging rights.

I guess the point I am trying to make with all of this is 6519 never should have been leaked, but it is the unfortunate fact that we have some people in this community that just can’t seem to keep anything under wraps and thinks that leaking a build will gain them some kind of celebrity status. That could not be more inaccurate. Within the last few years leakers have been looked upon as the black sheep in the community, for the exact reasons that I mentioned earlier. The fact is that these people will never learn, and will likely continue to do things like this.

Windows Mobile through Apple’s iCrystalBall

posted on June 9, 2008 by Bryant Zadegan

iCrystalBall

Wired has an interesting article on how the iPhone boosted smartphone sales for other manufacturers (most notably RIM and Palm). With the next version of the iPhone now released, you might be asking yourself

  • What will Microsoft do to keep Apple from breaking into the enterprise smartphone market?
  • Why haven’t I bought this new iPhone yet?
  • What’s that pretty thing in the Crystal Ball?

Now might be a good time to analyze the potential impact Apple’s iPhone might have on Windows Mobile.

Read More »