Topic: [ANN] [MΣC] Megacoin.co.nz - Forum, Github, Website Now in 18 Languages - page 112. (Read 330752 times)
September 27, 2013, 11:49:33 PM
Diff. at 12 for a prolonged amount of time!!! This is Blasphemy.
September 27, 2013, 07:44:19 PM
i really wish i had 1 million MΣC 
tehe though ive mined over 35k MΣC with my tiny 2.5 m hash and i think ive only ever sold like 1k
mine and hold; buy and hold
tehe though ive mined over 35k MΣC with my tiny 2.5 m hash and i think ive only ever sold like 1k
mine and hold; buy and hold
September 27, 2013, 07:25:10 PM
Trying to solo mine. Have the latest wallet setup and running on port 7950. I have. Number of remote computers mining. Computer wallet is on is behind NAT and port 7950 routed to it.
I have two computer solo mining both gpus and CPU. Have one other CPU mining. Other computer can't connect but ping the URL. They just fail connecting and exit in cgminer. Thoughts what's up here? Can mine all day against a pool on all computers.
Thanks.
JR
I have two computer solo mining both gpus and CPU. Have one other CPU mining. Other computer can't connect but ping the URL. They just fail connecting and exit in cgminer. Thoughts what's up here? Can mine all day against a pool on all computers.
Thanks.
JR
Cant mine you solo? Must set IP megacoin.conf in. Easier might be to stick to pool mining.
September 27, 2013, 07:16:47 PM
Trying to solo mine. Have the latest wallet setup and running on port 7950. I have. Number of remote computers mining. Computer wallet is on is behind NAT and port 7950 routed to it.
I have two computer solo mining both gpus and CPU. Have one other CPU mining. Other computer can't connect but ping the URL. They just fail connecting and exit in cgminer. Thoughts what's up here? Can mine all day against a pool on all computers.
Thanks.
JR
I have two computer solo mining both gpus and CPU. Have one other CPU mining. Other computer can't connect but ping the URL. They just fail connecting and exit in cgminer. Thoughts what's up here? Can mine all day against a pool on all computers.
Thanks.
JR
September 27, 2013, 06:35:47 PM
Aaaaand it has begun
September 27, 2013, 05:32:49 PM
It's definitely a great buy. Still...it's always frustrating paying 3 times as much as we were just a few short weeks ago...and mining at 3 times the difficulty. Smart investors just need to look past that, I suppose.
September 27, 2013, 05:17:57 PM
I'm still buying. MEC is still cheap imho.
September 27, 2013, 05:08:43 PM
Coins now selling for 0.00015000
Wish my current holdings were bigger. =]
Wish my current holdings were bigger. =]
September 27, 2013, 04:55:44 PM
I feel like the difficulty may explode soon with all this cryptsy activity 
September 27, 2013, 04:20:42 PM
Respectfully, I'm not saying it isn't occurring, I'm saying you guys need to take a harder look at your hardware, and settings. Maybe a certain motherboard, memory, PSU, OC settings, or something else. But it sure doesn't point to the client when you are the only ones having the issue.
Are you solomining from four hosts with a fifth host polling the rcp every five minutes for statistics?
Because that's what I'm doing and the megacoin client has always stopped replying on the rcp socket after a while for me.
Explicitly setting rpcthreads made the problem occur less frequently. You still convinced its my hardware?
This exact configuration of miners and qt-wallet-host has mined other coins for weeks at a time and not had this issue.
Respectfully, something in this wallets rpc code is finicky.
September 27, 2013, 04:01:40 PM
MEC just hit 0.00013 on Cryptsy...
September 27, 2013, 03:56:48 PM
very soon my MEC brethren , very soon some MEC things I will contribute
Look forward to it.
September 27, 2013, 03:49:31 PM
very soon my MEC brethren , very soon some MEC things I will contribute
Awesome! Can't wait to hear more.
September 27, 2013, 03:45:50 PM
September 27, 2013, 03:37:00 PM
Kriwest and Symzzi are known scammers. beware.
I don't know about any of their scams, but they sure don't seem to listen very well, or use much logic.
This completely baseless accusation comes from where exactly?
September 27, 2013, 03:32:34 PM
Yah, I still have the issue occasionally.
setting 'rpcthreads=50' in my ini helped a lot. (can't look now, pretty sure that was the setting.)
Now I only have to restart qt once every couple of days.
I've made a habit of quitting qt, force-quitting the lingering process in task manager and restarting it once a morning before I go into work.
Solomines all day that way.
Good luck!
And vtr99, this issue is occurring. I'm confirming it.
(this is on a i7 @ 3Ghz with 6G ram (4 of it free), running win7. no antivirus or other bs daemons, pretty stock.)
setting 'rpcthreads=50' in my ini helped a lot. (can't look now, pretty sure that was the setting.)
Now I only have to restart qt once every couple of days.
I've made a habit of quitting qt, force-quitting the lingering process in task manager and restarting it once a morning before I go into work.
Solomines all day that way.
Good luck!
And vtr99, this issue is occurring. I'm confirming it.
(this is on a i7 @ 3Ghz with 6G ram (4 of it free), running win7. no antivirus or other bs daemons, pretty stock.)
Respectfully, I'm not saying it isn't occurring, I'm saying you guys need to take a harder look at your hardware, and settings. Maybe a certain motherboard, memory, PSU, OC settings, or something else. But it sure doesn't point to the client when you are the only ones having the issue.
September 27, 2013, 03:29:37 PM
very soon my MEC brethren , very soon some MEC things I will contribute
September 27, 2013, 03:26:17 PM
Kriwest and Symzzi are known scammers. beware.
I don't know about any of their scams, but they sure don't seem to listen very well, or use much logic.
September 27, 2013, 03:25:51 PM
Yah, I still have the issue occasionally.
setting 'rpcthreads=50' in my ini helped a lot. (can't look now, pretty sure that was the setting.)
Now I only have to restart qt once every couple of days.
I've made a habit of quitting qt, force-quitting the lingering process in task manager and restarting it once a morning before I go into work.
Solomines all day that way.
Good luck!
And vtr99, this issue is occurring. I'm confirming it.
(this is on a i7 @ 3Ghz with 6G ram (4 of it free), running win7. no antivirus or other bs daemons, pretty stock.)
setting 'rpcthreads=50' in my ini helped a lot. (can't look now, pretty sure that was the setting.)
Now I only have to restart qt once every couple of days.
I've made a habit of quitting qt, force-quitting the lingering process in task manager and restarting it once a morning before I go into work.
Solomines all day that way.
Good luck!
And vtr99, this issue is occurring. I'm confirming it.
(this is on a i7 @ 3Ghz with 6G ram (4 of it free), running win7. no antivirus or other bs daemons, pretty stock.)
September 27, 2013, 03:22:28 PM
I'm done losing uptime over it, I'll just stay in a pool, but instead of being told I'm wrong I thought someone might be interested enough to look into it.
For some reason people seem to get very defensive as soon as someone points out any flaw or possible bug that needs fixing. I don't understand why? It's not a bad thing. If something needs looking into, people SHOULD point it out. It can only help make MEC better.
First of all, there is no evidence for a possible bug in the client. His hardware is minimal at best if he is running 4x 7950's on a 1250 watt PSU, and 8gb of memory. It doesn't make much sense to blame the least likely thing when you can see obvious issues. I have setup dozens of mining rigs, and never seen an issue caused by the Megacoin client. He gives us very little information, other than letting us know his system hardware is marginal, and then blames the client.
It's not about being defensive, it's about using common sense when troubleshooting!
Jump to: