Quote from: Athalbjorn on September 12, 2017, 01:28:51 PM

Quote from: pallas on September 11, 2017, 11:53:53 AM

Quote from: Athalbjorn on September 11, 2017, 11:38:47 AM

Quote from: joblo on September 10, 2017, 05:32:41 PM

Give it up with cudaminer, it's over 3 years out of date. The only algos it supports are either dead or taken
over by ASICs. The code won't compile with new tools and won't run on new hardware when compiled with
old tools.

Use one of the many forks of ccminer that are actively developped.

... not actually helpful.

I'm using an NVIDIA GPU, and I'm given to understand that cudaminer is optimized for that. It was suggested to me that I use it because of my GPU and because I couldn't get CGMiner to work since it doesn't support GPUs anymore.

I just want to know how to fix the file paths so it will look in the right location. If it still doesn't work after that, then I might try another miner.

Try this one:

https://bitcointalk.org/index.php?topic=770064.0

Well, I'm not getting any errors anymore, but it also doesn't look like it's actually mining. I let it run all night, and all it keeps saying is "auto block (#), diff (#.#), with the first number incrementing by 1 with each new line (about once every minute to a minute and a half), and the second number seems random.

Ok, I seem to have gotten it working. I had to put in --algo=scrpyt into my batch file and now it's actually mining, although I'm only getting about 295 kH/s for LINDA coins, where I was getting about 12 MH/s for Ethereum. I'm assuming the difference is due to the algorithm?