Page 1 of 1
Installed Windows on new SSD and configs got carried over
Posted: September 25th, 2013, 9:12 pm
by maxspiderx
With Windows still intact on my old HDD that's still connected to my PC, I installed Windows again on my new SSD. After reinstalling Sabnzb and Sickbeard, I found the exact configs have been carried over without me having to do anything. What's going on?
Re: Installed Windows on new SSD and configs got carried ove
Posted: September 26th, 2013, 5:01 am
by shypike
Depends a bit on where you told SABnzbd where your data is.
By default settings reside in the user profile, so unless Windows somehow took over
existing profile data, you should have a clean slate.
However, if you are using the -f option to set an explicit path and that location is preserved, what you describe will happen.
Re: Installed Windows on new SSD and configs got carried ove
Posted: September 26th, 2013, 8:04 am
by maxspiderx
How can Windows take it over when I performed a clean install on the new drive? Maybe it can detect another version of the OS on a secondary drive and automatically carried over the user settings?
What's an -f option?
Re: Installed Windows on new SSD and configs got carried ove
Posted: September 26th, 2013, 2:41 pm
by shypike
-f, see Wiki:
http://wiki.sabnzbd.org/command-line-parameters
Default locations:
http://wiki.sabnzbd.org/configure-0-7
Somehow Windows took over something from the previous installation.
I don't know, I'm not a Windows wizard.
SABnzbd doesn't look any further than the default location or the "-f" location.