Notes on comments.
Welcome to our blog dedicated to the engineering of Microsoft Windows 7
Welcome to our first post on a new blog from Microsoft—the Engineering Windows 7 blog, or E7 for short. E7 is hosted by the two senior engineering managers for the Windows 7 product, Jon DeVaan and Steven Sinofsky. Jon and Steven, along with members of the engineering team will post, comment, and participate in this blog.
Beginning with this post together we are going to start looking forward towards the “Windows 7” project. We know there are tons of questions about the specifics of the project and strong desire to know what’s in store for the next major release of Windows. Believe us, we are just as excited to start talking about the release. Over the past 18 months since Windows Vista’s broad availability, the team has been hard at work creating the next Windows product.
The audience of enthusiasts, bloggers, and those that are the most passionate about Windows represent the folks we are dedicating this blog to. With this blog we’re opening up a two-way discussion about how we are making Windows 7. Windows has all the challenges of every large scale software project—picking features, designing them, developing them, and delivering them with high quality. Windows has an added challenge of doing so for an extraordinarily diverse set of customers. As a team and as individuals on the team we continue to be humbled by this responsibility.
We strongly believe that success for Windows 7 includes an open and honest, and two-way, discussion about how we balance all of these interests and deliver software on the scale of Windows. We promise and will deliver such a dialog with this blog.
Planning a product like Windows involves systematic learning from customers of all types. In terms of planning the release we’ve been working with a wide variety of customers and partners (PC makers, hardware developers, enterprise customers, developers, and more) since the start of the project. We also continue our broad consumer learning through telemetry (Customer Experience Improvement Program), usability studies, and more. One area this blog will soon explore is all the different ways we learn from customers and the marketplace that inform the release.
We have two significant events for developers and the overall ecosystem around Windows this fall. The Professional Developers Conference (PDC) on October 27 and the Windows Hardware Engineering Conference (WinHEC) the following week both represent the first venues where we will provide in-depth technical information about Windows 7. This blog will provide context over the next 2+ months with regular posts about the behind the scenes development of the release and continue through the release of the product.
In leading up to this blog we have seen a lot of discussion in blogs about what Microsoft might be trying to accomplish by maintaining a little bit more control over the communication around Windows 7 (some might say that this is a significant understatement). We, as a team, definitely learned some lessons about “disclosure” and how we can all too easily get ahead of ourselves in talking about features before our understanding of them is solid. Our intent with Windows 7 and the pre-release communication is to make sure that we have a reasonable degree of confidence in what we talk about when we do talk. Again, top of mind for us is the responsibility we feel to make sure we are not stressing priorities, churning resource allocations, or causing strategic confusion among the tens of thousands of partners and customers who care deeply and have much invested in the evolution of Windows.
Related to disclosure is the idea of how we make sure not to set expectations around the release that end up disappointing you—features that don’t make it, claims that don’t stick, or support we don’t provide. Starting from the first days of developing Windows 7, we have committed as a team to “promise and deliver”. That’s our goal—share with you what we’re going to get done, why we’re doing it, and deliver it with high quality and on time.
We’re excited about this blog. As active bloggers on Microsoft’s intranet we are both looking forward to turning our attention and blogging energies towards the community outside Microsoft. We know the ins and outs of blogging and expect to have fun, provide great information, and also make a few mistakes. We know we’ll misspeak or what we say will be heard differently than we intended. We’re not worried. All we ask is that we have a dialog based on mutual respect and the shared goal of making a great release of Windows 7.
Our intent is to post “regularly”. We’ll watch the comments and we will definitely participate both in comments and potentially in follow-up posts as required. We will make sure that members of the Windows 7 development team represent themselves as such as well. While we want to keep the dialog out in the open, please feel free to use email to email@example.com should you wish to. In particular, email is a good way to suggest topics we might have a chance to discuss on the blog.
With that, we conclude our welcome post and ask you to stay tuned and join us in this dialog about the engineering of Windows 7.
Steven and Jon
Please note the availability of this blog in several other languages via the links on the nav pane. These posts are also created by members of our development team and we welcome dialog on these sites as well. We will continue to expand the list in other languages based on feedback.
Like others members already did, I'd want to stress about focusing in the development of a 64 bit OS. If everything out there is 64 bit, why mantain a 32 bit OS? I'm pretty sure that those who didn't update their rigs for years, will complain again in the future about W7 and performance.
So please, focus your development efforts in a native 64 bits, multi-CPU and GPU kernel. Other features can be implemented later.
Hello windows 7 Team!!!!
I write to advice you this:
1) Interface: i advise you, to change the icons folder because are bad, in particular, change icons foder, from vertical position to orizzontal position , in windows 7 , similar to windows xp icons folder, and high definition.
And also icons of programs: ( office icons in particular and computer-network icons: mahe a flat form for all these icons!!!!
2)always remember you to improve at maximum possible , the perfoemance of windows 7, in all of all:
Boot-very very fast in all applications ( apen-load applications) especially so many simultaneously!!!!!
Hence, massive multicore ( quad-octa core cpu) , gpgpu for all!!!!!!!!!!!!
and in the and improve very very much, the cpu-video memory and system memory use!!!!!! Improve all enormously !!!
And the manage of hard-disk drive , will be improve enormously!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Drastic and enormously improve consuption , use and fragmentation of hard-disk drive!!!!!!!!!!!!
Kernel will be real multicore power!!!!!!!!
In the end , windows 7 only 64 bit , for 64 bit version!!! Not emulation for 32 bit!!! Cut 32 bit in the 64 bit edition!!!!!!!!
First, I suggest if you want better reliability of the O/S you need to avoid program conflicts. Therefore all application programs should run in their own memory spaces with NO access to other applications memory. Hardware interfaces must be strictly intermediated by HAL (the hardware abstraction layer) with HAL drivers also confined to their own memory space. Additionally, no program should be allowed to take over all the CPU or hard drive resources of the PC thereby locking it up. The O/S should enforce resources available to applications always leaving itself interrupt capability and throtteling down useage of applications that prevent other applications from running. This implies that firewalls and virus programs may be able to interrupt the execution of another program, or examine its program memory, but not change or terminate the program without user approval.
Second, it should be unecessary to reboot the system when ana application makes changes that affect only its own operation, even if it is currently running, it should be allowed to change its own memory space. Likewise, O/S changes that do not effact running programs should not require a reboot.
Third, all programs and drivers that install registry entries or DLLs should, at the time of installation or update, have complete information stored on what was added (or simply makes use of some drivers or entries already there). In this way, no program should report that deleting some fo its components may cause other programs not to work when it is uninstalled. Instead, it should only uninstall componenets that are uniquely its own or in its own directories.
Fourth: Programs or services that are started when windows boots should be categorized according to the service they perform so that not all of these must be loaded into memory before other user applications can be run. For example a firewall or virus program should be allowed to load before internet access takes place but Wi-Fi drivers would be unecessary (absent a required Wi-Fi device).
Fifth: The capture of information at application failure should be much more specific and, if due to a bug in the operating system, generate an immediate service request.
Sixth: better use of multi-core proessing should be made by the operating system.
1) Goal: windows 7 must shine on a dual-core CPU.
Must fly on a Quad-Core cpu, must be as fast as the light on cpu Octa-Core and Cpu with 16 core in future !!!!!!!
So Windows 7 should be an operating system with "Dilit crystals."
Using this metaphor mean that Windows 7 should be so fast-stable and safe to bring the audience to travel in a new era.
Look that does not play more expensive Microsoft!!!!
Windows 7 should be the TOP operating system fully.
For you is not wrong this time!
It 'an imperative that users and businesses require, especially on 64-bit, multicore.
2) Almost we are forgetting: windows 7 must support the excellent manner in OpenGL acceleration, software 3d.
In this view windows vista was very low ,with corruption of viewport in open gl, the software 3d!
The imperative is excellent acceleration Open gl in windows 7, corruption never open gl!
Worked hard on this!
3) Optimize finally as possible, the graphical interface, already excellent Windows 7 pre beta!!!!!
Efficiency in pure gui!
Change the start buttons and window management !!!!!!
I would like a simple feature added into Windows 7, has an option. which includes the browsing of directory and file functionality changed, into a tab like view similar to internet explorer 7.
WHy did functionality have to be removed from XP? Why can't the Explorer toolbar be customizable anymore? Such as adding the delete command. And my wife and I always use the built-in windows slideshow to view pictures and while viewing the slideshow we rotate and also resize them. With Vista that's impossible (so probably W7 also)And why does loading a folder with lots of pictures cause explorer to max out it's memory usage when I start slideshow in Vista??
Windows 7 will miss the corporate mark AGAIN if there is not something done about configuration and deployment. This is only my opinion, but I have been building corporate images and managing deployments since Windows NT 3.51. I have more than 17 years experience in this area and I can tell you what I need.
I would like to see a configuratble Windows architecture. This should be very similar to the Windows Embedded toolset where I can decide what "components" I want to include in my Windows build. I should be able to, at a core level, with very simply wizards, be able to create something like Windows PE a very slim OS with nothing in it other than base communication layers (i.e. disk, network, and PNP USB support). This could be used as a utility and deployment interface with any special tools I want to add. Something this thin should be able to be booted via any device (i.e. disk, portable usb, cd, dvd, or WDS). I should be able to include any required management tools like Sysinternals, MMC (and any plug-in), AD management tools, TS Client, etc. I should be able to build out Windows the way I need it. If I want Windows without a shell, I should be able to support .NET architecture so a developer could build his own custom shell. I should be able to build Windows with nothing but a Windows Shell, toolbar, etc, and no security at all if I so choose. If I don't want firewall, UAC, etc. I should be able to exclude them from my build. With "Windows the way I want it", a thin sleek customizable OS, I could build Windows to boot from anywhere for pure cloud computing. Imagine a bootable Windows, PC's without disks to worry about, simply a Windows interface where I use IE8 as my shell. I can think of no better security than a global security model with static bootable Windows clients that can boot from any device including Windows Deployment Services...
Perhaps I dream too much, but this Windows would be a success beyond success. Performance could be based on how I build Windows and this Windows could be a true "Windows without walls". All the performance enhancements in the world could not compete with a stripped out "Windows the way I want it" architecture.
Come on Microsoft... Build me a Windows I can use!
A thing all novice users struggles to understand in Windows is that the Start Menu contains shortcuts and does not reflect what's in reality installed on the machine.
Change the Installer criteria so developers must mark the launcher(s) for a given program with some attribute so that Start Menu can figure out what to display/not display?
In effect StartMenu is then no longer a bunch of shortcuts but instead a replica of the 'Program Files'-folder.
This way StartMenu dynamically changes as apps are installed/uninstalled and you don't get obsolete or missing shortcuts all over the place.
Make 'Program Files' directory synced to Start Menu instead of them being separate concepts and add visual filters (So Start Menu only shows the exe-contents of directories)?
Hi, I would like to suggest a change in the way files are delete in windows explorer. When I delete many files and a specifc file is locked, windows explorer just aborts the deletion process. Windows explorer could just show the error message and continue with the deletion process. Thanks.
I believe this solution disables functionality used by millions of users (the ability to easily start legitimate software installed on portable devices) while still leaving a vulnerability that has been used in the past (malware autorunning from CDs/DVDs).
A better solution would be to check for signed code. This could be easily accomplished using the existing infrastructure and presented to the user simply with a minimum of coding changes.
I've put together a complete proposal with the details and screenshots here:
I just wanted to let you know, that Virtual Server 2005 SP1 R2 it's incompatible with Windows 7 RC. I had to uninstall it from my Computer in order to upgrade from Vista to Windows 7.
Like me, there are a lot of people that use this application for running a non production network (LAN) to test patches and critical updates and Drivers.
And everybody knows that most of the Microsoft certification labs run using Virtual Server.
Hopefully the Windows 7 engineering team will find a solution to this situation.
<a href="http://www.mustuniversity.com/Schools-Majors/index.asp">Online Schools</a> AND <a href="http://www.mustuniversity.com/Programs/Degree/Bachelors-Degree.html">Bachelors degree</a> AND <a href="http://www.mustuniversity.com/">Online University</a>
As we connect through this blog and through all of those talking about Windows 7 it is clear that folks have a lot of passion around many topics.? We learned early on about the passion around the boot/startup sequence and how important it was for that to go by quickly! At the same time, we know that it is really dull to watch a HDD light blink when resuming a machine from hibernate or powering up a machine. To improve this first connection with people, we set out to improve the boot sequence—jazz it up if you will.
I recently sent an email from the link on the main Engineering Windows 7 blog page about sound glitches on my system.
I was surprised to receive a reply and offer of help from Steve Ball who guided me through some steps to help the Microsoft engineers locate the source.
To cut a long story short, it wasn't too long before the problem source was located and a fix implemented.
I am very grateful for Steve Ball's assistance.
Overall, I find Windows 7 to be an extremely solid and polished OS.
Thank you Steve for being so helpful. :)
What's MS direction toward Windows and Windows Live? I really hope you can address this in future blog.
For what I have seen so far. Windows Live is the solution to the annoying EU law suites. I does not come with Windows and it is free. Windows Live app is better than Windows Vista counter part. So I can assume that Windows Live is more like a solution to modular OS (only this targets user applications rather than OS engineering). After all, the naming is catchy. Instead of MSN, it is re-branded as "Windows" Live.
So here is a list of questions:
1) Does Windows7 comes with its own Mail app, but doomed to be crappier than Windows Live Mail? Or Windows7 will not include a Mail app? (applies to Photo Gallery and other Live app)
2) How are you going to bundle Window Live?
3) Why get Windows7 if Windows Live runs on older Windows? Same problem to Vista.