Linux is case sensitive.  Make sure if your wallet is named Wallet.bin you don't try to open wallet.bin, etc.

Experiment with different thread counts.  Some people here have reported better results with fewer threads.  My theory was CPU throttling due to high temps.  But earlier in the thread it was mentioned that hyperthreading processors could possibly have a negative effect if the CPU uses hyperthreading for threads that should have a physical core dedicated.  I have 4 physical cores plus hyperthreading, and I actually get the best hash rate with 3 threads, even though I could use up to 8.

For what it's worth, I sent a few bips from one wallet of mine to another to test and received them ok.  I sent them using the CLI wallet with a mixin value of 2 (anything higher than 2 doesn't seem to work yet, probably because of the low volume of transactions).

Yeah...

a) If I wanted to sabotage it (even for profit) I wouldn't admit it in public.
b) I wouldn't accept payment in the currency I'm putting at risk.
c) Anyone who has mined bipcoin has some interest in the health of the coin, even if that means the difficulty goes up, because an increase in popularity means an increased probability that your existing coin is worth something.
d) You know where I live.   ;-)

For 200bip I'll start a rumor that a critical security flaw has been found in the BipCoin code, let it rest for just long enough to fill our coffers, then "expose" that dirty hoax and denounce the perpetrator using my other sock puppet accounts.   ;-)

CooperStupor,
    Based on your previous response it looks like you are expecting bipcoind in the folder /bipcoind.  If that is correct please navigate to that folder in a terminal "cd /bipcoind" and then list the contents in long format "ls -ald ./*" and post the exact output here.  Your error message indicates that bipcoind does not exist in that folder.  So either

a) You have the windows package, and the file list will show bipcoind.exe
b) You did not fully extract the contents (a GUI file extractor will show you the files contained within but you have to move them to your destination to actually extract them).  Or alternately you extracted the .gz part of the archive but did not extract the .tar that is contained within it.
c) You extracted them to a location other than where you thought they went.

I will note that it is unlikely that your files are in /bipcoind unless you use "su" or login as root because creating files in "/" usually requires root level permission.  If you are logging into your computer as root or doing these things with "su" I highly recommend that you login with a standard (non-privileged) user account, don't use "su" for any of this, then re-download and start over from the beginning, putting your files somewhere like "/home/XXXXXX/bipcoin/" (where XXXXXX would be your username).  There are many reasons for this related to safety and security.

Thanks,
    ir57

I recommend that you PM me if you would like help, in order to keep this thread clean.  However, in the interest of transparency I also recommend, after our correspondence is finished, that you copy all of our messages into PasteBin and post the link here.  I don't like giving people commands to execute on their computer in private communication due to the appearance of impropriety.  Plus the resolution to your problem may help others.  I just don't to want to hijack the thread with 30 posts back and forth for a very specific problem like this one.

If anyone disagrees with me, feel free to object.

When you say you "extract" it, did you extract it from within the terminal, or using a GUI file archiver (like file roller)?  Are you able to navigate to the bipcoin directory from within a terminal, and list all of the files using "ls"?  Can you post the output of "ls -ald ./*" from within the bipcoin directory (don't include the quotation marks)?

The linux binaries are 64-bit binaries.  Are you by chance running 32-bit OS?  Do you get an error message when you execute it?  As mentioned before, if any of the files end with ".exe" you have the wrong download.

Some processors throttle themselves when they reach a certain temperature for safety.  Could be you actually get better performance with fewer threads because you are not running hot enough to throttle.

MurderDawg, I've had a couple that failed verification for one reason or another.  You could check for this by searching your bipcoind.log for the phrase "failed verification".

In Windows, from a dos prompt: find /i "failed verification" bipcoind.log

In Linux: grep -i 'failed verification' bipcoind.log

Sounds good, thanks.

I just got another block that failed verification.  I've only gotten 2 blocks in the last 8 hours and both failed verification, even though my block chain appears to match the block chain explorer.  My current hash rate is 110. and bc_height is 4952.

The error is:

Block <f84bad72d6b0bf2009cd7cb53f698e419e2277890fff29fe91a8b2720c6e33e0> is too big: 22609 bytes, exptected no more than 22409 bytes
17:00:11.596619 ERROR mined block failed verification

I started mining a couple days ago when difficulty was 2M, with a hash rate of about 120.  I was getting coins every couple of hours.  Now the difficulty is about 500K and I haven't gotten anything since 9am PST, except that I got some blocks a couple minutes ago that failed verification.  Is something wrong?  The top of my block chain matches the height and hash of the top of the chain shown at the block explorer here:

http://democats.org/blockchain/?name=bipcoin