Mersenne: Bannerz
I've resumed work on my GIMPS banners again. If you have any suggestions as how to improve the current banners that I have, or as for new banner ideas, please E-mail me personally. Thanks! The gallery I have can be found at: http://members.aol.com/stl137/bannerz/gallery.html I have fixed numbers 4, 7, 9, and 17 to have more contrast. Number 12 now says 5300+ users. And I have 8 or so new banners cooking now. I'll upload all this when the new banners are done. Yah! STL
Re: Mersenne: Error: Illegal Sumout
At 01:29 PM 10/28/98 -0700, Chuck Baker wrote: >[...] "ERROR: ILLEGAL SUMOUT" [...] Any suggestions? It happened to me. Turned out to be bad tag RAM. --Luke
Re: Mersenne: Error: Illegal Sumout
At 01:29 PM 10/28/98 -0700, Chuck Baker wrote: > I think my Prime95 broke! I am on iteneration 479162/5518463 and get a >continuous stream of "ERROR: ILLEGAL SUMOUT" messages which are constantly >sent to the primenet server. I am running version 16.3.1 of Prime95. I >have no choice but to shut it down until I figure out what went wrong. Any >suggestions? This is probably an interaction with some new piece of software. I know that the OS should protect you from such interactions, but this problem is quite common. Have you installed any new device drivers lately - especially those that might use MMX (audio and midi cards)? Are you running any new programs? The good news is that these errors do not seem to affect prime95's accuracy (unlike other error messages). A recent double-check had 3 SUMOUT errors, but the residues matched anyway. Hope that helps, George
Re: Mersenne: Re: 128-bit CPU
With regard to the need for 128-bit cpus: Another area that will inevitably demand such data types is the financial industry. If you use packed BCD (very popular with the "exact" calculations that CPAs demand) and you want to represent anything under $100 trillion to the exact cent, you already need 64 bits for the significant digits, which means the sign nibble pushes you over the 64-bit limit. Budgets (especially national ones) are only going to get bigger and things like the Euro and conversions between currencies will make it necessary for the international financial types to go to such data sizes. Truett Lee Smith San Francisco, CA E-mail: [EMAIL PROTECTED]
Re: Mersenne: Re: 128-bit CPU
To the exact cent? I guess you have not heard the news that the Euro dollar is causing. The calculations must be correct to the 10th of a mil for the conversion factors. Thus one needs E,EEE,EEE,EEE,EEE.c (yes, 5 decimals to round up.) It is known in Europe as maybe worse than the Y2K issue. In Italy, they don't have decimals at all for the Lira so adding any decimals at all is a headache. P.S. All these side notes being passed around are very interesting, even if off the topic somewhat. At 01:48 PM 10/28/98 -0800, you wrote: >With regard to the need for 128-bit cpus: > >Another area that will inevitably demand such data types is the financial >industry. If you use packed BCD (very popular with the "exact" >calculations that CPAs demand) and you want to represent anything under >$100 trillion to the exact cent, you already need 64 bits for the >significant digits, which means the sign nibble pushes you over the >64-bit limit. Budgets (especially national ones) are only going to get >bigger and things like the Euro and conversions between currencies will >make it necessary for the international financial types to go to such >data sizes. > >Truett Lee Smith >San Francisco, CA >E-mail: [EMAIL PROTECTED] > >
Mersenne: Error: Illegal Sumout
I think my Prime95 broke! I am on iteneration 479162/5518463 and get a continuous stream of "ERROR: ILLEGAL SUMOUT" messages which are constantly sent to the primenet server. I am running version 16.3.1 of Prime95. I have no choice but to shut it down until I figure out what went wrong. Any suggestions? Thanks, Chuck Baker [EMAIL PROTECTED]
Re: CPU info (was RE: Mersenne: AMD K7 will)
At 05:32 PM 10/27/98 -0800, John R Pierce wrote: >The 286 had a 24 bit address bus but a 16 bit data bus. Nothing about the 286 >was 32bit. According to "Great Microprocessors of the past", it did have some 32-bitness: http://infopad.eecs.berkeley.edu/CIC/archive/cpu_history.html Although this was largely acceptable for assembly language, where control of the segments was complete (it could even be useful then), in higher level languages it caused constant confusion (ex. near/far pointers). Even worse, this made expanding the address space to more than 1 meg difficult. The 80286 (1982?) expanded the design to 32 bits only by adding a new mode (switching from 'Real' to 'Protected' mode was supported, but switching back required using a bug in the original 80286, which then had to be preserved) which greatly increased the number of segments by using a 16 bit selector for a 'segment descriptor', which contained the location within a 24 bit address space, size (still less than 64K), and attributes (for Virtual Memory support) of a segment. +--+ | Jud McCranie [EMAIL PROTECTED] or @camcat.com | | | | Where a calculator on the ENIAC is equipped with 19,000 | | vacuum tubes and weighs 30 tons, computers in the future | | may have only 1,000 vacuum tubes and perhaps only weigh | | 1.5 tons.-- Popular Mechanics, March 1949. | +--+