Detect if an EA is reading history *.fxt files in backtesting?

Back to topics list To post a new topic, please log in or register
avatar
2
style-sheets 2016.06.15 20:37
 

Hi,

 

I've seen in the past examples of EA who cheat by directly reading *.fxt history files & create fake results in backtesting.

 

It's easy to tell just by looking at the mq4 code, but what if I don't have access to the EA's source (only the compiled *.ex4 demo)?

 

Is there a way to detect if an EA is doing this in this case?

 

Thanks! 

avatar
1110
Ovo 2016.06.16 08:59 #
 
I do not think the fxt file can be accessed by the MQL4 file commands. If the winapi is used to access the file, then the handle to the FXT file would be listed in the resource monitor (resmon.exe).
avatar
2
style-sheets 2016.06.16 10:13 #
 
Ovo:
I do not think the fxt file can be accessed by the MQL4 file commands. If the winapi is used to access the file, then the handle to the FXT file would be listed in the resource monitor (resmon.exe).

Yes, that's what I meant: file access via winapi.

That's brilliant, Ovo! I totally forgot about resmon

Thanks! 

Back to topics list  

To add comments, please log in or register