Quote from: vgo on January 28, 2015, 05:10:33 PM

cgminer.exe --sha256 --icarus-options 115200:1:1 --rock-freq 300 -o http://localhost:17333 -u user -p password --btc-address ZaPcdijw44kFXAYWHRWbZJfMJScir3ynX6

En la última versión del CGminer no me reconoce "--sha256", porque al ejecutar la linea no llega a arrancar el programa.
Voy a pegar aqui unas lineas de texto tal cual salen del CGMiner:

[2015-01-28 18:40:10] Started cgminer 4.9.0
[2015-01-28 18:40:13] Probing for an alive pool
[2015-01-28 18:40:13] Solo mining to valid address: ZaPcdijw44kFXAYWHRWbZJfMJScir3ynX6
[2015-01-28 18:40:13] Block change for http://localhost:17333 detection via getblockcount polling
[2015-01-28 18:40:14] Network diff set to 31.6K
[2015-01-28 18:41:15] Block height change to 2384662 detected on pool 0
[2015-01-28 18:41:32] Block height change to 2384663 detected on pool 0
[2015-01-28 18:41:32] Network diff set to 30.1K
[2015-01-28 18:41:49] Block height change to 2384664 detected on pool 0
[2015-01-28 18:42:32] Block height change to 2384665 detected on pool 0
[2015-01-28 18:43:18] Block height change to 2384666 detected on pool 0
[2015-01-28 18:44:26] Found block for pool 0!
[2015-01-28 18:44:26] Rejected 02224ed9 Diff 30.7K/30097 BLOCK! LIR 0 (rejected)

Visto esto interpreto que hace la conexión, en la red se van encontrando bloques (que no soy yo) y finalmente encuentro un bloque ([2015-01-28 18:44:26] Found block for pool 0!) pero es rechazado (Rejected 02224ed9 Diff 30.7K/30097 BLOCK! LIR 0 (rejected)). En la parte superior del CGMiner se puede ver: A:0 R:30097 HW:0 WU:1646.1/m

Conclusión, que el minero no se está comunicando como debe con el wallet... digo yo (por eso era meter algo en medio)