The "Ecosystem"

Artigo
09/18/2008

In the emails and comments, there are many topics that are raised and more often than not we see the several facets or positions of the issue. One theme that comes through is a desire expressed by folks to choose what is best for them. I wanted to pick up on the theme of choice since that is such an incredibly important part of how we approach building Windows—choice in all of its forms. This choice is really because Windows is part of an ecosystem, where many people are involved in making many choices about what types of computers, configuration of operating system, and applications/services they create, offer, or use. Windows is about being a great component of the ecosystem and what we are endeavoring to do with Windows 7 is to make sure we do a great job on the ecosystem aspects of building Windows 7.

Ecosystem and choice go hand in hand. When we build Windows we think of a number of key representatives within the ecosystem beyond Windows:

PC makers
Hardware components
Developers
Enthusiasts

Each of these parties has a key role to play in delivering on the PC experience and also in providing an environment where many people can take a PC and provide a tailored and differentiated experience, and where companies can profit by providing unique and differentiated products and services (and choice to consumers). For Windows 7 our goals have been to be clearer in our plans and stronger in our execution such that each can make the most of these opportunities building on Windows.

PC Makers (OEMs) are a key integration point for many aspects of the ecosystem. They buy and integrate hardware components and pre-install software applications. They work with retailers on delivering PCs and so on. The choices they provide in form factors for PCs and industrial design are something we all value tremendously as individuals. We have recently seen an explosion in the arrival of lower cost laptops and laptops that are ultra thin. Each has unique combinations of features and benefits. The choice to consumers, while sometimes almost overwhelming, allows for an unrivaled richness. For Windows 7 we have been working with OEMs very closely since the earliest days of the project to develop a much more shared view of how to deliver a great experience to customers. Together we have been sharing views on ways to provide differentiated PC experiences, customer feedback on pre-loaded software, and partnering on the end-to-end measurement of the performance of new PCs on key metrics such as boot and shutdown.

Hardware components include everything from the CPU through the “core” peripherals of i/o to add-on components. The array of hardware devices supported by Windows through the great work of independent hardware vendors (IHVs) is unmatched. Since Windows 95 and the introduction of plug-and-play we have continued to work to improve the experience of obtaining a new device and having it work by just plugging it in—something that also makes it possible to experience OS enhancements independent of releases of Windows. This is an area where some express that we should just support fewer devices that are guaranteed to work. Yet the very presence of choice and ever-improving hardware depends on the ability of IHVs to provide what they consider differentiated experiences on Windows, often independent of a specific release of Windows. The device driver model is the core technology that Microsoft delivers in Windows to enable this work. For Windows 7 we have committed to further stabilization of the driver model and to pull forward the work done for Windows Vista so it seamlessly applies to Windows 7. Drivers are a place where IHVs express their differentiated experience so the breadth of choice and opportunity is super important. I think it is fair to say that most of us desire the experience where a “clean install” of Windows 7 will “just work” and seamlessly obtain drivers from Windows Update when needed. Today with most modern PCs this is something that does “just work” and it is a far cry from even a few years ago. As with OEMs we have also been working with our IHV partners for quite some time. At WinHEC we have a chance to show the advances in Windows 7 around devices and the hardware ecosystem.

Developers write the software for Windows. Just as with the hardware ecosystem, the software ecosystem supports a vast array of folks building for the Windows platform. Developers have always occupied a special place in the collective heart of Microsoft given our company roots in providing programming languages. Each release of Windows offers new APIs and system services for developers to use to build the software they want to build. There are two key challenges we face in building Windows 7. First, we want to make sure that programs that run on Windows Vista continue to run on Windows 7. That’s a commitment we have made from the start of the project. As we all know this is perhaps the most critical aspect of delivering a new operating system in terms of compatibility. Sometimes we don’t do everything we can do and each release we look at how we can test and verify a broader set of software before we release. Beta tests help for sure but lack the systematic rigor we require. The telemetry we have improved in each release of Windows is a key aspect. But sometimes we aren’t compatible and then this telemetry allows us to diagnose and address post-release the issue. If you’ve seen an application failure and were connected to the internet there’s a good chance you got a message suggesting that an update is available. We know we need to close the loop more here. We also have to get better at the tools and practices Windows developers have available to them to avoid getting into these situations—at the other end of all this is one customer and bouncing between the ISV and Microsoft is not the best solution.

Our second challenge is in providing new APIs for developers that help them to deliver new functionality for their applications while at the same time provide enough value that there is a desire to spend schedule time using these APIs. Internally we often talk about “big” advances in the GUI overall (such as the clipboard or ability to easily print without developing an application specific driver model). Today functionality such as networking and graphics play vital roles in application development. We’ve talked about a new capability which is the delivery of touch capabilities in Windows 7. We’ve been very clear about our view that 64-bit is a place for developers to spend their energy as that is a transition well underway and a place where we are clearly focused.

Enthusiasts represent a key enabler of the ecosystem, and almost always the one that works for the joy of contributing. As a reader of this blog there’s a good chance you represent this part of the ecosystem—even if we work in the industry we also are “fans” of the industry. There are many aspects to a Windows release that need to appeal the enthusiasts. For example, many of us are the first line of configuration and integration for our family, friends, and neighbors. I know I spent part of Saturday setting up a new wireless network for a school teacher/friend of mine and I’m sure many of you do the same. Enthusiasts are also the most hardcore about wanting choice and control of their PCs. It is enthusiasts sites/magazines that have started to review new PCs based on the pre-installed software load and how “clean” that load is. It is enthusiasts that push the limits on new hardware such as gaming graphics. It is enthusiasts who are embracing 64-bit Windows and pushing Microsoft to make sure the ecosystem is 64-bit ready for Windows 7 (we’re pushing of course). I think of enthusiasts as the common thread running through the entire ecosystem, participating at each phase and with each segment. This blog is a chance to share with enthusiasts the ins and outs of all the choices we have to make to build Windows 7.

There are several other participants in the ecosystem that are equally important as integration points. The system builders and VARs provide PCs, software, and service for small and medium businesses around the world. Many of the readers of this blog, based on the email I have received, represent this part of the ecosystem. In many countries the retailers serve as this integration point for the individual consumer. For large enterprise customers the IT professionals require the most customization and management of a large number of PCs. Their needs are very demanding and unique across organizations.

Some have said that the an ecosystem is not the best approach that we could do a much better job for customers if we reduce the “surface area” of Windows and support fewer devices, fewer PCs, fewer applications, and less of Windows’ past or legacy. Judging by the variety of views we've seen I think folks desire a lot of choice (just in terms of DPI and monitor size). Some might say that from an engineering view less surface area is an easier engineering problem (it is by definition), but in reality such a view would result in a radical and ever-shrinking reduction in the choices available for consumers. The reality is engineering is about putting constraints in place and those constraints can also be viewed as assets, which is how we view the breadth of devices, applications, and “history” of Windows. The ecosystem for PCs depends on opportunities for many people to try out many ideas and to explore ideas that might seem a bit crazy early on and then become mainstream down the road. With Windows 7 we are renewing our efforts at readying the ecosystem while also building upon the work done by everyone for Windows Vista.

The ecosystem is a pretty significant in both the depth and breadth of the parties involved. I thought for the purposes of our dialog on this blog it is worth highlighting this up front. There are always engineering impacts to balancing the needs each of the aspects of the ecosystem. Optimizing entirely along one dimension sometimes seems right in the short term, but over any period of time is a risky practice as the benefits of a stable platform that allows for differentiation is something that seems to benefit many.

With Windows 7 we committed up front to doing a better job as part of the PC ecosystem.

Does this post reflect your view of the ecosystem? How could we better describe all those involved in helping to make the PC experience amazing for everyone?

--Steven

Comments

Anonymous
September 18, 2008
What about the choice that the OS UI and OS features provide in terms of customizability? In that sense, Vista seems to narrow down everything available to power users and oversimplify stuff. Apps such as the Disk Defragmenter are a classic example. What about the choice which MS is giving less and less to Do-It-Yourselfers compared to what it does for OEMs (such as making MS software available exclusively through OEMs)? Vista still has some serious bugs by design in its driver UI/"experience". The other day I was installing a new device which failed initially because the drivers were on disc and I hadn't inserted the disc. Fair enough, but now when I go to install the driver automatically or using Have Disk, either way it fails and gives an error saying "Windows found software for your device but encountered an error while attempting to install it.". I have gone mad searching the knowledge base and the internet for a solution and while the same error comes up for another issue (a corrupt INFCACHE.1 file/pre-SP1 issue), that does not apply in my case. I cannot install my hardware without reinstalling when my existing installation is a new clean one! The "Found new hardware" wizard does NOT even allow users to choose from a list of available device drivers assuming that Vista has a driver in its database or online. You have to go to Device Manager and start the "Update Driver" wizard to manually choose a driver from a list. I've enabled Error Reporting and always submit the errors from Problem Reports and Solutions but a solution does not seem to exist except reinstalling for the device driver to install properly.
Anonymous
September 18, 2008
The comment has been removed
Anonymous
September 18, 2008
The comment has been removed
Anonymous
September 18, 2008
Windows "Ecosystem" ?? WORLD
Anonymous
September 18, 2008
"Optimizing entirely along one dimension sometimes seems right in the short term, but over any period of time is a risky practice as the benefits of a stable platform that allows for differentiation is something that seems to benefit many." --Steven The ecosystem... I think it's more than that, when you design Windows. It's about other operating systems, the mistakes of the past, the education system (and other OS byproducts) and the power Microsoft gets from an operating system.

Other operating systems. Why do you think Windows is number one worldwide and not another OS? Why IBM compatible PCs became top of the world? Why lots of companies prefer Windows to unix systems?
Mistakes of the past What was the main problem with Vista? Could it be UAC or DRM? How do you explain that "IBM compatible" laptops are doing well, even though they are not actually customizable? Are they going to survive in the future without "IBM compatible" and customizable desktop PCs?
The education system (and other OS byproducts) How profitable is the involvement of Microsoft in the education system? Could this ever exist without an operating system that is widely used?
The power Microsoft gets from a widely used operating system Profits from education, from companies, from other Microsoft products, all are connected to Windows. Simple users of the IBM compatible platform chose DOS and then Windows as their favorite platform. This is the real power of Microsoft. Break this connection, or make them angry and you lose everything. Optimizing entirely along one dimension is not right as Steven said. Though Windows users deserve special attention.

Anonymous
September 18, 2008
The comment has been removed
Anonymous
September 18, 2008
The comment has been removed
Anonymous
September 19, 2008
From today we can see Windows Ecosystem much drawn near http://www.microsoft.com/windows/default.aspx?icid=winvan I'm PC
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
The UI consistancy between apps both pre bundled (MS apps) and Dell or HP added is a major issue. Dont believe me Check out the http://www.aerotaskforce.com/ this site is full of enthuists pointing out old/inconsistant ui issues within the shell and preloaded vista apps.
Anonymous
September 19, 2008
... Okay, this is all well and good, but: With the targeted release of 2010, isn't all of this discussion kind of moot? The feature set should be determined by now if there's any hope of a decent Beta/RC cycle. The goals and features should be laid out by now and be locked. What are they?
Anonymous
September 19, 2008
I would like to say I really like reading this blog. On this particular topic I was reminded of something that annoys me with drivers. This is that the regular joe using his PC will find it diffucult to remove a driver for a specific hardware device even with explaination from a professional over the phone. I presonally would like to see something similar to 'Programs and Features' on Vista for 3rd party drivers. This could also have an option to view other drivers. The same could be said for problematic Codecs and make it easier for the end user to check if they even have the correct codecs to view a certain file. I find this information hidden in the depths of the system folders and as they say 'where angels fear to tread'. I really do like the fact that with Vista a lot of the regular hardware is plug and play, and often the windows OS drivers work better than that of actual hardware manufacturers. I really look forward to more comments on this topic and any future topics you present us with.
Anonymous
September 19, 2008
Why is the consumer not on the list? Surely they are the most important. The issue MS have is balancing between everyone. You dont want to make it tooo simple so that a sysadmin screams, but you dont want to use really long acronyms to annoy non-experienced people with computers. That is a hard one to fix, and I dont know a way on how to do it (Profiles e.g. User, Programmer etc. arent a good idea IMO).
Anonymous
September 19, 2008
@lsproc was certainly an oversight
Anonymous
September 19, 2008
I know MS likes to model different types of users and role-players into typified categories, but this can over-simplify what we do. For example, the notion that OEMs will never need to do a non-destructive or upgrade OS install - the assumption being that OEMs are so large, with such low levels of service quality, that they would never stoop to helping individual users at that level. However, as a small OEM, I often have requests to build new systems while preserving crucual but abandoned applications, i.e. those that cannot "just" be re-installed. In such cases I may have to preserve the application by installing the new OS over the old one. That's one example, but similar problems crop up elsewhere. The same user may be a non-tech consumer of certain aspects of the system, and an enthusiastic control freak in others ;-)
Anonymous
September 19, 2008
The first comment about driver installation issues reminded me of a Vista bug. It's often necessary to clear out Temp and Temporary Internet Files locations, e.g. as part of cleaning out malware (some tools automate this). It's usually best to do this "from orbit" rather than in the OS, and often one deletes the whole subtree rather than just the contents. If you do this in XP, no problem; the subtrees are re-spawned as needed. If you do this in Vista, it's often apparently OK, too - until months later, when some installation process fails. When this happens, the error messages you see will imply an unreadable source (e.g. file not available on CD-ROM drive). Copying the installation material somewhere else will cause the same error messages to refer to that new location. What's really happening is that Vista is trying to bounce this original source material through a Temp location that no longer exists. It fails to re-spawn the location (as XP does) and it also fails to report the error correctly, mis-reporting the "missing destination location" situation as "missing source material" instead. Please fix this in W7, and Vista too?
Anonymous
September 19, 2008
Of course consumers (aka everyone) are part of the ecosystem. When I was writing this my mindset was that the ecosystem is there to serve consumers. I hope that makes sense. --Steven
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
I believe that these are most of the important ecosystems to get to the end user experience. The problem comes when the end user doesn't know what to do when something doesn't work. If software or hardware isn't compatible with the OS, many people won't even bother trying to fix it or make it work because it's too much of a hassle. When you are talking about choice and customization, you come down to people who do know what they're doing and people who don't. Everything has to work in tandem between the ecosystems, though it often doesn't, which causes a majority of problems that people have with computers.
Anonymous
September 19, 2008
Steven - I think that ordinary users ("consumers", if you like) also serve each other. I say this looking at the way the staff in my department, none of whom is an expert or enthusiast, try to help each other through their computer problems before calling the IT guy. Also, the greatest "service" ordinary users give each other, and thereby are part of the ecosystem, is through word of mouth and helping each other. Vista has an awful reputation here because of experiences of several secretaries and PAs who decided that it was the pits to use, and kicked up such a fuss among themselves that I personally had to intervene and authorize the installation of XP on their Vista laptops. They're now very happy with XP, but continue to rubbish Vista very powerfully to their colleagues and friends. I do think that the ordinary user (however you define and segment him/her) has a role to play in the Windows ecosystem.
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
@Steven, I don't want to write here agressive comment...but I simply don't agree with some points from your post. > For Windows 7 we have been working with OEMs > very closely since the earliest days of the > project to develop a much more shared view of > how to deliver a great experience to customers

I think, that Microsoft was working closely during developing each Windows version. Results aren't too nice: OEMs are selling often Windows in form of hidden installation partition on disk (no CD/DVD), which can accessed and infected. There are added many programs, which can't be totally uninstalled. You can't create partitions like you want (you can reformat all HDD only). If this is great experience, something is wrong here. 2.I repeat my question: if you know problem of big resolutions, why can't you propose to manufacturers building computers (notebooks, netbooks) with smaller resolutions ? why can't you change "Designed for..." program and force them for it ? why can't you give new label "small/medium/large fonts in WIndows" (or something like that) ?

And some more comments: why have you forgotten about "end users" ? (I will repeat it although I have seen your comment) have you forgotten, that they're the most important ? and they don't like DRM (which makes problems for legal users only) - what is your opinion about ? will you increase it in Windows 7 ? what do you think about their problems with getting installation CD/DVD for their OEM system ? (and please don't say, that this is issue between OEM and end user)

Anonymous
September 19, 2008
The comment has been removed
Anonymous
September 19, 2008
PC Makers (OEMs)... Together we have been sharing views on ways to provide differentiated PC experiences, customer feedback on pre-loaded software, and partnering on the end-to-end measurement of the performance of new PCs on key metrics such as boot and shutdown. --Steven A PC is "IBM compatible" and customizable by the end user. Mac hardware vanished from earth. "IBM compatibles" won the battle. But Macs are still not customizable. They are Macs. I'm a PC. I have the freedom to use the same Windows OS on any IBM compatible hardware I choose. And it works. Break this connection and you are a Mac. Is Seven a PC or a Mac? Windows users deserve special attention.
Anonymous
September 19, 2008
@mariosalice, "Mac hardware vanished from earth" Hey, just to bring some fun into this discussion, I've found that there must be at least one mac left... http://www.appleinsider.com/articles/08/09/19/microsofts_im_a_pc_campaign_created_with_macs.html
Anonymous
September 19, 2008
PC means no artificial locks. PC Makers (OEMs)can freely build a certain hardware to give the same experience after installing Windows. Lock a special Windows edition to a certain OEM and this version of Windows is no more a PC. Though you may sell additional functionality, with certain hardware configurations as an extra, to everyone. This is still a PC.
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 20, 2008
@AndiG were is a problem?? See here http://pixobebo.com/index.php/pixonomy/articles/goodbye_mac_hello_windows_vista/
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 20, 2008
You talk about developers, but MS seems to favor VBScript and C# -languages it created. Let's face it, every developer writes Javascriptm, so why not broaden the devleoper ecosystem by making this language a first class language for Windows 7 and other Microsoft products. To be a first class language, you need to provide documentation and examples of use of all the major subsystems in the language. I mention Javascript, but other scripting languages should be considered, even if Microsoft doesn't provide the interpreter.
Anonymous
September 20, 2008
@stat_soft Windows 7 beta 1 is rumored to be released in December, currently in USA we have a little financial crisis (and people think more about "normal" things and don't work so good in such atmosphere), we don't see any excellent posts on this forum (like - yes, we will make such and such architecture changes), only "I'm a PC" campaign... Does Microsoft have enough power for making system with new kernel and architecture ? I have bigger and bigger doubts. It looks more and more, that Windows 7 can be Vista SP2 - no separating apps from each other, no known Windows XP interface, no Windows XP performance... And I don't want to write FUDs here. Market is changing - EA has notified, that DRM is wrong (see Spure game issue), more companies are joining it, DirectX 10 is not so popular (we have consoles from various manufacturers), etc. etc. Microsoft must notify it. If not, PC will be less and less used. Maybe it will be better for end users, maybe not. We will see...
Anonymous
September 20, 2008
@marcinw, you hit the point - I totally agree with you. When I read this post about ecosystem, I felt the same way as I felt when I saw the first episode of Microsofts campaign with Bill Gates and Seinfeld. i think there will be no big changes and it is already too late to discuss anything if Windows 7 beta will already appear in december this year.
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 20, 2008
Based on the current M3 screenshots and info I've heard from my sources, this blog is basically a waste of time to the public (or breath if we were talking face to face). You might be reading what we write but are you taking the information, advice, and critiques and actually using it? I think the latest M3 release answers that question. The next release of Mac OS will allow me to install Mac OS X on my PC. My PC wasn't supported on the current Leopard because NVidia had not created drivers yet. This will be resolved in Snow Leopard and I will be making the switch. I've made my living developing on Microsoft platforms and technology. Heck, Microsoft probably paid for my house. It's time to move on though. Too much was promised in Vista and then cut at the last minute. I'll see you all on the flip side (or on the way back up the stairs). Peace!
Anonymous
September 20, 2008
The next release of Mac OS will allow me to install Mac OS X on my PC. -- Kosher Are you talking about illegal installation on PCs with certain configuration? Microsoft considers "enthusiasts" the representatives of Windows users in their ecosystem. I am glad to hear from Steven that this ecosystem works for end users.
Anonymous
September 20, 2008
I would like to hear more about Microsoft's thoughts on the OEM 'crapware' bundling problem that PCs currently have.
Anonymous
September 20, 2008
mariosalice, It so happens that I purchased Mac OSX family pac for an old Macbook Pro and yes there are ways to install it on Intel hardware without buying a Mac. I just consider myself ahead of the curve in that regard. I used to be a Windows enthusiast but lost hope when they axed WinFS and nearly tossed out .NET 3.5 from the Windows SDK. I can see right through this blog about as clearly as I can see through the windows in the glass theme. Enjoy the next release. I am sure it will be everything you wanted and more.
Anonymous
September 20, 2008
The comment has been removed
Anonymous
September 21, 2008
The comment has been removed
Anonymous
September 21, 2008
@prixel inherent Ecosystem ??
Anonymous
September 21, 2008
I'm glad we are talking about our view of the ecosystem because it puts things in their place. This discussion can help erase some stereotypes. I'm pesonaly interrested in this discussion because I'm a philosopher and Windows plays an important role in our cultural environement. The way the next windows release will be designed will influence the daily life and work of billions poeple. Just think how many days of work one hundred millions poeple spending 2 minutes for, say, disabling superfetch. I calculated it makes 1600 payroll years lost, just disabling superfetch (assuming they do it at work - 380 real years otherwise)! Imagine the economic loss, globaly, of such insignificant thing... That's why it's extremely important that Microsoft not seek to talk only with industrial partners or huge incorporated clients. The "enthousiasts" plays an important role because what they say (what we say on this blog comments and on other forums) are things that will never appear in the statistics and will never be told by OEM partners. We are the voice of the millions of individual users. Not a perfect voice, but a voice nonetheless. The difference between us, the "enthousiasts" and the pa-and-mum and my sister type of users is that we know why, technicaly, they don't like Vista (or why they like it if you will). If Windows 7 developement reflects this view, I'm convinced that it will be a major version.
Anonymous
September 21, 2008
@Kosher, yes, I can read on more and more forums, that Windows 7 M3 is looking like Vista (I understand, that it's normal to start work from previous version, but in situation, when Vista and Vista interface is not too liked, it's a little strange for me) and the most notified changes are such "great" features like ribbons in default applications or new calculator... if this is future, I will be not PC probably ;-)
Anonymous
September 22, 2008
"yes, I can read on more and more forums, that Windows 7 M3 is looking like Vista (I understand, that it's normal to start work from previous version, but in situation, when Vista and Vista interface is not too liked, it's a little strange for me) and the most notified changes are such "great" features like ribbons in default applications or new calculator... if this is future, I will be not PC probably ;-)" I would like the windows 7 interface to be "simpler". I have nothing against a managed desktop or pixel shaded windows, but I think the vista ui could have been just a bit more clean from lines and stuff :)
Anonymous
September 22, 2008
I wouldn't mind if the UI look was similar or heck even the same as vista. But do remove some glaring UI inconsistencies in the interface. For starters please trash that Windows 95 style look for Wordpad. :)
Anonymous
September 22, 2008
Yes, I know; wrong thread for a wish list, but here goes nothing. I want Windows 7 to have:

Fonts with all the glyphs in Unicode 5.1
Finnish Speech Recognition
Finnish SAPI Speaker (male and female voices)
Both 64-bit and 32-bit versions on the same DVD disc
Ability to run old 16-bit DOS and Windows programs without installing VMware or VirtualPC. If I just double click the 16-bit calendar.exe, I want it to start without error messages (even in 64-bit Windows 7!)
WinFS
Windows PowerShell
Virtual desktops
Packet management
Unix-like directory structure (drive letters (from A: to Z:) could run out so easily!)
Mount-command (DOSBox has mount-command! http://www.hackszine.com/blog/archive/dosbox-vista.png)
Support for more than two physical processors
Support for larger amount of RAM
Support for (U)EFI (even in the 32-bit Windows 7!)

Anonymous
September 22, 2008
Win FS?? http://blogs.zdnet.com/Bott/?p=516
Anonymous
September 22, 2008
What kind of work has been done by Microsoft to get CableCard capability for media centers to smaller PC Makers? Thanks
Anonymous
September 22, 2008
What kind of work has been done by Microsoft with Cablelabs to get CableCard capability for media centers to smaller PC Makers? Thanks
Anonymous
September 22, 2008
WinFS, Thing is NTFS is a bit old. You need a replacement. Probably not WinFS though. I mean drive letters??? I found for exp search on Mac or Linux much faster. The filesystem is more responsive. You can rename or move files while they are open.
Anonymous
September 22, 2008
The comment has been removed
Anonymous
September 22, 2008
The comment has been removed
Anonymous
September 22, 2008
As one of the enthusiasts, one thing that I have always thought would be nice from the ecosystem is better in-system identification of hardware. It's happened plenty of times: I come to help fix a friend's computer and somehow the sound card (or some other device) isn't working. I check the Device manager to see if the drivers are in order, and there's absolutely nothing helpful to be found. The automatic driver installation fails, because it can't find what the hardware is. Then you're left to opening up the case on the unreliable chance that the make and model will be printed on the card. In light of this sort of problem, I could see some real benefit in well identified hardware at all contact points in the OS. A collaborative effort from Microsoft and the hardware vendors could result in some kind of unique, identifiable tag for a better experience. Maybe that's how the Plug-n-Play system already works, but it could use some improvements. A unique code automatically identified from a list online (hence up to date and not restricted to the list available when the OS was released) would go a long way to making troubleshooting easier. Identify the devices to the user in a legible and meaningful way, because "Generic Video Card" doesn't help much when you're trying to get things fixed.
Anonymous
September 22, 2008
These WinFS haters don't really understand what WinFS meant for the big picture. See, what really happens in WinFS is two things really: #1: You know all of those applications out there that microsoft keeps creating that have contacts, media, etc? Well they all have many things in common with their data but none of them really share data nicely. They each use a separate API or backing store for their information. The "schema" for those applications would be unified with WinFS. That scheme would allow ISVs and other developers to tie into a single API to gain the ability to add contacts across multiple applications. I for one DO NOT want to store this data in a "cloud" that I don't own. That's where WCF came in and where the P2P client, which was also axed came into play (but that's a whole different discussion really). #2. WinFS would allow the registry, files, active directory, and other "elements" in the filesystem to interact very easily. It would unify the "Backing store" for the various services that windows uses and allow each of these services to share common types via point #1. So next time you see some guy on ZDNet write about something he doesn't understand, make sure you understand what he doesn't. And lastly, if you knew the real reason that WinFS was dropped, you would see where Microsoft is at today and why it lives in a never ending paradox. They argue that having SQL server be a dependency that is required for your system to boot would be too much of a potential point of failure. SQL server is a very complex beast that, if not started, would cause your entire OS to sit around waiting for its core. In reality though, the problem is more political than anything else and I would hate to be at Microsoft during this huge blunder. So many great products were lost in translation.
Anonymous
September 22, 2008
These WinFS haters don't really understand what WinFS meant for the big picture. See, what happens in WinFS is two things really: #1: You know all of those applications out there that microsoft keeps creating that have contacts, media, etc? Well they all have many things in common with their data but none of them really share data nicely. They each use a separate API or backing store for their information. The "schema" for those applications would be unified with WinFS. That schema would allow ISVs and other developers to tie into a single API to gain the ability to add contacts across multiple applications. I for one DO NOT want to store this data in a "cloud" that I don't own. That's where WCF came in and where the P2P client, which was also axed came into play (but that's a whole different discussion really). #2. WinFS would allow the registry, files, active directory, and other "elements" in the filesystem to interact very easily. It would unify the "Backing store" for the various services that windows uses and allow each of these services to share common types via point #1. So next time you see some guy on ZDNet write about something he doesn't understand, make sure you understand what he doesn't. And lastly, if you knew the real reason that WinFS was dropped, you would see where Microsoft is at today and why it lives in a never ending paradox. They argue that having SQL server be a dependency that is required for your system to boot would be too much of a potential point of failure. SQL server is a very complex beast that, if not started, would cause your entire OS to sit around waiting for its core. In reality though, the problem is more political than anything else and I would hate to be at Microsoft during this huge blunder. So many great products were lost in translation.
Anonymous
September 22, 2008
And one additional point... WinFS in a P2P situation would be that so called "cloud". Why not own the cloud system if you're always connected via a cable connection like 90 percent of us are? Why share your personal and business data with Google et al? BE THE CLOUD. Think "you are the cloud", not this mentality that someone else owns you and your information. WinFS ... Just do it!
Anonymous
September 22, 2008
WinFS with WCF and P2P would turn us all into a part of the cloud owning our own data and sharing only what we want to. WinFS would enable an occasionally connected API that would tie into many other applications out there through a single API with a single schema defining the common types like "user, contact, role, telephone number, geo location, email message, file, media, etc.". Why must these fundamental data types, objects, and overall schema be replicated with no ability to talk to eachother? Tie it all together with one API, one Schema (Outlook, Windows Mail, Live Mail, all of your contacts, MS CRM, SharePoint, Active Directory, the list goes on) all using a single unified schema and single backing store. Each application would have its own ability to synchronize with the WinFS data through its own copy of the schema and own instance of SQL server. You just don't know a good thing until it hits you in the face.
Anonymous
September 22, 2008
The comment has been removed
Anonymous
September 22, 2008
The comment has been removed
Anonymous
September 23, 2008
The comment has been removed
Anonymous
September 23, 2008
The comment has been removed
Anonymous
September 23, 2008
The comment has been removed
Anonymous
September 23, 2008
@marcinw I can assure you that Microsoft employees are just as critical, maybe even more so, then those outside of the company. We use these products every day, are shareholders of the company and are very passionate about the software and solutions produced by this company. In terms of international exposure, our products are created, tested and dogfooded (internal beta testing) by one of the most international organizations in the world. It is difficult to be perfect all the time, especially when your systems are used in so many different ways, in so many different places and on so many different types of hardware. That is not necessarily an excuse, it is a mandate - our stuff has to live up to that standard. From Sales and Marketing to Technical Roles we are all committed to this.
Anonymous
September 23, 2008
The comment has been removed
Anonymous
September 23, 2008
The comment has been removed
Anonymous
September 24, 2008
It looks to me like the PnP protocol is ready for another spin. What are we missing and what can be improved?

Windows can identify the device by it's ID, but human-readable full product model, manufacturer and description are not always available, or not displayed to the user in an intuitive way. This information must be included into the hardware signature.
Hardware identification information should contain a link to web pages containing information about the product and a link to the location of the latest digitally signed driver package. This can tremendously help installing and updating drivers when a network connection is available, and to troubleshoot driver issues.
New hardware that is Windows 7 certified must be compatible with the core Windows Hardware Class drivers (e.g. PCI Express Graphics Controller, PCI Network Adapter, USB Video Capturing Device). When a new class of hardware is created, hardware manufacturer must submit it to Microsoft for certification, after which the new Windows Hardware Class Driver can be published in the Online Windows Driver Repository.

Anonymous
September 24, 2008
> The images you're talking about are > leaked M3 shots, > [...] I'm talking about really different sources... Steven needs to make release on the time and I'm going to afraid, that 7 will be mainly Vista (with Vista architecture issues) with removed by default some apps or possibility of making it (there will be added required inf/msi files) > It looks to me like the PnP protocol is ready > for another spin. What are we missing and > what can be improved? > [...] what Microsoft could do is displaying possible vendor of device based on IDs (Intel - 8086, etc.) > Overclockers and such represent maybe > 10~15$ of the market? Less? [...] Its worth > stating though that most people > overclock for performance > [...] Let's say the truth - many people read, that AMD CPUs are not so overclockable like Intel's and because of it they don't buy them (although will never use it). And this is not only my opinion... People hear overclockers a lot.
Anonymous
September 24, 2008
The comment has been removed
Anonymous
September 24, 2008
The comment has been removed
Anonymous
September 24, 2008
Vista was a frustrating release for me because for most users, I've had to install a virtual machine with Windows XP due to compatibility issues. It would be great if the next version of Windows had a built-in Virtual PC you could use to run XP applications in a transparant fashion. For example, without seeing the Virtual PC window borders. This would also ease the introduction of Vista/Windows7 in the corporate environment.
Anonymous
September 25, 2008
The comment has been removed
Anonymous
September 25, 2008
The comment has been removed
Anonymous
October 06, 2008
My entire understanding of just how much goes into Windows' backward compatibility was revamped when I read "The Old New Thing".
Anonymous
October 27, 2008
The comment has been removed
Anonymous
December 10, 2008
Well, i write for ask you this :: 1)In windows 7 , users should forget to make a defragmentation!!!!! So find a way so that the hard disk management in Windows 7, is very efficient , very fast and optimized!!!! No defrag for users, the user in Windows 7 must only work, not think about nothing else. Therefore find ways to optimize the management of records, and in performance with very low fragmentation !!!!!!!!!! That's very very important, windows 7 Team!!!!!!!!!!! Windows 7 will be easy , very very easy!!!!!!!!!!!! Just fragmentation, once and for all. The users are annoys to Defragment windows!!!!!!!!!!! Find a way to do this, maybe make an Api specific for this!!!!! 2)Reduce enormously , the memory and cpu occupation and consuption and Aero interface consuption, because also this , is very very important, for the windows 7 success!!!!! otherwise you risk really being overtaken by competitors this time!!!!!!!!!!!!!!!!

Multicore cpu consuption, will be balanced on each Core of quad-core and octa-core Cpu !!!!!! "And listen to the advice of a stupid user once every so often" Thanks!!!!!!

Anonymous
December 14, 2008
The comment has been removed
Anonymous
June 24, 2009
What kind of work has been done by Microsoft with Cablelabs to get CableCard capability for media centers to smaller PC Makers? Thanks
Anonymous
June 24, 2009
Windows "Ecosystem"?? what this?
Anonymous
August 15, 2009
You might be reading what we write but are you taking the information, advice, and critiques and actually using it? I think the latest M3 release answers that question. The next release of Mac OS will allow me to install Mac OS X on my PC. My PC wasn't supported on the current Leopard because NVidia had not created drivers yet. This will be resolved in Snow Leopard and I will be making the switch. I've made my living developing on Microsoft platforms and technology. Heck, Microsoft probably paid for my house. It's time to move on though. Too much was promised in Vista and then cut at the last minute. I'll see you all on the flip side (or on the way back up the stairs).
Anonymous
November 23, 2009
I was surprised to discover that if you right click an exe program in Vista and select 'properties', you have a choice of 'compatibility mode' starting with Windows 95. Incl. my favorite Win ME that had a lot of good try-out ideas for XP.
Anonymous
April 24, 2010
I believe that these are most of the important ecosystems to get to the end user experience. The problem comes when the end user doesn't know what to do when something doesn't work. If software or hardware isn't compatible with the OS, many people won't even bother trying to fix it or make it work because it's too much of a hassle. When you are talking about choice and customization, you come down to people who do know what they're doing and people who don't. Everything has to work in tandem between the ecosystems, though it often doesn't, which causes a majority of problems that people have with computers.
Anonymous
May 14, 2010
"Now Social sites have become a necessary part of my life and not only for killing my time but also for my business activites, I have to spend a huge amount of time in the world of social media. Roughly speaking, I spend more than seven hours each day on such sites but ya I love to stay in such sites"

Compartilhar via

The "Ecosystem"

Comments

Recursos adicionais