shroomshade Posted November 28, 2017 Share Posted November 28, 2017 (edited) Edit: I know people earlier in this thread have already explained a bit of tjis, and perhaps it just works differently when the junction is created to a Dropbox folder, but I wouldn't think so. Leaving the below anyway in case it helps someone! Maybe I am missing something, but if you are using mklink to make a junction (which is a hard link to a directory) to the physical location of your images, the real folder you are referring to is just a link, it doesn't actually contain the files and files are not being written to it. You will see the files if you open that folder, but those files actually exist in the linked location, and only in that location. It is really just a reference, and any changes to the folder referenced in the junction will propagate and be visible to the junction. For example, say your NES images are in D:Images\NES. You can create a junction to that location from "C:\Users\Username\Launchbox\Images\Nintendo Entertainment System", which will lead to Launchbox recognizing that folder as the file location, even though the files are physically located in the above referenced D:\ drive location. When you check the size of the C:\ Launchbox images folder, what you are really seeing are the details of the physical location on the D:\ drive, and all writes are happening on that drive as well. If you aren't already doing this, you can make a junction using the following command in a Windows command prompt. Note that you will need to use an elevated command prompt to do this, or else it will say you have insufficient privileges. You can do this by right-clicking the Command Prompt application and choosing Run as administrator to open the Command prompt. mklink /J "C:\Users\Username\Launchbox\Images\Nintendo Entertainment System" D:Images\NES Again, this will allow you to have your physical image files in the D:\ location and Launchbox will think they are in the C:\ location, since that location is now just a junction/reference to the true physical location. When I first did this, I shut down Launchbox, moved images to the desired D:\ folder, deleted the platform specific images folder from Launchbox and then created the junction as specified above. I did this with videos and not images, but should work the same. Apologies if I am missing something, but hopefully this helps some. Edited November 28, 2017 by shroomshade Quote Link to comment Share on other sites More sharing options...
housello Posted November 28, 2017 Share Posted November 28, 2017 1 hour ago, shroomshade said: Edit: I know people earlier in this thread have already explained a bit of tjis, and perhaps it just works differently when the junction is created to a Dropbox folder, but I wouldn't think so. Leaving the below anyway in case it helps someone! Maybe I am missing something, but if you are using mklink to make a junction (which is a hard link to a directory) to the physical location of your images, the real folder you are referring to is just a link, it doesn't actually contain the files and files are not being written to it. You will see the files if you open that folder, but those files actually exist in the linked location, and only in that location. It is really just a reference, and any changes to the folder referenced in the junction will propagate and be visible to the junction. For example, say your NES images are in D:Images\NES. You can create a junction to that location from "C:\Users\Username\Launchbox\Images\Nintendo Entertainment System", which will lead to Launchbox recognizing that folder as the file location, even though the files are physically located in the above referenced D:\ drive location. When you check the size of the C:\ Launchbox images folder, what you are really seeing are the details of the physical location on the D:\ drive, and all writes are happening on that drive as well. If you aren't already doing this, you can make a junction using the following command in a Windows command prompt. Note that you will need to use an elevated command prompt to do this, or else it will say you have insufficient privileges. You can do this by right-clicking the Command Prompt application and choosing Run as administrator to open the Command prompt. mklink /J "C:\Users\Username\Launchbox\Images\Nintendo Entertainment System" D:Images\NES Again, this will allow you to have your physical image files in the D:\ location and Launchbox will think they are in the C:\ location, since that location is now just a junction/reference to the true physical location. When I first did this, I shut down Launchbox, moved images to the desired D:\ folder, deleted the platform specific images folder from Launchbox and then created the junction as specified above. I did this with videos and not images, but should work the same. Apologies if I am missing something, but hopefully this helps some. For every kind of link i make in the dropbox folder, dropbox syncronises its destinarion, even if the files are in another disk. I don't want the cache folder to continuoslu upload files. Also, when a symlink is added, dropbox creates a folder on every device synched Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.