先載點來自官方論壇的信息
引用
@bluecow
The message box "An attempt was made to access an unnamed file..." only shows up, if emule receives a corrupted extended protocol message or a corrupted server packet. The term "unnamed" revers to an internal file object which has no filename -- as it is for temporary memory file objects. Therefore that message will not show up if there is a problem with the part file or shared file reading, because those files always have a name. Furthermore the part file and shared file reading is done while processing a standard edonkey protocol message and this message handler has an exception handler which prevents that message box to show up. Anyway, that possibility was defenitively worth to be double checked -- just to be sure
----------
the complete bug fix for the "An attempt was made..." message box or the according error log line which is created in 0.28a during searching will be implemented in 0.28b. I figured out that it's indeed related to some type of search results which are returned randomly by some servers -- that's why all of you experienced that bug under different scenarious and conditions. It depends on the server used for search and the clients which are conected to that server and the type of search pattern you used for searching -- well it's rather complex. It has nothing to do with any .NET updates or similar things.
附帶一提，有關這個錯誤的統計&資料：
1. 不是每個人都會出現
2. 隨時出現(所以奉勸還未“中招”的弟兄不要過早高興)
3. 可能與伺服器有關
4. 多數是搜索時才出現
5. 0.25b以後的版本均存在此bug(←隨時發病… 寒~)
小弟再盡力解釋一下：
成因-
EM收到一些來自伺服器有問題的封包，由於EM要試圖讀取的file object只是暫存性質，根本就沒有檔案名，造成錯誤，所以會出現這個提示。
(ps.如果只是平時的*.part，*.met corrupt的話，因為*.part *.met都有自己的名字，所以EM讀取時不致於會造成錯誤)
“解決”方法-
1) 關掉notification
2) 升級至0.28a
然而，這兩個所謂的“解決”方法只是治標，問題依然存在，只是將那個彈出的框框收起了(0.28a將提示移至log裡)，但至少可以減輕受滋擾的程度。
結論…… 很遺憾…… 只能盼望0.28b能真真正正解決了。
