Quote from: Palmdetroit on December 03, 2013, 05:45:15 AM

Quote from: broken_pixel on December 03, 2013, 03:50:23 AM

Quote from: jaycee1974 on December 03, 2013, 02:24:21 AM

False + ?
Ad-Aware    Trojan.Generic.9705038    20131203
Agnitum    Riskware.BitCoinMiner!mabHpPndSNc    20131202
AhnLab-V3       20131202
AntiVir    TR/BitCoinMiner.Gen    20131203
Antiy-AVL       20131129
Avast    Win32:Crypt-OSW [Trj]    20131203
AVG       20131202
Baidu-International    Trojan.Win32.Win64.aYo    20131202
BitDefender    Trojan.Generic.9705038    20131203
Bkav       20131129
ByteHero       20131127
CAT-QuickHeal       20131202
ClamAV       20131203
Commtouch       20131203
Comodo    UnclassifiedMalware    20131203
DrWeb       20131203
Emsisoft    Trojan.Generic.9705038 (B)    20131203
ESET-NOD32    a variant of Win64/BitCoinMiner.E    20131202
F-Prot       20131203
F-Secure    Trojan.Generic.9705038    20131203
Fortinet    W64/BitCoinMiner.E    20131202
GData    Trojan.Generic.9705038    20131203
Ikarus    Win32.Crypt    20131203
Jiangmin       20131202
K7AntiVirus    Trojan ( 004828c81 )    20131202
K7GW    Trojan ( 004828c81 )    20131202
Kaspersky    not-a-virus:RiskTool.Win64.BitCoinMiner.i    20131203
Kingsoft       20130829
Malwarebytes       20131203
McAfee    RDN/Generic PUP.x!blp    20131203
McAfee-GW-Edition       20131202
Microsoft       20131203
MicroWorld-eScan    Trojan.Generic.9705038    20131203
NANO-Antivirus       20131203
Norman    Troj_Generic.QRECX    20131202
nProtect       20131202
Panda    Trj/CI.A    20131202
Rising       20131203
Sophos       20131203
SUPERAntiSpyware       20131202
Symantec    Bitcoinminer    20131203
TheHacker       20131202
TotalDefense       20131203
TrendMicro    TROJ_GEN.R0CBC0OK913    20131203
TrendMicro-HouseCall    TROJ_GEN.R0CBC0OIS13    20131203
VBA32       20131202
VIPRE    Trojan.Win32.Generic!BT    20131203
ViRobot       20131202

I would not follow that link or repost the url

Is this legit?

http://www.share-online.biz/dl/L78K8NRMGUG

I got it from there:

Quote from: Neisklar on August 16, 2013, 11:28:06 PM

Quote from: quarkcoin on August 16, 2013, 09:43:56 PM

Thanks to Neisklar for releasing a version of CPU miner for Quark.

Announcement thread:
http://forum.quarkcoin.org/Thread-ANN-poolers-cpuminer-with-quarkcoin-support

Source code here:
http://www.share-online.biz/download.php?id=CU5H5NRMJK

The win executables took some time to compile, they are linkes in the announcement thread, and here:
Win64: http://www.share-online.biz/download.php?id=E7OXBNRMUU
Win32: http://www.share-online.biz/download.php?id=L78K8NRMGUG

Since the quark-algo is pure plain c, i compiled it for different processor/instructionsets, just pick one that works best for you. AVX better than SSE and so on. Win64 will definatly gain heavy speed improvements: On my old core2 laptop, I had a win32_sse3 run with around 9-12 khash/s per core. With w64_sse4 i got around 22-26 khash/s per core.

Quote from: yourofl10 on August 16, 2013, 09:47:36 PM

Is it faster? Github?

Yes definatly, one core on wallet: ~11kHash/s, w64_sse4 one core: ~23kHash/s
So at least on my testing machine and win64: around 100% gain

Github will come hopefully after the weekend, and hopefully coreectly setup as fork.

Quote from: quarkcoin on August 16, 2013, 09:53:39 PM

I don't think it is significantly faster, but you can use it to mine on a pool. Neisklar has also setup a p2pool for Quark here:

http://176.221.46.81:8372/static/

See above:) It's waaaaayyyy faster:)

The pool is for now only a standalone p2pool. The blocktimes in the stats page are hours off, but following the link into the block explorer shows the right times in UTC.
I hope to have next week some time to create/setup a traditional pool.

Quote from: stonefoz on August 16, 2013, 10:41:48 PM

https://github.com/uncle-bob

for nearly a 30% improvement in hash rate

Yeah nice, taking it out of the loop, need to try out whats the speedgain in the cpuminer.
I wonder if we get even more gain (since memory is not an issue) if we create for multiple times used hash functions in one hash run, distinct contexts, and then combine them in one big struct, so thats one big continous block of memory which can be copied with one single memcpy call, instead now 9 calls for smaller blocks.