@VegasGuy Does my 129 coins make me a high roller or just high?  No, just another annoying snotty nose kid, that has nothing useful to contribute. Vegas JeEz, LoEez...dude with a 'tude. Such a nice guy too. Wish I could have retired when I WAS a snot nosed kid. |
|
|
|
@VegasGuy Does my 129 coins make me a high roller or just high? |
|
|
|
Dev need to repair
Nothing huh? |
|
|
|
|
@TomVelvet,
Having a bad day?
Just wanted to let ya know, it's not as complicated as Grandpa made it out to be. Wallets can get messed up for a lot of reasons. I've messed up a few. Actually, my computer did. Some wallets don't like power outages, they don't close correctly. I don't know what happened to yours, so can't say, but if you want help, give me a shout. I'm not part of the dev team, but been fixing my 'puter problems for years.
|
|
|
|
ms updates should not affect the stand alone miners they will reconnect as soon as power and internet return  Yeah, my S3+ would come back online except when the batt backup is drained, it has to be manually reset. It runs while I do a restart after MS updates, not power loss. I've thought about reconfiguring, but then I lose the surge/spike protection. Sooo.. being a lone, small-time miner, I choose protection. Just dealin' with it & hangin' in there. My other stuff is dependent on the 'puter to run. |
|
|
|
|
@TomVelvet:
The dev here is a good guy...he can help ya figure it out. One to trust. Just a side note: I had the same trouble with a wallet once and it turned out to be my *.conf file. Maybe?
edit; any chance you are using tor? Just me..I'd go back and look @ my .conf tho...might have been a fat-finger day. I have those on occasion...type in too many numbers. lol Or...it's in the wrong place? It's the simple stuff that frustrates.
|
|
|
|
well if you haven't welcomed to Florida let me be the first one to do so Not really 'new' here....been here since '99,  but....it's messin' with my little farm!!  It's bad enough when ya have to do a restart for MS updates, then ya get knocked out by lightning. WTW...lol...nutin' I can do about it. I have batt backup, but it only lasts so long. Sheesh. I do love the sunshine tho. |
|
|
|
I gave up on this coin.So tried I to sell off but I Cant get wallet to work.It connects for a little bit then disconnects.I don't have time to keep downloading wallet after wallet and configuring this and that or keeping up with everysingle post here about every single wallet upgrade.It' Maddening to say the least.  We haven't put out a wallet upgrade for two weeks almost. Are you sure you have the latest? Yes I know that.However its same ole same ole.Gets a few connections then drops them got a little stake back on the 3rd nothing since then.The wallet wont stay connected and always out of sync.Just too much trouble if you ask me.I love high staking coins that's why I took an interest in this one but alas it has been a pain.I cant even dump them lol Just too much trouble.  Well..Howdy Partner...send 'em my way if ya get it going. Donation address is below...Thank ya! |
|
|
|
Question...what happens to your staking multiplier if you get kicked off line due to power loss? It means the wallet is down.
If your power loss is only a few hours, it shouldn't affect your multiplier significantly. There is a mistake in the whitepaper. It is possible to run more than one staking wallet for the same key. I did not realize at the time of writing the whitepaper that your own wallet would reject your 0 reward mints, meaning that you would never be subject to a penalty for "cheating" on the target interval of 2 minutes. There is one exception, which is the "experimental" build I put out during the midst of the biggest problems with Turbo Stake. One person was a victim of not updating and then staking two wallets. Their multiplier went from 18 to 0 and stayed that way 2 days. They had had plenty of time to update from the experimental build, but we will cover them under the Turbo Stake Warranty anyway. As long as you are running the latest client, you won't have to worry about this problem. The latest wallets will not allow you to get penalized for staking two blocks within the target interval. Well..heck...I've got less than 130 coin so it doesn't really matter, does it? lol But...I'm hangin' tough! |
|
|
|
#crysx
I have one of gigabyte's super overclocked and without any additional oc it humms at 1350 gig hertz. That's where I find nvidia's sweet spot on all types of gigabyte's 750 ti's even the standard or low clocked by them. I set it to 1350 gig hertz. Is that the actual clock speed or the setting in what ever program you use to OC? The actual clock speed CapnBDL. No oc.  [/quote] Thx...that's what I thought...I OC to 1400. Can't go higher without a crash. |
|
|
|
#crysx
I have one of gigabyte's super overclocked and without any additional oc it humms at 1350 gig hertz. That's where I find nvidia's sweet spot on all types of gigabyte's 750 ti's even the standard or low clocked by them. I set it to 1350 gig hertz. [/quote] Is that the actual clock speed or the setting in what ever program you use to OC? |
|
|
|
|
I used to really like lightning storms.....not so much since being in FL US. Twice in 24hrs my power has been knocked out!!
|
|
|
|
|
Question...what happens to your staking multiplier if you get kicked off line due to power loss? It means the wallet is down.
edit: Dang it...that's the 2nd time in 24 hrs. my power has gone out. Friggin' lightning.
|
|
|
|
Pool is down ? site does not work.
The pool/site appear to have gone down sometime in the last 12 hours. 24 hours - and still no news. I hope nothing bad has happened to the pool / the operator. Me too...I have a small amount of rented hash but can't access it. |
|
|
|
|
I think a 5 hr. test would be enough, but... We are a bit off topic...a little. I'm on my tablet right now & am sure I have a bookmark for that stat sheet somewhere. I believe it's on my 'puter. I'll get back & look.
Later-
|
|
|
|
OC +200core clock / +250 memory
yup - thats what i thought ... we really need to have some sort of standard that we can compare against ... non oc is the best way on a card by card basis ... every card oc's differently and some cards can be pushed harder than others - with others again being tweaked with firmware and such ... this means that the readings we give here are utterly useless to compare with ... they are great readings to compare oc'ing with - and a table / list that would be created as a comparison would be even better ... who has skills ( and time ) to do such a thing? ... is there already a site that has a comparison ( and settings ) list? ... would luv to see how ccminer-spmod compares to other with the same cards ... #crysx I think a standard is good, but stock clocks probably shouldn't be it. Pure stock clocks are usually so bad, most people don't mine at them - hurts efficiency. A slight OC that pretty much all cards can reach makes sense, though. shouldnt factory clocks BE the standard - even for a 25 minute test? ... a list for stock ( standard rates ) and a list for oc ( using the same card and what has been done to the card ) ... whether its is efficient or inefficient - a standard that the tweaks and overclocks ( with the methods of how it was done ) that can be compared to - is what i believe should be the 'norm' for comparison ... for example - you buy a car that is 'factory stock' and test it ... then you tweak and tune and improve then test - and THEN compare the results ... i believe it should be no different to gpu's ... within reason of course ... no use trying to compare a liquid nitrogen cooled gpu with no way of duplicating it for the home user ... as nice as that would be to see ... #crysx The goals of the GPU manufacturer and the miner are very different. The GPU manufacturer wants to maximize the number of cards that pass the tests, so they set the standards low. Any miner caring about efficiency will OC somewhat if they can - we're not comparing mining usage to regular gaming usage, we're trying to compare a reasonable baseline vs improvements or better OCs. With cars, whether you buy it to sit in traffic, or to race, it's still driving. Mining and gaming are two very different types of things - it's not just doing the same thing faster - which, I think, makes it reasonable to have a baseline more suited to mining (that almost all cards can still do) instead of one that was chosen by the manufacturer, who has entirely different goals in mind. makes sense ... so how would a baseline be agreed upon for comparison? ... there really is no standards to base a lot of this off ( omg - here we go with the extranonce standards issue again ) ... im curious ... #crysx There used to be a spreadsheet out there that users could upload results, etc, too... |
|
|
|
Ok...so I have a working .conf file but I have been trying to come up with a .conf that would allow me to pick the 'coin', (not just the algo), I want to mine. Yaamp allows mining to more than just BTC & I sometimes like to get paid in an altcoin. There has to be a way to rewrite the config to allow it. Right now I have to manually reconfigure it. Can it be written with something like a pulldown menu or such? Any ideas? Anyone? Somebody!!?? Thanks for any help. |
|
|
|
Thanks, Joblo, but my goal wasn't to setup my rig to auto-switch algo's, rather to know which was more profitable for reference. Yes, I know that. The page I pointed to lists the algo normalization factors so you can compare the profitability among all the aglos. Now if only the pool would come back up. Does anybody know if there are stats that list which 'coin' is more profitable and is there anything similar to MinerControl that would switch my rig to mine that way? |
|
|
|
Testing Release_53
x13 algo: error; " Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 714 : an illegal instruction was encountered. "
I made no changes to previous setup being used with switches; -i 18.9 -r 5 -R 10 --cpu-priority 2 -a x13
required a graphics driver reinstall or reboot.
x11 algo: error " Cuda error in func 'quark_blake512_cpu_setBlock_80_multi' at line 706 : an illegal instruction was encountered. "
Again, no changes from previous switches; -g 2 -i 18.3 -r 5 -R 10 --cpu-priority 2 -a x11
required graphics driver reinstall or reboot.
OK...that's all the testing I can do today. Am going back to 51.
later-
That looks like a problem with the ccminer executable. Try recompiling or redownloading as appropriate. Yep...I have to agree. I made some small changes to the intensity, etc., and still ran into the errors. I'll do a new compile and re-test as I don't believe that it would take that much of a change in the -i switch between the different releases. djm34 could be right but...Thx for the idea. |
|
|
|
"If it ain't broke...don't fix it" is what my Daddy always told me. |
|
|
|
|
Show Posts
