here is a link for windows wallet-qt:
https://drive.google.com/file/d/0B1cnD3W8c0jtaEJ1ajFIeDFSZnc/view?usp=sharing

always backup your wallet.dat file

no changes need to be done to your bitbar.conf file - you don't even need one now 


If your block count does not match http://btb.cryptocoinexplorer.com/ please remove everything except your wallet.dat file from C:\Users\-your name-\AppData\Roaming\BitBar and re-download the chain - simply by running bitbar-qt.exe  that will get you back on the right fork.

Thanks for helping here.

Running Centos 6.7 and i used this script to install but modified it for Bitbar: https://github.com/mikeminneman/dogecoind-centos

Ok, so my rpc password does match in both the pool config and bitbar.conf files. I think that is working because the debug log in Bitbar shows the rpc request from node "gettransactions".

Heres my Bitbar wallet "getinfo" - (I started a new wallet so its just downloading again)

  "version" : "v0.4.3.004-5-g903edf9-beta",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 83500,
    "moneysupply" : 14044.44104100,
    "connections" : 1,
    "proxy" : "",
    "ip" : "X.X.X.X",
    "difficulty" : 41.30374091,
    "testnet" : false,
    "keypoololdest" : 1450404332,
    "keypoolsize" : 101,
    "paytxfee" : 0.00010000,
    "errors" : ""


Heres the error in NOMP:

2015-12-18 15:45:44 [POSIX]     [Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2015-12-18 15:45:44 [Master]    [CLI] CLI listening on port 17117
2015-12-18 15:45:44 [Master]    [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file
2015-12-18 15:45:44 [Payments]  [bitbar] Payment processing setup to run every 120 second(s) with daemon (bitbar@127.0.0.1:9344) and redis (127.0.0.1:6379)
2015-12-18 15:45:45 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2015-12-18 15:45:45 [Pool]      [bitbar] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2015-12-18 15:45:46 [Payments]  [bitbar] Check finished - daemon rpc error with batch gettransactions {"type":"request error","message":"read ECONNRESET"}
2015-12-18 15:45:46 [Payments]  [bitbar] Finished interval - time spent: 995ms total, 3ms redis, 987ms daemon RPC
2015-12-18 15:45:46 [Pool]      [bitbar] (Thread 1) Could not start pool, error with init batch RPC call: {"type":"offline","message":"connect ECONNREFUSED"}

Here the Bitbar debug log that shows the last entry before it terminated due to the above request from NOMP.

Flushed 5740 addresses to peers.dat  78ms
Flushed 5740 addresses to peers.dat  78ms
ThreadRPCServer method=getinfo
ThreadRPCServer method=validateaddress
ThreadRPCServer method=getbalance

Heres the error if i run from the terminal as you can see "getbalance" returns info but "gettransactions" kills it.

# bitbard getbalance
0.00000000
# bitbard gettransactions
terminate called after throwing an instance of 'std::vector<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> > > >'
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file
Aborted (core dumped)

So it looks like an issue with the wallet when the "gettransactions" call is issued Im guessing there aren't any due to it being a new install. Any thing jump out at you? Maybe I'm missing something obvious....

the bitbard getinfo seemed to work well.
Do you get any errors if you do:
bitbard listtransactions     -or-
bitbard listaccounts

If those work, then I think the wallet database is working ok.

I have a couple of thoughts:
1) Are you running a firewall, blocking any ports??


         (I am unfamiliar with Centros, so this might not work)

2) compile bitbar from source using:
sudo apt-get install build-essential
sudo apt-get install libssl-dev
sudo apt-get install libdb4.8-dev        *this may give you trouble
sudo apt-get install libdb4.8++-dev
sudo apt-get install libboost-all-dev

make -f makefile.unix USE_UPNP=-

- why:
Boost is complaining a lot, and interacts with some of the other dependencies. I'd like to make sure you are using the same libraries.
The boost errors have to do with the RPC calls. (rpc problems keep popping up. humm)

3) you might not like this one:
switch to Ubuntu server (or desktop) It is what I am using and could provide links to step by step instructions on how to set up Ubuntu and NOMP.
guess I could add a link anyway:
scratch that - the web site has been down for a while. I will just have to add it to Bitbar.co when I have time..

just had a thought -
I have to use sudo to start my nomp - it would give errors (but I don't remember what they are) if I don't use sudo:

sudo node init.js     <-- try this first

Let me know how it goes

I assume you are in sync with CCE, and have made a backup of your wallet.dat

If the coins in your wallet were gained from a different chain - like mined from a pool that was on a different chain, the tx information will not match anything on this chain. ( 'this chain' being the one followed be CCE) making those coins orphans.
I don't know the order in which the coins are removed from your wallet, but it sounds like it tried to send coins from a different chain.

Did you remove everything in your bitbar folder except wallet.dat and let the wallet sync fresh ??
That's what I would try first.
The second thing I would try, and it might not help at all, but what the heck - is open a command prompt and start the wallet like this:
bitbar-qt.exe -rescan
that will Rescan the block chain for missing wallet transactions,and hopefully mark the 'bad' ones as orphaned.

If that doesn't help, the next step would be to export your private keys, rename the bitbar directory, and start over.(and import key)
This step may not be possible with bitbar wallets so far, I don't remember seeing those commands in the bitbar help. It might be from litecoin or bitcoin - I will have to investigate.

I would also wait to make sure Cryptsy joins our chain, before sending any bitbars.
If you are on one chain and send coins (even to yourself) the transaction gets put into the chain your wallet is on. It doesn't matter if the coins are from two years ago or not. IF for some reason Cryptsy goes with a different chain (I don't see why they would) the coins you sent would become orphans. (you burnt them)
I don't see that happening, but why take the chance, when all you have to do is wait a little more (I know it sucks)

You can't discard with coin control, but you can choose which coins to send.

The wallet updates were fairly simple, and did not touch anything to do with transactions.
The coin control will be a while down the road. It will take a month or two to test, sending coins, waiting to see if they stake. Don't want to do that with real bitbars.

I asked the poolmaster@ H2C to add btb again and let him know about the updated wallet, even said "pretty please" lol

I'm the 173 address

BTB is back on H2C! theres already like 1500 MH right now on the net, just from there!

mastermining showed on the peer list at CCE but has been gone for a while.  His btb pool is still down for maintenance, maybe he didn't like loosing all those bitbars they mined for a month+ on a wrong chain ??

cryptsy still not accepting deposit. i have 20 BTB in wallet but it didnt stake any for me, what is the minimum require?

Difficulty getting close to 42 !
maybe we should have waited to get the 'other chain' miners on ours  -  just kidding !
but my little 9 Mhash isn't doing much now....