Forex Hacked (By rsmereka)

The user has deleted this system.

Forex Hacked Discussion

Jan 06, 2012 at 14:12
3,645 Views
15 Replies
gusrix
forex_trader_51376
Member Since Oct 25, 2011   22 posts
Feb 07, 2012 at 16:12
Hi Rick Smereka,

Can you share your Forex Hacked settings with me?

Thanks,
Member Since Oct 16, 2009   51 posts
Feb 08, 2012 at 15:31
Post #2 the discussion thread of the master account https://www.myfxbook.com/members/rsmereka/forex-hacked-alpari-uk/107706.

Rick
Member Since Oct 16, 2009   51 posts
Feb 08, 2012 at 15:36
As stated in the General tab, this account is a slave/receiver of a trade copier (MT4i Personal Copier). The master account is https://www.myfxbook.com/members/rsmereka/forex-hacked-alpari-uk/107706.

You may download the Forex Hacked settings file (used on the master) from https://www.pipcop.com/forums/current-live-robot-reviews/411-forex-hacked.html. Pipcop.com is my Forex home.

Any request asking a silly question like 'what settings are you using' or 'what copier are you using' will be ignored.

Rick
Member Since Aug 07, 2011   78 posts
Jun 13, 2012 at 13:35
Hello Rick,

i also use the MT4i Personal Copier for some other projects, test, etc. But my problem with this copier is, that it fills the RAM of the machine in a very short time. After a few hours every of my 4 running receiver-instances has about >800 MB RAM in use, so i have to restart these instances 2-3 times a day to free the memory. If i don't do this, then some time i get error messages in the expert tab like this: 'Memory handler: cannot allocate 40961 bytes of memory' and the receiver isn't working anymore. This only happens with the receiver-instances, not with the senders.

Do you encounter the same problems?

Member Since Oct 16, 2009   51 posts
Jun 13, 2012 at 14:55
I have never encountered this issue,

I don't think it is the copier and if it is, then there is an issue with the VPS or computer.

You need to do some serious problem determination by removing everything from the MetaTrader account (all the EA's, indicators and charts), then add them back, one at a time waiting and measuring as you go. That is the only way you are going to find out which component is causing the problem.

Also, use the task manager (processes tab) to see which application is consuming all the memory. Verify that it is an instance of MetaTRader. It may be something else.

Rick
Member Since Aug 07, 2011   78 posts
Jun 13, 2012 at 15:35
Hi Rick,

thank you for answer. I'm employeed in IT business, programming a little bit in some languages and also mql and so on, so i'am familiar with these things. Sorry i didn't tell before, you couldn't know it.

What i want to say is, that i tried all this before.. to eliminate everything, what could cause this issue. I made a clean and fresh mt4 install, copied only the receiver ea and dll into the folder, opened ONLY ONE chart with the receiver EA, nothing else. But still had this problem. 8 mt4 instances running, only the ones with the receiver cause this, the other ones have around 50 mb RAM in use. Easy to see in taskmanager -> processes -> right click on RAM eating terminal.exe -> properties. same problem on 2 different machines, one commercial rented VPS (Windows Server 2008) and one private at my home (Windows 7 Pro).

But your answer was already helpful, so i know now that the problem is caused somewhere on my side... but have to find... ;)

Thanks!
Member Since Jul 01, 2011   41 posts
Jun 18, 2012 at 10:33
I had a similar problem with possible memory leak of MT4i Personal Copier. I got rid of it eventually, after updating my VPS (Windows Server 2003) with all the latest patches, in particular patches related to Microsoft .NET Framework 4.
Member Since Aug 07, 2011   78 posts
Jun 18, 2012 at 12:07
thanks, i can see some new updates available for .net fw 4 with the date of 12.06.2012. i'll give it a try.
Member Since Oct 16, 2009   51 posts
Jun 18, 2012 at 15:05
The 10%+ drop in equity on Jun 18, 2012 was due to a bug in the MT4i Personal Trade Copier. See https://www.pipcop.com/forums/general/455-mt4i-personal-copier-bug.html

Rick
Member Since Jul 24, 2012   3 posts
Jul 24, 2012 at 17:06
I don't understand why you are using settings for Hacked that didn't fail in the past... When looking from maths point of view, every martingale will fail at some point. It is just a fact, you can't deny it. So when choosing a set file that didn't fail so far, you have the odds against you. Shouldn't you rather use a set file that failed...?

Well anyway, it looks like you're busted... Hope not, I really appreciate your hard work!
Member Since Jan 03, 2012   5 posts
Aug 17, 2012 at 17:32
Great tip, I feel more secure already, using settings that have blown my account in the past.
rob559
forex_trader_29148
Member Since Feb 11, 2011   1916 posts
Sep 30, 2012 at 14:52
why are using a trade copier?
Member Since Jul 17, 2011   7 posts
Oct 24, 2012 at 17:16

Placing the EA on the Live Account will produce varying results from the demo account he is currently copying from, especially since two different brokers are being used. I trade the same way on my live accounts. I personally copy all my demos to my real accounts. This has definitely proved to give me better performance over the years.

rob559 posted:
why are using a trade copier?
rob559
forex_trader_29148
Member Since Feb 11, 2011   1916 posts
Oct 25, 2012 at 03:50 (edited Oct 25, 2012 at 03:54)
what setting you are using into the receiver?
Member Since Jun 28, 2012   8 posts
Mar 02, 2013 at 00:42
A real shame this long lasting account had to blow.
Member Since May 15, 2012   247 posts
Mar 02, 2013 at 07:50 (edited Mar 02, 2013 at 07:52)
Yep, but at least he took some Money out.....

anybody here who´s trading FX (I do Hedging, Grid & Martiangale) + CFDs?
If yes click on my Nick...
Sign In / Sign Up to comment
You must be connected to Myfxbook in order to leave a comment
*Commercial use and spam will not be tolerated, and may result in account termination.
Tip: Posting an image/youtube url will automatically embed it in your post!
Tip: Type the @ sign to auto complete a username participating in this discussion.