I installed the newe wallet and it does start faster, and I actually have peers and current connections. Problem is. All my coins are gone. Any help appreciated.
Scrap'
i have been testing 2.2.1 on my wallet since over a month, no problems.
as to your wallet -
coins still show after launching again old wallet ( before 2.1.1 version ? ) this would be critical test for your headache
pls try asap
Started old wallet and yes it shows 700,000 ac, but no peers, no connections.
when there are problems with wallet, often helps technical - diagnostic running the Asiacoin core
exactly same procedure as bitcoin core
1.open elevated command prompt ( right click on command prompt > run as administrator )
2.in command prompt change directory to Asiacoin program folder for instance
''cd c:\Program Files\Asiacoin''
or
''cd c:\Users\*username*\AppData\Roaming\Asiacoin''
enter
3.run asiacoin core with diagnostic options
diagnostic options are listed in the wallet : help > debug window > Information > Command-line options + press ''show'' button
there are following diagnostic options
Options:
-? This help message
-conf=<file> Specify configuration file (default: AsiaCoin.conf)
-pid=<file> Specify pid file (default: AsiaCoind.pid)
-gen Generate coins
-gen=0 Don't generate coins
-datadir=<dir> Specify data directory
-dbcache=<n> Set database cache size in megabytes (default: 25)
-dblogsize=<n> Set database disk log size in megabytes (default: 100)
-timeout=<n> Specify connection timeout in milliseconds (default: 5000)
-proxy=<ip:port> Connect through socks proxy
-socks=<n> Select the version of socks proxy to use (4-5, default: 5)
-tor=<ip:port> Use proxy to reach tor hidden services (default: same as -proxy)
-torname=<host.onion> Send the specified hidden service name when connecting to Tor nodes (default: none)
-dns Allow DNS lookups for -addnode, -seednode and -connect
-port=<port> Listen for connections on <port> (default: 8333 or testnet: 18333) {35656 ?} {25656)?}
-maxconnections=<n> Maintain at most <n> connections to peers (default: 125)
-addnode=<ip> Add a node to connect to and attempt to keep the connection open
-connect=<ip> Connect only to the specified node(s)
-seednode=<ip> Connect to a node to retrieve peer addresses, and disconnect
-externalip=<ip> Specify your own public address
-onlynet=<net> Only connect to nodes in network <net> (IPv4, IPv6 or Tor)
-discover Discover own IP address (default: 1 when listening and no -externalip)
-irc Find peers using internet relay chat (default: 1)
-listen Accept connections from outside (default: 1 if no -proxy or -connect)
-bind=<addr> Bind to given address. Use [host]:port notation for IPv6
-dnsseed Find peers using DNS lookup (default: 0)
-nosynccheckpoints Disable sync checkpoints (default: 0)
-banscore=<n> Threshold for disconnecting misbehaving peers (default: 100)
-bantime=<n> Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
-maxreceivebuffer=<n> Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
-maxsendbuffer=<n> Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
-upnp Use UPnP to map the listening port (default: 1 when listening)
-detachdb Detach block and address databases. Increases shutdown time (default: 0)
-paytxfee=<amt> Fee per KB to add to transactions you send
-server Accept command line and JSON-RPC commands
-testnet Use the test network
-debug Output extra debugging information. Implies all other -debug* options
-debugnet Output extra network debugging information
-logtimestamps Prepend debug output with timestamp
-shrinkdebugfile Shrink debug.log file on client startup (default: 1 when no -debug)
-printtoconsole Send trace/debug info to console instead of debug.log file
-printtodebugger Send trace/debug info to debugger
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 36565 or testnet: 26565)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-blocknotify=<cmd> Execute command when the best block changes (%s in cmd is replaced by block hash)
-walletnotify=<cmd> Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
-upgradewallet Upgrade wallet to latest format
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-salvagewallet Attempt to recover private keys from a corrupt wallet.dat
-checkblocks=<n> How many blocks to check at startup (default: 2500, 0 = all)
-checklevel=<n> How thorough the block verification is (0-6, default: 1)
-loadblock=<file> Imports blocks from external blk000?.dat file
Block creation options:
-blockminsize=<n> Set minimum block size in bytes (default: 0)
-blockmaxsize=<n> Set maximum block size in bytes (default: 250000)
-blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)
SSL options: (see the Bitcoin Wiki for SSL setup instructions)
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-rpcsslcertificatechainfile=<file.cert> Server certificate file (default: server.cert)
-rpcsslprivatekeyfile=<file.pem> Server private key (default: server.pem)
-rpcsslciphers=<ciphers> Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)
UI options:
-lang=<lang> Set language, for example "de_DE" (default: system locale)
-min Start minimized
-splash Show splash screen on startup (default: 1)
4.when there are problems with quantity of coins, could help running Asiacoin core with -rescan option
(after changing directory as described in point 3 above )
write in elevated command prompt
''asiacoin-qt -rescan -debug -logtimestamps''5.after running Asiacoin core in diagnostic mode as in point 4
-either coins are found
-either in debug.log text file there is description of error
6.could post here any text lines from debug.log where there is a word ''error''
