Would some kind soul please inform me of how to run the wallet from my second hard drive? (E:\)
With all of the other wallets I have, I have moved them to E:\Crypto_Wallets. So for example Hush.exe would would look like this:
E:\Crypto_Wallets\Hush\Hush.exe
With the other coins, all I had to do was take the from appdata\roaming and moved them to E:\Blockchains, so it looks like this:
E:\Blockchains\Coinfolder
Then all I had to do was create a shortcut from the wallet EXE, and edit the properties of the shortcut to add this line to the end of the shortcut: whatever.exe -datadir=E:\Blockchains\Nexus (or whatever coin)
All of them work except Hush. It seems Hush is determined to keep the data in my C:\blah\blah\ appdata\roaming folder. How can I fix this? Thanks.
-datadir is generally available on ETH forks,
the best method under windows is to use junction links which cleanly works for any blockchain
https://steemit.com/cryptocurrency/@xaq/windows-wallets-how-to-change-block-chain-data-directory-for-any-given-currency-fast-initial-downloadsmd E:\Blockchains\Hush\ 2> nul
move C:\Users\yourusername\AppData\Roaming\Hush E:\Blockchains\Hush
mklink /J C:\Users\yourusername\AppData\Roaming\Hush E:\Blockchains\Hush\
edit: you will need to run command prompt as administrator to create junctions (mklink /J)
Hmmm......thanks for this. I'm going to have to study it a bit. See my other response to the other fella' regarding mklink/J.
it should just work, i think i added an extra "Hush" in the first command
md E:\Blockchains\ 2> nul
This will create the folder Blockchains, you can skip it if you already have the folder. make sure you do NOT have a Hush folder there
move C:\Users\yourusername\AppData\Roaming\Hush E:\Blockchains\Hush
will move the Hush folder in C drive to E
mklink /J C:\Users\yourusername\AppData\Roaming\Hush E:\Blockchains\Hush\
will create a junction. when you run the "move" command in 2nd step, it should "move" the folder so make sure you don't have a Hush folder in C:\Users\yourusername\AppData\Roaming\ before running 3rd step.
But if you run these back to back it should just work
