Surface pro 3 Type Cover keyboard不能用

Reply

硬件生态wagsoft Post a question • 1 person concerned • 0 replies • 8 views • 2017-08-01 16:36 • 来自相关话题

如何添加驱动到Windows 10操作系统?

开发中心微士博 Published the article • 0 comments • 46 views • 2017-06-05 12:04 • 来自相关话题

最近因为要测试中国区版本的某个功能,需要安装RS2 RTM中文版到PC上,但比较头疼的是,这台PC,OEM只给了裸机设备,并没有带更新的驱动,比较,最基本的USB boot 引导和磁盘识别等,自己动手解决吧,内容如下:
准备Windows 10 RS2 RTM 镜像文件(ISO) .准备驱动安装文件,类似a.inf 这样使用DISM /Mount-Wim /WinFile:D:\images\sources\boot.wim /index:1 /MountDir:D:\test 命令导出boot.wim文件.使用DISM /Image:D:\test /Add-Driver /Driver:D:\driver\*.inf /Recurse 命令添加驱动到根目录.提示已经安装成功后,执行 DISM /Unmount-Wim /MountDir:D:\test /Commit 提交更改 查看全部
最近因为要测试中国区版本的某个功能,需要安装RS2 RTM中文版到PC上,但比较头疼的是,这台PC,OEM只给了裸机设备,并没有带更新的驱动,比较,最基本的USB boot 引导和磁盘识别等,自己动手解决吧,内容如下:
  • 准备Windows 10 RS2 RTM 镜像文件(ISO) .
  • 准备驱动安装文件,类似a.inf 这样
  • 使用DISM /Mount-Wim /WinFile:D:\images\sources\boot.wim /index:1 /MountDir:D:\test 命令导出boot.wim文件.
  • 使用DISM /Image:D:\test /Add-Driver /Driver:D:\driver\*.inf /Recurse 命令添加驱动到根目录.
  • 提示已经安装成功后,执行 DISM /Unmount-Wim /MountDir:D:\test /Commit 提交更改

【创新杯】灵感激扬,非同凡想

会员讨论微士博 Published the article • 0 comments • 74 views • 2017-05-15 22:36 • 来自相关话题

Microsoft Imagine 作为微软每年都会在全球举办的盛事,受到很多高校学生的喜爱, ImagineCup将学生与工具、资源和他们所需的经验连接在一起,以提升他们的技能,应对当今的工作环境,从这个出发点考虑,我们更加建议学生团体积极参与其中,无论是开发游戏、设计应用程序还是启动项目,Microsoft Imagine 都有助于激发学生的创意,并将其勇敢付诸实践。



2017微软科技“创新荟”今年选址富有科幻感著称的”魔都“上海,以”灵感激扬,非同凡想“为主题,参与中国区总决赛的队伍有20多支,涉及到各个社会学科,精彩程度不亚于2016年”创新杯“,纵观参赛入围的项目或产品,Point-Cloud,几何科技,52Hz,Meige,SEU_WirelessLaboratory,Light Favor等等,简单介绍几个我们比较重点关注的产品:
 
Light Favor-交互式公用室内导盲终端
今年电子导盲不断发展,现有电子导盲仪器大多功能单一,仅能给予定点语音提示,交互性差,且导盲仪器昂贵,增添视力障碍者的经济负担,Light Favor 据说首创交互概念和导盲设备公有复用的概念,通过APP终端输入,语音提示及地面牵引设备兼容导航,避障,求助等功能,采用PID自平衡,云端适配,语音输出和手势识别技术,结合改进的最短路径算法尽最大成都提高导盲系统的交互性和用户友好性,切实帮助盲人朋友。




SEU_WirelessLaboratory-基于HoloLens的4D住宅体验中心
要说2016年最牛X的黑科技是什么?非微软增强现实产品HoloLens莫属,在刚刚过去的2017年Build大会上,微软携手艺术家再次展示HoloLens技术强大的科技力量,任何新事物的发展,必然要经历一段苦苦探寻的过程,SEU_WirelessLaboratory团队提供4D虚拟沙盘,将沙盘的影像通过HoloLens放置到任意水平平面上,而平面上显示的就是小区的模型,用户可以放大部分区域以观察细节,同时可以点击某栋楼层的基本信息,销售情况,具体房型的平面图等等。




几何科技-废旧电池回收机
顾名思义,该产品主要以回收废旧电池为主,这也是倡导大家多多关注环境,不要随意将废旧电池随手扔,这个产品的流程有些意思,使用微信作为登陆认证的方式,用户将废旧电池投入到回收机里面,回收机则根据电池的“成色“判断其”价值“,同时返回”积分“到显示设备上告知用户,云端使用Azure服务存储每次交互的数据。我们认为,此项目还有进一步提升的可能,比如:与国内一些公益组织合作,推出一些类似可口可乐瓶收集的创意活动,相信更有社会效益。





至于更多精彩的现场比拼及项目展示,欢迎关注社区专题或关注微软官方账号的活动。
 
  查看全部
Microsoft Imagine 作为微软每年都会在全球举办的盛事,受到很多高校学生的喜爱, ImagineCup将学生与工具、资源和他们所需的经验连接在一起,以提升他们的技能,应对当今的工作环境,从这个出发点考虑,我们更加建议学生团体积极参与其中,无论是开发游戏、设计应用程序还是启动项目,Microsoft Imagine 都有助于激发学生的创意,并将其勇敢付诸实践。
ImagineCup_Logo.jpg
2017微软科技“创新荟”今年选址富有科幻感著称的”魔都“上海,以”灵感激扬,非同凡想“为主题,参与中国区总决赛的队伍有20多支,涉及到各个社会学科,精彩程度不亚于2016年”创新杯“,纵观参赛入围的项目或产品,Point-Cloud,几何科技,52Hz,Meige,SEU_WirelessLaboratory,Light Favor等等,简单介绍几个我们比较重点关注的产品:
 
Light Favor-交互式公用室内导盲终端
今年电子导盲不断发展,现有电子导盲仪器大多功能单一,仅能给予定点语音提示,交互性差,且导盲仪器昂贵,增添视力障碍者的经济负担,Light Favor 据说首创交互概念和导盲设备公有复用的概念,通过APP终端输入,语音提示及地面牵引设备兼容导航,避障,求助等功能,采用PID自平衡,云端适配,语音输出和手势识别技术,结合改进的最短路径算法尽最大成都提高导盲系统的交互性和用户友好性,切实帮助盲人朋友。
20170515_ImagineCup_1.png

SEU_WirelessLaboratory-基于HoloLens的4D住宅体验中心
要说2016年最牛X的黑科技是什么?非微软增强现实产品HoloLens莫属,在刚刚过去的2017年Build大会上,微软携手艺术家再次展示HoloLens技术强大的科技力量,任何新事物的发展,必然要经历一段苦苦探寻的过程,SEU_WirelessLaboratory团队提供4D虚拟沙盘,将沙盘的影像通过HoloLens放置到任意水平平面上,而平面上显示的就是小区的模型,用户可以放大部分区域以观察细节,同时可以点击某栋楼层的基本信息,销售情况,具体房型的平面图等等。
20170515_ImageCup_HoloLens.jpg

几何科技-废旧电池回收机
顾名思义,该产品主要以回收废旧电池为主,这也是倡导大家多多关注环境,不要随意将废旧电池随手扔,这个产品的流程有些意思,使用微信作为登陆认证的方式,用户将废旧电池投入到回收机里面,回收机则根据电池的“成色“判断其”价值“,同时返回”积分“到显示设备上告知用户,云端使用Azure服务存储每次交互的数据。我们认为,此项目还有进一步提升的可能,比如:与国内一些公益组织合作,推出一些类似可口可乐瓶收集的创意活动,相信更有社会效益。
20170515_ImagineCup_Battey.png


至于更多精彩的现场比拼及项目展示,欢迎关注社区专题或关注微软官方账号的活动。
 
 

创建应用包错误: File 'C:\somepath\bin\ARM\Release\*.appx' not found. 解决方案

UWP 微士博 Published the article • 0 comments • 34 views • 2017-04-11 08:38 • 来自相关话题

VS2017更新到Windows 10 SDK 15063后,如果创建应用商店部署包操作,将在编译ARM架构的过程中,出现如下错误:

 
解决方案如下:
 下载:http://pan.baidu.com/s/1c1RtQy0 工具,解压到指定位置 关闭所有的Visual Studio 实例 以系统管理员模式,打开Visual Studio 2017开发者命令行工具 在命令行工具中,使用cd 命令导航到 步骤1 的目录下面。 运行 Apply.cmd 
 
Happy Coding for Every Day ! 查看全部
VS2017更新到Windows 10 SDK 15063后,如果创建应用商店部署包操作,将在编译ARM架构的过程中,出现如下错误:

 
解决方案如下:
  1.  下载:http://pan.baidu.com/s/1c1RtQy0 工具,解压到指定位置
  2.  关闭所有的Visual Studio 实例
  3.  以系统管理员模式,打开Visual Studio 2017开发者命令行工具
  4.  在命令行工具中,使用cd 命令导航到 步骤1 的目录下面。
  5.  运行 Apply.cmd 

 
Happy Coding for Every Day !

Windows开发者设计指南

UWP 微士博 Published the article • 0 comments • 101 views • 2017-03-29 08:39 • 来自相关话题

 参考PDF文件
http://prodbdk.blob.core.windo ... e.pdf

如果获取TextBox控件焦点并自动弹出虚拟键盘

UWP 微士博 Published the article • 0 comments • 55 views • 2017-03-09 11:46 • 来自相关话题

如标题问题,在UWP的产品开发过程中,我们肯定会遇到要求用户输入信息的场景,好一点的产品设计师,会考虑的全一点,说白了,就是从用户体验上入手,将每个产品细节做到位,下面记录当页面导航到登陆、评论页等这些需要输入信息的页面时,如何确保输入框(TextBox)获取到焦点,并顺势弹出输入法虚拟键盘。
 
操作步骤:
1、新建项目,随便找个页面,拖个TextBox空间,简单设置一些样式,如背景色,边框,高度之类的,目的就是要让你的肉眼看到有这么一个控件在页面上,设置控件的 InputScope为 default 。
2,F7快捷键,导航到代码页(a.xaml.cs),在页面的构造函数中,加入loaded事件,Tab快捷键自动创建好了。
3,在Loaded_Page事件函数中,加入:
tbTest.Focus(FocusState.Programatic);
4,流程就是:当页面加载完毕后,TextBox获取焦点,焦点状态是自动弹出键盘.
 
以上实例代码如下可以到 这里获取  https://github.com/WinEcos/Samples  查看全部
如标题问题,在UWP的产品开发过程中,我们肯定会遇到要求用户输入信息的场景,好一点的产品设计师,会考虑的全一点,说白了,就是从用户体验上入手,将每个产品细节做到位,下面记录当页面导航到登陆、评论页等这些需要输入信息的页面时,如何确保输入框(TextBox)获取到焦点,并顺势弹出输入法虚拟键盘。
 
操作步骤:
1、新建项目,随便找个页面,拖个TextBox空间,简单设置一些样式,如背景色,边框,高度之类的,目的就是要让你的肉眼看到有这么一个控件在页面上,设置控件的 InputScope为 default 。
2,F7快捷键,导航到代码页(a.xaml.cs),在页面的构造函数中,加入loaded事件,Tab快捷键自动创建好了。
3,在Loaded_Page事件函数中,加入:
tbTest.Focus(FocusState.Programatic);
4,流程就是:当页面加载完毕后,TextBox获取焦点,焦点状态是自动弹出键盘.
 
以上实例代码如下可以到 这里获取  https://github.com/WinEcos/Samples 

UWP Community Toolkit 1.3 正式对外发布v1.3.0版本

UWP 微士博 Published the article • 0 comments • 75 views • 2017-02-11 08:17 • 来自相关话题

昨晚(北京时间) ,David Catuhe 和  Giorgio Sardo正式对外发布了UWP Community Toolkit 1.3版本,自从社区工具包推出后,受到很多开发者的欢迎,毕竟是微软自己主力推荐的开源项目,超过82%的贡献来自开发者社区,非常推荐国内开发者朋友们使用。




本次版本更新内容如下:
控件类
WrapPanel, Positions child elements in sequential position from left to right or top to bottom, breaking content to the next lineTextboxMask and TextBoxRegex (attached properties). Allows setting common or custom masks (like telephone numbers) for input.SurfaceDialTextboxHelper (attached property). Extends any Textbox control to be controlled directly from a Surface Dial.MarkdownTextBlock. Embeds and renders in real-time markdown syntax.TileControl. Enables repeatable tile content.ScrollHeader. Builds upon FadeHeader and enables Quick Return, Sticky and Fade behaviors.Expander. Provides an extendable container to show/hide any content by clicking the header.AdvancedCollectionView: Builds upon CollectionView and easily sorts and filters collections before displaying them.Loading control. Shows an animation with some content when the user should wait in some tasks of the app.   


















服务类
OneDrive service. Roam user files through the new OneDrive service with a simplified API model (similar to StorageFolder). The new service makes it easy to authenticate OneDrive users and more in the same consistent way you have come to expect from the toolkit services.Microsoft Translator Service. Translate text in 60 languages supported by Microsoft Translator Services. The free tier supports up to 2 million requests per month.We’ve added support for geographical metadata to tweets 

动画类
Light. Add light effects to your page or controls to draw user attentionReorder grid animations (attached property). Add smooth animations when resizing a grid view.ParallaxService. Allows to create a parallax effect for items contained within an element that scrolls like a ScrollViewer or ListView. 

消息推送
New toast features. Allows group toasts notifications (only available on Creator Update). 

辅助功能
With the support of the community, we started the journey to add accessibility capabilities to all the controls in the toolkit 

实例应用
The Sample App now has embedded documentation (using the new Markdown control).The Sample App provide pointers to a few external OSS resources, for example, the newly released Windows SDK for Google Analytics.It is now available for preview on Xbox One 

用户反馈
Tookit控件当前可以提交用户反馈信息与新功能请求, 戳:Tookit用户反馈
 
 
 
UWP 社区工具包深入了解,戳:这里 
Windows 应用商店下载,戳:这里  查看全部
昨晚(北京时间) ,David Catuhe 和  Giorgio Sardo正式对外发布了UWP Community Toolkit 1.3版本,自从社区工具包推出后,受到很多开发者的欢迎,毕竟是微软自己主力推荐的开源项目,超过82%的贡献来自开发者社区,非常推荐国内开发者朋友们使用。
IMAGE1.png

本次版本更新内容如下:
控件类
  • WrapPanel, Positions child elements in sequential position from left to right or top to bottom, breaking content to the next line
  • TextboxMask and TextBoxRegex (attached properties). Allows setting common or custom masks (like telephone numbers) for input.
  • SurfaceDialTextboxHelper (attached property). Extends any Textbox control to be controlled directly from a Surface Dial.
  • MarkdownTextBlock. Embeds and renders in real-time markdown syntax.
  • TileControl. Enables repeatable tile content.
  • ScrollHeader. Builds upon FadeHeader and enables Quick Return, Sticky and Fade behaviors.
  • Expander. Provides an extendable container to show/hide any content by clicking the header.
  • AdvancedCollectionView: Builds upon CollectionView and easily sorts and filters collections before displaying them.
  • Loading control. Shows an animation with some content when the user should wait in some tasks of the app.  
  •  



















                                      服务类
                                      • OneDrive service. Roam user files through the new OneDrive service with a simplified API model (similar to StorageFolder). The new service makes it easy to authenticate OneDrive users and more in the same consistent way you have come to expect from the toolkit services.
                                      • Microsoft Translator Service. Translate text in 60 languages supported by Microsoft Translator Services. The free tier supports up to 2 million requests per month.
                                      • We’ve added support for geographical metadata to tweets 


                                      动画类
                                      • Light. Add light effects to your page or controls to draw user attention
                                      • Reorder grid animations (attached property). Add smooth animations when resizing a grid view.
                                      • ParallaxService. Allows to create a parallax effect for items contained within an element that scrolls like a ScrollViewer or ListView. 


                                      消息推送
                                      New toast features. Allows group toasts notifications (only available on Creator Update). 

                                      辅助功能
                                      With the support of the community, we started the journey to add accessibility capabilities to all the controls in the toolkit 

                                      实例应用
                                      • The Sample App now has embedded documentation (using the new Markdown control).
                                      • The Sample App provide pointers to a few external OSS resources, for example, the newly released Windows SDK for Google Analytics.
                                      • It is now available for preview on Xbox One 


                                      用户反馈
                                      Tookit控件当前可以提交用户反馈信息与新功能请求, 戳:Tookit用户反馈
                                       
                                       
                                       
                                      UWP 社区工具包深入了解,戳:这里 
                                      Windows 应用商店下载,戳:这里 

                                      Windows CMD命令行工具“被”死亡

                                      开发中心微士博 Published the article • 0 comments • 58 views • 2017-01-06 23:37 • 来自相关话题

                                      国际知名的“计算机世界”杂志在2016年12月6日发表了一篇“Say goodbye to the MS-DOS command prompt”的文章, 感兴趣的,可以到 这里 看看,包括后续的文章Follow-up: MS-DOS lives on after all, 为此,微软Rich Turner的特别发了一篇博客,阐述在未来的Windows版本中并没有“死亡”,以下是全篇内容,全英文。
                                       

                                      This post is in response to a story published on December 6th 2016 by ComputerWorld titled “Say goodbye to the MS-DOS command prompt” and its follow-up article “Follow-up: MS-DOS lives on after all“.
                                      These “stories” were subsequently picked up by Business Insider and Life Hacker among others and fueled a number of concerned Tweets some of which I responded to directly, along with much discussion on Reddit, Hacker News, and elsewhere. It also resulted in several customers/partners sending me concerned emails asking if this “news” was true.
                                      So, I’d like to take a moment to allay everyone’s fears:
                                      The Windows Cmd / Command-Line shell is NOT being removed from Windows in the near or distant future!
                                      The Cmd shell remains an essential part of Windows, and is used daily by millions of businesses, developers, and IT Pro’s around the world.
                                      In fact:
                                      Much of the automated system that builds and tests Windows itself is a collection of many Cmd scripts that have been
                                      created over many years, without which we couldn’t build Windows itself!
                                      Cmd is one of the most frequently run executables on Windows with a similar number of daily launches as File Explorer,
                                      Edge and Internet Explorer!
                                      Many of our customers and partners are totally dependent on Cmd, and all it’s quirks, for their companies’ existence!
                                      In short: Cmd is an absolutely vital feature of Windows and, until there’s almost nobody running Cmd scripts or tools, Cmd will remain within Windows.
                                      So, what was this article actually “reporting”?
                                      The articles above were written in response to this paragraph from the release notes for the Windows 10 Insiders build 14971:

                                      PowerShell in the Shell: In an effort to bring the best command line experiences to the forefront for all power users, PowerShell is now the defacto command shell from File Explorer. It replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu, and in the context menu that appears when you shift-right-click the whitespace in File Explorer. Typing “cmd” (or “PowerShell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location. For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off“.

                                      Notice the nuance here:
                                      The above paragraph states that “[PowerShell] replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu“.
                                      It does not say “[PowerShell] replaces Command Prompt“, period! The paragraph even goes on to show you how to quickly launch Cmd, and points out that you can revert this default setting to launch Cmd by default instead if you prefer.
                                      So, to be ultra-clear here: All that’s happening is that, in the [Win] + [X] (“Power User’s menu”), or File Explorer’s File menu, PowerShell is presented instead of Cmd. That’s all! Nothing is being removed, your scripts will continue to run just as they always have, the sky is not falling!
                                      Also, Cmd != MS-DOS!
                                      I also want to point out a common misconception perpetuated by articles like the ones above: Cmd <> MS-DOS!
                                      In FACT:
                                      Microsoft last shipped a “new” version of MS-DOS (v8.0 in Windows ME), on September 16th, 2000 – 16 years ago (as of this writing)!!
                                      MS-DOS was an operating system (albeit a relatively simple OS by today’s standards) whose primary user-interface was a command-line shell, until Windows 3.x & 9.x arrived and ran on/around MS-DOS
                                      MS-DOS’ command-line shell’s scripting language was relatively terse and moderately powerful, but lacked many of the richer, and more advanced features we enjoy in modern-day PowerShell, Bash, etc.
                                      While later versions of MS-DOS grew in sophistication and added/replaced some older assembly with new code written in ‘C’, much of MS-DOS remained written in x86 assembly for efficiency, and because it was the only way at the time to gain access to many hardware devices and peripherals. This made MS-DOS non-portable to non-x86 CPU’s. If you’re so inclined, you can actually download the source code for MS-DOS v1.1 and v2.0 to see just how much of the earlier versions of MS-DOS were written in x86 assembly (hint: pretty much all of it)!

                                      Interesting note: 32-bit versions of Windows derived from NT include an additional shell “command.com” which runs many MS-DOS scripts and legacy 16-bit apps in a Windows NT Virtual DOS Machine (NTVDM) using the x86 Virtual 8086 mode along with some legacy “quirks”. 64-bit versions of Windows do not include command.com or the NTVDM.

                                      On the other hand:
                                      Cmd is a Win32 app written entirely in ‘C’ – this is important since one of the key goals of NT was to be portable across many different processor and machine architecturesCmd is the default command-line shell built-in to the Windows NT family of OS’ (i.e. Windows NT, 2000, XP, Vista, 7, 8, 10)The Cmd scripting language was designed to be generally compatible with many MS-DOS scripts, to help users migrate from MS-DOS and Windows 9x/ME to the new NT-based OS family, but lacks many MS-DOS features since it is a Win32 shell running atop the Windows NT kernel and OSCmd is used to automate millions of businesses’ login scripts, shop floor/manufacturing systems, data capture systems, etc., and millions of developers’ build, test and deployment systems, etc.So why the move to default to PowerShell
                                       Cmd has served us all well for almost 30 years now, and will continue to do so for a long time to come. But, WHILE CMD IS NOT BEING REMOVED FROM WINDOWS ANYTIME SOON (if ever), the reality is that PowerShell is a far, FAR more powerful shell than Cmd could ever be. Hence PowerShell’s name. Surprise!
                                      We’ve gotten to the point with Cmd that we can no longer easily make improvements, enhancements or modifications to it! On the very rare occasions where we do make a fix, or change something, we generally break someone in the real world whose scripts/tools depend on that legacy feature/behavior. The last thing we want to do is break the Windows build system (that team get really upset when we break them ), or worse, break a PC OEM’s production line, or damage a farm equipment manufacturer’s welding robots, or prevent an enterprise’s 150,000+ employees from logging-in to their PC’s in the morning! This also means it is tricky to add new usability features such as auto-complete, color highlighting, etc.: If we change Cmd, we tend to break someone!
                                      PowerShell, on the other hand, is much newer than Cmd and was built for today and the future. In fact, PowerShell celebrated its 10th birthday on October 25th 2016! It ably handles the rigors of the most demanding scripting environments on earth today and is highly extensible, flexible and … well … powerful! It was also recently open-sourced and ported to run on Linux, and is the backbone of the cross-platform Desired State Configuration (DSC) cross-platform declarative configuration initiative.

                                      PowerShell’s full syntax is seen by some as “verbose”, esp. compared to some of the more “terse” Linux command-line tools (e.g. ‘tar xvzf file-1.0.tar.gz’ … whut?). However, PowerShell was built specifically for long-term readability and discoverability (PowerShell’s tab completion is AWESOME).
                                      If you don’t enjoy typing the longer commands, PowerShell makes it is easy to create your own shorter aliases (using the “set-alias” command), and scriptlets for more complex/verbose PowerShell operation. PowerShell also pre-defines a set of convenient aliases to abbreviate many common commands (run “get-alias” for the full list), along with aliases for common *NIX commands, e.g.: ls == get-childitem.
                                      Now that we’re seeing an ever increasing number of developers and IT admins (the primary users of shells) use PowerShell, we wanted to give them the ability to launch PowerShell as their default shell, instead of Cmd, while still allowing them to revert back to Cmd by default if they’re not yet ready to move to PowerShell.
                                      Hence the changes in Windows 10 Creator Update’s UI, noted above.

                                      In closing
                                      I hope this post clears-up any last remaining concerns, fears, worries, confusion you may have about Microsoft’s commitment to Cmd and the UI changes we’re making to Windows 10 Creator Update, to help you find and use PowerShell more often, while still allowing you to revert back to Cmd as your default shell should you wish.
                                      If you do see anyone claiming that Cmd is being removed from Windows, please reply with one or more of “No! Nope! Niet! Non! Negative! Nuh-huh! [Shake head vigorously], etc.”, and refer them to this post. Thanks!
                                      If you have any unanswered questions on these subjects, do fire-off below, or ping me on Twitter at richturn_ms! 查看全部
                                      国际知名的“计算机世界”杂志在2016年12月6日发表了一篇“Say goodbye to the MS-DOS command prompt”的文章, 感兴趣的,可以到 这里 看看,包括后续的文章Follow-up: MS-DOS lives on after all, 为此,微软Rich Turner的特别发了一篇博客,阐述在未来的Windows版本中并没有“死亡”,以下是全篇内容,全英文。
                                       

                                      This post is in response to a story published on December 6th 2016 by ComputerWorld titled “Say goodbye to the MS-DOS command prompt” and its follow-up article “Follow-up: MS-DOS lives on after all“.
                                      These “stories” were subsequently picked up by Business Insider and Life Hacker among others and fueled a number of concerned Tweets some of which I responded to directly, along with much discussion on Reddit, Hacker News, and elsewhere. It also resulted in several customers/partners sending me concerned emails asking if this “news” was true.
                                      So, I’d like to take a moment to allay everyone’s fears:
                                      The Windows Cmd / Command-Line shell is NOT being removed from Windows in the near or distant future!
                                      The Cmd shell remains an essential part of Windows, and is used daily by millions of businesses, developers, and IT Pro’s around the world.
                                      In fact:
                                      Much of the automated system that builds and tests Windows itself is a collection of many Cmd scripts that have been
                                      created over many years, without which we couldn’t build Windows itself!
                                      Cmd is one of the most frequently run executables on Windows with a similar number of daily launches as File Explorer,
                                      Edge and Internet Explorer!
                                      Many of our customers and partners are totally dependent on Cmd, and all it’s quirks, for their companies’ existence!
                                      In short: Cmd is an absolutely vital feature of Windows and, until there’s almost nobody running Cmd scripts or tools, Cmd will remain within Windows.
                                      So, what was this article actually “reporting”?
                                      The articles above were written in response to this paragraph from the release notes for the Windows 10 Insiders build 14971:


                                      PowerShell in the Shell: In an effort to bring the best command line experiences to the forefront for all power users, PowerShell is now the defacto command shell from File Explorer. It replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu, and in the context menu that appears when you shift-right-click the whitespace in File Explorer. Typing “cmd” (or “PowerShell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location. For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off“.


                                      Notice the nuance here:
                                      The above paragraph states that “[PowerShell] replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu“.
                                      It does not say “[PowerShell] replaces Command Prompt“, period! The paragraph even goes on to show you how to quickly launch Cmd, and points out that you can revert this default setting to launch Cmd by default instead if you prefer.
                                      So, to be ultra-clear here: All that’s happening is that, in the [Win] + [X] (“Power User’s menu”), or File Explorer’s File menu, PowerShell is presented instead of Cmd. That’s all! Nothing is being removed, your scripts will continue to run just as they always have, the sky is not falling!
                                      Also, Cmd != MS-DOS!
                                      I also want to point out a common misconception perpetuated by articles like the ones above: Cmd <> MS-DOS!
                                      In FACT:
                                      Microsoft last shipped a “new” version of MS-DOS (v8.0 in Windows ME), on September 16th, 2000 – 16 years ago (as of this writing)!!
                                      MS-DOS was an operating system (albeit a relatively simple OS by today’s standards) whose primary user-interface was a command-line shell, until Windows 3.x & 9.x arrived and ran on/around MS-DOS
                                      MS-DOS’ command-line shell’s scripting language was relatively terse and moderately powerful, but lacked many of the richer, and more advanced features we enjoy in modern-day PowerShell, Bash, etc.
                                      While later versions of MS-DOS grew in sophistication and added/replaced some older assembly with new code written in ‘C’, much of MS-DOS remained written in x86 assembly for efficiency, and because it was the only way at the time to gain access to many hardware devices and peripherals. This made MS-DOS non-portable to non-x86 CPU’s. If you’re so inclined, you can actually download the source code for MS-DOS v1.1 and v2.0 to see just how much of the earlier versions of MS-DOS were written in x86 assembly (hint: pretty much all of it)!

                                      Interesting note: 32-bit versions of Windows derived from NT include an additional shell “command.com” which runs many MS-DOS scripts and legacy 16-bit apps in a Windows NT Virtual DOS Machine (NTVDM) using the x86 Virtual 8086 mode along with some legacy “quirks”. 64-bit versions of Windows do not include command.com or the NTVDM.

                                      On the other hand:
                                      • Cmd is a Win32 app written entirely in ‘C’ – this is important since one of the key goals of NT was to be portable across many different processor and machine architectures
                                      • Cmd is the default command-line shell built-in to the Windows NT family of OS’ (i.e. Windows NT, 2000, XP, Vista, 7, 8, 10)
                                      • The Cmd scripting language was designed to be generally compatible with many MS-DOS scripts, to help users migrate from MS-DOS and Windows 9x/ME to the new NT-based OS family, but lacks many MS-DOS features since it is a Win32 shell running atop the Windows NT kernel and OS
                                      • Cmd is used to automate millions of businesses’ login scripts, shop floor/manufacturing systems, data capture systems, etc., and millions of developers’ build, test and deployment systems, etc.
                                      • So why the move to default to PowerShell

                                       Cmd has served us all well for almost 30 years now, and will continue to do so for a long time to come. But, WHILE CMD IS NOT BEING REMOVED FROM WINDOWS ANYTIME SOON (if ever), the reality is that PowerShell is a far, FAR more powerful shell than Cmd could ever be. Hence PowerShell’s name. Surprise!
                                      We’ve gotten to the point with Cmd that we can no longer easily make improvements, enhancements or modifications to it! On the very rare occasions where we do make a fix, or change something, we generally break someone in the real world whose scripts/tools depend on that legacy feature/behavior. The last thing we want to do is break the Windows build system (that team get really upset when we break them ), or worse, break a PC OEM’s production line, or damage a farm equipment manufacturer’s welding robots, or prevent an enterprise’s 150,000+ employees from logging-in to their PC’s in the morning! This also means it is tricky to add new usability features such as auto-complete, color highlighting, etc.: If we change Cmd, we tend to break someone!
                                      PowerShell, on the other hand, is much newer than Cmd and was built for today and the future. In fact, PowerShell celebrated its 10th birthday on October 25th 2016! It ably handles the rigors of the most demanding scripting environments on earth today and is highly extensible, flexible and … well … powerful! It was also recently open-sourced and ported to run on Linux, and is the backbone of the cross-platform Desired State Configuration (DSC) cross-platform declarative configuration initiative.

                                      PowerShell’s full syntax is seen by some as “verbose”, esp. compared to some of the more “terse” Linux command-line tools (e.g. ‘tar xvzf file-1.0.tar.gz’ … whut?). However, PowerShell was built specifically for long-term readability and discoverability (PowerShell’s tab completion is AWESOME).
                                      If you don’t enjoy typing the longer commands, PowerShell makes it is easy to create your own shorter aliases (using the “set-alias” command), and scriptlets for more complex/verbose PowerShell operation. PowerShell also pre-defines a set of convenient aliases to abbreviate many common commands (run “get-alias” for the full list), along with aliases for common *NIX commands, e.g.: ls == get-childitem.
                                      Now that we’re seeing an ever increasing number of developers and IT admins (the primary users of shells) use PowerShell, we wanted to give them the ability to launch PowerShell as their default shell, instead of Cmd, while still allowing them to revert back to Cmd by default if they’re not yet ready to move to PowerShell.
                                      Hence the changes in Windows 10 Creator Update’s UI, noted above.

                                      In closing
                                      I hope this post clears-up any last remaining concerns, fears, worries, confusion you may have about Microsoft’s commitment to Cmd and the UI changes we’re making to Windows 10 Creator Update, to help you find and use PowerShell more often, while still allowing you to revert back to Cmd as your default shell should you wish.
                                      If you do see anyone claiming that Cmd is being removed from Windows, please reply with one or more of “No! Nope! Niet! Non! Negative! Nuh-huh! [Shake head vigorously], etc.”, and refer them to this post. Thanks!
                                      If you have any unanswered questions on these subjects, do fire-off below, or ping me on Twitter at richturn_ms!

                                      Build 14986 - Error Code 80240031解决方案

                                      开发中心微士博 Published the article • 0 comments • 60 views • 2016-12-19 08:00 • 来自相关话题

                                      微软在快速分支下面发布14986 for PC, 但很多Insider更新时遇到 80240031错误,微软已经发布解决方案,如下:
                                      下载troubleshooter工具 下载 保险为先,运行后重启电脑再次进入系统后,导航到:设置->Windows更新->查找更新
                                       
                                      注意:
                                      如果你参考过其他社区或网站的方法,修改过注册表 ,请把它们恢复到原始值后再执行以上操作。
                                       
                                      PS:配图来源于网络
                                        查看全部

                                      微软在快速分支下面发布14986 for PC, 但很多Insider更新时遇到 80240031错误,微软已经发布解决方案,如下:
                                      • 下载troubleshooter工具 下载 
                                      • 保险为先,运行后重启电脑
                                      • 再次进入系统后,导航到:设置->Windows更新->查找更新

                                       
                                      注意:
                                      如果你参考过其他社区或网站的方法,修改过注册表 ,请把它们恢复到原始值后再执行以上操作。
                                       
                                      PS:配图来源于网络
                                       

                                      winecos商店买了后盖,多久发货?

                                      Reply

                                      会员讨论梁天雄 Post a question • 1 person concerned • 0 replies • 45 views • 2016-12-09 23:51 • 来自相关话题