2022/03/16

重灌win10找不到硬碟

 今天把win10 iso做成安裝usb,重灌的時後,居然在過程中,找不到任何硬碟,換了不同的win10版本也是,這台筆電是這兩年出的,怎麼會這樣。

後來上網查了一下,居然是少了某個驅動,要去下載下來丟到隨身碟裡,重灌時要載入這驅動才看得到硬碟,方法就參考下列網址吧。

https://www.asus.com/tw/support/FAQ/1044458/


when creating a Windows 10 installation USB from an ISO file and attempting to reinstall the operating system, no hard drives were detected during the process. Even after trying different versions of Windows 10, the issue persisted. This laptop was released within the past two years, so it was unexpected.

After conducting an online search, it was discovered that a specific driver was missing. It was necessary to download the driver and save it to a USB drive. During the reinstallation process, the driver needed to be loaded in order to detect the hard drives. For detailed instructions, please refer to the following website:

https://www.asus.com/tw/support/FAQ/1044458/

2022/03/11

Fortinet VPN 程式開啟錯誤 a javascript error occurred in the main process

 一台新的win10電腦在安裝完fortinet sslvpn的連線程式後,開啟都會有java的錯誤










請安裝 Microsoft Visual C++ Redistributable ,把最近的版本裝一下就ok了。

https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170 


Fortinet VPN Program Error: A JavaScript error occurred in the main process.

After installing the Fortinet SSL VPN client program on a new Windows 10 computer, an error related to JavaScript occurs every time it is launched.

To resolve this issue, please install Microsoft Visual C++ Redistributable by installing the latest available version.

You can download the latest supported version of Microsoft Visual C++ Redistributable from the following link:

https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170

2022/03/09

本週再一次失敗的選擇權策略操作-part2

 這次的操作真的是失敗中的失敗。

一開始因為put避險買太貴,然後區間太大,要大漲或大跌500點才有機會賺,所以週五晚上看了一下,決定買比較靠近價平的兩組put價差單跟買put的部位先平掉,只虧損一點點,這樣的話馬上把虧損降到500內。

沒想到星期一就直接大跌,星期二繼續跌,put價差單避險沒了,狂賠....

如果當初買put有留著,賺個幾千塊沒問題。

真的要做好避險,不然依現在的盤勢,一天要漲跌個三百點,也不是多難的事。

2022/03/04

本週再一次失敗的選擇權策略操作-part1

 一樣是用大區間的策略,在一個區間外用價差單跟買call/put做搭配。

這次發現一個很重要的問題,就是如果你多空兩邊都要做到,那你在買call跟put的成本,很難用價差單的權利金來抵消,像是大盤從上漲時,買put的成本很便宜,但這時後是call的價差單有立即的危險,要趕快買call,這個成本就會很貴。

盤勢很難剛好一直在一個很安全的區域上上下下讓你可以收到權利金,又買到便宜的put跟call。

這個策略還有可以在調整的地方,這個星期已無望,好好研究下星期該怎麼辦。

2022/02/25

本週又是一次失敗的選擇權策略操作

 本周採用了一個大區間策略,用call跟put的價差單,配合買call跟put避險。

星期三都還ok,但星期四早上一個下殺,沒做到買put的避險,結果put價差單死傷慘重。

不過有記得可以用小台空單來對沖虧損,但小台空單做下去後,一開始還不錯,但後來突然大盤又往上衝,結果小台空單開始虧損~當下天人交戰,最後我決定50點停損小台,結果停損沒多久,又往下殺,真的是要我命啊。

晚上回家重新看了教學,乎略一個很重要的地方,小台空單進去後,要順便在買call抵銷小台往上漲的風險。

最後決定就用call價差單把put價差單對鎖.....才星期四,就已決定是失敗 的一週。

2022/02/23

遠端桌面連線 查詢來源IP

 如果發現電腦有被遠端桌面連線,想了解來源的IP,可以到事件檢視器去看,路徑是 

Event Viewer > Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager > Operational

可以搜尋這三個ID的事件內容:

Event ID 21 : 工作階段登入成功

Event ID 24 : 工作階段已中斷連線

Event ID 25 : 工作階段重新連線成功


也可以用指令的方式來查詢,速度比較快:

netstat -n | find ":3389" | find "ESTABLISHED"



To inquire about the source IP of a remote desktop connection, you can navigate to the Event Viewer. If you suspect that your computer has been accessed via a remote desktop connection and you wish to determine the source IP, you can follow these steps:

  1. Open the Event Viewer.

  2. Navigate to Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager > Operational.

  3. Search for events with the following three IDs:

    • Event ID 21: Successful session login.
    • Event ID 24: Disconnected session.
    • Event ID 25: Reconnected session.

Alternatively, you can use the following command to perform a faster query:

netstat -n | find ":3389" | find "ESTABLISHED"



2022/02/16

雙買配小台~太早進場啦

 新的週選開始,來試試雙買加小台的搭配。

看教學,配點價差單,可以先回收一些雙買的成本。

但實際操作,發現價差單的位置,如果在週三新合約一開始就衝進去買,權利金好少,等到現貨開讓指數先跑出個方向在進,權利金反而可以多拿一些,是個要好好記住的重點。


2022/02/14

選擇權賣方價差單心得

過年前用月選做了鷹式的價差單,想靠不斷的停利跟對沖來賺錢。

但實際執行了快一個月,才發現有些事真的跟事前想的不一樣。

像是權利金比較少的那一邊,其實虧損會比較大,但常常會把權利金當成本金,以為權利金比較多,虧損也會比較多。

還有就是帳面上的未實現損益統計,其實跟你到結算日的損益是兩回事,系統上的未實現損益並非你真正的損益。

這些事沒看清楚,就無法算出對沖的部位要買在哪比較好,看網路教學好像都很簡單,但很多細真的是要實際操作後才能學到。

2022/02/10

outlook 主旨無法排序 "無法依據這個欄位排序"

 有使用者反應在outlook收件匣中,無法依主旨排序信件,會出現"無法依據這個欄位排序"的錯誤訊息。









其他欄位排序卻都沒問題,一開始用這個錯誤訊息去找出來的解法,都沒什麼用,也沒在細查,因為電腦有其他比較麻煩的問題,所以這個就先不管。

等電腦其他outlook問題解決時,這問題還是有,又在看了一下,突然發現,上面欄位不是"主旨",而是"工作主旨",所以就點開欄位設定,順便看了一下其他outlook,正常的話,都是顯示主旨這個欄位。

使用者不知怎麼弄的,變成工作主旨,這個欄位本來就是無法排序的,只要把它改回主旨就行了。










Users reported that they were unable to sort their emails in Outlook's inbox by subject, and encountered an error message saying "Cannot sort by this column."

Sorting by other columns worked without any issues. Initially, the suggested solutions found using this error message were ineffective, and further investigation was not conducted due to other pressing computer issues.

However, even after resolving the other Outlook problems on the computer, this sorting issue persisted. Upon closer examination, it was discovered that the column header was not "Subject" but rather "Subject (Work)." The column settings were opened, and a comparison with other Outlook instances revealed that the normal display should be "Subject."

It was unclear how the user had changed it to "Subject (Work)," but this column was inherently unsortable. Simply changing it back to "Subject" resolved the issue.

2022/02/09

MS Project 2016 無法登入"很抱歉 發生暫時性的伺服器問題"

 在使用租用一年的MS Project2016版時,要先去office365下載安裝程式,安裝完後執行程式時,需要做登入,登入有授權使用的帳號,才能使用Project上的功能。

但按下登入時,無法正常出現登入的視窗提供輸入,反而是顯示"很抱歉 發生暫時性的伺服器問題"。

一開始以為是OS的問題,但試了其他台的WIN7 OR WIN10,都OK。

後來又想是不是本機office版本的問題,但在其他台office2010沒問題,在使用者上的2007或2010都不行。

最後發現使用者電腦只裝到IE9,試著升到IE11,Project的登入視窗就正常了,搞死人了。

"Unable to log in to MS Project 2016" Sorry, there was a temporary server issue.

When using the one-year subscription of MS Project 2016, you need to first download the installation program from Office 365. After installation, when you run the program, you are required to log in with an authorized account in order to access the features of Project.

However, when you click on the login button, the login window doesn't appear as expected and instead shows the message "Sorry, there was a temporary server issue."

Initially, it was thought to be an issue with the operating system (OS), but after trying on other computers running Windows 7 or Windows 10, it worked fine.

Later, it was considered that it might be an issue with the local version of Office, but on other computers with Office 2010, there were no problems. However, when using versions 2007 or 2010 on the user's computer, the issue persisted.

Finally, it was discovered that the user's computer had only Internet Explorer 9 installed. After upgrading to Internet Explorer 11, the login window for Project started functioning properly.