|
Title: upgraded to v0.9.1 and "bitcoin-qt -conf=..." on win7 stops working Post by: mhps on April 13, 2014, 03:40:57 AM On Win7 32bit when I start v0.9.1 qt with
c:\abc\bitcoin\bitcoin-qt -conf=f:\def\btc\bitcoinqt.conf it doesn't start. Not even the splash screen shows. In f:\def\btc\bitcoinqt.conf I define datadir=f:\def\btc I have used the above with v0.8 qt fine. If I start the new qt without -conf= it starts fine. At least the installation is correct. But it uses the standard %appdata% data dir , which I don't intend to use. This seems to be a bug. It breaks drop-in substitution with the new qt. Title: Re: upgraded to v0.9.1 and "bitcoin-qt -conf=..." on win7 stops working Post by: grue on April 13, 2014, 03:53:17 AM you can't set datadir from a .conf file.
Title: Re: upgraded to v0.9.1 and "bitcoin-qt -conf=..." on win7 stops working Post by: mhps on April 13, 2014, 05:14:35 AM you can't set datadir from a .conf file. Is this new for 0.9.1 ? I have been doiing it for months with bitcoin, ltc, ppc, xpm .... how could they have worked? how else did my 0.8 qt know the custom datadir I specified in the .conf file? Title: Re: upgraded to v0.9.1 and "bitcoin-qt -conf=..." on win7 stops working Post by: shorena on April 18, 2014, 05:33:00 AM Quote All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file. from here: https://en.bitcoin.it/wiki/Running_Bitcoin Just put the data dir in the command link like Code: c:\abc\bitcoin\bitcoin-qt -conf=f:\def\btc\bitcoinqt.conf -datadir=f:\def\btc and you should be fine. According to the wiki, this isnt news either. https://en.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=prev&oldid=20069 Title: Re: upgraded to v0.9.1 and "bitcoin-qt -conf=..." on win7 stops working Post by: shorena on April 18, 2014, 11:16:20 AM Hmm 0.8.0 is from early 2013
https://bitcoin.org/en/release/v0.8.0 The info from the wiki is from 2011, so it might have been an unintended feature. |