您的電腦遺失api-ms-win-crt-runtime-l1-1-0-dll

 有些電腦在執行某些程式時，時會出現"您的電腦遺失api-ms-win-crt-runtime-l1-1-0-dll"，以致程式打不開。

重裝程式也沒用，因為這個.dll檔是其他程式提供的，就是微軟的c++可轉發套件。

去下載後重新安裝c++可轉發套件，就可解決此問題。

Your computer is missing api-ms-win-crt-runtime-l1-1-0.dll.

On certain computers, when running certain programs, an error message may appear stating "Your computer is missing api-ms-win-crt-runtime-l1-1-0.dll," causing the program to fail to launch.

Reinstalling the program does not resolve the issue because this .dll file is provided by another program, namely Microsoft's C++ redistributable package.

To resolve this problem, you need to download and reinstall the C++ redistributable package. This will ensure that the missing api-ms-win-crt-runtime-l1-1-0.dll file is properly installed on your computer.

選擇權操作-202206w3-只做最後兩天雙買，被殺爆了

 最近 都是開低走高，所做做空方都被殺。

又賠了快130點，真的慘。

如果做賣方，反而都會賺錢....

休息一下好了，不順就要暫停一下，不能一直賠下去。

OUTLOOK很舊的信變亂碼 比較新的信正常

因為換新電腦，所以把舊電腦的PST檔一起移到新電腦上。

但 在查詢一些信件時發現一個怪事，大概在2013年以前的信件，全變成亂碼。之後的信件，卻都正常。

在舊電腦上是完成正常的，所以就在找另外兩台電腦來測試，測試後發現，同一個PST檔，在某些電腦上都有這個問題，在另一些電腦卻沒事，跟OUTLOOK或WINDOWS的版本都沒直接關係。

最後才發現，原來是OUTLOOK裡面的編碼設定造成的。

編碼如果改成BIG5，就沒有亂碼的問題，調成UTF8就有。

但還是跟使用者說，因為都是很舊的信才有影響，平常還是建議用UTF8，有需要查舊資料，才用BIG5。

Old emails in Outlook are displayed as garbled characters, while newer emails appear normal. 

Due to a computer upgrade, the PST file from the old computer was transferred to the new computer. However, upon checking some emails, a strange issue was discovered. Emails dated before approximately 2013 appeared as garbled characters, while those after that period appeared correctly.

The emails displayed correctly on the old computer, so additional testing was conducted on two other computers. It was found that the same PST file exhibited this issue on certain computers but not on others, regardless of the version of Outlook or Windows being used. Eventually, it was discovered that the encoding settings within Outlook were causing the problem.

Changing the encoding to BIG5 resolved the issue and prevented the garbled characters. However, it is still recommended to use UTF8 encoding for general use, as it is more widely supported. The BIG5 encoding should be used only when accessing old data that is affected by this issue.

選擇權操作-202206w2-上週賺的3千，本週全吐回

 本週做了三次雙買，只有今天結算這天小小賺，其他兩天都賠，而且多次IOC進場不順，都跟原本要進場的價格有一點差距了。

這周基本上震盪小，做雙買就是不順。

結果這天進場後一開始還不錯，誰知道下半場開始拉回，50多點的獲利一點一滴的消失。

很不順的一週啊。

選擇權操作-202206w2-出師不利 雙買組合單多次IOC一直沒成交

 今天做雙買，結果盤勢不如預期，從反方向走，所以就註定要賠錢。

只是在多次IOC下單時，又一直沒成交，一直在那洗，最後又是又單獨下單才成交，然後再組合。

後來要停損，又是一樣的問題，就是洗不到成交，然後就先拆單，各別平倉，才出掉。

以後都分開下好了。

選擇權操作-202206w1-本週只賺3千，但已經週獲利新高~~

 這週只交易兩天，做2次雙買1次雙賣。

賺3千左右，已是我獲利最高的一週了，太感動了。

策略本身還需要調整，看下週能不能有更好的獲利。

選擇權操作-202206w1-雙買買不到

 今天現貨開盤十多分鐘，就要在價內做雙買，掛多次IOC組合單，價格條件都有達到，但就一直沒成功成交，等了兩分多鐘都沒成功。

最後就放棄，直接各別下單，一下就成交了。

還好最好還是有進場，沒放棄，不然今天就沒賺到了。

選擇權操作-202206w1-雙賣居然沒出掉

 今天是6月第一週第一次做單，有做雙買跟雙賣。

運氣不錯，理論算應該要賠錢，但下單時沒注意，做反了，結果賺錢了。

但是雙賣的部分13:44開始掛多次IOC要出掉，結果居家都沒成交，只能等下午開盤繼續，因為雙賣的部份是虧錢的，一定要趕快脫手。

選擇權操作-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.