Bitcoin Forum
December 03, 2016, 10:10:33 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 [117] 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 ... 232 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 481584 times)
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
June 14, 2013, 03:37:47 PM
 #2321

Ah yes.  Armory doesn't support compressed keys, yet.  They were going to be supported with the new wallet format, but that got put on hold for obvious reasons.  Once RAM-reduction is done, maybe I'll finally be able to finish that.

Until then, Armory can't handle compressed keys.  At all.

Good, it's no news then!
Maybe put some hint into the error message?
"Error importing.. invalid.. maybe compressed?"
So people don't throw away good keys or similar.
Nah, probably not important at all.

Cheers!

Ente

If you look at the code, I do have a condition that warns about compressed keys... but I guess the "This number is too big" warning somehow takes precedence.  So I had thought about it... I guess I just didn't do a good job Smiley

https://github.com/etotheipi/BitcoinArmory/blob/master/qtdialogs.py#L2427

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
1480803033
Hero Member
*
Offline Offline

Posts: 1480803033

View Profile Personal Message (Offline)

Ignore
1480803033
Reply with quote  #2

1480803033
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480803033
Hero Member
*
Offline Offline

Posts: 1480803033

View Profile Personal Message (Offline)

Ignore
1480803033
Reply with quote  #2

1480803033
Report to moderator
1480803033
Hero Member
*
Offline Offline

Posts: 1480803033

View Profile Personal Message (Offline)

Ignore
1480803033
Reply with quote  #2

1480803033
Report to moderator
1480803033
Hero Member
*
Offline Offline

Posts: 1480803033

View Profile Personal Message (Offline)

Ignore
1480803033
Reply with quote  #2

1480803033
Report to moderator
Ente
Legendary
*
Offline Offline

Activity: 1834



View Profile
June 14, 2013, 03:42:54 PM
 #2322

Ah yes.  Armory doesn't support compressed keys, yet.  They were going to be supported with the new wallet format, but that got put on hold for obvious reasons.  Once RAM-reduction is done, maybe I'll finally be able to finish that.

Until then, Armory can't handle compressed keys.  At all.

Good, it's no news then!
Maybe put some hint into the error message?
"Error importing.. invalid.. maybe compressed?"
So people don't throw away good keys or similar.
Nah, probably not important at all.

Cheers!

Ente

If you look at the code, I do have a condition that warns about compressed keys... but I guess the "This number is too big" warning somehow takes precedence.  So I had thought about it... I guess I just didn't do a good job Smiley

https://github.com/etotheipi/BitcoinArmory/blob/master/qtdialogs.py#L2427

..one of the things I love about how you work - you look forward and solve possible obstacles before anyone comes up with them! :-)

Ente
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
June 15, 2013, 03:17:55 PM
 #2323

THANK YOU!

I have been receiving substantial donations recently, but donors frequently don't identify themselves, so I have no one to thank!  In recent past I have gotten quite a a few 0.2-1.0 donations, and been taking my fiancée out to nice dinners with it Smiley.  I have been meaning to broadcast a thank-you post, then this donation from yesterday reminded me to do it!


People in this community are quite generous, and I'm thrilled to see people are impressed enough with Armory to make such substantial donations!  It means a lot to me.

So thank you!
-Alan


P.S - If you want to identify yourself to me--publicly or privately--I'll be happy to send you a T-shirt and Armory-branded USB key.  This goes for anyone donating the equiv of $50 or more.  I have only a few T-shirts left from the original crowdfunding a year ago, all black, L or XL (and maybe an XXL).  >= $20 gets a USB key (I'd do it for less, but these branded USB keys are surprisingly expensive when you don't order 10,000 of them!).

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Rampion
Legendary
*
Offline Offline

Activity: 1078


View Profile
June 15, 2013, 05:55:08 PM
 #2324

THANK YOU!

I have been receiving substantial donations recently, but donors frequently don't identify themselves, so I have no one to thank!  In recent past I have gotten quite a a few 0.2-1.0 donations, and been taking my fiancée out to nice dinners with it Smiley.  I have been meaning to broadcast a thank-you post, then this donation from yesterday reminded me to do it!


People in this community are quite generous, and I'm thrilled to see people are impressed enough with Armory to make such substantial donations!  It means a lot to me.

So thank you!
-Alan


P.S - If you want to identify yourself to me--publicly or privately--I'll be happy to send you a T-shirt and Armory-branded USB key.  This goes for anyone donating the equiv of $50 or more.  I have only a few T-shirts left from the original crowdfunding a year ago, all black, L or XL (and maybe an XXL).  >= $20 gets a USB key (I'd do it for less, but these branded USB keys are surprisingly expensive when you don't order 10,000 of them!).

You deserve it all Alan. Armory is a must have for anyone serious with Bitcoin. Keep up the good job!

halfawake
Hero Member
*****
Offline Offline

Activity: 490


View Profile
June 17, 2013, 09:30:18 PM
 #2325

THANK YOU!

I have been receiving substantial donations recently, but donors frequently don't identify themselves, so I have no one to thank!  In recent past I have gotten quite a a few 0.2-1.0 donations, and been taking my fiancée out to nice dinners with it Smiley.  I have been meaning to broadcast a thank-you post, then this donation from yesterday reminded me to do it!


People in this community are quite generous, and I'm thrilled to see people are impressed enough with Armory to make such substantial donations!  It means a lot to me.

So thank you!
-Alan


P.S - If you want to identify yourself to me--publicly or privately--I'll be happy to send you a T-shirt and Armory-branded USB key.  This goes for anyone donating the equiv of $50 or more.  I have only a few T-shirts left from the original crowdfunding a year ago, all black, L or XL (and maybe an XXL).  >= $20 gets a USB key (I'd do it for less, but these branded USB keys are surprisingly expensive when you don't order 10,000 of them!).

You deserve it all Alan. Armory is a must have for anyone serious with Bitcoin. Keep up the good job!

Ditto what Rampion said.  Armory is an awesome client.  We really appreciate all the hard work you put into it.

BTC: 13kJEpqhkW5MnQhWLvum7N5v8LbTAhzeWj
dashingriddler
Legendary
*
Offline Offline

Activity: 1009


Bringing Bitcoin to Billions!


View Profile WWW
June 20, 2013, 10:12:52 AM
 #2326

Hello,
As this is a Armory discussion thread i have a general question about armory. I know if you store a paper backup of a wallet, it holds the data for all past and future addresses that wallet ever creates. The root and chain hold a key to sequence. But theoretically for how many addresses in the sequence does armory check to see if there are any transactions on it? As in there can be a billion address possible in the sequence of bitcoin address that wallet generates i guess

https://www.unocoin.com - India's most popular bitcoin wallet. We make it super easy to securely buy, sell, store, use and accept bitcoin.

http://www.twitter.com/unocoin | http://www.facebook.com/unocoin | http://www.indiabitcoin.com | http://www.meetup.com/IndiaBitcoin | http://www.bitcoinalliance.in
Khertan
Full Member
***
Offline Offline

Activity: 193


View Profile WWW
June 21, 2013, 06:38:17 AM
 #2327

Android Sad No Meego love?  Grin (Nokia N9 here).

Even if there is no Armory client for MeeGo ... there is BitPurse a client for MeeGo Harmattan (n9).

http://khertan.net/pages/bitpurse (Available for free in Nokia Store)

Donation is accepted Smiley

</pub>

runeks
Legendary
*
Offline Offline

Activity: 924



View Profile WWW
June 21, 2013, 10:46:18 AM
 #2328

I can't get Armory to work any more.

It just sits at "99% - Synchronizing with Network - 0 blocks". My log looks like this: http://pastebin.com/PmncB0AB

Ie. these lines just keep repeating in the log:

Code:
2013-06-11 18:39 (INFO) -- ArmoryQt.py:4349 - Starting load blockchain
2013-06-11 18:39 (INFO) -- ArmoryQt.py:1243 - loadBlockchainIfNecessary
2013-06-11 18:39 (INFO) -- ArmoryQt.py:1289 - Setting netmode: 0

Gah.  This is familiar.  I think jl2012 had a similar problem at one point.  The issue had to do with Bitcoin-Qt being detected, but failure to successfully open a connection.  It had turned out to be a problem with a timeout parameter. 

It's also possible that there's a problem with the blockfile location...change anything recently?
Turns out it was entirely my own fault.

I had added the option

nolisten=1

to bitcoin.conf, in order for bitcoind not to consume too much outgoing bandwidth (nodes that want to sync the block chain generally connect to nodes rather than let nodes connect to them, so this avoids most clients that want to sync the entire block chain).

I have another problem that I hope you can help me with though.

I frequently experience Armory losing connection to bitcoind.

In the function

Code:
clientConnectionLost(self, connector, reason)

in armoryengine.py I added a line to print the reason for the disconnect using this line:

Code:
reason.printBriefTraceback()

And the result is the following lines appearing very frequently in the CLI output (several times per second):

Code:
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
(ERROR) armoryengine.py:10259 - ***Connection to Satoshi client LOST!  Attempting to reconnect...
Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.

The text in the lower right corner keeps flashing between "Disconnected" and "Connected [...]".

There's a secondary bug associated with this. After letting Armory run like this for a while and then closing Armory, the disconnected/connected notifications keep on reappearing after the program has been closed for a long time. I think the reason is that they happen so frequently (several times per second) so there are thousands of these notifications queued up. And with each notification having a timeout of 10 seconds, they just keep reappearing until the queue is empty (long after the program is shut down).

Perhaps it would be necessary to, when displaying the notification, check whether a previous notification is still being displayed, and only display a new one if the previous notification is no longer there (more than 10 seconds have passed since calling self.sysTray.showMessage()) or perhaps cancel the previous notification, if that is possible.
etotheipi
Legendary
*
Offline Offline

Activity: 1428


Core Armory Developer


View Profile WWW
June 25, 2013, 11:13:53 PM
 #2329

Update: (25 June, 2013)

Things have been hectic.  Very hectic.  I am quite aware about the usability issues, and I have been making some progress on the "persistent blockchain" update for Armory, but not at nearly the pace I had hoped.  Other critical priorities have cropped up.  I will explain more about these priorities in a week or two.  I just wanted to assure those of you who still follow this thread that development does continue, despite things looking rather stagnant lately...

On the persistent blockchain front: I have found myself in the awkward position of deciding to just make an identical version of Armory that uses LevelDB, or to actually upgrade huge parts of the codebase as long as I'm tearing it all up and putting it back together, anyway.  It seems that the best solution is the latter -- I've always been a fan of short-term sacrifice for long-term gain.  Even though it's slowing down the resolution of the RAM issues, a lot of what I am doing now will benefit multiple other things I have on my TODO list, including the new wallet stuff that will come shortly after persistent blockchain upgrades.  

What I'm talking about is things like properly handling and indexing multi-sig scripts, P2SH scripts, and compressed public keys.  Additionally, I'm trying to make the whole thing easily extensible to both partial/lite/pruned operation (storing only data necessary for computing balance and creating transactions) and also super-node operation (maintaining a full address-lookup index for immediate balance/UTXO queries for any address).  These are all things that I need to do eventually, anyway.  For instance, I had claimed that the new wallet format was nearing completion before getting sidetracked by this stuff, but I was still going to have to upgrade a bunch of blockchain utilities and re-test it to be compatible with the new wallet functionality.  I might as well kill 7 birds with one stone.

It looks like I've found a coherent way to fit all this together.  And it means that many of these changes can be implemented and tested in one rigorous round of testing, instead of rewriting and re-testing multiple times.  More importantly, after the first persistent blockchain update, it will be much tougher to modify the blockchain utilities, because users will have persistent databases that will need to be rebuilt to accommodate changes.  And that may be quite painful.  If you were wondering why it was beneficial for me to do full scans on every load and not save any blockchain data between loads.... that is why (simple!).

That's all I have for now.  I'm excited that when I'm finally done with this, Armory will be miles ahead of where it was before.  So many problems will go away.  Until then... you'll all have to suffer while I take my time doing it right Smiley

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
solex
Legendary
*
Offline Offline

Activity: 1078


100 satoshis -> ISO code


View Profile
June 25, 2013, 11:31:04 PM
 #2330

Thanks for the update. All your work is much appreciated.

gweedo
Legendary
*
Offline Offline

Activity: 1246


Java, PHP, HTML/CSS Programmer for Hire!


View Profile WWW
June 25, 2013, 11:45:11 PM
 #2331

Update: (25 June, 2013)

Things have been hectic.  Very hectic.  I am quite aware about the usability issues, and I have been making some progress on the "persistent blockchain" update for Armory, but not at nearly the pace I had hoped.  Other critical priorities have cropped up.  I will explain more about these priorities in a week or two.  I just wanted to assure those of you who still follow this thread that development does continue, despite things looking rather stagnant lately...

On the persistent blockchain front: I have found myself in the awkward position of deciding to just make an identical version of Armory that uses LevelDB, or to actually upgrade huge parts of the codebase as long as I'm tearing it all up and putting it back together, anyway.  It seems that the best solution is the latter -- I've always been a fan of short-term sacrifice for long-term gain.  Even though it's slowing down the resolution of the RAM issues, a lot of what I am doing now will benefit multiple other things I have on my TODO list, including the new wallet stuff that will come shortly after persistent blockchain upgrades. 

What I'm talking about is things like properly handling and indexing multi-sig scripts, P2SH scripts, and compressed public keys.  Additionally, I'm trying to make the whole thing easily extensible to both partial/lite/pruned operation (storing only data necessary for computing balance and creating transactions) and also super-node operation (maintaining a full address-lookup index for immediate balance/UTXO queries for any address).  These are all things that I need to do eventually, anyway.  For instance, I had claimed that the new wallet format was nearing completion before getting sidetracked by this stuff, but I was still going to have to upgrade a bunch of blockchain utilities and re-test it to be compatible with the new wallet functionality.  I might as well kill 7 birds with one stone.

It looks like I've found a coherent way to fit all this together.  And it means that many of these changes can be implemented and tested in one rigorous round of testing, instead of rewriting and re-testing multiple times.  More importantly, after the first persistent blockchain update, it will be much tougher to modify the blockchain utilities, because users will have persistent databases that will need to be rebuilt to accommodate changes.  And that may be quite painful.  If you were wondering why it was beneficial for me to do full scans on every load and not save any blockchain data between loads.... that is why (simple!).

That's all I have for now.  I'm excited that when I'm finally done with this, Armory will be miles ahead of where it was before.  So many problems will go away.  Until then... you'll all have to suffer while I take my time doing it right Smiley


You do what you have to do! I can't wait!

Want to earn 2500 SATOSHIS per hour? Come Chat and Chill in https://goseemybits.com/lobby
Ente
Legendary
*
Offline Offline

Activity: 1834



View Profile
June 26, 2013, 08:44:16 AM
 #2332

Update: (25 June, 2013)

Things have been hectic.  Very hectic.  I am quite aware about the usability issues, and I have been making some progress on the "persistent blockchain" update for Armory, but not at nearly the pace I had hoped.  Other critical priorities have cropped up.  I will explain more about these priorities in a week or two.  I just wanted to assure those of you who still follow this thread that development does continue, despite things looking rather stagnant lately...

On the persistent blockchain front: I have found myself in the awkward position of deciding to just make an identical version of Armory that uses LevelDB, or to actually upgrade huge parts of the codebase as long as I'm tearing it all up and putting it back together, anyway.  It seems that the best solution is the latter -- I've always been a fan of short-term sacrifice for long-term gain.  Even though it's slowing down the resolution of the RAM issues, a lot of what I am doing now will benefit multiple other things I have on my TODO list, including the new wallet stuff that will come shortly after persistent blockchain upgrades.  

What I'm talking about is things like properly handling and indexing multi-sig scripts, P2SH scripts, and compressed public keys.  Additionally, I'm trying to make the whole thing easily extensible to both partial/lite/pruned operation (storing only data necessary for computing balance and creating transactions) and also super-node operation (maintaining a full address-lookup index for immediate balance/UTXO queries for any address).  These are all things that I need to do eventually, anyway.  For instance, I had claimed that the new wallet format was nearing completion before getting sidetracked by this stuff, but I was still going to have to upgrade a bunch of blockchain utilities and re-test it to be compatible with the new wallet functionality.  I might as well kill 7 birds with one stone.

It looks like I've found a coherent way to fit all this together.  And it means that many of these changes can be implemented and tested in one rigorous round of testing, instead of rewriting and re-testing multiple times.  More importantly, after the first persistent blockchain update, it will be much tougher to modify the blockchain utilities, because users will have persistent databases that will need to be rebuilt to accommodate changes.  And that may be quite painful.  If you were wondering why it was beneficial for me to do full scans on every load and not save any blockchain data between loads.... that is why (simple!).

That's all I have for now.  I'm excited that when I'm finally done with this, Armory will be miles ahead of where it was before.  So many problems will go away.  Until then... you'll all have to suffer while I take my time doing it right Smiley


I applaud your decision!
Thank you for doing the right thing, sacrifying short-term development for long-term goals.

In fact you are the dev here I trust the most, be it technically, vision, endurance or incorruptable.
Not implying I see issues with other devs, but you I trust the most.

It will be a big day once Armory is self-contained, without any external component (like bitcoind). It's in the far future still, but it will be a milestone for the Bitcoin ecosystem as a whole.

Oh, are you a paid full-time Armory dev yet? If not, we have to change this! :-)

Ente
superresistant
Legendary
*
Offline Offline

Activity: 1316



View Profile
June 27, 2013, 08:18:37 AM
 #2333

So we wait for the next proper working version of Armory ?

Kluge
Donator
Legendary
*
Offline Offline

Activity: 1218


Michael, send me some coins before I hitman you


View Profile
June 27, 2013, 10:48:52 AM
 #2334

I applaud your decision!
Thank you for doing the right thing, sacrifying short-term development for long-term goals.

In fact you are the dev here I trust the most, be it technically, vision, endurance or incorruptable.
Not implying I see issues with other devs, but you I trust the most.

It will be a big day once Armory is self-contained, without any external component (like bitcoind). It's in the far future still, but it will be a milestone for the Bitcoin ecosystem as a whole.

Oh, are you a paid full-time Armory dev yet? If not, we have to change this! :-)

Ente
AFAIK, Alan *IS* Armory.  Cheesy

Only client I can bear to use, even if the RAM requirements (- and it seems almost guaranteed to crash if certain parts wind up on virtual RAM) and need of maintaining the blockchain make it nearly unusable in my situation. I go to great lengths to be able to use Armory, because even while it currently has critical flaws, it's the most flexible and powerful client I've ever used. Alan's a freakin' rockstar in handling support issues, too. It's actually unnerving how interested he is in ensuring users have good experiences.

I really can't imagine a better way to donate money for the fundamental growth of Bitcoin and the ventures it spawns than to send it to Alan.

Don't mix your coins someone said isn't legal
13Charlie
Full Member
***
Offline Offline

Activity: 214



View Profile
June 27, 2013, 01:07:03 PM
 #2335

I applaud your decision!
Thank you for doing the right thing, sacrifying short-term development for long-term goals.

In fact you are the dev here I trust the most, be it technically, vision, endurance or incorruptable.
Not implying I see issues with other devs, but you I trust the most.

It will be a big day once Armory is self-contained, without any external component (like bitcoind). It's in the far future still, but it will be a milestone for the Bitcoin ecosystem as a whole.

Oh, are you a paid full-time Armory dev yet? If not, we have to change this! :-)

Ente
AFAIK, Alan *IS* Armory.  Cheesy

Only client I can bear to use, even if the RAM requirements (- and it seems almost guaranteed to crash if certain parts wind up on virtual RAM) and need of maintaining the blockchain make it nearly unusable in my situation. I go to great lengths to be able to use Armory, because even while it currently has critical flaws, it's the most flexible and powerful client I've ever used. Alan's a freakin' rockstar in handling support issues, too. It's actually unnerving how interested he is in ensuring users have good experiences.

I really can't imagine a better way to donate money for the fundamental growth of Bitcoin and the ventures it spawns than to send it to Alan.
+1,000

Armory is the ONLY way to keep MY Bitcoin (and yours for that matter) safe . . . PERIOD
Thanks Alan, take your time

Not ignoring anyone. . . . . Yet
Tip Jar - 18YWB8cQ8vb5s7PTGvxu1E6DqmQV3Srj2W
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
June 27, 2013, 01:37:52 PM
 #2336

+1 to all of the above comments.

Alan has good reason to be sidetracked right now but in the end it will benefit us all.

patience.
Exocyst
Sr. Member
****
Offline Offline

Activity: 266


Science!


View Profile
June 27, 2013, 02:45:25 PM
 #2337

Armory 0.88.1-beta is working great for me on Ubuntu 13.04 and MacOS 10.8

I am looking forward with great anticipation to future performance improvements.

Thank you for great software.

vokain
Legendary
*
Offline Offline

Activity: 1610


V.V.V.V.V.


View Profile
June 27, 2013, 07:25:18 PM
 #2338

Armory 0.88.1-beta is working great for me on Ubuntu 13.04 and MacOS 10.8

I am looking forward with great anticipation to future performance improvements.

Thank you for great software.

Finally! thank you so much (from the OSX side)!!

...مكتوب
Escape the plutocrats’ zanpakutō, Flower in the Mirror, Moon on the Water: brave “the ascent which is rough and steep” (Plato).
picobit
Hero Member
*****
Offline Offline

Activity: 547


Decor in numeris


View Profile
June 28, 2013, 08:35:57 AM
 #2339

So we wait for the next proper working version of Armory ?
The current one works fine - if you have 8 GB of RAM.  So if you are impatient, that is an option ...

 Grin
Kluge
Donator
Legendary
*
Offline Offline

Activity: 1218


Michael, send me some coins before I hitman you


View Profile
June 28, 2013, 08:47:26 AM
 #2340

So we wait for the next proper working version of Armory ?
The current one works fine - if you have 8 GB of RAM.  So if you are impatient, that is an option ...

 Grin
8GB RAM on a minimalist Linux distro, maybe. I have 8GB on Win7 and Armory still crashes every few hours when Doze starts stuffing Armory resources onto hard drive. Not sure if there's software to help force RAM priorities on certain applications -- that'd be super.

It'd probably work on modern Doze if all other applications were shut off. Skype, a couple pages on Chrome, some productivity software, AND Armory was just too much for my machine, though.  It reminds me of living in a run-down warehouse for a while with all available outlets on one circuit, and sometimes I'd dare to run a PC, coffee maker, AND toaster oven on the same circuit. Never tripped immediately, but maybe half the time, ~20-40 minutes in (if I forgot to stop the coffee maker from continuing to warm the pot), there'd be a pop and I'd roll my eyes and walk over to reset the breaker... again.

Don't mix your coins someone said isn't legal
Pages: « 1 ... 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 [117] 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 ... 232 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!