選擇權操作-202206w1-準備開始交易

 最近在想新的策略，這周前幾天就都沒做單，因為統計了一下，星期二跟三獲利的機會最高，所以要明天跟後天在來做。

outlook信件有迴紋針，但信裡看不到附件

 偶爾都會有使用者反應，收到的信件，旁邊有迴紋針，表示信中有附件，但信打開，裡面卻只有內文，沒有任何附件。

後來仔細的查詢，當信件進來後，經過第一層的圾垃郵件過濾系統，信還是完整的，附件也都有。

之後進到Mail Server，信也是正常的，然後Outlook收信時，從Mail Server的log上看到，的確也是整封信傳過去，所以就判斷問題是在本機端產生，不是Mail Server的問題。

防毒軟體在安裝時，有另外在Outlook內插入一個增益集程式，做附件掃描的功能，後來在Outlook裡把這個功能關閉，有問題的信在重寄一次，附件就出現了。

Occasionally, users have reported receiving emails with paper clips indicating the presence of attachments, but upon opening the emails, they find only the body text and no attachments.

Upon further investigation, it was found that when the emails arrive, they pass through the initial spam filtering system intact, with all attachments included.

Subsequently, when the emails reach the Mail Server, they are still in their original state. However, while receiving the emails in Outlook, it was observed from the Mail Server logs that the complete emails were indeed being transmitted. This led to the conclusion that the issue originated on the local machine and was not a problem with the Mail Server.

During the installation of the antivirus software, an add-in was inserted into Outlook to enable attachment scanning. However, after disabling this functionality within Outlook, the problematic emails were resent, and the attachments appeared as expected.

選擇權操作-202205w4-又賠錢了

 這周只做兩筆雙賣，星期五中午12點多做勒式，星期一中午也是12點多，做跨式。

其實進場點不好，因為如果想等時間價值流掉，12點多進，只剩1小時，太失敗了，不應該手癢亂下單的。

兩筆單含手續費大概虧時是2千，對一個還沒辦法賺錢的人來說，實在痛。

選擇權操作-近期心得

操作選擇權5個多月了，主要是從Youtube找了兩個比較有名的選擇權頻道做學習，並還有購買過其中一個人的線上課程，也有訂閱另一個的Youtube會員頻道。

主要是價差組合單跟跨式雙賣，有幾個心得:

1.未實現損益還是要注意 : 不能因為你覺得結算當天，價格還是非常有機會回到你預期的地方，就不管現在已經被穿價，然後放著不管它，如果價格真的往反向走，會虧很慘。

2. 組合單還要在做保險部位 : 做成組合單，其實就已經同時有多空兩個部位了，可限制或減緩虧損的速度，如果還要在加個BP或BS，又增加了更多交易成本，有時後反而更難獲利。

3. 還是要停損 : 有看到一些人說做價差單就不用停損啊，因為最大虧損已固定，但如果會了勝率高，做比較價外的地方，損益比其實很差，賺很多次可能一次就賠光，除非對沖或調整部位的手法非常熟練，不然還是要適時停損，不要賠太多，才能繼續生活下去。

4. 部位不要太大 : 還不熟時，部位不要太多，不然到時行情突然不如預情，產生大量的帳面虧損，就會不知該怎麼做，部位調的亂七八糟。

大概就這些了。

選擇權操作-202205w3-雙賣賺錢了

 這週全做雙賣，從星五夜盤開始做，做了七組跨式，5組獲利，最後賺了24點，雖然只是賺了一點點，但跟之前一直賠錢相比，算是有進步了。

希望能繼續保持下去，能穩定，再來慢慢放大口數。

Adobe reader開啟檔案錯誤 : 處理註解或連結時出錯。字型指定的編碼(CMap)遺失。

 今天收到一個PDF檔，上面有被加上一些註解，在用最新版的Adobe reader開啟時，就會跳出"處理註解或連結時出錯。字型指定的編碼(CMap)遺失"的錯誤。

內文本身可以看，但註解的部份就無法顯示。

電腦本身除了有裝Adobe reader，也有裝字型包，裡面的註解也都是中文，所以一開始也不知為何會有錯誤。

最後就是把Adobe reader跟字型包重裝，就沒事了。

Error opening file with Adobe Reader: Error processing annotations or links. The specified font encoding (CMap) is missing.

Today I received a PDF file with some annotations added to it. When I tried to open it using the latest version of Adobe Reader, an error message popped up saying, "Error processing annotations or links. The specified font encoding (CMap) is missing."

The main content of the document was visible, but the annotations were not displayed. My computer had Adobe Reader installed, and I had also installed a font package that included Chinese annotations. Therefore, initially, I was unsure why this error occurred.

In the end, I resolved the issue by reinstalling Adobe Reader and the font package, and the problem was fixed.

啟動 office2010 錯誤 0x80070190

 在啟動office時，出現0x80070190的錯誤，這不是序號錯誤，也不用去改機碼。

只要在啟動office的程式時，選擇用"系統管理員身份執行"，開啟程式後在去啟動office授權，就ok了。

When launching Office, an error with the code 0x80070190 appears. This is not a serial number error, and there is no need to modify the registry. To resolve this issue, simply launch the Office program with "Run as administrator" option. Once the program is open, proceed with activating the Office license, and the issue should be resolved.

選擇權操作-202205w2-測試雙賣當沖 還抓不到感覺

 這週都在做當沖測試，有做單方向的跟雙賣。

單方向的單，跟期貨差不多，選錯方向就是賠錢，只是賠錢的速度比較慢一點點，這就不是我想做選擇權目的。

再來就是雙賣，主要就可擇價平或上下一檔雙賣，本來想說時間價值的流失會比兩邊權利金的變化更快，要賺時間價值的錢。

但事情並非如此，只要大盤大漲或大跌，權利金反而會升的比時間價值消耗的更多，然後就打到停損了。

這就要繼續研究什麼時間盤比較不會動，才能做雙賣。

選擇權操作-202205w1-繼續賠錢，但還行

 這周就一開始的雙買很失敗。

之後做了兩組價平的組合單，其中一組還是剛好最大虧損是0，很難得。最後結算日又做了雙賣。

搞到最後不算手續費，只賠幾點而已，個人覺得還行啊。

OCS Inventory NG 2.9.2 很多頁面是空白的

 因為原本的OCS Inventory NG太舊了，agent已不支援最新版的win10，所以要來升級到最新的 2.9.2。

最新的OCS server只能裝在Linux上，所以就選欲centos7來安裝，安裝過程主要是照 https://kifarunix.com/install-and-setup-ocs-ng-inventory-server-on-centos-7/ 這篇來操作。

裝的過程都蠻順利的，agent也要裝到client上了，但最後產生兩個問題。

1. 有抓到client，但軟體清單都是0，這個是因為OCS上有一個整理軟體的程序並不會自動執行，要自己去把這程序設到排程裡，才會統計軟體清單，程序是  /usr/share/ocsinventory-reports/ocsreports/crontab/cron_all_software.php

2. 看到軟體清單後，又發現另一個問題，系統會統計所有軟體被多少電腦安裝的數量，點擊那個次數就可以秀出是哪些電腦，但點擊後卻是空白畫面。

查了兩天，試過升級OCS nightly最新版，OS重裝，關閉SELINUX，都沒用，然後突然發現一篇文章就是在說這個問題，原來是PHP的版本太舊了，只要把PHP的版本升到最新，OCS也不用重裝，網頁畫面就可以正常顯示了。

Due to the outdated version of OCS Inventory NG, the agent no longer supports the latest version of Windows 10. Therefore, it is necessary to upgrade to the latest version, 2.9.2.

The latest OCS server can only be installed on Linux, so CentOS 7 was chosen for the installation process. The installation was primarily performed following the steps outlined in the article: "https://kifarunix.com/install-and-setup-ocs-ng-inventory-server-on-centos-7/".

The installation process went smoothly, and the agent was also installed on the client. However, two issues arose at the end of the process.

The client was detected, but the software inventory showed as 0. This occurred because OCS has a software sorting process that does not execute automatically. To resolve this, it is necessary to manually set up the process in the scheduler. The process is located at "/usr/share/ocsinventory-reports/ocsreports/crontab/cron_all_software.php".

After the software inventory was visible, another issue arose. The system was supposed to track the number of installations of each software on different computers. Clicking on the installation count was expected to display which computers had the software installed, but it resulted in a blank page.

After two days of investigation, attempts were made to upgrade to the latest version of OCS nightly, reinstall the OS, and disable SELINUX, but none of these resolved the issue. Then, by chance, an article was found that addressed this problem. It turned out that the issue was caused by an outdated version of PHP. Upgrading PHP to the latest version resolved the problem, and there was no need to reinstall OCS. The web page now displays correctly.