Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Moving my MEGA synced folder location

Options
  • 09-05-2014 5:35pm
    #1
    oceanclub
    Registered Users Posts: 3,411 ✭✭✭


    I'm currently using MegaSync and it syncs by default with C:\Users\{username}\Documents\MEGA. However, I'm running out of space on my C: SSD drive. What is the easiest way to move the MEGA folder to my E: drive _and_ ensure MEGASync recognises the move? Thanks.

    P.
    Tagged:


Comments

  • Options
    #2
    900913
    Registered Users Posts: 367 ✭✭900913


    Right click the Megasync icon in the system tray and select SYNCS.

    There's an option to add a new Dir path.


  • Options
    #3
    oceanclub
    Registered Users Posts: 3,411 ✭✭✭oceanclub


    900913 wrote: »
    Right click the Megasync icon in the system tray and select SYNCS.

    There's an option to add a new Dir path.

    Thanks, but I don't see that strangely; am running the latest Megasync as far as I know (1.0.18, says "up to date").

    lU5JLlL.png

    P.


  • Options
    #4
    Lundar.
    Registered Users Posts: 120 ✭✭Lundar.


    hi Oceanclub,

    i recently moved my mega sync folder to my D drive. just click on setting and then click Sync and specify where you want it, i cut and pasted the files and so on to the new location and let it sync up, took a while.


    306571.png


  • Options
    #5
    keiser13
    Registered Users Posts: 2 ✭keiser13


    "Add" folders appears under "sync" but is not working under version 1.0.35.
    Is there a workaround for this?


  • Options
    #6
    keiser13
    Registered Users Posts: 2 ✭keiser13


    "Add" folders appears under "sync" but is not working under version 1.0.35.
    Is there a workaround for this?


  • Advertisement
Advertisement