How to install the Dropbox folder on the drive of my choice?

[David222]

I want to install my Dropbox folder onto my new computer.

My Dropbox folder is 1.5 Terabytes, consisting of my iTunes library.

My c: drive is only 1 Terabyte, so I need to install the Dropbox folder to my d: drive, which is 6 Terabytes.

However, it seems Dropbox will only install to c: drive, even if I change the default download location.

How do I address this?

I need to either make Dropbox download to d: drive OR swap drive names so c: drive is the larger one?

NOTE: To MOVE the Dropbox folder to another drive is not an option here, as it's not on the computer to move. I'm asking how to INSTALL the Dropbox folder to the correct drive - or other workaround.

Any information or advice would be much appreciated.

[David222]

(Addition removed, original post edited instead.)

[Megan]

Hi @David222, welcome to our Community! 

Upon installation, and the initial set-up steps, you should be able to see the "Advanced settings".

If you click there, you should be asked where you'd like to save your Dropbox folder. That way, you can choose to save your folder to your d: drive, instead of C:. Can you give this one a go, and let me know how it turns out?

Keep me posted! 

[David222]

Thanks for your reply Megan.

Your instructions seem to be working (just noting here also as a reference for myself):

Upon installing, the "Set Up Dropbox" box asks the question "How do you want files stored?"

The options are "Online-only (recommended)" and "Local".

When I choose "Local" there's a message: "Not enough hard drive space. Choose online-only."

The only options presented are the "Next" button and "Learn more", which just links to help pages.

When I choose "Next" there is indeed an advanced option whereby you can choose the download destination.

I selected D drive and at this stage it seems to be going OK installing to D drive.

It seems it will take a very long time to download 1.5 terabytes, so I'll leave it going and check back later.

[Hannah]

Thanks for the update here, @David222.

If you run into any issues, let us know!