8800GT is newer and probably more efficient than the beast that is the 8800GTX! The GTX is far more powerful, but dude we're talking about a $10 difference on a 6 year old card.
|
|
|
I say keep the advertising internal, or put up Operation Fabulous banners since the advertisers will be paying per-day and the amount of clicks received will be irrelevant and the advertisers will not be paying for clicks from people for no reason. You will also likely earn a lot more BTC this way, because once the traffic starts to build up, people will bid, and you will earn BTC all day whether people click or not.
|
|
|
congrats on the quick sale!
|
|
|
the main page just contains a link to gblse.com? very professional!
|
|
|
kk I followed you. man, you got a long ways to go!
@bitcointrading
|
|
|
to edit the pool file: now the whole file has # in front of all the lines except the last one. the # means a line is commented and is ignored, so essentially there will be 1 line at the end without a #, that's the line we need to edit. You can add more pools for failover and whatnot, but for a basic installation it will be just a single URL. make it something like this: http://username:password@api.bitcoin.cz:8332/
|
|
|
betco.in moved to offline due to hack
|
|
|
I must say that I would still love one of these, but now with some pretty reliable guaranteed funds payback borrowers - say paying the least risk 2% per week, then the effective holding cost of these beauts is their own bitcoin value in one year 1,040 BTC uncompounded, but for absolute cold storage then still hits the sweet spot especially if it's to be generational, lets hope that their collectable/rarity value increases eventually at the same 100% or so per year that putting the coins out to work would do here's what I really, really wants though - one of these, but made out of a 1,000 BTC Casascius coin http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=270980470752would need some different tech to house the private key inside (or somewhere) tamper proof & drool proof, but would be sweet edit, actually maybe on the inside of the backside of the coin protected by hologram same as now would work simply & fine That's a wicked idea, that would be the most 1337 watch on earth!
|
|
|
25 GH/s is a drop in the bucket and you would need a lot of them to protect us from a theoretical 51% attack.
|
|
|
do you have a lot of stock of these?
|
|
|
The 2900 BTC debt, that's a substantial amount, when the site incurred the debt, was the USD trading price at a much lower amount?
|
|
|
Thanks for the list!
no prob!
|
|
|
I tell bitcoin to EVERY person I see, even random strangers. I know people who run radio shows on a popular radio station here in town and I might get some airtime to talk about bitcoin, i'd say its a 99% chance that's going down. I also am related to TWO people who have a TV show on BNN doing finances and whatnot, it's called 'Market Call', a zillion people watch it and they're my 2nd cousins! I'm trying to get ahold of them so they can mention bitcoin on BNN!!!
|
|
|
edit: the VGX has only 786 cuda cores total across all 4 GPUs? SAD! no longer excited. It seems more reasonable to me that it would be 768 core per each of the GPU. Yeah but it says GPU Specifications Number of GPUs 4 Total NVIDIA CUDAŽ Cores 768 Shader Perf (TFLOPS) 1.3 Power (W) 150 So.. Total CUDA cores = 768? What a rip!
|
|
|
As a side note to McLovin's fix - you can accomplish the same thing by right clicking on the network icon and set your static IP in the GUI. Works fine for me on the machines that experience this problem. Hmm. From experience, if you have a system running bamt and the monitor is connected and then you disconnect it, you have a pretty good chance that it will stop reporting and spit out the magic cookie/Xauthority errors. I find that doing a fresh bamt w/no monitor connected and then SSHing into the box is the absolute best way. Thus anything in the GUI is not accessible. Hi.
I finally managed to get my 7970 working on BAMT with cgminer. Upgraded to SDK 2.6 and installed the 8.921 ATI driver (wich is the only one that doesn't cause HW errors with cgminer at least) Installed also the last cgminer (2.4.1 now) and I get around 715 Mh/s.
All good except the damn high CPU usage bug, so I have to use GPU_USE_SYNC_OBJECTS=1 to get rid of it. The thing is I don't know (yes, noob) how to correctly integrate this in BAMT scripts. I wandered desperately through those scripts and finally added in /opt/bamt/common.pl after line 955 (cgminer section): $ENV{GPU_USE_SYNC_OBJECTS} = "1";
Seems to be working, the CPU usage is back to normal but I have no idea if this is the proper way to to do it. Can someone point me to the correct way?
Thanks
We got two 7970s mining with bamt on one machine, been running stable for weeks now. We were able to get CPU usage to be 60-80%, and it also reports to the other machines running mgpumon using the local API... BUT mining has to be started manually from the /opt/miners/cgminer folder.
|
|
|
|