Now I'm having a compiling issue. I'm getting the following error. Anybody have a clue? build/ui_overviewpage.h:205:32: error: ‘LogText’ is not a member of ‘Qt’ label_2->setTextFormat(Qt::LogText); ^ make: *** [build/overviewpage.o] Error 1
Ubuntu Linux compile Sync QT Wallet Instructions1- sudo apt-get update 2- sudo apt-get dist-upgrade 3- sudo apt-get install g++ libboost-all-dev qt4-qmake libqt4-dev build-essential libssl-dev libdb5.1-dev libdb5.1++- libcurl4-openssl-dev 4- qmake USE_UPNP=- 5- make Only part of that I didn't do was step 4. Has UPNP been removed, as I do have the proper dependencies for it. I have compiled well over a hundred wallets without this error I'll try it without UPNP when I get home and let you know. From dev: "His version of QT needs to do this: try to find in this .ui file string “Qt::LogText” and change it – Qt::TextFormat" That didn't work. But what did was forcing qmake to use the lower version (QT4) as I had both installed. I didn't know how to do this, so in case somebody else runs into this, It works like this: Note that I compiled WITH UPNP support, and static libraries for portability, so some of the command lines options, particularly STATIC=1, are optional. qmake-qt4 sync-qt.pro make STATIC=1 -f Makefile This worked, and the new wallet is very pretty
|
|
|
Quick, important, question...
Do we have a list of all pools that have made the switch or will be making the switch prior to the fork? I'd like to make sure that I'm not going to mine on a bad chain.
It's a very good question. I don't have the answer, though this change shouldn't affect Proof of Work mining in the least. I'm not certain of that, however, and if nobody else has contacted the pools, I will. I know of dsync and miner's point. I'll check for others.
|
|
|
Any mac users out there that can compile a wallet for mac, it would be greatly appreciated. To my knowledge, everybody currently working on the wallet is either a Windows or Linux user.
|
|
|
Just to let everyone know... Just bought few TEK from cryptsy, did withdraw, and minutes later received it... Seems they are sorted. (Test first to be safe IMO)
There is nothing new for me. Still 1775 TEK pending. They only pay small amounts immediately. For larger amounts, they do not have the money. Why pay, when you can 40% more on Monday. nope. they have staking disabled.
|
|
|
Now I'm having a compiling issue. I'm getting the following error. Anybody have a clue? build/ui_overviewpage.h:205:32: error: ‘LogText’ is not a member of ‘Qt’ label_2->setTextFormat(Qt::LogText); ^ make: *** [build/overviewpage.o] Error 1
Ubuntu Linux compile Sync QT Wallet Instructions1- sudo apt-get update 2- sudo apt-get dist-upgrade 3- sudo apt-get install g++ libboost-all-dev qt4-qmake libqt4-dev build-essential libssl-dev libdb5.1-dev libdb5.1++- libcurl4-openssl-dev 4- qmake USE_UPNP=- 5- make Only part of that I didn't do was step 4. Has UPNP been removed, as I do have the proper dependencies for it. I have compiled well over a hundred wallets without this error I'll try it without UPNP when I get home and let you know. From dev: "His version of QT needs to do this: try to find in this .ui file string “Qt::LogText” and change it – Qt::TextFormat" Just got home. I'll do that in a few minutes and let y'all know.
|
|
|
Now I'm having a compiling issue. I'm getting the following error. Anybody have a clue? build/ui_overviewpage.h:205:32: error: ‘LogText’ is not a member of ‘Qt’ label_2->setTextFormat(Qt::LogText); ^ make: *** [build/overviewpage.o] Error 1
Ubuntu Linux compile Sync QT Wallet Instructions1- sudo apt-get update 2- sudo apt-get dist-upgrade 3- sudo apt-get install g++ libboost-all-dev qt4-qmake libqt4-dev build-essential libssl-dev libdb5.1-dev libdb5.1++- libcurl4-openssl-dev 4- qmake USE_UPNP=- 5- make Only part of that I didn't do was step 4. Has UPNP been removed, as I do have the proper dependencies for it. I have compiled well over a hundred wallets without this error I'll try it without UPNP when I get home and let you know.
|
|
|
Ok, My friend at Cryptsy just got back to me. There was a minor problem with their system, and the hot wallet didn't get refilled automatically. He's doing it now. Everything should be good shortly.
|
|
|
If I withdrawal from Cryptsy to the new wallet, will the coins deposit OK??
Thanks, Jason
It's the same wallet.dat, nothing major is changed. It's just an update to the code. Everything works the same, except that when the fork block is reached, staking should work again. Prior to the fork, all remains the same. EDIT: I just spoke with one of the Cryptsy guys who's a friend. He's looking into the current issues.
|
|
|
Is someone informing Cryptsy and the various mining pools of the wallet update?
Yes. Some of the people who helped work for Cryptsy, they've been aware and involved for the whole time. As to the guys still having trouble with the .dll's, I'm not sure what's going wrong. Perhaps the install in 7 is not adding the missing dll's to your general path. Use the search function to find where they are installed, and copy them into the same directory as your Tekcoin-qt.exe file. That SHOULD solve it. To the gentleman who is getting the block index error, I suggest moving your wallet.dat to a safe place and try to sync from nothing at all. If that works, then delete the new wallet.dat and copy the old one in. That should solve it. If not, PM me or Thundertoe, we'll get you sorted.
|
|
|
How do I get the wallet updated?
Step by step instruction please.
Save wallet.dat and remove old wallet or is it just a new Tekcoin exe file?
It's just a new Tekcoin-qt.exe or daemon (though you'll have to compile that from source). You're wallet.dat and blockchain data in the .tekcoin (linux) or appdata\roaming\Teckcoin (Windows) folders are not affected. Just run the new client instead of the one you had previous.
|
|
|
Ok, here's the fix for those of you with missing dll's. Install this (light version is fine) http://slproweb.com/products/Win32OpenSSL.htmlshould solve the problems. Edit: Credit where it's due. Argakiig, both for the Windows wallet and this fix
|
|
|
hi!
My zs wallet won't sync, i added nodes from OP, even deletet blockchain and trying to redownload but no luck
wallet version v1.0.1.5
How and where i can now withdrawal from bittrex ?
We have no connections either, so even if you could sync, we couldn't send anything "version" : "v1.0.1.5-ZS", "protocolversion" : 60015, "walletversion" : 60000, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 171641, "timeoffset" : 0, "connections" : 0, thanks, richie@bittrex I'll look into it tomorrow. I am going to bed right now, but I can probably set up a node, or at least make sure my wallet's node is known.
|
|
|
Ive downloaded and installed the new wallet on windows 7 32bit and it works. Should it start staking blocks its missed from last week? Its still showing the weight
It will approximately monday. The code is set to change at block 506500, after which staking should resume. Reason is because it IS a hard fork, it gives everyone time to get the new wallet, sort any problems, etc. The new wallet will work just fine for everything but staking prior to the fork, and after that all of your weighted blocks should start staking. Given the long interval while it was getting fixed, there will probably be quite a few orphans and a lot of competition for stake in the first few days past the fork, so nobody panic if you see higher than usual orphans. Again, just to make sure everyone knows, no stake weight has been lost in this fix. What it does is reduce the difficulty to stake significantly, and there's a patch going forward to make sure this particular incident can never happen again. Everything should be fully functional as of block 506500. Those of you with the .dll issues on Windows, it is being addressed. The smart guys have gone to bed, so I'm guessing sometime tomorrow. Please post up any problems here, everybody involved in the fix is paying attention. I don't know if there's a Mac wallet in the works or not, but if anybody out there cares to compile and post one up, I'm sure your fellow Mac users would love you for it. I'm running ubuntu, as I mentioned earlier, and so far the only problem I had was an ID 10 T error on my part. I forgot to delete the test chain and a line in my .conf file that made sure I connected to it. Since it was a deliberate fork and the test node was no longer up, I spent about an hour trying to get a connection before I realized what I'd done But once that was fixed, I caught 5 connections in seconds and the wallet is syncing up. Caveat to anyone doing off chain tests: Back up your blockchain or you'll be syncing for a LONG time. Not as bad as Bitcoin, but not trivial either.
|
|
|
same here win 7 64 bit missig dll, help fix pls
found missing libeay32.dll file on my system , where do i copy and paste to?/
ps. biomech , i only know how to use windows unless you care to teach me how to use other system , gui base hopefully . suspect johan only know windows also
I recently stopped using windows, and have no quarrel with it overall. But Vista and 8.1 are horrible. 7 kicks ass, and so did XP, though it's kind of limp now. I currently use ubuntu, and I like it better, but I'm far from being an expert. Novice would actually probably be overstating it, but I'm learning quick On topic, paste the .dll's in to the same directory as the Tekcoin-qt.exe file. i have dll on system and i copy to tek dir, and the same - TLSv1_1_client_method procedure entry point could not be located in the dynamic link library libeay32.dll found (translate) I think Argakiig has gone to bed like a smart person, but I've passed on the info. It was working on his system and in sync when he uploaded it to Thundertoe. We'll get it sorted
|
|
|
same here win 7 64 bit missig dll, help fix pls
found missing libeay32.dll file on my system , where do i copy and paste to?/
ps. biomech , i only know how to use windows unless you care to teach me how to use other system , gui base hopefully . suspect johan only know windows also
I recently stopped using windows, and have no quarrel with it overall. But Vista and 8.1 are horrible. 7 kicks ass, and so did XP, though it's kind of limp now. I currently use ubuntu, and I like it better, but I'm far from being an expert. Novice would actually probably be overstating it, but I'm learning quick On topic, paste the .dll's in to the same directory as the Tekcoin-qt.exe file.
|
|
|
Dev, please provide an update on the status of the new wallet, testing, code peer review, etc. Thanks here you go for the source, i still need to dig up a windows compiled version, ill figure that out tomorrow. https://github.com/maxxine/TEKhardfork block on 506500 apprx 4-6 days Thanks to defaced, presstab, tranz, biomech, dyoungi, everyone who helps i know there are more, and thank you too. here is the new windows wallet with the fix thanks Argkiig: https://docs.google.com/file/d/0BwGL9FkcBurENzRxaTVURllUVkk/editwin wallet not function properly - TLSv1_1_client and SSLEAY32.dll - problem - not start - test on Vista 64 and 32 bit 2003 server - need repair this Same problem here. Windows 7 - 64bit. But I installed Tek in the Programfilesx86 folder. Some DLL's seem to be missing. Downloading them from the net made my virusscanner pop-up. Lot of virusses spread using DLL dowload sites. Will wait for the fix from the dev. That will be more safe I think. It's being looked into now. However, it's likely you'll find the missing dll's in most other coin's base directory. Just copy it to the tek directory and see if it works. Worst case you waste a bit of hard drive space. I don't know what the first one is, but the second one is an SSL .dll, so it's a safe bet that if you have SSL installed, you have the dll in your system. On a nearly unrelated note, Johan? Why would you inflict yourself with Windows Vista?
|
|
|
Why pool mine ASC? Solo or a private pool using Nomp at this diff is easy and you pay no fees.
|
|
|
Now I'm having a compiling issue. I'm getting the following error. Anybody have a clue? build/ui_overviewpage.h:205:32: error: ‘LogText’ is not a member of ‘Qt’ label_2->setTextFormat(Qt::LogText); ^ make: *** [build/overviewpage.o] Error 1
|
|
|
Trying to get the train back on the tracks Sorry I haven't gotten back to you guys. Had a really bad day today. I'll have more shortly. Probably tomorrow.
|
|
|
Thundertoe already knows this and it will be fixed. There is a minor error in the new release. It shows version 1.1 Aside from that, we tested this pretty heavily over a couple days on a test chain, and it staked without issue. Only downside for me is having to forgo all those pretty stakes since they were on a deliberate fork Thanks to Tranz, Defaced, Presstab, Thundertoe and everyone else who helped out, and thanks for the community for no dumping into oblivion!
|
|
|
|