Detect if an EA is reading history *.fxt files in backtesting?
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).
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).
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!
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
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!