Bitcoin Forum
April 26, 2018, 12:11:15 PM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Poll
Question: How often you want to be paid?
Every 1-2 days (300 satoshis 1M shares)
Every Friday with revenue share (more than 300 satoshis / 1M shares)
I don't care, just pay Smiley

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 [23] 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
Author Topic: TomosMining - HIGHEST PAID MINING (BTC->FaucetHub) 5% REF!  (Read 13391 times)
gmf10000
Jr. Member
*
Offline Offline

Activity: 44
Merit: 0


View Profile
January 17, 2018, 10:19:13 AM
 #441

can you chek your system, i am not mining naw and i get lots of btc, or som person is mining for my adres Cheesy i wont to be fair to you

1524744675
Hero Member
*
Offline Offline

Posts: 1524744675

View Profile Personal Message (Offline)

Ignore
1524744675
Reply with quote  #2

1524744675
Report to moderator
1524744675
Hero Member
*
Offline Offline

Posts: 1524744675

View Profile Personal Message (Offline)

Ignore
1524744675
Reply with quote  #2

1524744675
Report to moderator
1524744675
Hero Member
*
Offline Offline

Posts: 1524744675

View Profile Personal Message (Offline)

Ignore
1524744675
Reply with quote  #2

1524744675
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1524744675
Hero Member
*
Offline Offline

Posts: 1524744675

View Profile Personal Message (Offline)

Ignore
1524744675
Reply with quote  #2

1524744675
Report to moderator
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 17, 2018, 10:20:52 AM
 #442

can you chek your system, i am not mining naw and i get lots of btc, or som person is mining for my adres Cheesy i wont to be fair to you



PM me your BTC address Smiley

gmf10000
Jr. Member
*
Offline Offline

Activity: 44
Merit: 0


View Profile
January 17, 2018, 10:30:01 AM
 #443

i send pm
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 17, 2018, 11:57:34 AM
 #444

Small update:  Added actual earnings in $$$ value to BTC address check for cmd line mining page

Wink

tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 17, 2018, 03:00:03 PM
 #445

my proxy went crazy and switched 3x the pool... if it will happen one more time, i will increase temporary the payouts..
there can happen , this 15 minutes theminres will have less hashrate, but no stress about it Smiley

1manshow
Jr. Member
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 17, 2018, 07:10:20 PM
 #446

Hi tomos81, have you got the chance to test GPU mining with Nvidia?
Smiley Smiley
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 17, 2018, 07:23:20 PM
 #447

Hi tomos81, have you got the chance to test GPU mining with Nvidia?
Smiley Smiley

hi yes, i had chance ,via remote desktop i tested NVIDIA TESLA , it was great, but remote desktop stucked  Cheesy Cheesy

but it is ok, i will send here the result tomorrow (command line etc) , when i will be able to turn on the monster server again


1manshow
Jr. Member
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 17, 2018, 08:19:29 PM
 #448

Hi tomos81, have you got the chance to test GPU mining with Nvidia?
Smiley Smiley

hi yes, i had chance ,via remote desktop i tested NVIDIA TESLA , it was great, but remote desktop stucked  Cheesy Cheesy

but it is ok, i will send here the result tomorrow (command line etc) , when i will be able to turn on the monster server again



Thank you very much matey. Waiting badly for it, wanna turn my laptop CPU and GPU combo to mine as much satoshis as possible. Also any chance you going to bring dogeminer back? Was fun getting tons of doges that way.
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 18, 2018, 06:40:56 AM
 #449

Hi tomos81, have you got the chance to test GPU mining with Nvidia?
Smiley Smiley

hi yes, i had chance ,via remote desktop i tested NVIDIA TESLA , it was great, but remote desktop stucked  Cheesy Cheesy

but it is ok, i will send here the result tomorrow (command line etc) , when i will be able to turn on the monster server again



Thank you very much matey. Waiting badly for it, wanna turn my laptop CPU and GPU combo to mine as much satoshis as possible. Also any chance you going to bring dogeminer back? Was fun getting tons of doges that way.

the simpliest way is to exchange in faucethub : btc to doge Smiley 

krugerxxx
Jr. Member
*
Offline Offline

Activity: 35
Merit: 0


View Profile WWW
January 18, 2018, 06:46:16 AM
 #450

Hi tomos81, have you got the chance to test GPU mining with Nvidia?
Smiley Smiley

hi yes, i had chance ,via remote desktop i tested NVIDIA TESLA , it was great, but remote desktop stucked  Cheesy Cheesy

but it is ok, i will send here the result tomorrow (command line etc) , when i will be able to turn on the monster server again



Thank you very much matey. Waiting badly for it, wanna turn my laptop CPU and GPU combo to mine as much satoshis as possible. Also any chance you going to bring dogeminer back? Was fun getting tons of doges that way.

I'm sorry I wasn't able to reply for days lol.

So download the XMR-stak-win64
run as admin
type monero
copy paste tomosming pool
copy paste your user (btc add)
password is x
and let it run
 Smiley)
1manshow
Jr. Member
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 18, 2018, 10:38:23 AM
 #451


the simpliest way is to exchange in faucethub : btc to doge Smiley  


Yes, but I don't want to loose BTC for doge, instead on one computer would run dogeminer if possible. My powerful laptop I would want to earn BTC only.

Thanks krugerxxx, tried your tutorial, it worked but combined hashrate of both CPU/GPU didn't went above 110. My CPU alone when using tomosmining miner does 150-180 h/s. Do note that nothing extra is used on this system, I'm simply leaving this for mining only.
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 18, 2018, 12:08:28 PM
 #452

Hi graphic card owners! This post is for you, and explains how to use graphic card +  CPU at once:

1) download https://github.com/fireice-uk/xmr-stak/releases/download/v2.2.0/xmr-stak-win64.zip
2) unzip to folder and exclude from antivirus!
3) download and install vcredist (if you dont have): https://www.microsoft.com/en-us/download/details.aspx?id=52685
4) in the directory where you have xmr-stak unzipped (from step 1) , create config.txt file and copy paste this, change only red text to your BTC address linked with faucethub - there you will get payments.. DO NOT use spaces in your BTC address, before or after address also! Otherwise your payment will not be processed
Quote

/*
 * pool_address    - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
 * wallet_address  - Your wallet, or pool login.
 * pool_password   - Can be empty in most cases or "x".
 * use_nicehash    - Limit the nonce to 3 bytes as required by nicehash.
 * use_tls         - This option will make us connect using Transport Layer Security.
 * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
 * pool_weight     - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
 *                   with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
 *
 * We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com
 */
"pool_list" :
[
   {"pool_address" : "80.211.205.216:3333", "wallet_address" : "YOUR_BTC_ADDRESS_WITHOUT_SPACES", "pool_password" : "x", "use_nicehash" : true, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 },
],

/*
 * currency to mine
 * allowed values: 'monero' or 'aeon'
 */
"currency" : "monero",

/*
 * Network timeouts.
 * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
 * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
 * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
 * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
 * server usually takes to process our calls.
 *
 * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
 * retry_time   - How long should we wait before another connection attempt.
 *                Both values are in seconds.
 * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
 *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
 */
"call_timeout" : 10,
"retry_time" : 30,
"giveup_limit" : 0,

/*
 * Output control.
 * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
 * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
 * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
 * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
 *
 * verbose_level - 0 - Don't print anything.
 *                 1 - Print intro, connection event, disconnect event
 *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
 *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
 *                 4 - All of level 3, and automatic hashrate report printing
 *
 * print_motd    - Display messages from your pool operator in the hashrate result.
 */
"verbose_level" : 3,
"print_motd" : true,

/*
 * Automatic hashrate report
 *
 * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
 *                This option has no effect if verbose_level is not 4.
 */
"h_print_time" : 60,

/*
 * Manual hardware AES override
 *
 * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
 * to false to force disable AES or null to let the miner decide if AES is used.
 *
 * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
 */
"aes_override" : null,

/*
 * LARGE PAGE SUPPORT
 * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
 * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
 * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
 * on Windows, please read the common issues in the README.
 *
 * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
 * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
 *
 * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
 * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
 * 3. Expand Security Settings, and then expand Local Policies.
 * 4. Select the User Rights Assignment folder.
 * 5. The policies will be displayed in the details pane.
 * 6. In the pane, double-click Lock pages in memory.
 * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
 * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
 * 9. Reboot for change to take effect.
 *
 * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
 * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
 *
 * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
 * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
 * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
 * recommended for security reasons.
 *
 * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
 * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
 * locked and unlocked memory. If that is your setup see option "no_mlck".
 */

/*
 * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
 * always  - Don't even try to use large pages. Always use slow memory.
 * warn    - We will try to use large pages, but fall back to slow memory if that fails.
 * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
 *           It will never use slow memory, but it won't attempt to mlock
 * never   - If we fail to allocate large pages we will print an error and exit.
 */
"use_slow_memory" : "warn",

/*
 * TLS Settings
 * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
 * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
 *
 * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
 */
"tls_secure_algo" : true,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : false,

/*
 * Buffered output control.
 * When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
 * each output line immediately. This can cause delays when running in background.
 * Set this option to true to flush stdout after each line, so it can be read immediately.
 */
"flush_stdout" : false,

/*
 * Output file
 *
 * output_file  - This option will log all output to a file.
 *
 */
"output_file" : "",

/*
 * Built-in web server
 * I like checking my hashrate on my phone. Don't you?
 * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
 * outside of your home network. Ports lower than 1024 on Linux systems will require root.
 *
 * httpd_port - Port we should listen on. Default, 0, will switch off the server.
 */
"httpd_port" : 0,

/*
 * HTTP Authentication
 *
 * This allows you to set a password to keep people on the Internet from snooping on your hashrate.
 * Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
 * who is able to read your traffic it is as easy to break a bog door latch.
 *
 * http_login - Login. Empty login disables authentication.
 * http_pass  - Password.
 */
"http_login" : "",
"http_pass" : "",
 
/*
 * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
 *               This setting will only be needed in 2020's. No need to worry about it now.
 */
"prefer_ipv4" : true,



here is an example how it looks like:


1manshow
Jr. Member
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 18, 2018, 06:27:44 PM
 #453

Hi graphic card owners! This post is for you, and explains how to use graphic card +  CPU at once:

1) download https://github.com/fireice-uk/xmr-stak/releases/download/v2.2.0/xmr-stak-win64.zip
2) unzip to folder and exclude from antivirus!
3) download and install vcredist (if you dont have): https://www.microsoft.com/en-us/download/details.aspx?id=52685
4) in the directory where you have xmr-stak unzipped (from step 1) , create config.txt file and copy paste this, change only red text to your BTC address linked with faucethub - there you will get payments.. DO NOT use spaces in your BTC address, before or after address also! Otherwise your payment will not be processed
Quote

/*
 * pool_address    - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
 * wallet_address  - Your wallet, or pool login.
 * pool_password   - Can be empty in most cases or "x".
 * use_nicehash    - Limit the nonce to 3 bytes as required by nicehash.
 * use_tls         - This option will make us connect using Transport Layer Security.
 * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
 * pool_weight     - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
 *                   with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
 *
 * We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com
 */
"pool_list" :
[
   {"pool_address" : "80.211.205.216:3333", "wallet_address" : "YOUR_BTC_ADDRESS_WITHOUT_SPACES", "pool_password" : "x", "use_nicehash" : true, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 },
],

/*
 * currency to mine
 * allowed values: 'monero' or 'aeon'
 */
"currency" : "monero",

/*
 * Network timeouts.
 * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
 * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
 * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
 * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
 * server usually takes to process our calls.
 *
 * call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
 * retry_time   - How long should we wait before another connection attempt.
 *                Both values are in seconds.
 * giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
 *                don't mine while the connection is lost, so your computer's power usage goes down to idle.
 */
"call_timeout" : 10,
"retry_time" : 30,
"giveup_limit" : 0,

/*
 * Output control.
 * Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
 * really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
 * performance monitors, there is very little reason to spew out pages of text instead of concise reports.
 * Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
 *
 * verbose_level - 0 - Don't print anything.
 *                 1 - Print intro, connection event, disconnect event
 *                 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
 *                 3 - All of level 1, and new job (block) event in all cases, result submission event.
 *                 4 - All of level 3, and automatic hashrate report printing
 *
 * print_motd    - Display messages from your pool operator in the hashrate result.
 */
"verbose_level" : 3,
"print_motd" : true,

/*
 * Automatic hashrate report
 *
 * h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
 *                This option has no effect if verbose_level is not 4.
 */
"h_print_time" : 60,

/*
 * Manual hardware AES override
 *
 * Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
 * to false to force disable AES or null to let the miner decide if AES is used.
 *
 * WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner.
 */
"aes_override" : null,

/*
 * LARGE PAGE SUPPORT
 * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
 * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
 * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
 * on Windows, please read the common issues in the README.
 *
 * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
 * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
 *
 * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
 * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
 * 3. Expand Security Settings, and then expand Local Policies.
 * 4. Select the User Rights Assignment folder.
 * 5. The policies will be displayed in the details pane.
 * 6. In the pane, double-click Lock pages in memory.
 * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
 * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
 * 9. Reboot for change to take effect.
 *
 * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
 * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
 *
 * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
 * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
 * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
 * recommended for security reasons.
 *
 * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
 * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
 * locked and unlocked memory. If that is your setup see option "no_mlck".
 */

/*
 * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
 * always  - Don't even try to use large pages. Always use slow memory.
 * warn    - We will try to use large pages, but fall back to slow memory if that fails.
 * no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
 *           It will never use slow memory, but it won't attempt to mlock
 * never   - If we fail to allocate large pages we will print an error and exit.
 */
"use_slow_memory" : "warn",

/*
 * TLS Settings
 * If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
 * to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
 *
 * tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
 */
"tls_secure_algo" : true,

/*
 * Daemon mode
 *
 * If you are running the process in the background and you don't need the keyboard reports, set this to true.
 * This should solve the hashrate problems on some emulated terminals.
 */
"daemon_mode" : false,

/*
 * Buffered output control.
 * When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
 * each output line immediately. This can cause delays when running in background.
 * Set this option to true to flush stdout after each line, so it can be read immediately.
 */
"flush_stdout" : false,

/*
 * Output file
 *
 * output_file  - This option will log all output to a file.
 *
 */
"output_file" : "",

/*
 * Built-in web server
 * I like checking my hashrate on my phone. Don't you?
 * Keep in mind that you will need to set up port forwarding on your router if you want to access it from
 * outside of your home network. Ports lower than 1024 on Linux systems will require root.
 *
 * httpd_port - Port we should listen on. Default, 0, will switch off the server.
 */
"httpd_port" : 0,

/*
 * HTTP Authentication
 *
 * This allows you to set a password to keep people on the Internet from snooping on your hashrate.
 * Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
 * who is able to read your traffic it is as easy to break a bog door latch.
 *
 * http_login - Login. Empty login disables authentication.
 * http_pass  - Password.
 */
"http_login" : "",
"http_pass" : "",
 
/*
 * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
 *               This setting will only be needed in 2020's. No need to worry about it now.
 */
"prefer_ipv4" : true,



here is an example how it looks like:


Can you try with ccminer? I tried xmr stak, but it doesn't yield good hash rates on my laptop with Core i7 4710HQ and Geforce GTX 860M. Combined it reaches 110 only. Not sure if it's missing something. This laptop is only for mining purpose, so nothing else running and not even in active use.

How come you are getting so high hash rate?
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 18, 2018, 06:40:34 PM
 #454

Hi graphic card owners! This post is for you, and explains how to use graphic card +  CPU at once:
blah

Can you try with ccminer? I tried xmr stak, but it doesn't yield good hash rates on my laptop with Core i7 4710HQ and Geforce GTX 860M. Combined it reaches 110 only. Not sure if it's missing something. This laptop is only for mining purpose, so nothing else running and not even in active use.

How come you are getting so high hash rate?

ccminer will not work, bcs not nicehash compatible (nonce)..
try to run xmr-stak as i told, but edit .txt for cpu's, that they will not use CPU.. so you will have open 2 miners, one for GPU (xmr-stak)  and one for CPU (claymore)

my hashrate was so high bcs i was testing a monster for 20k USD (but only 50% resources used):
56 CPUs intel xeon , and NVIDIA TESLA (3 from 4 cards used)

gmf10000
Jr. Member
*
Offline Offline

Activity: 44
Merit: 0


View Profile
January 18, 2018, 08:05:23 PM
 #455



for me not workin on amd i have hd 7900 , new drivers itd. :/
1manshow
Jr. Member
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 18, 2018, 08:41:54 PM
 #456


ccminer will not work, bcs not nicehash compatible (nonce)..
try to run xmr-stak as i told, but edit .txt for cpu's, that they will not use CPU.. so you will have open 2 miners, one for GPU (xmr-stak)  and one for CPU (claymore)


I tried edit the CPU.txt file, but it then gave me this parameter error after running the program.
JSON config parse error(offset 1642): Missing a name for object member.

Can you paste me the content of CPU.txt here if I want to exclude it completely?

krugerxxx
Jr. Member
*
Offline Offline

Activity: 35
Merit: 0


View Profile WWW
January 19, 2018, 01:00:45 AM
 #457


ccminer will not work, bcs not nicehash compatible (nonce)..
try to run xmr-stak as i told, but edit .txt for cpu's, that they will not use CPU.. so you will have open 2 miners, one for GPU (xmr-stak)  and one for CPU (claymore)


I tried edit the CPU.txt file, but it then gave me this parameter error after running the program.
JSON config parse error(offset 1642): Missing a name for object member.

Can you paste me the content of CPU.txt here if I want to exclude it completely?



On the CPU.txt file

Delete all texts inside [] (DONT DELETE [])

Have fun!
krugerxxx
Jr. Member
*
Offline Offline

Activity: 35
Merit: 0


View Profile WWW
January 19, 2018, 01:02:14 AM
 #458


the simpliest way is to exchange in faucethub : btc to doge Smiley  


Yes, but I don't want to loose BTC for doge, instead on one computer would run dogeminer if possible. My powerful laptop I would want to earn BTC only.

Thanks krugerxxx, tried your tutorial, it worked but combined hashrate of both CPU/GPU didn't went above 110. My CPU alone when using tomosmining miner does 150-180 h/s. Do note that nothing extra is used on this system, I'm simply leaving this for mining only.

Try to edit maybe the CPU.text file..
Me too i felt it so I went to a separate GPU and CPU miner lol..
krugerxxx
Jr. Member
*
Offline Offline

Activity: 35
Merit: 0


View Profile WWW
January 19, 2018, 06:31:34 AM
 #459

Tomos I have a question!

I have tried the CPU and GPU mining separately with 1 account..
I dont know but it is running at 200+hs and 40+hs but see the picture..



Is there an error on the server? Or should i use 2 separate btc address for CPU and GPU?  Huh Huh
tomos81
Hero Member
*****
Offline Offline

Activity: 588
Merit: 501



View Profile
January 19, 2018, 08:16:35 AM
 #460

Tomos I have a question!

I have tried the CPU and GPU mining separately with 1 account..
I dont know but it is running at 200+hs and 40+hs but see the picture..



Is there an error on the server? Or should i use 2 separate btc address for CPU and GPU?  Huh Huh

hi send me pls BTC address to PM , i am registering some bug with updates of hashes, but hashes are not lost, it's just visual thing

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 [23] 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!