THANK YOU for compiling this for Windows. I've been banging my head against the wall trying to get cygwin to like it and I'm sure I'd have succeeded eventually, but now I can forsake that sad battle

Also, I'm glad to finally see open source code enabling GPU mining for ProtoShares using all modern GPUs on all platforms.

[Edit: I'm sending you a PTS donation.]

Stats:
~400c/p on Radeon HD 78 (using 512 mem. Crashes with 1024 mem).
Crashes on Radeon HD 580, not sure why.

I think I'll break down and migrate my rig to linux, as I suspect I'll get much better speeds via that platform . . .

Questions: does this include the hidden options for different algorithms, and if so how are they invoked? Also, what ocl binary file is it wanting to read (when run on Windows), and would it load faster with that, and if so, where can I get said file?

(And if so, do you use your powers for good or for awesome?)

Well, ur free to add that if you haven't already (and sorry).

Please update the spreadsheet which I link to from this post:

https://bitsharestalk.org/index.php?topic=2437.0

--with anything I'm missing. I'm not sure whether I'd put any speed tests in it; maybe that could be another spreadsheet?

Quote

The actual code is Invictus, by third party we mean to say that they are bot being financed or supported via AGS.

Dan, can we get some clarification on this point?

Quote

your licensing and restrictions you chose to not to separate commons and non-commons use of the product ergo you left out the key parts where we restrict those who subscribe to IP and wish to use the product without honouring the SCSL

I understand the philosophical argument here about believing and not believing in IP; however, in reality, this is almost impossible to enforce.  How do you know what I believe and don't believe? Even then, what if my belief changes? At the end of the day, a DAC that doesn't honor the SCSL doesn't get the license to use and modify the code.  At that point, you have a community of PTS and AGS holders that can be very vocal about DACs that steal the code and don't honor the consensus.

It's very possible I misunderstand (it's been known to happen ) so I will write all of the following under the assumption that I do misunderstand. Which, actually, may be the assumption y'all would want to make, also, because if I misunderstand it in the following way, maybe this illuminates a risk that others misunderstand it in this way, also.

So, again, please assume that I misunderstand, and consider: for me, discussion in a legal document of questions about the status quo of law, and whether any given set of beliefs supports that status quo or not--this rings loud alarm bells of anarchism (which, after all, is quite frowned upon, oh, say . . . in courts of law. Yes, I realize how ironic it is for me to say this, in light of the fact that others have cited my writing in this thread as sounding deeply anarchist). For me, it shouts: "Anarchy! Anarchy! We may have qualms with the entire status quo conception of law--so that we might not uphold the law!" Yoink! How scary might a license document be (and how untenable and unenforceable) if it bears any potential shades of lawlessness in it?

To further play out this "what if?" -- if any court of public opinion forms around the license (and against it) which derive from any misunderstandings similar to mine, that may run the risk of making other substantial (and potentially enforceable) questions about the document harder to ask. I fear it would undermine the credibility of the whole document in any setting wherein it may eventually become desirable to wield said document as real, verifiable, and powerful legal weaponry. I suggest we want to lend every possible strength of precedent, credibility and enforceability which it is possible to lend to the document--and I therefore propose omitting any philosophical discussions (from the document) about who believes what about law. I suggest it may be most desirable to couch all the language and assumptions in the most strictly lawful (and perhaps even conservative businessman-type) language that it can afford (obviously, while avoiding undue complexity and also lending it as much immediate clarity and enforceability as possible).

The following may be an aside, but as possibly supporting case precedent: I've read about folks who refused to register for Social Security Numbers under the auspices that their religious beliefs forbid them to do so. I'm sorry to say this is only anecdotal (and I wager some here might more easily find the references than I, or know more of what I speak), but my recollection is that it didn't hold up in the end . . . I think they were compelled to obtain SSNs. (And aren't SSNs an essential mechanism for the IRS to ensure it gets its lawful tax cut in all the settings where the law supports it?)

LOL!

I'm glad you spotted this, barwizi--and I had meant to link here from yon referenced rant (and the disquiet which ensued (I gathered) therefrom), which I will now do.

For the curious, that's there: https://bitsharestalk.org/index.php?topic=1708.msg26428#msg26428

A teenager who mortgages half of his buddies' "huts" (million-dollar mansions) on a credit card . . . and his buddies are, well . .  just about everyone in the country . . .

(Somebody stop me, now . . .)

hi. How to use cudapts to connect to ypool.net?

EDIT: That may not work: does ypool use a different work-sharing protocol?

I detail a hack here:

https://bitsharestalk.org/index.php?topic=2338.msg28809#msg28809

--but I suggest using beeeeer.org, as (last I heard) ypool had vastly more than 51% of all hashing power going for this coin.

I get this info using the tool in the launcher:

1 OpenCL computing platforms found -- [0] AMD Accellerated Parallel Processing -- GPU OpenCL Devices on this platform: [0] Pitcairn, maximum memory setting 544MB -- [1] Cypress, maximum memory setting 544MB
From which I derive this command line:

arOpenCLminer.exe -pl 0 -g 0 -m 544 -i SSE4 -u myUsername.1 -myPassword
-- and all it does is start and then exit execution. ? (Really odd, same thing happened with your cuda miner in a test--it ran and then exited immediately.)

What's my error, or what may be wrong?