Thank you very much. Please take your time, my request is the lowest priority. Former coworker of mine produced such a generic Java private zip files for several old runtimes 1.3, 1.4 & 1.5 and it covered 4 platforms that we use: Solaris, Windows, Linux and MacOS. Unfortunately he didn't leave any instructions and I couldn't reproduce his feat for 1.6 and 1.7. Java had recently gotten really bad reputation for lack of security and currently the majority of the guest computers I would use simply don't have it installed and I don't want to ask for administrative privileges do an install and then uninstall.

Please let me know if the instructions for private Java configurations are available somewhere that you know. I maybe able to figure it out on my own, without handholding.

Thanks again.
 

Jim, is there any chance that you'll follow up on the promise of the portable JRE?
I'm particularly interested if it is possible to produce a FAT32 USB drive with all the runtimes, or at least the two for 32-bit Windows and 32-bit Linux. I know that Java is a nice lady, but she has recently been seen in public with some not-that-nice men, and people are afraid to let her stay overnight on their computer. 

Thanks.

When I first heard the following read really fast over the radio I started laughing. But now I understand why things like that are getting done: litigation is the only other option.

Yes, I misremembered. There is a "Design Goal" for "Power Optimization" that invokes synthesis with "Optimization Goal" of "Area" and adds "Power Reduction" flag. It must have scrolled so many times on my terminal that I completely forgot about the top-level goal.

I haven't really tried anything on Kintex-7, but various Virtex-[456] that I had available. After what you've said about Vivado and Family-7 I'm getting motivated to upgrade my toyset.

I apologise for my mistakes.

I've mixed up Lithuania with Latvia. I've corrected my previous message in this thread. To make such a mistake for me is completely unexcusable, I'm well aware of the .lt versus .lv distinction and the distinctive history of both nations.

Equally bad on my part is mixing up Slavs with Balts.

I regret making those mistakes.

What I reconfirm is the information about the cooperation and mutual support of the national-socialistic, neo-fascist, old-falangist and similar totalitarian and human-purity movements in Europe. Unfortunately this phenomenon is so recent that there is very little publicly-available information about this in English. Whatever is available in English tends to use code-words, like 88 for "Heil Hitler".

Edit: It is equally hard to come by a reliable and representative information about the social situation in the Baltic independent states that were former republics of the USSR. But please don't try to make direct comparisons between the LGBT rights in the USA and the LGBT rights in the former Soviet Bloc. You will completely miss the point both in the historical and current social context.

I've tried to follow this disussion here: MysteryMiner contra The Board, and I see that The Board is completely missing the social context.

MysteryMiner is a Latevian neofascist. If you aren't aware of the neo-nazism in the ex-USSR you'll need to gain the understanding of the social context.

There is a documentary entitled "The Pack of White Wolves" which is a Greek/English movie about neo-nazism in Russia, primarily about Slavic Union. The initials of this organization in Russian are "CC" which is the same as the German abbreviation "SS" for Schutzstaffel. The movie was made in 2011 and should be easy to find on the web, and the subtitles and transcripts are available for several languages.

Please note that MysteryMiner is Latevian, so for him Slavic Union is both an ally and an enemy. An ally because as a Latevian he is of Slavic heritage like Russians. An enemy because  Latevia was occupied by the Soviet Union and the native Latevians were subject to forced russification.

Also please note that "The Pack of White Wolves" is made by the anti-fascists, therefore the pro-nazi characters are crudely drawn.

If you want to get a better emotional understanding of the neo-nazism in the ex-USSR I can recommend two science-fiction movies that contain deeper portayal of the pro-nazis. The movies are completely fictious, they are in the action/adventure/sci-fi/fantasy genre, but all the characters are well-drawn and very grounded in the reality of the contemporary Commonwealth of Independent States.

Those movies are "My iz budushchego" and "My iz budushchego 2". They were distributed under various titles like "Paradox Soldiers", "We Are from the Future", "Amongst Heroes", etc.

http://www.imdb.com/title/tt1192431/
http://www.imdb.com/title/tt1590125/

Edit: I made a mistake. MysteryMiner is Latevian, not Lithuanian. I'm correcting this message.

How about the old chestnut: "Web 3.11 for Workgroups"?

I just wanted to point one thing: trying to achieve a timing closure is a blind alley. What you should really aim is power optimization. To my knowledge none of the popular toolchains has such a goal available.

With the unrolled design the fanout of some registers is high enough to trigger combinatorial logic duplication when searching for the closure. I haven't tried Vivado, but ISE was even doing the register duplication. This is exactly what you don't want to do when doing an FPGA design that has to compete with an ASIC design. In the absence of pure power optimization your next-best goal is try to optimize for the area.

I guess working with the two unrolled copies of SHA-256 produces such a wild mess of trees primitives that it is possible to lose ones bearing in the jungle of vines signals.

Please John! Nitpicking on somebody's grammar is not a way to show that you are a great thinker. Let me restate the complaint in a more unambiguous way: core development team cares for some idealized mentaly deficient user, politely expressed as Gavin's grandma. Out-of-core developers and users care mostly for acceptance amongst knowledgeable IT geeks and innovative financial people. There is a serious disconnect right here.

I hope that this disconnect soon will be quantitatvely measured by the sales of Trezor. Originally it was conceived for the "grandma" market. After I and other people applied little presure on the designers there will be two versions: for "grandmas" and for "geeks", the second one being an unlocked device that doesn't use jail and doesn't require jailbreak.

https://bitcointalk.org/index.php?topic=122438.msg1496928#msg1496928

This strawman is not yet completely burnt, so lets dissect what had left of it.

A simple definition of "commercial success" would be that the sum total of income of everyone involved in the enterprise is positive and increases as the product adoption increases.

A simple example of "commercial failure" would be an enterprise where the "accounts receivable" department gets all the bonuses, "accounts payable" department is constantly getting laid off and the "research and development" department lives on the handouts received openly and the bribes delivered in secret. Do you recognize it? This type of operation is sometimes called "asset stripping".

The original ideal of Bitcoin was that every peer would be its own accounts payable, accounts receivable and some of the peers will do R&D on the side while doing accounting. It didn't work out that way: the accounts receivable function broke out of the ranks and concentrated into the mining pools. This destroyed the balance of the original design. The balance needs to be restored by some compromise.

Being a businessman is an art of forging compromises.

So I'll finish burning the strawman with the following: tax the miners with proceeds going to at least two pockets, one of them Gavin's and Bitcoin Foundation and one in escrow for another R&D and implementation effort. Just don't repeat the devcoin mistake and set the tax rate to 90%.

You aren't going to get anywhere on this line of thinking, except simply digging a deeper foxhole for yourself.

The benefit of the so called "coin control" for nearly every user is in allowing him/her to see the how the protocol operates "under the hood". This is a great learning tool both for the beginning users and for the developers that begin to work with Bitcoin.

Even if the significant portion of the "coin control" users wont use it for the "control" but just as a magnifying glass to see whats inside their wallet, it will be a great upgrade to the reference client.

Maybe just rename it from "coin control" to "coin loupe & tweezers"?

Yeah, I've heard about smoking, flaming and fires too in the white-label reseller channels (like MWave, etc.). Because the people in my company were involved in the reselling of the AMD products I have some additional inside information:

1) on-the-motherboard thermal protection was too slow acting in the most common failure mode: spring loaded heatsink mount unsnapped because it either:

1a) was never snapped in properly all the way
1b) was snapped properly but snapping-in caused cracking of the plastic socket latch

2) rampant remarking and overclocking of AMD Athlons, including defective chips destined for industrial waste disposal. AMD Malaysia was the leaky culprit here: chips that failed tests were shipped to Taiwan or Singapore for intended destruction/recycling but it fact were remarked and shipped back to Malaysia for reintroduction into the reseller channel. This was made easier by the fact that the clock selection and feature selection (Athlon XP/MP/Mobile) traces were easily accessible on the Athlon OPGA package. Additionally AMD was really tardy in investigating and prosecuting the in-the-channel diversion.

In my company they dealt with 1) and 2) with simple visual inspection after dismounting the heathsink, remounting it and doing additional burn-in with memtest86. I came at the tail edge of the problem and changed the burn in to use PRIME95 from the GIMPS prime number search. The before-burn-in failure rate was apparently quite high, I don't know the numbers because it was essentially free to us, MWave covered that. After-the-burn-in failure rate was very low, lower than what we were getting later on with white-label Dells and Supermicros. Cheap ECC RAM support in Athlons was a real godsend. I still have several of those machines in the QA farm alongside Slot-1 Intel Pentiums III.

I wish somebody who was really involved in this in South-East Asia would write some sort of war memoir of the whole story.

I kinda recall that to have the AMD Athlon release the smoke one had to remove the cooler? I worked more with Intel Itanium and Itanium 2 machines and those indeed were beastly: the CPU replacement required the wrenches from the car mechanic's toolset.

Actually coin control GUI would be an excellent teaching tool to help the beginning users and developers understand the Bitcoin protocol.

At the same time this is exactly why people who think like Mike Hearn oppose it: they oppose educating people about the inner working of the machinery. The key to control the people is to make them believe that they really need somebody more knowledgeable to ensure their safety.

Coin control is a beautiful example of anti-paternalistic stance and how it aggravates anyone who is a paternalist and wants to treat every user like a potential "grandma" or whatever else is the current polite word for "mentally deficient".

I think the Bitcoiner emancipation movement is getting formed here and now.

What you wrote is self-contradictory.

Trusted private key holders already exist in Bitcoin: only Gavin has the private key to issue the network alerts.

With M-of-N signatures the PoW-type currency can be both decentralized and limited, where M is the decentralization parameter and N is the limitation parameter. Such a schemes were already discussed here and elsewhere under the concept of "licensed mining".

What can I say? Rebuid your bitcoind without stripping the debug symbols. The default makefile.unix already has "-g" to enable debugging.

Actually it is trivial to produce a private PoW currency: just include an asymmetric cryptographic operation in the hashing function.

It is somewhat more complex to make such a "private PoW" currency really decentralized. The scalar difficulty will have to be changed to a vector of difficulty values, one for each distributed shareholder.

The main advantage would be that it doesn't require billions invested for hashing hardware: each shareholder needs to maintain only a minimum hashing power required to sufficiently distribute the nodes working on his share.

It would be just a couple of weeks of work for a single software engineer. It would involve way more legal work to produce the required contractual agreement that are both legally and technically sound and where the legal side exactly mirrors the technical side.

Edit: Such an implementation already does exist, except that it isn't a full currency: it just serves as a sort of DRM for eldentyrell's implementation of FPGA hashing bitstreams.

before invoking bitcoind is your friend. Then wait for the crash and do the postmortem:. Post the results.

I've clicked over and noticed that you are an Israeli, thus I have a constructive answer:

to test your sense of humour.

Seriously, you have a great opportunity there in Isreal: serve in the IDF and apply into the Talpiot program. Even if you ultimately don't qualify the testing process is going to really build your character:
I had an oppotunity to work with many Israelis, and I was always very surprised why Israeli girls/women have more fortitude than their American and Western European boy/men peers. The answer turned out to be the service in the IDF.

After that you are going to laugh at the version of yourself who was flustered by some random loser on some random Internet board not being "nice". Unless you are "Profile 21".

is your friend. Then do post-mortems on those coredumps with:.

Still graded FAIL, but shows promise. BTW, reading stackexchange is not doing homework. StackExchange is shaping up to be a premiere resource for pretenders lacking education, it gets really good at consolidating the mutual admiration rings of upvoters.

1) "addresses carying balance" is a wrong measure. You need to count the "unspent transaction outputs" (UTxO)
2) search this board for "ultraprune" and other discussions of pruning

What happened to the old "researching the field first, thinking it through second and publishing it last?"