introduction

2018年9月19日 星期三

Input method issue of Win 10 version 1803

Cpime appears to be the only available free Cantonese input method for Win 10. Yet it only supports desktop panel only. It needs to be added to the input method lists after installation before it can be used. However Windows 10's control panel no longer has input method edition section. Yet Windows' Setting only support metro panel language edition. I searched the web and at last found the solution:

關鍵在於「語言」的代號 {BF782CC9-5A52-4A17-806C-2A894FFEEAC5}
有兩種添加方法:
一、資料夾式
任意位置新增資料夾,輸入(任意名稱).{BF782CC9-5A52-4A17-806C-2A894FFEEAC5}
(包括小數點和大括號)
例如:lang.{BF782CC9-5A52-4A17-806C-2A894FFEEAC5}
便可直接進入語言設定

二、捷徑式
任意位置新增捷徑,輸入 explorer shell:::{BF782CC9-5A52-4A17-806C-2A894FFEEAC5}
自己指定名稱,也可更改圖示。如語言設定的預設圖示位於 %SystemRoot%\System32\UserLanguagesCpl.dll

現在便可進入以前控制台的語言設定頁面,並對僅限桌面版本的輸入法進行新增/移除了。

2018年5月23日 星期三

Issues after updating Win 10 to version 1803

My computers were automatically updated to version 1803 recently, of course without my prior approval. It was a terrible nightmare, thanks to M$. My system ran into chaos. The client computers' CMS failed to start because they could not connect to the server. In fact no computers appeared at the windows explorer page any more. That meant we could not find one another and share files or use others' sharing printers attached to print files. My clinic procedures almost came to a halt. Fortunately one of the client computer had been updated but not yet rebooted. It's still running the old version and thus our work could be carried on temporarily.

 More fortunately was that a friendly old client attended me at that damn right time. He is an IT professional and he helped me to solve this emergency.

First of all, after the update. the computers were no longer publicizing their presence in the network. To recover this, two services' startup type need to be set to: automatic (delayed start) for all computers:

  1.  Function Discovery Provider Host
  2.  Function Discovery Resource Publication

Open a CMD and type services.msc to get the list of services to edit and enable.

After that the network group was retrieved to a seemingly normal state but the client CMS still could not connect to the server. Eventually we found out that now the Win 10 had become so stupid that we could ping by IP but not by name. Since CMS connects to the server by its host name, it failure is certain. The solution we used was fixing the server name to its IP address.

Open a CMD at the server. Type ipconfig to check its IP. Open a CMD with administrative right at each client computer. change directory to

     C:\Windows\System32\drivers\etc, type notepad hosts, edit it by inserting a line:
     the host computer’s IP(eg 192.168.1.138) its name(eg master)
and save. Fix the IP address to static as such at the router's control panel. it worked. The system could be run again.





The same worked for network printer by fixing the host's name to its IP.