Movie Maker En Windows 7
Edelira Longinotti
What is there? The following garbage is there. Microsoft Autoupdate Exclusive test package, Microsoft Autoupdate Reboot test package, Microsoft Autoupdate testpackage1, Microsoft AUtoupdate testpackage2, Microsoft Autoupdate Test package3.
Someone decided to trash the one part of Windows that was usable? The file system is no longer usable. The registry is not usable. This program listing was one sane place but now it is all crapped up.
But that is just the start of the crap. Later I have listed things like Windows XP Hotfix see Q329048 for more information. What is Q329048? Why are these series of patches listed here? Some of the patches just things like Q810655 instead of saying see Q329048 for more information.
So after more than an hour of craziness and making my programs list garbage and being scared and seeing that Microsoft.com is a terrible website I haven't run Moviemaker and I haven't got the plus package
The lack of attention to usability represented by these experiences blows my mind. I thought we had reached a low with Windows Network places or the messages I get when I try to use 802.11. (don't you just love that root certificate message?)
Can you guys coordinate between you on how to deal with this situation on our bits? Bill's situation is worse than my personal experience but still, this aspect of the system needs to be looked at carefully and become a sign off item for each release.
I don't know what it means to "own website issues", nor am I yet sure the best way to handle the complex mess of coordinating between product teams, WU, and MS.COM. Dave, would you please forward the other reply you mentioned?
I have always been concerned about this and feel that this has a lot of engineering implications. I also feel that the reason is it such a mess is because marketing teams own release to web in this company. Frankly, we should be up in arms about this and want to program manager and develop whatever code we need to to ensure that every customer that even thinks they want to download our bits can do so in as easy and painless a way as possible. Downloading is the first step to setup and we should think of them equally or as one experience. But, if you want nothing revolutionary and want to band-aid (which is fine and understandable) then I agree with your plan to give it to Dave.
I don't think you can abdicate this entirely to marketing. If WU is the preferred way to deliver bits to end users we all need to drive WU to deliver what we need, both individually and as a collective request from DMD.
One of the biggest issues today is that WU provides no way to promote a download to an end-user. We want to promote MM2 and WMP9S to end-users as something new and cool that they can get for Windows. Three lines of text describing it buried under "Windows XP" in a page that the user has to purposefully go find just isn't good enough. Why can't the WU client-side piece proactively display a bubble "Look! Cool, new features for Windows XP" and the option to display a much richer "advertisement" for the feature if the user wants to read more?
Other issues -
MUI - I guess this is getting fixed now but it's always been an issue for us
Link to download through WU - why can't we send a user right in to WU to get MM2 without them having to wade through the whole site?
Critical updates that aren't really critical - if you machine is behind a firewall many just aren't critical
Too many fixes bombarding users all the time - I routinely ignore them now and perhaps update once a month as otherwise I'd be rebooting all the time
WU's inflexible release schedule. If there is a major tradeshow at which we want to announce we need flexibility in timing the release
So, I take from this that we have lots of opinions and input. However, no one appears to be saying that we, WMPG, are chartered and/or should own this. So my feedback on the thread would then be that Dave should take ownership for driving groups around today's inconsistencies, and that we should send this mail to Bharat (owns WU) as well and ask who in his team can take requirements from DMD.
I don't know what it means to \\\"own website issues\\\", nor am I yet sure the best way to handle the complex mess of coordinating between product teams, WU, and MS.COM. Dave, would you please forward the other reply you mentioned?
One of the biggest issues today is that WU provides no way to promote a download to an end-user. We want to promote MM2 and WMP9S to end-users as something new and cool that they can get for Windows. Three lines of text describing it buried under \\\"Windows XP\\\" in a page that the user has to purposefully go find just isn't good enough. Why can't the WU client-side piece proactively display a bubble \\\"Look! Cool, new features for Windows XP\\\" and the option to display a much richer \\\"advertisement\\\" for the feature if the user wants to read more?
Other issues -
MUI - I guess this is getting fixed now but it's always been an issue for us
Link to download through WU - why can't we send a user right in to WU to get MM2 without them having to wade through the whole site?
Critical updates that aren't really critical - if you machine is behind a firewall many just aren't critical
Too many fixes bombarding users all the time - I routinely ignore them now and perhaps update once a month as otherwise I'd be rebooting all the time
WU's inflexible release schedule. If there is a major tradeshow at which we want to announce we need flexibility in timing the release
Window Maker is a free and open-source window manager for the X Window System, allowing graphical applications to be run on Unix-like operating-systems. It is designed to emulate NeXTSTEP's GUI as an OpenStep-compatible environment.[2] Window Maker is part of the GNU Project.[3][4]
Window Maker has been characterized as reproducing "the elegant look and feel of the NeXTSTEP GUI" and is noted as "easy to configure and easy to use."[5] A graphical tool called Wprefs is included and can be used to configure most aspects of the UI. The interface tends towards a minimalist, high performance environment directly supporting XPM, PNG, JPEG, TIFF, GIF and PPM icons with an alpha-channel and a right-click, sliding-scrolling application menu system which can throw off pinnable menus, along with window-icon miniaturization and other animations on multiple desktops. Menus and preferences can be changed without restarting. As with most window managers it supports themes and many are available. Owing to its NeXT inspiration, Window Maker has a dock like macOS, but Window Maker's look and feel hews mostly to that of its NeXT forebear.
Window Maker has window hints which allow seamless integration with the GNUstep, GNOME, KDE, Motif and OpenLook environments. Significantly it has almost complete ICCCM compliance and internationalization support for at least 11 locales. Window Maker uses the lightweight WINGs widget set which was built specifically for Window Maker as a way to skirt what its developers said would have been the "overkill" (or bloat) of using GNUstep.[6] WINGs is common to other applications including a login display manager called WINGs Display Manager (WDM) and many dockapps. Window Maker dock and clip applets are compatible with those from AfterStep's wharf.
d3342ee215