To move all your BTC to a new wallet with one computer:

A. Backup and remove original wallet:
 1. Close bitcoin, verify it's not running.
 2. Have lots of backups, such as making a 7-zip of the whole bitcoin data directory.
 3. Move your existing wallet.dat out of the bitcoin data directory to a new location bitcoin/wallet1.

B. Create a new blank wallet:
 1. Restart bitcoin, it will think for a while and silently create a new wallet without complaining that your old one is missing.
 2. Record the first bitcoin address of the new wallet (notepad cut and paste, etc)

C. Send old coins to new address:
 1. Close bitcoin, verify it's not running.
 2. Move the new empty wallet.dat to a new location bitcoin/wallet2.
 3. Copy the original wallet back from bitcoin/wallet1 to the main bitcoin directory
 4. Launch bitcoin, send your new address a small amount of test coins (.01 BTC + fee).
 5. Close bitcoin, and re-backup your old wallet to bitcoin/wallet1 (not always necessary, but best practice, since you could have exhausted your private key pool and sending could have created a new one.)

D. Verify they got there:
 1. Copy the new wallet from bitcoin/wallet2 to the main bitcoin directory
 2. Launch bitcoin
 3. See that your test transfer appears after a few blocks and it gets eventually confirmed.

Repeat C and D for all your bitcoins, shred all old backup files to avoid confusion and backup your new wallet.dat encrypted. If you send money and it doesn't show up right in the new wallet using this technique, you can run bitcoin -rescan to rescan the blockchain for missing transactions; that's only a local problem though, the bitcoin network knows the new address got the bitcoins sent to it.

The first thing to do is back up everything in you bitcoin data directory. Backup the backups.

Ensure you are running the mainline bitcoin client .23 or .24.

First try the bitcoin -rescan option to rescan the block chain for transactions. See if this resolves your problems.

Secondly, your data directory may have corrupted blockchain or other files, the easiest way to rectify this is to remove all files except the wallet.dat, and download a nightly version of the the blockchain from http://eu1.bitcoincharts.com/blockchain/ and place this in the bitcoin data directory and launch bitcoin again and let it update to the latest block. If that doesn't fix your problem, try the -rescan option with this new blockchain.

If that fails, your wallet.dat is probably corrupted, restore from a recent backup, or use repair utilities on it.

Same problems here, there are no docs about the build versions at all. To get a suitable environment I finally installed:
Python 2.6.6
Python setuptools-0.6c12dev-r85381
Python 2.6 Base-11.5.23
Python 2.6 numpy-1.6.0
Python 2.6 scipy-0.7.1
Python 2.6 Twisted-10.1.0
Python 2.6 zope.interface-3.6.3

Most of those are pre-built here: http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy

Then I installed boost libraries 1.42 (timedate, python, threads; multithreaded dll), and copied the boost_date_time-vc90-mt-1_42.dll, boost_python-vc90-mt-1_42.dll, and boost_thread-vc90-mt-1_42.dll to the windows\system32 directory

added Python to the path, added a HOME environment variable.

Installed full ATI Stream SDK 2.4.

I then got the pyOpenCL 0.92 (the last version that doesn't complain about kernels using deprecated functions), and built and installed it using MSVC9. Multiple fails to come up with this as my siteconf.py:

BOOST_INC_DIR = [r'C:\Program Files\boost\boost_1_42']
BOOST_LIB_DIR = [r'C:\Program Files\boost\boost_1_42\lib']
BOOST_COMPILER = 'msvc'
BOOST_PYTHON_LIBNAME = ['boost_python-vc90-mt-1_42']
USE_SHIPPED_BOOST = False
CL_TRACE = False
CL_ENABLE_GL = False
CL_INC_DIR = [r'C:\Program Files\AMD APP\include']
CL_LIB_DIR = [r'C:\Program Files\AMD APP\lib\x86']
CL_LIBNAME = ['OpenCL']
CXXFLAGS = ['/EHsc', '/DBOOST_PYTHON_NO_PY_SIGNATURES']
LDFLAGS = ['/FORCE']

Or something like that... with all that, now I can run phoenix source.

 A step-by-step 'how to install python for phoenix.exe' would be many many steps, it would be nice if Jedi95 would just document building, especially how he makes the EXE since I have yet to duplicate the binary he distributes.

I have bad news to report - phatk 2.1 sends bad shares.

On pool mining hardware that consistently gets <2% rejects (and those only are stales within 5 seconds of a new block), I have only changed the phatk kernel:

2956/190 = 6.0% rejected
1944/290 = 13.0% rejected
2656/116 = 4.2% rejected
2615/184 = 6.6% rejected

Here's a log from this new kernel showing the atypical random rejects:
(old links)

We can see on the result line that the hashes are bad, by not starting with 00000000:
[03/08/2011 22:17:48] Result c877f46db0d6ab44... rejected

These do not give an "OpenCL error, hardware problem?", or a "didn't meet minimum difficulty, not sending", they are sent and rejected.

For an improvement in hashrate of 1% (333.58->336.53 typical) over Diapolo's 07-17 kernel, I get a 5% increase in rejects. I will have to revert. This is on WinXP/5830/11.6/SDK2.4 running phoenix.py 1.50 unmodified source on Python 2.6.6/numpy-1.6.0/... Two miner instances per GPU.

Command line is:
python phoenix.py -v -u http://xxx/ -k phatk VECTORS AGGRESSION=13 BFI_INT WORKSIZE=256 PLATFORM=0 DEVICE=0

I say more like:

How dare Dwolla randomly lock accounts and funds, and then demand more information that they never suggested was required. This is ripping a page from the PayPal playbook. Next they will start randomly locking accounts and then demanding proof that you shipped an item or demand invoices and business licenses and SSN cards to see how much money they can keep? Maybe they can pull money back out of your account with no notification, while revising their web page and rewriting history where they stated that wouldn't happen. Oh, they already do that. Changing the terms I agreed to, terms that had no provision for change in them? Already did that.

The sign-up page and terms and conditions still have no indication that they will require more information from you, conveniently when you have steal-able funds in the account. There is also no indication of federal pressure brought to bear on them to comply with anti-money-laundering laws and to randomly lock Islamic sounding account names, or that they even looked into their responsibility to comply with money exchange laws before opening and won't end up in Federal pound-me-in-the-ass prison with the e-gold guy with all our assets seized.

How about I take my security seriously. Dwolla has not stated what they plan on doing with my photo ID, keeping it on their servers forever for rogue employees to copy to USB drives, for hackers to steal and sell to Ukrainian identity thieves, or sending it to the IRS or the Secret Service?

Got one I'll never use, $6 USD PayPal (preferred, I need to make a PayPal donation to another forum, you can see my high seller reputation when sending payment) or .6 BTC. That's with me just putting the adapter in an envelope and mailed to US. PM me.

If you use a miner based on poclbm/phatk (Phoenix/Guiminer), you can set the GPU aggression very low with a command line option. Aggression 2 instead of 12 will put out 20mhash instead of 30mhash.

If you use a CPU miner on a multi-core processor, you can set the CPU affinity for just some of the cores, and can set it to low or idle priority so it doesn't slow down your system.

Either the CPU or the nVidia card are very inefficient; you will get about 30mhash/s instead of the 300-400mhash/s that a $130-$200 ATI 5xxx GPU would, while using more electricity than the BTC you earn.

A real mybitcoin post could/would be signed: http://pgp.mit.edu:11371/pks/lookup?search=mybitcoin

Deleted wallets would also mean copied and emptied wallets...

Sorry for the confusion, that's regarding the 2.0 phatk that came this weekend.

I tried the new kernel with phoenix/11.6/2.4/Win7/5830, and gave it lots of different command line options. I could only get it to be 'miner idle' five times a second, or 5Ghash/s with no share solves.

That's a pretty sweet application, good info! I can put my media center AthlonX2 to 4.0x instead of 6.5x for cool 'n quiet, plus shave off some volts.

Here's my mining Sempron undervolted, it's probably drawing about 1 watt at 600MHz @ .0784v (considering it's max power is 40W at 2700MHz/1.3v):

The code that creates this error is in the phatk init file:

                    if not hash.endswith('\x00\x00\x00\x00'):
                        self.interface.error('Unusual behavior from OpenCL. '
                            'Hardware problem?')

The error is reported if the hash returned by OpenCL does not begin with zeros. The error means that the hash-checking done in OpenCL thought the hash was valid and returned it, but this simple sanity check showed it was invalid. Either the hash-checking math was done wrong in OpenCL (saying that a bad hash was good, and perhaps silently discarding good hashes), or the correct hash is being corrupted when it is returned back to phatk core. It seems like something about the 07-17 kernel causes more errors on high overclock cards (perhaps running a different shader instruction that in silicon that is less tolerant to overclock?), errors that were not produced before at the same clock speed, which reduces overclockability.

The 11.6b driver reintroduces the CPU race bug.

As the creator, let me guess how early you made your bet...

2. You are doing it correctly (you don't need the "start" though). Namecoin is not available in client form, just a daemon, and that it is running. If you have run it, it created a wallet and an address for you. You need to leave it running so it can get the entire blockchain up to the current block number.

1. You need to open a second command prompt window to issue RPC commands to the running daemon. A typical command would be "namecoind.exe help" or "namecoind.exe getblocknumber". Another command might be "namecoind.exe getaddressesbyaccount 0".

3. If you are using a solo miner to connect to your local namecoind, it's status should change to 1 accepted, 0 rejected, after hours or weeks of mining. You can also issue the command "namecoind.exe getbalance" and see if it is 50.0000000 instead of 0.00000000. If you are pool mining, the pool balance should slowly increase as they find blocks for which you have contributed.

You can also remove all the existing ATI software, and do a fresh "display driver only" install of the WHQL Catalyst 11.6 driver (which does include OpenCL despite it's name). This version does not have a CPU problem, and I have 2 miners running at 0-1% CPU.

You should post in a rpcminer-cuda or guiminer thread, your question has nothing to do with this thread's topic.

Actually, since the service is case insensitive, that makes it just Base35 you'd spam. Every 1+3 char to 1+6 char could be blasted for 18.4 BTC plus a BTC in fees to get them picked up,  and you can check the blockchain for them first and save maybe 25% too.. BTW, no need to validate a private key, just add a correct checksum to your public one (plus add your advertising message or obscenity if you suck). Now the shortest firstbits you could get would be eight digits, like 1Ef3oe2K, and for that you might as well be emailing your whole payment address.

It sounds more like it is just a way to spam that service up for the few that find it useful. For 7 BTC I can send a block with outputs to every 3-5 character address, so now you have to remember six.

People that 'register' these relatively simple vanity bitcoin addresses by sending them some coins are completely silly. What do they think they have? Even if you have found 1ULT1MATEADDRESSzUYmbsNX3d3a, there are still 55,000,000,000,000,000,000,000,000,000,000 other addresses with that same prefix to be had. Do they think they are somehow 'protecting' them by sending money to show everyone they got it, or that it is needed because generating the exact same address is computationally feasible before the end of the universe? I'm not going to be buying them; I'm not sending my money to an address that anyone else knows the private key of.

Oh, and vanitygen seems to work!