Quote from: shorena on November 28, 2014, 04:29:06 PM

Quote from: xhrike on November 28, 2014, 01:44:23 PM

-snip-

Answers or suggestions?

Launch with -connect=IP to a fast node for the rest.

For windows hit Win+R to open the "run" window:
enter: c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=IP
change the IP to one from the list, the path as needed and click ok.

For linux, open a terminal and enter

bitcoind -connect=IP

change the IP and on some distros you have to give the full path to bitcoind.
Note, this will not launch a GUI, use bitcoind getinfo so see the status.

or run bitcoin-qt instead of bitcoind for GUI.

Once synced, close bitcoin core and launch as usual.

List of possible nodes:

Code:

last updated 2014.11.25
-------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
eldinhadzic.org[4] - LA, USA - eldinhadz - 1000 mbit/s - no - no
84.200.34.113 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
185.45.192.129 - Amsterdam, NL, EU - anon - 1000 mbit/s - /node.php[3] - yes
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
50.7.68.180 - New York, USA - Newar - 100 mbit/s - yes - no
5.9.24.81 - Germany, EU - zvs - unknown - no - no
178.79.173.71 - United Kingdom, EU - zvs - unknown - no - no
107.155.104.194 - Dalls, USA - zvs - unknown - no - no
106.185.32.195 - Japan, Asia - zvs - unknown - no - no
94.242.57.173 - Russia, Asia - zvs - unknown - no - no
-------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] IP is 173.236.158.177

Ah.. I didn't know that. Thanks!

I used bitcoind and then tail'd the log file.. But this -connect=IP is very helpful.

Much reading to do still