Latest posts of: wartywarlock2

Show Posts
Pages: [1]

on: October 30, 2018, 03:41:25 PM

Cheers both you guys, that's the winning answer couple more days to go and I can do it.

on: October 29, 2018, 07:52:48 PM

Quote from: Krakatoa87 on October 29, 2018, 05:11:32 PM You have to keep your 5k AKA on your masternode wallet for it to work, just send the surplus to another address on wich you will build your 2nd masternode when you'll get 5k on it. How can I guarantee the coins left is the right 5k though? I can't see any options for coin control (picking sources of coins to send) or does the node just "see" the 5k and that's all that counts? Other MN coins I have allow you to lock out the coins for a node and only send from the pool of coins unrelated to your MN. It's not exactly a hardship to set up nodes just seems a little backwards compared to other coins.

on: October 29, 2018, 11:47:31 AM

Coin control / new masternodes Seems like a silly question but hey ho, don't think it actually is. I have an existing masternode, and would like to use it's returns plus mining to set up a second one, however either through wallet or webwallet I cannot see options for coin controls. What is the best way of moving forwards with a 2nd node? Should I just bite the bullet and create 2 new nodes? I don't know how important the reputation is right now but if I've been building that up over the last few months then throwing it away might not be a good plan? If I send all the coins to a new address, then 5k back to the original node address will it pick it up as the same masternode or would I need to set up a new one with the old coins as well as my new node?

on: October 23, 2018, 03:41:05 PM

Any chance of SGminer_brian getting updted, it's called https://bitcointalk.org/index.php?topic=3330680.0 Avermore now, not sure why it needs to be revoted back in after a name change. New OC groups is awesome, great addition dude.

on: August 13, 2018, 09:21:12 PM

https://imgur.com/a/mn0enVB#cWdAZHi Hi, I set up the node according to instructions from https://github.com/XDNA-Core/XDNA-InstallMN, started the wallet process and went back to the VM, where it eventually came up with the above error. Using Virtualbox on win10, port is forwarded to the machine from router, bridged network mode. Install of Ubuntu server is fresh, tried twice on new install after apt-get upgrade.

on: August 08, 2018, 10:46:04 AM

Quote from: peteris-apse on August 08, 2018, 08:00:17 AM please add latest z-enemy version 1.15a https://bitcointalk.org/index.php?topic=3378390.msg43672800#msg43672800 Yes please! I know you just pushed 1.14 but 15 contains some new algos I'd love to hit up!

on: July 09, 2018, 11:38:01 AM

Really liking the OS buddy, but one probably simple question - does the OS allow undervolting of memory or just core clock? It only has the one option, I assume core clock. Thanks

on: July 06, 2018, 12:08:30 PM

If I have 10k coins will putting them all in the same masternode yield the same as 2 5k MNs or would running two seperate nodes be better? Can't seem to find this anywhere.

on: March 07, 2018, 12:13:48 PM

Regarding the Debugger Error, I have a thing maybe. I discovered that when my troubled rig was installed, it was selected Windows 10 Pro N version. The same USB media installed to another rig (literally exact same hardware!) but just normal Pro, it works fine. Granted I have not swapped out the HDD and tested the error machine but it's literally the only difference I can manage to find. Maybe it helps, maybe it's coincidence.

on: March 01, 2018, 10:39:17 AM

Quote How do you manage to get that far off? I'm a third party - who doesn't have a stake in it, which is why I thought I might look and give my input. Because you just replied to a post directed at Claymore acting like it was at you. Easy enough conclusion, if far fetched in reality. Quote It's definitely not a hardware problem - this is the anti-debug code activating without good reason apparently. We are trying to make these checks smarter and lighter but obviously we aren't there yet. Still, we are hesitant to relax the checks too much for obvious reasons - apparently there is no lack of highly esteemed developers trying to reverse our miner Wink No worries, as I said the only difference I can give is that I used the latest ISO for Win10 from MS, but then all the other machines are fully up to date AFAIK, and we have 2 other builds with the exact same hardware (built from ISO from around June 17). The machine itself has crashed/rebooted a couple of times over the last day so maybe it's a problem with the mobo. Will visit the mine later and see about copying bios settings from one of the fully working ones incase some arcane setting balls deep in the menus got missed!

on: February 28, 2018, 10:12:56 AM

Hi did anybody ever figure out the Fatal Error: debugger detected problem? Over the last week I have installed 3 rigs, 2 went fine, third one was a problem. The only thing I can point out as different is that on the 3rd one I had to grab a new win10 ISO from MS as I lost my USB, otherwise it is the same https://www.scan.co.uk/products/asrock-z270-killer-sli-intel-z270-s-1151-ddr4-sata3-m2-(pcie-sata)-2-way-sli-crossfire-gbe-usb-30-ap?v=c same ram, same psu, and same cpu. Cards are a bit different but shouldn't be relevant. At work so I can't check the bios but all 6 cards are present and correct, dagpatch done etc. Claymores is currently running fine so it's not as far as I can tell a hardware issue. Can remote in and try settings if anyone has suggestions. Otherwise superb miner, can't wait for linux version (focus on Ubuntu as that seems most common!).

Pages: [1]