SEO杂碎 http://blog.zxlm.cn 一个经得起时间考验的人 Tue, 10 Mar 2015 15:35:02 +0000 zh-CN hourly 1 http://wordpress.org/?v=4.1.5 Evernote国际版的同步速度 http://blog.zxlm.cn/2015/03/evernote-sync-speed.html http://blog.zxlm.cn/2015/03/evernote-sync-speed.html#comments Tue, 10 Mar 2015 15:34:51 +0000 http://blog.zxlm.cn/?p=3191 最新版本Everything 5.8.4.6840（274870）Public 同步319条笔记，时间20分钟，好意思啊！

23:28:17 [5448] Client synchronization finished, status: complete
23:28:17 [5448] * 319 items received
23:28:17 [5448] * elapsed time: 19m 44s

 

]]> http://blog.zxlm.cn/2015/03/evernote-sync-speed.html/feed 0 Evernote开发真的SB http://blog.zxlm.cn/2015/03/evernote-sb.html http://blog.zxlm.cn/2015/03/evernote-sb.html#comments Tue, 10 Mar 2015 13:45:48 +0000 http://blog.zxlm.cn/?p=3185 Evernote笔记的同步问题，出了几十个版本都没有解决，这些开发人员真的是SB。
妈的。

 

21:40:27 [4056] Command line: “D:\PROGRA~1\Evernote\Evernote\Evernote.exe” /DebugMenu
21:40:27 [4056] Evernote for Windows 5.8.4.6870 (274870) Public
21:40:27 [4056] Client info: Evernote Windows/274870; Windows/5.2.3790 Service Pack 2;
21:40:27 [4056] Bootstrap info: Evernote-China,Evernote[1] (loadedLastUsed)
21:40:27 [5796] Requesting bootstrap info from “app.yinxiang.com” (zh-CN)
21:40:27 [5796] 0% Connecting to app.yinxiang.com/edam/user
21:40:29 [5796] Bootstrap info: request to “app.yinxiang.com” returned profiles: Evernote-China,Evernote
21:40:29 [5796] Bootstrap info: Evernote-China,Evernote[1] (loadedFresh)
21:40:30 [4056] Registered session count: 1, last session: 2015/03/10 21:30:00
21:40:30 [4056] Reengagement Notifications – session logged
21:40:30 [4056] Loaded session count: 0, last session: 2015/03/10 21:00:00
21:40:30 [4056] Reengagement Notifications – Start
21:40:30 [868] 0% Connecting to www.evernote.com/shard/s417/utility
21:40:30 [4056] Opened database: D:\Documents and Settings\Administrator\Local Settings\Application Data\Evernote\Evernote\Databases\firehack119.exb (8.5MB Fixed)
21:40:31 [5740] 0% Connecting to WebSocket at ws.www.evernote.com:443
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:35 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [4056] EmailLastPrompted updated. EmailLastConfirmed = 2014/08/05 18:30:05 (UTC+8:00), EmailLastPrompted = 2015/03/10 21:40:36 (UTC+8:00).
21:40:36 [4056] Showing email confirmation dialog. EmailLastConfirmed = 2014/08/05 18:30:05 (UTC+8:00), EmailLastPrompted = 2015/03/10 21:40:36 (UTC+8:00).
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:36 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:37 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:38 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5616] 0% Connecting to www.evernote.com/edam/note/s417
21:40:39 [5616] 0% Connecting to www.evernote.com/edam/note/s6
21:40:39 [5616] 0% Authenticating shared notebook “0近期工作安排” shared by firehack
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [4056] Registered session count: 1, last session: 2015/03/10 21:30:00
21:40:39 [4056] Reengagement Notifications – session logged
21:40:39 [5512] 0% Connecting to www.evernote.com/edam/note/s6
21:40:39 [5512] 0% Authenticating shared notebook “0近期工作安排” shared by firehack
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5616] 0% Retrieving note lock status for “行政督办”
21:40:39 [5616] 0% * guid={0532ABC2-DEC4-4BB8-BBBC-AA2CB2779F9A}
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:39 [5740] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:40 [5512] 0% Retrieving lock status for 5 notes from “www.evernote.com/s6″
21:40:43 [5616] 0% * noteUpdateSequenceNumber: 174730
21:40:43 [5616] 0% * viewingUserIds: (me)
21:40:43 [4056] Saved session count: 1, last session: 2015/03/10 21:30:00
21:40:43 [4056] Reengagement Notifications – Stop
21:40:43 [5512] 0% * 1 note returned
21:40:43 [5512] 0% Authenticating shared notebook “数字工程中心” shared by firehack
21:40:44 [5512] 0% EDAMUserException: errorCode=DATA_REQUIRED parameter=”authenticationToken”
21:40:45 [4056] Closed database: D:\Documents and Settings\Administrator\Local Settings\Application Data\Evernote\Evernote\Databases\firehack119.exb (8.5MB +0B)
21:40:45 [4056] Bootstrap info: Evernote-China,Evernote[1] (loadedDatabase)
21:40:45 [4056] Loaded session count: 0, last session: 2015/03/10 21:15:00
21:40:45 [3880] 0% Connecting to WebSocket at ws.www.evernote.com:443
21:40:45 [4056] Reengagement Notifications – Start
21:40:45 [2560] 0% Connecting to www.evernote.com/shard/s6/utility
21:40:45 [4056] Opened database: D:\Documents and Settings\Administrator\Local Settings\Application Data\Evernote\Evernote\Databases\firehack.exb (1.6GB Fixed)
21:40:45 [4056] Registered session count: 1, last session: 2015/03/10 21:30:00
21:40:45 [4056] Reengagement Notifications – session logged
21:40:45 [2716] 0% Connecting to www.evernote.com/edam/note/s6
21:40:45 [2716] 0% Connecting account firehack
21:40:45 [2716] 0% Retrieving lock status for 1 note from “www.evernote.com/s6″
21:40:45 [2716] 0% * 0 notes returned
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:46 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:47 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [2716] 0% Connecting account firehack
21:40:48 [2716] 0% Retrieving lock status for 7 notes from “www.evernote.com/s6″
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3616] 0% Connecting to www.evernote.com/edam/note/s6
21:40:48 [3616] 0% Retrieving note lock status for “院级行政发文（发文拟办选择人员）”
21:40:48 [3616] 0% * guid={0CBD6C7B-0053-4A26-925A-A68F6B53E5DC}
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [4196] Finding related content for note 64394
21:40:48 [4196] * Retrieved 0 cached related content items for note 64394
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [2716] 0% * 3 notes returned
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:48 [3616] 0% * noteUpdateSequenceNumber: 175008
21:40:48 [3616] 0% * viewingUserIds: (me)
21:40:48 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:49 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [5516] Client synchronization started
21:40:50 [6060] 0% Connecting account firehack
21:40:50 [6060] 0% Loaded updateCount: 175033
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [2716] 0% Connecting account firehack
21:40:50 [2716] 0% Retrieving lock status for 7 notes from “www.evernote.com/s6″
21:40:50 [6060] 0% Usage Metrics: sessionCount=1
21:40:50 [6060] 0% Client is up to date with the server, updateCount: 175033
21:40:50 [6060] 0% Connecting account firehack
21:40:50 [6060] 0% Connecting account firehack
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [2716] 0% * 4 notes returned
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:50 [6060] 0% Retrieving missing search text for 8 resources
21:40:50 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [5516] Client synchronization finished, status: complete
21:40:51 [5516] * elapsed time: 0s
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [3880] 0% LWS: SSL connect error 336134278: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
21:40:51 [

]]> http://blog.zxlm.cn/2015/03/evernote-sb.html/feed 0 工作电脑换SSD硬盘 http://blog.zxlm.cn/2014/02/ssd.html http://blog.zxlm.cn/2014/02/ssd.html#comments Thu, 13 Feb 2014 17:07:43 +0000 http://blog.zxlm.cn/?p=3167 电脑在日常办工中经常需要打开VS、Eclipse等编译代码，还需要同时使用Evernote、ManicTime、数据库管理工具等比较消耗磁盘IO的软件，因而虽然电脑配置中等（I5、8G内存），但是在各软件的响应速度才不理解，甚至于开机需要5分钟之久。

尽管经常清理垃圾优化性能，使用 Diskeeper、Process Lasso、VSuite Ramdisk (Server Edition)等软件仍旧无法满足需要，而且电脑中软件较多，各配置已经固定，重装系统的方案根本不可取。

基于上述原因一直关注SSD磁盘对系统性能的作用和价格，在确定其对性能提升的提升程度后，于￥509（含运维）的价位通过天猫购入“金士顿SSD 120G 固态硬盘V300”一枚，将系统盘和日常工作文件切换到SSD上后确实感受到了钢钢的速度，最明显的是开机速度缩短至2分钟内，在Evernote中搜索文件再也不用等待了。

提供商品地址：http://detail.tmall.com/item.htm?id=18194215031

]]> http://blog.zxlm.cn/2014/02/ssd.html/feed 2 Lantern最新完整安装包下载 http://blog.zxlm.cn/2013/12/lantern-full-install.html http://blog.zxlm.cn/2013/12/lantern-full-install.html#comments Sun, 01 Dec 2013 13:14:35 +0000 http://blog.zxlm.cn/?p=3157 大家期待Lantern 1.2的发布吧！ Lantern 1.2.0 将会在接下来的几个星期内陆续发到各位已被邀请的用户手上。

20140217：Lantern原地满血复活（可以连接到云服务器）

百度网盘下载地址：Lantern最新版

更新：已经提供最新的  Lantern 1.0.0-rc1 的完整安装程序，欢迎试用。

需要正常使用请确保已经安装JRE（1.6以上）或JDK

当前版本：Lantern 1.0.0-beta9（下一版本预计9天后）

 

改变：
1、”处于代理站点”增加一些新的站点
2、提供新版本Lantern完整包的下载地址
3、被邀请的人是否打开邀请邮件了，被邀请的人是否安装客户端了，之前没有统计，从这个版本开始统计
4、客户端左上方不显示你的邮箱地址
5、增加如何更新的说明(卸载旧版本，重新运行那个90多KB的文件)
6、支持多国语言
修复：
1、添加好友的时候，总是提示添加失败
2、右下角出现别人添你为好友的信息，朋友的名字有时候是乱码
3、Ubuntu系统下，chromium浏览器的路径有问题
4、【重大BUG】连接云服务器还是连接自己的好友取决于邀请你的人，现在取消这个规则(之前Lantern官方是这么决定的：网友A注册成功了，A连上的云服务器是1，然后A邀请了网友B和C，那么B和C只能连跟A一样的云服务器1,而不是2、3等服务器)
5、facebook等网站图片不能正常显示
6、好友列表一直处于加载状态
7、win8下Lantern界面不能正常显示
8、底部提示”连接失败：无法连接能提供连接的Lantern网络用户”，但是仍然可以翻墙
9、越南网友安装Lantern出现错误提示”we’re sorry,but lantern install failed due to the follo wing error:HTTP/1.1 400 Couldn’t URL”
10、下载的90多KB文件，该文件名有时会出现 ‘0_0_1’这样的错误字符
12、Lantern更新后，”处于代理站点”的配置将被重置
13、Ubuntu系统下，系统左上角提示”untitled”

]]> http://blog.zxlm.cn/2013/12/lantern-full-install.html/feed 1 解决Lantern无法添加好友的问题 http://blog.zxlm.cn/2013/11/lantern-friends.html http://blog.zxlm.cn/2013/11/lantern-friends.html#comments Thu, 28 Nov 2013 17:10:27 +0000 http://blog.zxlm.cn/?p=3150 解决方案：安装Lantern最新版本程序

解决Lantern无法添加好友的问题，目前的彻底方案：
下载已经打包的文件 或者 下载已经编译的Class，不放心的下载器 .java文件直接编译再替换lantern.jar包（一般在电脑的 C:\Documents and Settings\Administrator\Application Data\Lantern\ 目录）中的已有文件，下载地址：

B：懒人直接下载 “软件  >  Fix  >  lantern.jar”
http://pan.baidu.com/share/link?shareid=27398&uk=168094346

A：软件  >  Fix  >  org_lantern_oauth（目录下有已经编译文件和源文件），将.class文件替换掉  lantern.jar 文件（使用Zip、RAR等压缩软件打开）中 org\lantern\oauth\ 下的同名文件。

或者自行将 OauthUtils.java 文件编译（javac -classpath:lantern.jar OauthUtils.java）生成class文件再替换
Update：
问题已经提交给Lantern官方Git，回应将在RC1中解决，大家期待吧。

Lantern成功添加好友

问题分析：

最新的翻墙软件 Lantern在安装后无法添加好友，在进行好友添加时将出现”操作失败“的提示。

添加好友的界面因为一直显示正在加载中的动画，被大家称为”滚菊花“。

经过分析Lantern生成的日志文件（C:\Documents and Settings\Administrator\Application Data\Lantern\logs\java.log）

发生系统出现了类似这样的异常信息：

org.codehaus.jackson.JsonParseException: Illegal unquoted character ((CTRL-CHAR, code 10)): has to be escaped using backslash to be included in string value
at [Source: java.io.StringReader@e6ba7; line: 26, column: 20]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
at org.codehaus.jackson.impl.JsonParserMinimalBase._throwUnquotedSpace(JsonParserMinimalBase.java:482)
at org.codehaus.jackson.impl.ReaderBasedParser._finishString2(ReaderBasedParser.java:1359)
at org.codehaus.jackson.impl.ReaderBasedParser._finishString(ReaderBasedParser.java:1330)
at org.codehaus.jackson.impl.ReaderBasedParser.getText(ReaderBasedParser.java:200)
at org.codehaus.jackson.map.deser.std.StringDeserializer.deserialize(StringDeserializer.java:26)
at org.codehaus.jackson.map.deser.std.StringDeserializer.deserialize(StringDeserializer.java:13)
at org.codehaus.jackson.map.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:299)
at org.codehaus.jackson.map.deser.SettableBeanProperty$MethodProperty.deserializeAndSet(SettableBeanProperty.java:414)
at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:697)
at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580)
at org.codehaus.jackson.map.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:217)
at org.codehaus.jackson.map.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:194)
at org.codehaus.jackson.map.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:30)
at org.codehaus.jackson.map.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:299)
at org.codehaus.jackson.map.deser.SettableBeanProperty$MethodProperty.deserializeAndSet(SettableBeanProperty.java:414)
at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:697)
at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2732)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)
at org.lantern.endpoints.FriendApi.listFriends(FriendApi.java:61)
at org.lantern.state.DefaultFriendsHandler$1.call(DefaultFriendsHandler.java:154)
at org.lantern.state.DefaultFriendsHandler$1.call(DefaultFriendsHandler.java:145)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
14733580 2013-11-28 18:38:26,697 ERROR [Friends-Loader-0] state.DefaultFriendsHandler.call (DefaultFriendsHandler.java:167) – Could not list friends?
java.io.IOException: Could not parse friends!

]]> http://blog.zxlm.cn/2013/11/lantern-friends.html/feed 1 怒：这些不负责任的软件厂商 http://blog.zxlm.cn/2013/11/product-safe.html http://blog.zxlm.cn/2013/11/product-safe.html#comments Wed, 06 Nov 2013 04:06:50 +0000 http://blog.zxlm.cn/?p=3145 信息化过程中接触了较多的软件厂商，在此过程中发现一些厂商的产品存在严重安全漏洞：

1、中软国际ResourceOne Portal Framework：通过漏洞可以直接控制应用服务器；
2、数字天堂（移动OA）：通过漏洞可以取得系统管理权限，进而可以控制应用服务器、更为严重的是进而可以向手机发送“短信炸弹”（根据厂商的技术白皮书）。

在抓项目的时候也要把自身产品的安全问题解决好啊！

]]> http://blog.zxlm.cn/2013/11/product-safe.html/feed 0 Chrome插件：Google Publisher Toolbar无法通过OAuth2认证 http://blog.zxlm.cn/2013/09/chrome-google-publisher-toolbar-oauth2.html http://blog.zxlm.cn/2013/09/chrome-google-publisher-toolbar-oauth2.html#comments Wed, 25 Sep 2013 07:49:31 +0000 http://blog.zxlm.cn/?p=3140 解决方案：在弹出的“需要访问权限”的小窗口上右键并选择“审查元素”，按下图所示操作删除oauth开关的两个Key

Image(6)

然后在Chrome的任务管理器（Shift+ESC）结束进程“Google Publisher Toolbar”，再点击系统右下角的提醒重新加载。

     或者在扩展程序管理中“禁用”再“启用”

Image(7)

每次Chrome重启之后此插件需要重新认证。

但是在网页上“允许”

Image(3)

后仍旧无法获取到数据，点击 Image(4) 一直出现此页面：

Image(5)

需要访问权限：Google发布商工具栏需要您登录到一个或多个Google账户。

]]> http://blog.zxlm.cn/2013/09/chrome-google-publisher-toolbar-oauth2.html/feed 0 PowerPoint 发现无法更正的错误.最好保存演示文稿并退出,然后重启 PowerPiont http://blog.zxlm.cn/2013/09/powerpoint-error-need-restart.html http://blog.zxlm.cn/2013/09/powerpoint-error-need-restart.html#comments Wed, 25 Sep 2013 06:55:56 +0000 http://blog.zxlm.cn/?p=3127 20130519：发现解决此问题的原因，仅在打开下载的PPT文件时出现此问题，当下载文件后右键属性“解除锁定”即可解决此问题。

Image

Image(1)

20130508：在“添加修改程序”中“修复” Microsoft Office后解决此问题，估计是 配置 或 文件丢失。

Image(2)

PowerPoint打开文档一会儿后就出现这个错误，然后就只能强制中止了（与文档安全无关）

好像跟打开的文档相关

一般是通过网络下载的文档打开后出现上述问题

用别人电脑的PowerPoint打开另存一下就OK 了。

   –奇怪！

了解集群.pptx

PS:PPT文件修复工具Kernel PowerPoint Recovery

     KernelPowerPointRecovery是一款PPT文件修复工具，它可以修复由于意外的系统关机，软件崩溃，病毒攻击损坏的PPT演示文稿文件。该软件使用实时预览技术，完成扫描后，损坏或破坏的PowerPoint演示文稿的是可以在窗口中预览。在修复过程中一个完整的扫描损坏的PowerPoint文件进行定位和提取可恢复的信息。

http://ishare.iask.sina.com.cn/f/16691312.html

]]> http://blog.zxlm.cn/2013/09/powerpoint-error-need-restart.html/feed 0 中软国际R1 Portal性能优化（ResourceOne 4.1 Portal Framework） http://blog.zxlm.cn/2013/06/r1-portal.html http://blog.zxlm.cn/2013/06/r1-portal.html#comments Sat, 08 Jun 2013 09:06:29 +0000 http://blog.zxlm.cn/?p=2938 下图为我对中软国际R1 Portal产品进行优化的工作笔记，有遇到同样的性能问题的管理人员，可以考虑交流一下。另外附上此产品生成的一段SQL语句，大家理论一下：

SELECT DISTINCT APPUUID FROM RO_MODULEGROUP WHERE ENABLED=1 AND ADMINFLAG  = 0 AND(MGID NOT IN( SELECT MGID FROM RO_MODULERELATION WHERE ENABLED = 1) OR (MGID IN(SELECT MGID FROM RO_MODULERELATION MR ,RO_MODULE MODDD WHERE MR.MUUID=MODDD.MUUID AND MODDD.ADMINFLAG  = 0 AND MODDD.APP_STATUS = 1 AND MR.ENABLED= 1 AND MODDD.ENABLED = 1  AND MR.MUUID IN(SELECT MUUID FROM RO_MODULERES WHERE STATUS=’1′ AND (ENTRYFLAG =’1′  OR FENTRYFLAG = ‘1’) AND ((NEEDRIGHT=’1′ AND RESUUID IN( SELECT RR.RESUUID FROM RO_ROLERIGHT_3 RR, RO_RIGHTSHORTCUT_3 RS WHERE RR.ROLEID = RS.ROLEID AND RS.PERSONUUID = ‘4028492f3d855b79013de76a510d002d’ AND RR.SYSID =3)) OR NEEDRIGHT=’0′))))) AND APPUUID IN(SELECT SYSAPP.APPUUID FROM RO_SYSAPP SYSAPP, RO_APPGRPRES GRP, RO_APPLICATION APP WHERE SYSAPP.APPUUID = GRP.APPUUID AND GRP.APPUUID = APP.APPUUID AND SYSAPP.USEABLE IN(1 , 2) AND SYSAPP.SYSID = 3 AND APP.APP_STATUS = 1)

Evernote笔记

Evernote笔记

]]> http://blog.zxlm.cn/2013/06/r1-portal.html/feed 0 Android：修改Evernote包名 http://blog.zxlm.cn/2013/05/android-evernote-package.html http://blog.zxlm.cn/2013/05/android-evernote-package.html#comments Wed, 08 May 2013 14:23:23 +0000 http://blog.zxlm.cn/?p=2930 成功修改 Evernote.apk 手机版程序的包名，实现了在手机上安装两个版本的同一个Evernote应用的需求，官方Evernote应用使用国际版账号登录、修改版应用登录印象笔记。

具体的方法网络上一大堆，大致的流程为：反编译、更换包名、打包、复制资源进新apk、重新签名、安装测试。

只是在修改 smali 文件时需要进行特殊处理才能使打包后的应用安装后能够正常使用。

成功更换包名的版本有：

Evernote 3.2.0

Evernote 4.0.4

有同样需求的笔记控可以找我噢！

Android APK 包名修改

]]> http://blog.zxlm.cn/2013/05/android-evernote-package.html/feed 0 YYETS人人影视网站再次关闭 http://blog.zxlm.cn/2013/04/yyets.html http://blog.zxlm.cn/2013/04/yyets.html#comments Fri, 26 Apr 2013 05:39:55 +0000 http://blog.zxlm.cn/?p=2925 风头一过，重新开放，继续接收福利。

就在刚刚去看看“权力的游戏”更新的动态时，发现YYETS.com（人人影视网）再次被关闭。

估计此次站点关闭的原因与此事件关联：国内最顶尖的蓝光高清网站思路网(SILUHD.com)，同时也是国内最著名的盗版高清电影网站，因涉嫌侵犯知识产权被北京市文化执法总队将该网站 CEO 周某等人抓获。国内最大盗版高清门户思路网被查封：30名员工或拘留

人人影视的运营模式与思路网何其相似，及时关站当只猴子吧！

 

]]> http://blog.zxlm.cn/2013/04/yyets.html/feed 0 Android如何永久删除从Google相册同步到手机中的相片 http://blog.zxlm.cn/2013/04/android-gallerygoogle.html http://blog.zxlm.cn/2013/04/android-gallerygoogle.html#comments Thu, 18 Apr 2013 02:48:20 +0000 http://blog.zxlm.cn/?p=2921
/system/app/GalleryGoogle.apk
在“图库”中一直显示关联的Google账号中的相册和相片，同时大量的相片缩略图也占用了SD空间（见：sdcard/DCIM/.thumbnails文件夹里的.thumbdata3文件）
在不重置手机数据的情况下删除这些同步相片的方法：
注：在“图库”中是无法删除同步的相册或相片的；
1.“系统设置”-“账户与同步”-取消“同步 Google-相册”
2.清空“图片”的数据
3.清空“媒体存储”（系统程序）的数据
4.清除SD卡缓存的数据，删除SD卡根目录下 Android/data/com.google.android.gallery3d/cache 中的所有文件；
5.重启手机
]]> http://blog.zxlm.cn/2013/04/android-gallerygoogle.html/feed 0 “SoftEther VPN Gate”死翘翘 http://blog.zxlm.cn/2013/03/softether-vpn-gate.html http://blog.zxlm.cn/2013/03/softether-vpn-gate.html#comments Fri, 29 Mar 2013 10:50:47 +0000 http://blog.zxlm.cn/?p=2913 SoftEther VPN Gate 公共 VPN 中继服务器

20130328：发现所有VPN服务器无法连接；防火墙再次进化对VPN翻墙的行为进行了大清洗。
        在VPNGate网站的实时监控VPN在线用户网页上现在已经找不到来自中国的用户了！
镜像站点：
]]> http://blog.zxlm.cn/2013/03/softether-vpn-gate.html/feed 1 封锁=突破 http://blog.zxlm.cn/2013/01/telex-ip-blocked.html http://blog.zxlm.cn/2013/01/telex-ip-blocked.html#comments Thu, 24 Jan 2013 09:13:42 +0000 http://blog.zxlm.cn/?p=2909 内网无法访问博客的xmlrpc

Telex is down
前段时间可用的IP都已被攻下

仅余一枚VPN苟活

20130409：改用GoAgent

]]> http://blog.zxlm.cn/2013/01/telex-ip-blocked.html/feed 2 购入23寸显示器 DELL U2312HM http://blog.zxlm.cn/2012/03/dell-u2312um.html http://blog.zxlm.cn/2012/03/dell-u2312um.html#comments Tue, 20 Mar 2012 14:46:00 +0000 http://blog.zxlm.cn/?p=2899 观望多时，最终选择购入一台23寸显示器：戴尔（DELL）UltraSharp U2312HM 23英寸宽屏LED背光IPS液晶显示器。（帮京东打个广告）

电商：京东商场

显示器价格：￥1529

显示器特殊功能：IPS屏，可调节高度的支架、可倾斜、可侧转。

显示器侧转的功能比较适合程序员代码开发或者Review，可以在一屏内显示整个文件的源代码，有利于程序员代码开发和日常办公时阅读文件。

U2312HM

]]> http://blog.zxlm.cn/2012/03/dell-u2312um.html/feed 0