Quote from: Schleicher on September 03, 2015, 03:56:10 PM

Quote from: tbearhere on September 03, 2015, 12:50:40 PM

Quote from: djm34 on September 03, 2015, 12:20:09 PM

Quote from: tbearhere on September 03, 2015, 11:21:08 AM

Quote from: djm34 on September 03, 2015, 10:26:20 AM

Quote from: tbearhere on September 03, 2015, 10:14:01 AM

Quote from: sp_ on September 03, 2015, 10:10:06 AM

Quote from: tbearhere on September 03, 2015, 09:59:32 AM

Quote from: tbearhere on September 01, 2015, 11:55:20 AM

sp could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx

Well I still can't wallet mine with latest versions. http protocol failed.

Does it work in the 1.6.6 fork by tvpruvot?

I don't know sp . Do you mean 1.5.64 ?

my version works with solomining (and was tested with...) so it is probably on your hand (wrong rpc port, username or password)

I know someone who is using your older version because the new ones won't work solo mining.
maybe cuda build app files have changed ..because about the same time sp releases aren't working either.
I'm going to try an older version of lyra2v2 of yours djm.

older ? there are 4 releases which are mostly bug correction (and compatibility issues) and none of these changes are related to solo mining.
all are there, and all are working: https://github.com/djm34/ccminer-lyra/releases

regarding solo mining, I don't know what is the default vtc port, I use a custom config file to define which port are used and some other settings.
(make sure as well, that you are using the latest wallet... Grin

)

also I am using --api-bind 0 (as it becomes problematic when there are several instances) and obviously don't use the same port for api-bind and the wallet

edit: there was a changed pushed by pallas to bmw256, however I don't think it would break solo mining, you can probably test that with testnet

Ok thank you djm. The other person had to use your version before ver4 to make it work.
But still something happened , related?, to solo mining about the time your oldest version was released I think. Will try your oldest tomorrow.
But to clarify ... sp r43 solo mining a coin works....now with exactly the same bat file and using r55 or r60 or r62 it won't work.
Will try again tomorrow. thx

I have tested solo mining Quarkcoin with release 64 now on my system.
Command line: ccminer -O name:password -o http://localhost:8372 -a quark --no-gbt
This happened:

ccminer actually crashed:

Quote

Unhandled exception at 0x00C99824 in ccminer.exe: Stack cookie instrumentation code detected a stack-based buffer overrun.

SOLO MINING VERTCOIN--

The question was asked a few pages back about solo mining VertCoin. I was able to set-up and mine VTC with CCminer release dot 66 on Windows. Here is what I learned:

   1) The VertCoin wallet looks for a file called "vertcoin.conf" BY DEFAULT on startup.
   2) The VertCoin configuration file "vertcoin.conf" only needs to be minimal.
   3) The folder to place "vertcoin.conf" is in ...appdata/roaming/vertcoin in windows, under the login user files.

Here is my vertcoin.conf file:
=======CUT LINE=======
server=1

daemon=1

rpcuser=username

rpcpassword=x

rpcallowip=127.0.0.1
=======CUT LINE=======

Notice that no ports are mentioned here!

Here is my CCminer command line:

ccminer.exe -c solo-vtc.conf

I use a configuration file to launch. Here is my configuration file, solo-vtc.conf:

========CUT LINE=========
{
   "url" : "127.0.0.1:5888",
   "user" : "username",
   "pass" : "x",
   "algo" : "lyra2v2",
   "devices" : "0",
   "intensity" : "19",
   "cpu-priority" : 5,
   "cpu-mining" : "true",

   "api-bind" : "0",
   "statsavg" : 20,
   "quiet" : false,
   "debug" : false,
   "protocol" : false
}
========CUT LINE=========

Leave the cut lines out, but don't forget the curly brackets. THERE IS A PORT HERE! It is the default RPCport (5888) for VertCoin. You may want to lower the cpu-priority or intensity for your hardware.

It works for me. --scryptr

EDIT: MINE ON A LAN--

For those of you that have a "work" or "home" computer with a wallet, and one or more mining rigs, the setup is a little different. In "vertcoin.conf", set the "rpcallowip" line to "rpcallowip=192.168.1.*", or similar if your local net uses a different configuration. The asterisk is a "wildcard" that will allow any rig on the local net to link to the wallet on the home computer. On the mining rig(s), for the url use the physical, numerical address of the home computer, i.e. "192.168.1.111:5888". If you are using a command line only, use "ccminer -a lyra2v2 -o http://192.168.1.111:5888 -u username -p x". You can get the lan address of the home computer from your router; I set this example to "111".

There may be a looong pause on miner lanch, but if you don't see red, just wait. Hash results for your cards should appear within 90 seconds. Of course, you can tweak the command line with performance flags. If you also mine with a card on the home computer, make sure you use the lan address for the wallet, just as in the previous paragraph, not "localhost" or "127.0.0.1". There is still a long pause before hash results.

Local GTX 960 card on Win 7 work computer and Linux 750ti mining rig on LAN

The cards will hash until an "accept" is received. Then your wallet will be 50 VTC fatter. --scryptr