Hey guys I just installed the new wallet release... All went without a hitch...
The new installer was much faster then before...Woot..
The updated GUI much more streamlined and seems much more responsive so far... Good job guys....
Will experiment when I get home hopefully the chain will be downloaded by then.....How Long does it take to synchronize from scratch?
Again good job guys keep up the good work
Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 496. (Read 1192347 times)
March 26, 2017, 02:31:04 PM
March 26, 2017, 02:16:42 PM
There is the Swing wallet for people who want a basic wallet
March 26, 2017, 02:01:26 PM
yeah i suggest a easy wallet too i only want to store my kmd at a safe place and maybe then the bittrex wallet maintaince will go away too.
price will go up higher etc. pp.
price will go up higher etc. pp.
March 26, 2017, 01:58:11 PM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Did you try to the zip or installer release? i.e.
AgamaApp-0.1.6.0e-beta-win-x64.zip
or
AgamaApp-0.1.6.0e-beta-windows-installer.exe
Do you have Visual C++ Redistributable Packages installed? The installer releases install these to your system. Double check you have them.
https://www.microsoft.com/en-nz/download/details.aspx?id=48145
Hi Devs,
-Yes i tried both of the versions, zip and installer.
-Yes i have the Visual C++ Redistributable Packages installed installed too.
But still have the same error on my Windows 10 laptop computer.
But it working on my Windows 10 desktop computer...but it not working on my Windows 10 laptop computer.
As i said earlier, the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe
i am using a laptop too (netbook)
Hi Devs,
Can i suggest you guys to focus on releasing the simple Windows wallet for Komodo first.
Because it seem you still need a lots of time to iron out all the bugs from Agama wallet. At least after you guys releasing the simple Komodo wallet, then you guys can get back to upgrading Agama wallet and adding all the Apps and Decentralize Exchange into Agama.
I remember not long ago, that you guys wanted to release the update for the Windows wallet..so hope it will be out soon.
By the way, I have no plan to sell my KMD any time soon...just need a good wallet to check my 5% dividend everyday
March 26, 2017, 12:52:34 PM
There is still alot of technical problem that this project is still encountering, this doesn't built trust in the capapcity of the team to deliver on their promises, I think that is the reason the price is currently below the ICO price when most of the Altcoins are doing perfectly well in the market
Don't bother getting a serious answer... they will call you a troll and give you negative feedbacks. This coin is a waste of time.
Actually, it's you who are the waste of time. It's very clear to see that you have never coded anything in you life let alone a complicated system such as this. But, some of us do find your comments comical, although I'm sure they were not intended to amuse, so, there is that entertainment factor.
March 26, 2017, 11:47:51 AM
There is still alot of technical problem that this project is still encountering, this doesn't built trust in the capapcity of the team to deliver on their promises, I think that is the reason the price is currently below the ICO price when most of the Altcoins are doing perfectly well in the market
Don't bother getting a serious answer... they will call you a troll and give you negative feedbacks. This coin is a waste of time.
Then why you are wasting your time here ??
March 26, 2017, 11:36:28 AM
There is still alot of technical problem that this project is still encountering, this doesn't built trust in the capapcity of the team to deliver on their promises, I think that is the reason the price is currently below the ICO price when most of the Altcoins are doing perfectly well in the market
Don't bother getting a serious answer... they will call you a troll and give you negative feedbacks. This coin is a waste of time.
March 26, 2017, 11:29:00 AM
There is still alot of technical problem that this project is still encountering, this doesn't built trust in the capapcity of the team to deliver on their promises, I think that is the reason the price is currently below the ICO price when most of the Altcoins are doing perfectly well in the market
March 26, 2017, 11:26:52 AM
[/quote]
i fix all issues (also in node code too) and pool works very well now.
Komodo daemon in 2x faster now, nice work jl777!
i add port 6666 for big gpus rigs with max diff(16)
( !! NOT USE ZCASH ADDRESS to T-ADDRESS AND Z_ADDRESS !! )
HOW TO CONNECT
To mine KMD just use any ZCASH (EquiHash) miner with komodo address
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1 ( Auto VarDiff - suitable for CPU and GPU )
example : ZecMiner64.exe -zpool komodominingpool.com:6666 -zwal komodo_address -zpsw x -allpools 1 (Max VarDiff - suitable for big GPUs RIG )
Happy mining komodo users
Cheers
[/quote]
When should we expect payouts ? also i'm missing statistics in the pool for recent blocks, projected payout based on shares and all info related to payments.
March 26, 2017, 11:02:21 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Did you try to the zip or installer release? i.e.
AgamaApp-0.1.6.0e-beta-win-x64.zip
or
AgamaApp-0.1.6.0e-beta-windows-installer.exe
Do you have Visual C++ Redistributable Packages installed? The installer releases install these to your system. Double check you have them.
https://www.microsoft.com/en-nz/download/details.aspx?id=48145
Hi Devs,
-Yes i tried both of the versions, zip and installer.
-Yes i have the Visual C++ Redistributable Packages installed installed too.
But still have the same error on my Windows 10 laptop computer.
But it working on my Windows 10 desktop computer...but it not working on my Windows 10 laptop computer.
As i said earlier, the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe
i am using a laptop too (netbook)
March 26, 2017, 10:45:41 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Did you try to the zip or installer release? i.e.
AgamaApp-0.1.6.0e-beta-win-x64.zip
or
AgamaApp-0.1.6.0e-beta-windows-installer.exe
Do you have Visual C++ Redistributable Packages installed? The installer releases install these to your system. Double check you have them.
https://www.microsoft.com/en-nz/download/details.aspx?id=48145
Hi Devs,
-Yes i tried both of the versions, zip and installer.
-Yes i have the Visual C++ Redistributable Packages installed installed too.
But still have the same error on my Windows 10 laptop computer.
But it working on my Windows 10 desktop computer...but it not working on my Windows 10 laptop computer.
As i said earlier, the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe
March 26, 2017, 10:37:00 AM
i have visual c++ installed. i used the windows installer
Ok, did you try also the zip release? Maybe it works, there could be a bug in the installer itself.
I'll report this issue to our dev
I want to withdraw my coins to the bittrex exchange but It seems some issues which are reported here so Should I make a withdrawal or wait for new information from DEV?
I think currently the Bittrex withdrawals are disabled.
Did you try the zip release? Does it work for you?
March 26, 2017, 10:33:38 AM
i have visual c++ installed. i used the windows installer
Ok, did you try also the zip release? Maybe it works, there could be a bug in the installer itself.
I'll report this issue to our dev
I want to withdraw my coins to the bittrex exchange but It seems some issues which are reported here so Should I make a withdrawal or wait for new information from DEV?
March 26, 2017, 10:27:54 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
my antivirus (kaspersky security 17) detected something as a thread i cleaned it up but this error showed up before
after i clicked on ok at that error the loading screen of agama daemon was showing up but nothing happened.
after this nothing happens when you get that error.
Seems to have installed at wrong place. Try zip file and see how it works.
March 26, 2017, 10:27:30 AM
Bittrex wallet is still under maintenance. Has anyone from the Komodo community been in contact with them? Missing out on staking rewards while they figure out their wallet issues. (yes, I'm well aware that this isn't Bittrex support - I just figured I'd ask here first)
Of course we are in touch. I advised them to wait until after the 250000 changes kick in to make sure there are no issues.Good thing too, as we found that there is underpayment for interests with the current version for mid sized utxo. exact size depends on when minutes * 5% nValue overflows 64 bits.
I had a feeling that during my sleep deprived period I made some errors, so we are continuing to review and I have made a new version that will activate proper interest calculations as of April 5th. Just too many updates recently and this gives a bit more than a week to update. What this means is that if you spend utxo that overflows before April 5th, it will not give you all the interest.
Running the 250000 version for now is fine, just another update will be required before April 5th.
March 26, 2017, 10:24:29 AM
i have visual c++ installed. i used the windows installer
Ok, did you try also the zip release? Maybe it works, there could be a bug in the installer itself.
I'll report this issue to our dev
March 26, 2017, 10:23:09 AM
Bittrex wallet is still under maintenance. Has anyone from the Komodo community been in contact with them? Missing out on staking rewards while they figure out their wallet issues. (yes, I'm well aware that this isn't Bittrex support - I just figured I'd ask here first)
Yes, we asked them to disable deposits/withdrawals due to the recent attacks (4 in total) we experienced. Thus no one can lose money while we implement the bug fixes. Like jl777 explained previously, these attacks happen after we publish the fix for a known attack-vector as the code is open source.
There's one crucial block we need to get over with, and after that we will ask them to enable withdrawals/deposits again. It's better to play it safe.
March 26, 2017, 10:21:28 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Did you try to the zip or installer release? i.e.
AgamaApp-0.1.6.0e-beta-win-x64.zip
or
AgamaApp-0.1.6.0e-beta-windows-installer.exe
Do you have Visual C++ Redistributable Packages installed? The installer releases install these to your system. Double check you have them.
https://www.microsoft.com/en-nz/download/details.aspx?id=48145
i have visual c++ installed. i used the windows installer
March 26, 2017, 10:19:05 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Did you try to the zip or installer release? i.e.
AgamaApp-0.1.6.0e-beta-win-x64.zip
or
AgamaApp-0.1.6.0e-beta-windows-installer.exe
Do you have Visual C++ Redistributable Packages installed? The installer releases install these to your system. Double check you have them.
https://www.microsoft.com/en-nz/download/details.aspx?id=48145
March 26, 2017, 09:17:16 AM
If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:
Quote from: grewalsatinder
I see 1 question asked again and again, and someone also asked that same in PM. So, sharing the answer here in public channel as well:
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
Quote
I had a question about Iguana's name change
Why as it done?
Why as it done?
Iguana Desktop execution file name was Iguana with capital I, and iguana daemon which provides iguana APIs was iguana with small letter i
now we have noticed the wallet sometimes doesn’t kill the previous iguana daemon, and the session keeps running using that.
user starts the wallet again, and the new session password doesn’t match with the previous session password running iguana daemon process.
that leads to non-responsive, non-working Desktop.
So, the solution was when the Desktop Wallet starts, kill any previously running iguana daemon, and then start the new iguana daemon process.
But, there’s the problem
to the kill command it doesn’t really matter if it’s small letter iguana or capital letter Iguana. It’ll just kill that.
So, activating that code resulting in killing the Desktop Iguana Process, and that made impossible to solve this technical issue.
On the other hand from marketing point of view, it was quite confusing talking about Iguana Desktop an iguana core!
So, the most ideal solution! Rename the Desktop Wallet name!
Since we are at very small scale and still building our userbase it doesn’t cost anything to do this change.
And we renamed Iguana Desktop to Agama Desktop.
ok but i have now a real issue when i start agama i get that error
Hi Devs,
I got the same error when i installed wallet versions 0.1.5 & 0.1.6 on my Windows 10 laptop computer too.
But i have no problems to installed Agama wallet on my Windows 10 desktop computer.
I only having this error on my Window 10 laptop computer...the only version that can work on my laptop computer is version "IguanaApp-0.1.4-beta-windows-installer.exe"
EDIT: i already deleted everything in my AppData directory before i installed the wallet too
Jump to: