Home Forums Tickstory Lite Issue/Bug tracking Can’t define the mt4-folder to launch the terminal??

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • gooly
    Participant
    Post count: 57

    Hi again,
    I have tried to find where TickStory stores it’s default path (with which it is started) of the mt4-terminal – and failed. 🙁
    As I cannot change this terminal-path using the ‘official’ way I might be successful changing its ‘set-file’.
    Can you tell me – as a temporary workaround – how I might be able to launch another terminal than only the actual one?

    Is there a next version planed to be issued – when?

    Thanks in advance,
    Gooly

    gooly
    Participant
    Post count: 57

    Hi again,

    Could it be this situation?
    After I found that the huge fxt-files were copied and save a second time by what ever program to the default install.-folder of an mt4 installation:
    ..AppDataRoamingMetaQuotesTerminalF3FCE634953CAFEE1AF7E348742EF8CB
    I deleted some sub-folders with in those folders and start the terminals by fix shortcuts always in /portable-mode.

    Are you searching there (..AppData…) for a valid installation?
    Can you change this – or can you define what you need there?

    Regards,
    Gooly

    imported_tickstory
    Participant
    Post count: 1479

    Hi Gooly,

    Tickstory attempts to work as per the “spec” of MT4’s directory structure. That is, it firstly checks the roaming directories and within these directories it has a “origin.txt” which contains the actual program folder of MT4. Of course, if this is not valid, then this would be throwing things out. For the moment the “lowest touch” way of resolving the issue should be to rename the origin.txt file in the ..AppDataRoamingMetaQuotesTerminalF3FCE634953CAFEE1AF7E348742EF8CB folder (or deleting it) so Tickstory ignores this directory and instead checks the installation folder to see if everything is there.

    We’ll try to work on a suitable method of relaxing some of the checks that are done for validating an install (or perhaps warning the user), but generally speaking the checks are doing what they are designed to do.

    Hope this helps.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.