|
You may have seen me say before that it's not worth it to buy the S1, but considering these prices, it might be now(sort of, still too many unknown factors).
I ordered my S1 and paid 0.893, it is Unpaid,Expired but it's due to blockchain.info, hopefully tomorrow it will be resolved.
|
|
|
|
|
A device that can only hash in a specific pool is definitely not worth $5000.
|
|
|
|
have you tried contacting the company about your findings?
Yup, and they claim that I only can use the machine with BTCGuild with the setting 1024/1THs as minimal diff. So this would be a limitation I can't accept. Now that's becoming interesting. When I look at the history in the bash, I see that the name "Bitmine" appears again and again. However, the machine itself is the one sold by the "LK Group" in China ( http://www.lketc.com). But the interface is produced by another company in Switzerland (roxas.ch). So I'll dig a bit deeper into this during the weekend. What would be interesting is if anybody who bought from LK in China has the same issue... That sounds like a bogus claim, cgminer doesn't care what pool it is, it passes the work to the driver which sends it to the ASIC, mine for another 30 minutes to an hour and if the speed is still 16gh/s, I smell a scam. |
|
|
|
Technobit devices are now supported on cgminer 4.0.0 on Windows. The reason it didn't work stemmed from a GCC extension feature which was broken under Windows. Took me a couple of days to figure out the problem and I reported to marto74 along with binaries. The only device that needed further patching to be detected under Windows was their very first device, the HEX16A1(the only available one I had for testing). I could provide binaries, but you don't know me so instead I link to 2GOOD's post with the binaries https://bitcointalk.org/index.php?topic=476970.msg5903836#msg5903836 but note that those binaries will work with devices >HEX16A1 since it doesn't feature my HEX16A1 patch. |
|
|
|
If they open sourced Windows XP then I'd be very happy but I doubt that will never happen.
I'm waiting for this too.  You're gonna have to wait another 20-30 years. |
|
|
|
|
I don't know VB, but I only see binaries in there, you could've slipped malicious code in any of them.
|
|
|
|
I don't believe you can send coins at all if your wallet is not connected to the internet. I could be wrong, could someone else concur?
You can't send without an internet connection, correct. However you can receive funds to an address without being connected to the internet. Later on, you just need to sync your wallet and you'd have all your funds displayed in the client. |
|
|
|
|
Yes, and it all coincided with Bruce Wagner disappearing all of a sudden. Hell, the last time he was online was almost a year ago. I know he had 25,000 bitcoins on mybitcoin which he "claims" he lost.
|
|
|
|
I like the title.  |
|
|
|
Yesterday evening I compiled again with the old MinGW version which ckolivas described in his readme. But not as recommended with "Download latest repository catalogs". I chose to take the old reposity catalogs. After that I patched and then compiled as described in the readme. The error is not relevant, cause it compiles the cgminer-4.0.0.exe anyway. Now Im running my HEX16B miner on Windows 7 (64-Bit) with CGminer-4.0.0, because I got the right WinUSB Driver by http://zadig.akeo.ie/Some newer GCCs did have a problem with an extension the HEX driver was working, but even before I patched CGMiner to work with COM Ports, using Zadig and trying all drivers(including WinUSB), cgminer wouldn't even detect it. I am surprised it worked for you. EDIT:Windows support "completed". |
|
|
|
After patching the cgminer 4.0.0 patch I tried to "make" my cgminer-4.0.0 with MinGW/MSYS-Shell for the HEX16B. But it failed! Sinturvy@SINNETWORK ~/cgminer-3.8.5
$ make
make all-recursive
make[1]: Entering directory `/home/Sinturvy/cgminer-3.8.5'
Making all in lib
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
GEN arg-nonnull.h
GEN c++defs.h
GEN warn-on-use.h
GEN signal.h
GEN string.h
make all-recursive
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/lib'
CC dummy.o
CC memmem.o
CC sigaction.o
CC sigprocmask.o
AR libgnu.a
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/lib'
Making all in compat
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat'
Making all in jansson-2.5
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make all-recursive
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
Making all in src
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5/src
'
CC dump.lo
CC error.lo
CC hashtable.lo
CC load.lo
CC memory.lo
CC pack_unpack.lo
CC strbuffer.lo
CC strconv.lo
CC utf.lo
CC value.lo
CCLD libjansson.la
Creating library file: .libs/libjansson.dll.a
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5/src'
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/jansson-2.5'
Making all in libusb-1.0
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make all-recursive
make[4]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
Making all in libusb
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0/libu
sb'
CC libusb_1_0_la-core.lo
CC libusb_1_0_la-descriptor.lo
CC libusb_1_0_la-io.lo
CC libusb_1_0_la-sync.lo
CC os/libusb_1_0_la-poll_windows.lo
CC os/libusb_1_0_la-windows_usb.lo
GEN libusb-1.0.lo
CC libusb_1_0_la-hotplug.lo
CC os/libusb_1_0_la-threads_windows.lo
CCLD libusb-1.0.la
Creating library file: .libs/libusb-1.0.dll.a
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0/libus
b'
make[5]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[5]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[4]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat/libusb-1.0'
make[3]: Entering directory `/home/Sinturvy/cgminer-3.8.5/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat'
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/compat'
Making all in ccan
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5/ccan'
CC opt/libccan_a-helpers.o
CC opt/libccan_a-opt.o
CC opt/libccan_a-parse.o
CC opt/libccan_a-usage.o
AR libccan.a
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5/ccan'
make[2]: Entering directory `/home/Sinturvy/cgminer-3.8.5'
CC cgminer-cgminer.o
CC cgminer-util.o
CC cgminer-sha2.o
CC cgminer-api.o
CC cgminer-logging.o
CC cgminer-usbutils.o
usbutils.c: In Funktion »_usb_init«:
usbutils.c:1760:5: Warnung: Unverträgliche implizite Deklaration der eingebauten
Funktion »bzero« [standardmäßig aktiviert]
CC cgminer-driver-hexminera.o
driver-hexminera.c: In Funktion »hexminera_get_results«:
driver-hexminera.c:278:5: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
CC cgminer-driver-hexminerb.o
driver-hexminerb.c: In Funktion »hexminerb_get_results«:
driver-hexminerb.c:290:3: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
CC cgminer-driver-hexminerc.o
driver-hexminerc.c: In Funktion »hexminerc_get_results«:
driver-hexminerc.c:276:5: Warnung: Unverträgliche implizite Deklaration der eing
ebauten Funktion »bzero« [standardmäßig aktiviert]
CCLD cgminer.exe
make[2]: Leaving directory `/home/Sinturvy/cgminer-3.8.5'
make[1]: Leaving directory `/home/Sinturvy/cgminer-3.8.5'
Sinturvy@SINNETWORK ~/cgminer-3.8.5
$ CGminer.exe is compiled but I'm getting the following error: USB init, open device failed, err -12, you need to install a WinUSB driver for - HEXb device 3:2
See README.txt file included for help
hexminerb detect (3:2) failed to initialise (incorrect device?)
No devices detected!
Waiting for USB hotplug devices or press q to quit Would be awesome if anyone could help me! As of now you can't mine on Windows with cgminer on Technobit devices, however I have told marto74 of my progress with the patches to enable mining on Windows, I have enabled mining on the HEX16A1, possibly HEX16A2. I plan Coincraft A1 and HEX16B as well, but you have to be patient. Meanwhile, you need linux. |
|
|
|
Well, how do we know if he is still alive, what if he passed away when we all thought he dropped out of bitcoin. Unless, Dorian is actually him   He replied on his p2p foundation profile? |
|
|
|
Anyone hear good with VanityGen? I know how to use ot and have created an address with my cpu but it will not work with oclvanitygen!? this is the error:
Error loading kernel file 'calc_addrs.cl': No such file or directory
The file is in the same folder as oclvanitygen!? im using windows. Ive been trying to figure this out for like a week now and just cant find anything!
Sounds to me like vanitygen is looking for the file in the wrong working directory. How are you executing oclvanitygen? |
|
|
|
|
You claim to have found flaws in the Bitcoin protocol, but don't know how the Bitcoin-Qt client works?
|
|
|
|
Watching this one. Hopefully works with CGMiner.
So long as the driver is created for the device, it will work. It will also as of soon work on Windows too(hopefully). |
|
|
|
"Vircurex is freezing your BTC, LTC, FTC, TRC."
The title of this thread is misleading. Vircurex isn't "freezing" anyone's BTC, LTC, FTC, TRC. They are refusing to honor the IOUs which they issued when someone deposited their BTC, LTC, FTC, TRC.
If you aren't the sole controller of your private keys, you don't have any bitcoins.
In case anyone was further mislead by this post, he basically means the same thing just said with fancy words. |
|
|
|
|
Sent a TX and within 2 minutes it was confirmed. The amount was only 0.0189btc and I paid a fee of 0.0002.
|
|
|
|
The QR code looks like it was photoshopped in.
What QR code? lol. Look at the picture in the first post. |
|
|
|
|
The QR code looks like it was photoshopped in.
|
|
|
|
|
I suggest installing MSYS on top of MinGW, makes your life easier and might solve your problem.
|
|
|
|
|
Show Posts
