No. There's definitely something fishy going on with your connection. The certificate for bitcoin.it is valid from 2010-12-15 17:29:24 GMT to 2012-12-16 21:21:39 GMT. It is currently perfectly valid. Since your clock is correctly set, you should not be getting this error. It is possible an attacker is trying to trick you with a fake certificate (though if that's the case, you'd expect them not to put a timestamp from the future on it  ) The real certificate has the following fingerprints: SHA1: 1bdbaa0ac1c3cc464d8edad56870c401dc035ee7MD5: fa03fccec71a3d95f7bc3a858a0e5a6cWhat are the fingerprints of the certificate you're getting? |
|
|
|
If you suspect that the database index is corrupt (blkindex.dat in the bitcoin data directory), it can be deleted, the blockchain files blk0001.dat and blk0002.dat moved out of the data directory (like to the root of C: drive) and then the blocks can be re-imported from these original blockchain files:
bitcoin-qt -loadblock=c:\blk0001.dat -loadblock=c:\blk0002.dat
Thanks. |
|
|
|
However, there was an error writing the blkindex.dat file; likely this file was corrupted, there is a disk CRC write error/bad block, or another Bitcoin is concurrently attempting to access it, etc. The error is unanticipated/unhandled by the code.
Huh. So any kind of failure to write to a critical file causes the client to either crash or hang while leaving the database in an inconsistent state without even displaying an error message? That seems like a pretty big oversight to me.  In this case, rebuilding the index, or restoring/redownloading the blockchain is the remedy.
For future reference, how exactly does one rebuild the index? I don't see any command-line options for doing this. |
|
|
|
|
The blockchain is currently 3.5GB, so there's nothing wrong with your file sizes, and there's probably nothing wrong with your configuration if it's working at all (which it is). Though it certainly shouldn't have taken you several weeks. Usually it should take anywhere from a several hours to a few days, depending on your system. What sort of Internet connection do you have? Were you connected continuously during those weeks, or just (eg) a few hours per day? Also, Bitcoin has to verify blocks as well as download them, so your CPU and hard drive speed are a factor as well.
|
|
|
|
but i saw something about a guy who was raided because they thought he was growing marijuana but instead was "mining" bitcoins.
Welcome, Annie. Just to clear up a possible misconception, bitcoin mining is by no means a "get-rich-quick" scheme or a way to make "free" money with your computer. That guy you mentioned was raided because bitcoin mining (on the scale necessary to earn a living from it) consumes a very large amount of electricity. Regardless of the scale of your intended operation, unless you have specialised (and expensive) equipment, the increased electricity cost will almost certainly exceed the value of the bitcoins you are able to mine. It is a highly competitive industry, and only the most efficient miners are able to make a profit from it. I'm not saying you shouldn't mine, just don't be surprised or disappointed if you find that you're unable to make any money from it. |
|
|
|
First, the Casascius 10 BTC Silver Round ( http://casascius.appspot.com/group?type=5) has 3 circles of seemingly random 0s and 1s around it (visible even w/o microscope ;-) ). Is it really random, or does this sequence of bits carry any hidden message/meaning (byte code, morse code or whatever)? It would surprise me if these carefully and well-designed coins did not carry any meaning in this bit sequence... It's ASCII for "Bitcoin: an idea too big to fail". The BTC25 coin has a similar message that reads "You asked for change, we gave you coins". |
|
|
|
Bitcoin 0.7.0 just crashes with no error message and nothing in debug.log, leading to 22DbRunRecoveryException fun. 
Bitcoin 0.7.1 does not crash, instead it just gets stuck while spewing a ton of errors to debug.log:received block 00000000000002b0fa88
connection timeout
trying connection 109.123.33.243:8333 lastseen=20.2hrs
ERROR: SetBestChain() : TxnCommit failed
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
getblocks -1 to 00000000000000000000 limit 500
received block 000000000000004055b1
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004e815d6
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
received block 00000000000004086917
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
trying connection 98.197.66.251:8333 lastseen=32.4hrs
received block 000000000000021f176d
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: FetchInputs() : faa4a7ffaa mempool Tx prev not found 17ffdc0de5
stored orphan tx faa4a7ffaa (mapsz 1)
received block 00000000000001e2fc4f
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002168e46
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000013d86b8
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004df9d9b
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
received block 00000000000000ca2211
trying connection 206.214.221.145:8333 lastseen=19.6hrs
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000003a0e50d
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000049a671d
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004d162f0
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: FetchInputs() : 469a200091 mempool Tx prev not found f88ad4fe16
stored orphan tx 469a200091 (mapsz 2)
connection timeout
received block 00000000000002e19724
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
trying connection 58.59.138.210:8333 lastseen=12.1hrs
ERROR: FetchInputs() : 3062710bb1 mempool Tx prev not found 337837ef71
stored orphan tx 3062710bb1 (mapsz 3)
connection timeout
trying connection 90.213.200.159:8333 lastseen=39.7hrs
received block 00000000000000e8cdb2
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000040cc0d5
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000001a5ff5
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002470854
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004a42633
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004e9e3f2
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002559d98
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000003eee1d3
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: FetchInputs() : 7578d33c75 mempool Tx prev not found 996dbc5b74
stored orphan tx 7578d33c75 (mapsz 4)
ERROR: FetchInputs() : 5189182976 mempool Tx prev not found cc94b2a774
stored orphan tx 5189182976 (mapsz 5)
connection timeout
trying connection 83.31.49.235:8333 lastseen=107.1hrs
received block 00000000000004c20256
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
received block 00000000000000d0c8b6
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000001914137
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000015d4742
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
trying connection 50.73.45.241:8333 lastseen=25.7hrs
received block 000000000000024c8527
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000025fd8c7
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 74.138.246.128:8333 lastseen=8.5hrs
ERROR: FetchInputs() : dc303332d5 mempool Tx prev not found 7578d33c75
stored orphan tx dc303332d5 (mapsz 6)
connection timeout
trying connection 217.9.91.118:8333 lastseen=36.5hrs
Added 536 addresses from 67.170.161.21: 729 tried, 12522 new
received block 00000000000004ceb4ae
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 109.86.14.23:8333 lastseen=6.9hrs
received block 00000000000004585e25
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 2.230.36.153:8333 lastseen=37.9hrs
received block 0000000000000284a36c
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 24.178.88.230:8333 lastseen=9.3hrs
ERROR: FetchInputs() : 5b67be65e9 mempool Tx prev not found 8e890d7104
stored orphan tx 5b67be65e9 (mapsz 7)
ERROR: FetchInputs() : b1f58cba76 mempool Tx prev not found b05cfb03f2
stored orphan tx b1f58cba76 (mapsz 8)
connection timeout
trying connection 195.202.218.108:8333 lastseen=23.4hrs
connection timeout
trying connection 93.81.254.9:8333 lastseen=10.8hrs
ERROR: FetchInputs() : 18c5195d6b mempool Tx prev not found 52bfcc2590
stored orphan tx 18c5195d6b (mapsz 9)
ERROR: FetchInputs() : 354e163bca mempool Tx prev not found 9fdfcc266e
stored orphan tx 354e163bca (mapsz 10)
received block 00000000000001ed301a
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004e0b5da
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 0000000000000497e056
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002b3ba2c
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Added 570 addresses from 67.170.161.21: 729 tried, 12557 new
connection timeout
trying connection 81.84.211.237:8333 lastseen=27.0hrs
received block 0000000000000188994a
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 72.53.3.229:8333 lastseen=45.7hrs
ERROR: CAddrman::Write() : open failed
Flushed 13286 addresses to peers.dat 24ms
received block 000000000000047a390d
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 190.246.43.47:8333 lastseen=37.0hrs
received block 00000000000001df9f9f
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Added 7 addresses from ::: 729 tried, 12559 new
13 addresses found from DNS seeds
ThreadDNSAddressSeed exited
received block 000000000000018e4a82
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000026168ea
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000000888968
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000001064014
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002e26a33
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000000cd9ded
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 217.147.162.222:8333 lastseen=11.2hrs
received block 000000000000012b7d43
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000002b5e089
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Added 114 addresses from 95.172.9.82: 729 tried, 12567 new
Added 1 addresses from 95.172.9.82: 729 tried, 12567 new
connection timeout
trying connection 70.162.76.144:8333 lastseen=15.0hrs
connected 70.162.76.144:8333
send version message: version 60002, blocks=206457, us=xxx.xxx.xxx.xxx:8333, them=70.162.76.144:8333, peer=70.162.76.144:8333
received block 000000000000014f4645
ProcessBlock: ORPHAN BLOCK, prev=000000000000024c3771
ERROR: FetchInputs() : 131ea92385 mempool Tx prev not found 3443ab8753
stored orphan tx 131ea92385 (mapsz 11)
ERROR: FetchInputs() : c92bec7498 mempool Tx prev not found ed8d2cec6f
stored orphan tx c92bec7498 (mapsz 12)
ERROR: FetchInputs() : 8b6e65ed5a mempool Tx prev not found dddc000e08
stored orphan tx 8b6e65ed5a (mapsz 13)
ERROR: FetchInputs() : ce701db2a0 mempool Tx prev not found ecef494aad
stored orphan tx ce701db2a0 (mapsz 14)
ERROR: FetchInputs() : 03b972ac88 mempool Tx prev not found eaf11c833e
stored orphan tx 03b972ac88 (mapsz 15)
ERROR: FetchInputs() : a277e3e29b mempool Tx prev not found 55678a46e9
stored orphan tx a277e3e29b (mapsz 16)
ERROR: FetchInputs() : ef07e48ee5 mempool Tx prev not found 66b40a0ad4
stored orphan tx ef07e48ee5 (mapsz 17)
ERROR: FetchInputs() : 6adc8799db mempool Tx prev not found 0dbc3a8bd7
stored orphan tx 6adc8799db (mapsz 18)
ERROR: FetchInputs() : 5ba6b6e6ce mempool Tx prev not found f1469cbbba
stored orphan tx 5ba6b6e6ce (mapsz 19)
ERROR: FetchInputs() : be09a2d11c mempool Tx prev not found 6adc8799db
stored orphan tx be09a2d11c (mapsz 20)
ERROR: FetchInputs() : 68e01c7d0b mempool Tx prev not found 3366845f26
stored orphan tx 68e01c7d0b (mapsz 21)
ERROR: FetchInputs() : 7cb74aad6a mempool Tx prev not found 3fc244e381
stored orphan tx 7cb74aad6a (mapsz 22)
trying connection 82.58.25.9:8333 lastseen=18.2hrs
Added time data, samples 5, offset -265 (-4 minutes)
nTimeOffset = -255 (-4 minutes)
receive version message: version 60001, blocks=206541, us=xxx.xxx.xxx.xxx:35887, them=70.162.76.144:8333, peer=70.162.76.144:8333
received block 000000000000021139f8
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: FetchInputs() : 605f931912 mempool Tx prev not found dcdeecf4e0
stored orphan tx 605f931912 (mapsz 23)
connection timeout
trying connection 76.85.165.113:8333 lastseen=30.0hrs
connect() failed after select(): No route to host
Added 530 addresses from 70.162.76.144: 729 tried, 12576 new
trying connection 65.185.46.38:8333 lastseen=43.4hrs
Added 523 addresses from 70.162.76.144: 729 tried, 12623 new
Added 251 addresses from 70.162.76.144: 729 tried, 12639 new
connection timeout
trying connection 84.110.216.9:8333 lastseen=11.5hrs
ERROR: FetchInputs() : d8deba3120 mempool Tx prev not found 5ba6b6e6ce
stored orphan tx d8deba3120 (mapsz 24)
ERROR: FetchInputs() : a6ca346571 mempool Tx prev not found 021996e8fd
stored orphan tx a6ca346571 (mapsz 25)
connection timeout
trying connection 78.36.70.200:8333 lastseen=14.3hrs It seems everything just goes horribly wrong somehow with block 206548. I've tried several times (from old backups of the blockchain) with both versions and it's always the same block. There's nothing unusual about that block, is there? In any case, is it possible to fix it without downloading the whole blockchain again? (Though I doubt that would help anyway unless my blockchain got corrupted a while ago and it's only just causing an issue now for some reason.)EDIT: The problem seems to have fixed itself. Bitcoin 0.7.0 (I gave up on trying to get 0.7.1 to work) is now fully synchronised after restoring a backup of the blockchain (the same backup which kept crashing on block 206548 earlier). Though I'm still curious what caused the problem in the first place. What do those errors mean? |
|
|
|
Wow, what if you were that guy? Spend 10.000 BTC on a pizza, while now you would have a real nice savings account!
If I were that guy, I wouldn't have spent the entire contents of my Bitcoin wallet on a couple of pizzas. He probably had something like BTC100,000 more and is now laughing at everyone who thinks it was stupid of him to buy those expensive pizzas.  |
|
|
|
"So I recently purchased this amazing little program which gives me a slow but steady trickle of bitcoins."...
It's a scam, not a miner. Not that it can't be both, ie, an attempt to get you to pay money for a miner that you could have downloaded for free. But it's probably just a scam. |
|
|
|
Could a google or facebook or paypal get a competing digital currency going, then use their computing power to wipe out BC value with 51% computing power?
The so called 51% attack (which is actually the >50% attack) doesn't require a competing currency (just the hardware hashing power) - what such an attack potentially can do is either "undo" some tx's or refuse any new tx's (the latter being perhaps of more concern). In either case if such an attack were to be carried out it certainly would be an issue for Bitcoin (please also note the that Bitcoin is one word not two) although not necessarily fatal (ideas such as "proof of stake" are already being trialled in other alts). Also note that the cost (in terms of hardware) to carry out such an attack would be rather high. There is one more thing to note about a 51% attack. Specifically, no company (not even Bitcoin's competitors) has any logical reason to do any such thing. Assuming they did have sufficient computing power (which is a big if), they wouldn't need to attack Bitcoin, as they could use their computing power to produce more bitcoins than everyone else entirely legitimately. Remember, companies are all about profit, and they're not going to invest in a huge amount of computing power to pull of a crazy (and highly public) attack against their competitors when they could just as easily use that computing power to make a buttload of money legally. The incentive structure of Bitcoin is specifically designed so that anyone who has the power to attack Bitcoin will find it far more profitable not to do so. Any attack will come not from a large company, but from an extremely well-funded entity that is willing to throw away huge amounts of money just to make a point. Like a government, for example.  |
|
|
|
That's freaking awesome. I am aware the museum was interested in the coins and sent some without giving it a second thought but am super flattered to see they are being displayed.
Are they loaded? I hope you are not thinking what I think your thinking...  I hope he is thinking what I think you think he's thinking. It'd be good publicity. |
|
|
|
I have one little suggestion. Would it be possible to change the red wording “(out of sync)” to something a little less concerning like “updating please wait”? I have been using the client for a long time and it alarmed me the first time I saw it because for a moment I thought something was wrong. I can only imagine what new users think when they see it. Thanks
As far as I know, it's supposed to be alarming. There were recently a lot of newbies complaining "Help! It's not working! I just bought coins and they're not showing up!! Where are they?! Oh, by the way, it hasn't finished synchronising yet, is that important?" *collective facepalming* Hopefully this way newbies will get the idea that they shouldn't even try to use the client until it is synchronised, and have some idea of what the problem might be if something goes wrong as a result. |
|
|
|
I've read on the wiki that this is meant to take long and it could even take up to a day to sync with the network however I've noticed in the past hours that I've been watching it that sometimes progress skips back. What I mean is at some point there were about 9500 blocks left to load and suddenly it skipped back to over 10000. Is this normal? Should I just wait it out and stop starting at it?
Yes, this is normal. What is actually happening when the client is synchronising with the network is it is downloading and verifying the complete history of every transaction that has ever taken place on the Bitcoin network. Naturally, this history is constantly growing as new transactions are made, which causes your progress to slide back every now and again. But don't worry; unless you have an extremely slow connection, the client will be able to keep up and will eventually finish synchronising. Also, I haven't seen any clear answer around, but will I have to wait long times every time I run the client?
No. When the client synchronises with the network, it only downloads and verifies blocks of transaction history that it doesn't already have. When you start the client after it has fully synchronised previously, this means it only needs to download new transactions that occurred since the last time you closed it. This also means that if you close the client before it has finished synchronising, it will pick up where it left off the next time you start it. It never has to start from scratch again unless something goes horribly wrong, eg, the file gets corrupted or something. And lastly, would I be better off using an online alternative or a more lightweight client? Is it worth sacrificing encryption and security for a faster load time?
Probably not, as long as you can spare the bandwidth. The extremely long synchronisation time only happens the very first time you run it, after that it shouldn't be an issue. |
|
|
|
Two tries, I wrote a message, Then hit encrypt, Chose your key, And when I try to decrypt it it fails
I was able to successfully decrypt the first message, but the second one is encrypted with a key I don't recognise (key ID: 5B911638F2043B3D). Naturally you won't be able to decrypt it, as you don't have my private key (it would be a pretty major screw-up on my part if you did). When you encrypt a message with somebody's public key, only the person with the corresponding private key will be able to decrypt it. Nobody else can, not even the person who originally composed the message (unless they made a copy of the message before encrypting it). So, whatever you did with the first message, you did it right. Don't know how you screwed up the second message, though. |
|
|
|
I assume you couldnt decrypt it because of what i did x3 This is why i asked for help :3
Yeah, if a message is encrypted with your own public key, nobody other than yourself will be able to decrypt it. That's kind of the whole point of encryption, after all.  To send messages to other people, you need to encrypt it with their public key. I get "GPGME library has returned an unexpected error, The error was : General Error" when trying to decrypt the message in the link
There's no encrypted message in that link. It's a public key. Save it, then in GPA click Import and open the file. (Though I'm not sure why GPA didn't do that automatically, as GPG will automatically detect what type of file it's being fed and act accordingly, unless you explicitly tell it to try to do something else - how exactly did you try to open that file?) You can then use this public key to send encrypted messages to me. |
|
|
|
C1 is my favorite! If it can be made more gold-colored like C2 is so the color in center does not look like a pizza chart it would be awesome! Maybe something to do with 256color restriction in ICO files but seriously I have not paid much attention to ICO format specifications since Windows98. Can I get the "source" files for this icon so I can fix it for myself?
Source files? For an image? What the Hell kind of image editor are you using that doesn't support images in binary formats? The Microsoft Icon format in particular is well supported by all decent image editors, being one of the standard web image formats (in addition to GIF, PNG, and JPEG). You probably made the image with Photoshop or some other advanced image editor and then converted to lower resolution ICO format. I want that PSD file (the source) so I can fine tune the image to my taste and share the results. I probably didn't even create these icons in the first place. But what exactly do you want to do to it that can't be done with the image in its current format?  |
|
|
|
C1 is my favorite! If it can be made more gold-colored like C2 is so the color in center does not look like a pizza chart it would be awesome! Maybe something to do with 256color restriction in ICO files but seriously I have not paid much attention to ICO format specifications since Windows98. Can I get the "source" files for this icon so I can fix it for myself?
Source files? For an image? What the Hell kind of image editor are you using that doesn't support images in binary formats? The Microsoft Icon format in particular is well supported by all decent image editors, being one of the standard web image formats (in addition to GIF, PNG, and JPEG). |
|
|
|
-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.17 (MingW32)
hQEMAyj0GJmKDgINAQf/VIawpjDjsyUiocjdNyhXpC2RG0dc38X5dWNxIyiudWrS
iDddSayesSbjlMlyp1ee3SP2w5+hOd4eRZPPXNJn9gMOGkZKC0BBMXGmT/WUCw4R
l/7RX1+XauAA8uw2hQBvu99kO6ijqw4Ywr1AAk7JmnLfBKmTpDqLgYjyKzxXeHWi
gnJ/1jjyjiNbBkCxEejAiUKiQ9Jpd58JWNnm37fEgyFLjQqhAKZDeVJMyjlZtjvV
SgLZJTyjwy+ku79UP4x7S11gvpcw/MPb+2jUCdYVXG3/FpQAJpJjc8kJhdyUiaRQ
j+UWBBMfC/Uv9v1AUa8dz13xpkg20LWzgjMwbCl2OdLBJwGpx/bt1m0oE1/jaxt/
SCMLQQzytr5EdMBSGiVFj8Jba48yEwCmgxkaESo46mTyd4Sw8Fxmf+ldPfzS4zDN
apevIDJrySjezkwYJgO2SnUUnF8FrV5fD3KsLu1KjKMwJtv3EY6aybdP4uWBBKj+
/CBgWabglc3JmN3JzhRml0cyb92USRkN1FHy13U+PbNBNWAewUDa0NDgtb+EqVYR
UJV0eyjm4gmBeUME7GaTslggiGcuJl5EncNfhw/3bLd+Y+3o6LfkBjCSGo8PZpAI
bGHrIn+p9YC86RTpI07sx7DLZpzYVdT8dyPtVvzp4bN1XcxXRsUR1R0IxtDDVvl6
NrGxVdZWDacO+yXssUnQylpP4k2QesBDSrTHC0EqaRpjrEzg04dES3AUpiP1+nb6
CqNEX1QoYKb+Q+fhHqwyIWnorkyhERkqrEwApbgyJbS7l4V41X9ZVf9+a0INUwmq
6wrv/2HiA6+vwXVwmaSixf1FkiHm0DJQgr1Rfl23jJbx7pl5ZQ90ymub/eSeVoN2
qPRuHL0S4By4J7VsjshyLss3/CLbvkHzPnLqjCLWhm8lKfSQGwRd1W/gz/duRnQ2
K4ye1mNH0Utp55mQAV0J/U9t8C/KHBm1iHyFqguUvL3OQq6pDy73qW8=
=Eq6y
-----END PGP MESSAGE-----
Uh, it might be more helpful if you tried encrypting a message to my public key, instead of your own. |
|
|
|
|
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.10 (GNU/Linux)
hQEMAyj0GJmKDgINAQgAjhW5QHJkZpFXys38ftXGmzXJV+rjP+QEZYdxjzdW6CAj
aTk3cBHU37xFfdOYtuTo+hntrw8tMt2MJkKgcG+vwLYkGUrYhGUykqRUGRRegX/+
/Jhc5A82iIM337Ti7SoSlKUhzMT8AeIQG49Qh6P9i9lZDtoAQl8RVWvdYsaCBHvJ
o0Ofu4/JBpvUNHhNZD78VBty5EAoIxmIdtths617l+Pios/ZUuXG3gK6feQOoQuH
Am6gSecqBel74P7xP4E7oTqB2Jgwg0yTJuLPNQnxHUf6jRUP4wkACxjwPFHib0iU
8xx1L75CFAOQd42sPHY1nzZz6wAsJAx1FBrPTV9U0NKUAXcMtyw/+5N2kFUvH+TR
7AYqPK5u+u9OpNh5nYXsUlL8U9UGStaCbwV2uC4h3a5Ffiy5mAT+nLSt0Vr2ZsY4
SB6n27p9cQiXuQ/OXrnKgR7d7vIAhZhvIkmx8BAAULzIwrFYfLHblc33x2gn+42Z
YYQBE8MdxI8KZ3ncijjUTf2lEvXmTYjkL9IxA719/8/VTZWF4g==
=hz9e
-----END PGP MESSAGE-----
|
|
|
|
I also contacted my ISP (Acanac) and they say they dont block ports and asked me telnet to their server on port 8333 and that failed so they are looking into it. Ill report back later what they say.
Well, unless they were running the client at that IP or had some other listener on 8333 your attempt to connect to them would fail. I'm pretty sure they wouldn't have asked him to try to telnet their server if they didn't actually have a telnet server listening on that port. Most ISPs aren't that incompetent. |
|
|
|
|
Show Posts
