[ANN] TagCoin - Multi Token Wallet and Trading Platform - page 36.

ehalvers

hero member

Activity: 513

Merit: 500

Crypto ehalvers

Quote from: FortuneSeeker on February 16, 2014, 07:37:36 PM

Can someone please tell me where I'm getting a problem with this .bat file using sgminer if it matters

color 02
timeout /t 30
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer kernel : scrypt130302 -I 13 --thread-concurrency 8192,8192,8192 --lookup-gap 2 -g 2 -w 256 --gpu-engine 1065,1065,1065 --gpu-memclock 1500,1500,1500 --temp-cutoff 90,90,90 --temp-overheat 85,85,85 --temp-target 68,68,68 --auto-fan --expiry 1 --scan-time 1 --queue 0 -o stratum+tcp://eu.pickaxe.cc:3330 -u Fortuneseeker.warflow1 -p kensei79

I've taken the settings from this guy

https://litecointalk.org/index.php?topic=12369.0;prev_next=next#new

though i have no idea what the expiry/scantime/queue bit do. but he has the same cards exactly as i do and is getting 700 + hash. anyway I get the "unexpected extra commandline arguments" error. I took out the expiry/scan-time/queue parts and got the same thing. I noticed that each card has its own setting and though he has different ones for each card for gpu engine as i'm starting i was keeping mine the same.

any help please

I dont think you need to tell sgminer to use scrypt as that is the only thing it does.

Let me know if that fixes it haha. I have a couple rigs using sgminer on windows 7

ClutchThese

sr. member

Activity: 448

Merit: 250

make a .bat file with this:

Code:

sgminer.exe -o stratum+tcp://usa2.wemineltc.com:3334 -u worker -p password

then create a .conf file and edit the settings in .conf

don't bother will all that other ish.

FortuneSeeker

member

Activity: 107

Merit: 10

Can someone please tell me where I'm getting a problem with this .bat file using sgminer if it matters

color 02
timeout /t 30
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer kernel : scrypt130302 -I 13 --thread-concurrency 8192,8192,8192 --lookup-gap 2 -g 2 -w 256 --gpu-engine 1065,1065,1065 --gpu-memclock 1500,1500,1500 --temp-cutoff 90,90,90 --temp-overheat 85,85,85 --temp-target 68,68,68 --auto-fan --expiry 1 --scan-time 1 --queue 0 -o stratum+tcp://eu.pickaxe.cc:3330 -u Fortuneseeker.warflow1 -p kensei79

I've taken the settings from this guy

https://litecointalk.org/index.php?topic=12369.0;prev_next=next#new

though i have no idea what the expiry/scantime/queue bit do. but he has the same cards exactly as i do and is getting 700 + hash. anyway I get the "unexpected extra commandline arguments" error. I took out the expiry/scan-time/queue parts and got the same thing. I noticed that each card has its own setting and though he has different ones for each card for gpu engine as i'm starting i was keeping mine the same.

any help please

ClutchThese

sr. member

Activity: 448

Merit: 250

Well, if you don't want to build it... use someone elses built version:

http://www.reddit.com/r/litecoinmining/comments/1va8g2/ann_sgminer_400_release/ceqvjwn

you can download 4.1 or 4.0 from that thread. Then build a .bat file and start mining.

FortuneSeeker

member

Activity: 107

Merit: 10

OK yeah I found that.. about 2 seconds after I said I can't see it... sheessh this head cold makes me slow!

Ok now whats this about 'building' it Can't I just use it as it comes? like I did cgminer? (obviously I've got to create my .bat file)

ClutchThese

sr. member

Activity: 448

Merit: 250

github download link is on the right side... you'll see "download as zip"

click that and you're downloading.

FortuneSeeker

member

Activity: 107

Merit: 10

Quote from: ClutchThese on February 16, 2014, 04:27:41 PM

I use it. I have r9 290's and this is the only miner i know of that doesn't crash on restarts.

http://www.reddit.com/r/litecoinmining/comments/1va8g2/ann_sgminer_400_release/

that's the reddit announcement for 4.0, they are on 4.1 i believe now. But that post should link to the newest version.

I don't see the download link though.. probably being dumb Sad

I don't understand GIthub either... a bunch of files but for what and where is the download link

ClutchThese

sr. member

Activity: 448

Merit: 250

I use it. I have r9 290's and this is the only miner i know of that doesn't crash on restarts.

http://www.reddit.com/r/litecoinmining/comments/1va8g2/ann_sgminer_400_release/

that's the reddit announcement for 4.0, they are on 4.1 i believe now. But that post should link to the newest version.

FortuneSeeker

member

Activity: 107

Merit: 10

Does anyone here use sgminer and understand how to 'build' it, or save me the trouble and tell me where i can just download the complete thing

cheers

ClutchThese

sr. member

Activity: 448

Merit: 250

what if it doesn't?

TAG has, by far, one of the most dedicated Dev teams. I don't like the orphan issues, just the same as all of you. BUT, i do believe in the longevity of the coin. It will be fixed, and the price will go up. What you do depends on you.

jtphenom

member

Activity: 110

Merit: 10

Quote from: ClutchThese on February 16, 2014, 01:04:38 PM

Quote from: ny2cafuse on February 16, 2014, 11:41:23 AM

Quote from: tagbond on February 16, 2014, 12:26:10 AM

I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.

Hard fork update with code that puts a lock on the sync process unless the user is updated to the latest version. If I remember correctly, I'm pretty sure it's how Litecoin did it last year. Basically, "if version !=x then sync=false". And they get a big red update notice in the area that says "you need to update you wallet or else you're a dope".

Force them to update, and let's eliminate this variable.

-Fuse

This ^^^

100 times.

I'm stocking up on TAG... so the longer it goes on, the better for me.

The longer it goes on the better for you? Why, cause the price is so low? What if it completely crashes because the problem takes too long to get fixed? lol

ClutchThese

sr. member

Activity: 448

Merit: 250

Quote from: ny2cafuse on February 16, 2014, 11:41:23 AM

Quote from: tagbond on February 16, 2014, 12:26:10 AM

I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.

Hard fork update with code that puts a lock on the sync process unless the user is updated to the latest version. If I remember correctly, I'm pretty sure it's how Litecoin did it last year. Basically, "if version !=x then sync=false". And they get a big red update notice in the area that says "you need to update you wallet or else you're a dope".

Force them to update, and let's eliminate this variable.

-Fuse

This ^^^

100 times.

I'm stocking up on TAG... so the longer it goes on, the better for me.

ny2cafuse

legendary

Activity: 1582

Merit: 1002

HODL for life.

Quote from: tagbond on February 16, 2014, 12:26:10 AM

I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.

Hard fork update with code that puts a lock on the sync process unless the user is updated to the latest version. If I remember correctly, I'm pretty sure it's how Litecoin did it last year. Basically, "if version !=x then sync=false". And they get a big red update notice in the area that says "you need to update you wallet or else you're a dope".

Force them to update, and let's eliminate this variable.

-Fuse

tagbond

hero member

Activity: 627

Merit: 501

It's safe as far as we are concerned yes..

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Quote from: tagbond on February 16, 2014, 12:26:10 AM

I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.

Funny reading this thread is like reading the Orb thread last month. Same excuse's from the dev almost verbatim.

Why don't you get in touch with Mad_Max like I recommended. He probably will only take a small bounty to fix your issue.

He fixed ORB because he liked the coin and the dev turned it into a all out war instead of adopting the fix. But they have worked it out and Max is now a dev.

Lurkmode on.

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Quote from: vesperwillow on February 14, 2014, 01:03:13 PM

I haven't had time to look at the code, but I posted the relevant sniippets in case someone can digest the math from the code. I won't be available for the next few days, for anything other than quick message responses. Otherwise I would've looked into it..

There's still orphans occuring, not as bad as before, but it's odd how some pools seem to get waves and others don't. We're trying to look into possibilities why. I've been focused on POTcoin lately, and even with significant hash flux, it's never been an issue on that coin.

Hehehe He said Hash.

Just checking to see if this coin is safe yet. I'm guessing no?

tagbond

hero member

Activity: 627

Merit: 501

I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.

ahmed_bodi

hero member

Activity: 518

Merit: 500

Bitrated user: ahmedbodi.

Quote from: tagbond on February 15, 2014, 05:59:00 AM

@vesperwillow - we wrote that code, and so far we don't see anything wrong with it. Can you?..As for orphans being created from old confirmed blocks, we are at a loss as to explain this. Can you say what other coins this is happening to?

maxpower just created a mac version of the 1.0.5 wallet:
https://www.dropbox.com/s/gyyra84qm9zcdmu/TagCoin-Qt-1.0.5-Mac.zip

Just trying to push that up to the server from here in Korea, but not going up just yet...can use the link above till then..will work on the ubuntu version when I am back in the office on Tuesday.

the main ones that its happened to is orbitcoin, i believe android tokens, starcoin, colossuscoin and possibly others may have had this issue

tagbond

hero member

Activity: 627

Merit: 501

@vesperwillow - we wrote that code, and so far we don't see anything wrong with it. Can you?..As for orphans being created from old confirmed blocks, we are at a loss as to explain this. Can you say what other coins this is happening to?

maxpower just created a mac version of the 1.0.5 wallet:
https://www.dropbox.com/s/gyyra84qm9zcdmu/TagCoin-Qt-1.0.5-Mac.zip

Just trying to push that up to the server from here in Korea, but not going up just yet...can use the link above till then..will work on the ubuntu version when I am back in the office on Tuesday.

crypto777

full member

Activity: 221

Merit: 100

TAGCOIN - ON POSITION 55 - TRADING ACTIVITY ON CRYPTSY.COM

Here Cryptsy Live Statistics - http://live.myip.ms

Topic: [ANN] TagCoin - Multi Token Wallet and Trading Platform - page 36. (Read 301277 times)