<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Pi Day Rematch: Apple II vs. HP-41C</title>
	<atom:link href="http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/feed/" rel="self" type="application/rss+xml" />
	<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/</link>
	<description>* some assembly required</description>
	<lastBuildDate>Thu, 06 Jun 2013 12:30:47 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: bdeckers</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-76</link>
		<dc:creator><![CDATA[bdeckers]]></dc:creator>
		<pubDate>Mon, 05 Mar 2012 09:23:34 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-76</guid>
		<description><![CDATA[Hi,

I am selling on eBay “HP-41C Synthetic Programming Manual”,   the original manual (Larken Publications-Oregon,  92 pages (letterformat), March 1982)
http://www.benl.ebay.be/itm/120871262164?ssPageName=STRK:MESELX:IT&amp;_trksid=p3984.m1558.l2649 

I you  are interested, could be an opportunity….

Thank you,]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am selling on eBay “HP-41C Synthetic Programming Manual”,   the original manual (Larken Publications-Oregon,  92 pages (letterformat), March 1982)<br />
<a href="http://www.benl.ebay.be/itm/120871262164?ssPageName=STRK:MESELX:IT&#038;_trksid=p3984.m1558.l2649" rel="nofollow">http://www.benl.ebay.be/itm/120871262164?ssPageName=STRK:MESELX:IT&#038;_trksid=p3984.m1558.l2649</a> </p>
<p>I you  are interested, could be an opportunity….</p>
<p>Thank you,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: datajerk</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-75</link>
		<dc:creator><![CDATA[datajerk]]></dc:creator>
		<pubDate>Sat, 05 Nov 2011 23:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-75</guid>
		<description><![CDATA[Yep.  Now I really want to see your code.]]></description>
		<content:encoded><![CDATA[<p>Yep.  Now I really want to see your code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: datajerk</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-74</link>
		<dc:creator><![CDATA[datajerk]]></dc:creator>
		<pubDate>Sat, 05 Nov 2011 23:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-74</guid>
		<description><![CDATA[Machine code.  That&#039;s hard core.  :-)

Stomer&#039;s Arc-tangent is a bit faster than Machin (http://sense.net/~egan/hpgcc/#Example:%20%20%CF%80%20Shootout). 

If you still got your code, I&#039;d really like to see it.

BTW, I am working on an article about the Apple II cassette tape.  Hopefully I&#039;ll be done in about a month.]]></description>
		<content:encoded><![CDATA[<p>Machine code.  That&#8217;s hard core.  :-)</p>
<p>Stomer&#8217;s Arc-tangent is a bit faster than Machin (<a href="http://sense.net/~egan/hpgcc/#Example:%20%20%CF%80%20Shootout" rel="nofollow">http://sense.net/~egan/hpgcc/#Example:%20%20%CF%80%20Shootout</a>). </p>
<p>If you still got your code, I&#8217;d really like to see it.</p>
<p>BTW, I am working on an article about the Apple II cassette tape.  Hopefully I&#8217;ll be done in about a month.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Peterson</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-73</link>
		<dc:creator><![CDATA[Craig Peterson]]></dc:creator>
		<pubDate>Thu, 03 Nov 2011 18:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-73</guid>
		<description><![CDATA[PS - Using your &#039;square of the ratios of the digits&#039; method, I would guess that the program above would have calculated the value of Pi to 1000 digits in about 2 minutes and 23 seconds.  I&#039;m sure I did some timings for this in 1980, but I can&#039;t find any record of it.  So machine code was faster than integer basic, but we all knew that anyway.  

Craig Peterson]]></description>
		<content:encoded><![CDATA[<p>PS &#8211; Using your &#8216;square of the ratios of the digits&#8217; method, I would guess that the program above would have calculated the value of Pi to 1000 digits in about 2 minutes and 23 seconds.  I&#8217;m sure I did some timings for this in 1980, but I can&#8217;t find any record of it.  So machine code was faster than integer basic, but we all knew that anyway.  </p>
<p>Craig Peterson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Peterson</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-72</link>
		<dc:creator><![CDATA[Craig Peterson]]></dc:creator>
		<pubDate>Thu, 03 Nov 2011 18:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-72</guid>
		<description><![CDATA[Just a quick note.  Although the old Apple II (not Plus, not e, not c, not gs) was VERY limited in some ways, with an inexpensive 8 bit 6502 processor with a limited instruction set and a 1 mHz cpu clock speed, its real strength was that it finally gave the public nerds inside access to a computing machine, largely because of Steve Wozniak&#039;s contributions, a hacker at heart.  And they took off and ran with it, helping to start Apple into becoming the company that it is today.  

I, too, was intrigued by Bob Bishop&#039;s _Micro_ magazine article on calculating Pi.  So much so that in 1980 I wrote a machine language program for my 48K Apple II that was able to calculate Pi to 36,364 digits in 52 hours, 28 minutes and 29 seconds.  I was able to check the accuracy of my result by visiting the UCLA library and comparing the last few hundred digits in my result.  I wrote it in machine code (no assembler), using Woz&#039;s internal disassembler to check my work.  I tried Gauss&#039; equation and Stirling&#039;s equation, but I found Machin&#039;s formula to be the fastest on my Apple II.  I printed the result with a short AppleSoft program that &#039;co-habitated&#039; memory with my machine code.  A major issue in outputing 36,000+ on a 48K machine (minus room for the lower 2k+ used for the Applesoft program) is that you don&#039;t have a lot of room for partial results as you complete the task, particularly when changing the binary to decimal for output.  And the code was fully relocatable on this 8 bit processor.  It was a fun challenge.

I actually submitted it to Apple as a lark program.  It was submitted on the media of that time, a cassette tape.  :-)

Craig Peterson
Apple II owner since 1978
(and Apple II Plus, Apple IIgs, Macintosh 128K, 512K, iMac, Mac LC, and PCs as well)]]></description>
		<content:encoded><![CDATA[<p>Just a quick note.  Although the old Apple II (not Plus, not e, not c, not gs) was VERY limited in some ways, with an inexpensive 8 bit 6502 processor with a limited instruction set and a 1 mHz cpu clock speed, its real strength was that it finally gave the public nerds inside access to a computing machine, largely because of Steve Wozniak&#8217;s contributions, a hacker at heart.  And they took off and ran with it, helping to start Apple into becoming the company that it is today.  </p>
<p>I, too, was intrigued by Bob Bishop&#8217;s _Micro_ magazine article on calculating Pi.  So much so that in 1980 I wrote a machine language program for my 48K Apple II that was able to calculate Pi to 36,364 digits in 52 hours, 28 minutes and 29 seconds.  I was able to check the accuracy of my result by visiting the UCLA library and comparing the last few hundred digits in my result.  I wrote it in machine code (no assembler), using Woz&#8217;s internal disassembler to check my work.  I tried Gauss&#8217; equation and Stirling&#8217;s equation, but I found Machin&#8217;s formula to be the fastest on my Apple II.  I printed the result with a short AppleSoft program that &#8216;co-habitated&#8217; memory with my machine code.  A major issue in outputing 36,000+ on a 48K machine (minus room for the lower 2k+ used for the Applesoft program) is that you don&#8217;t have a lot of room for partial results as you complete the task, particularly when changing the binary to decimal for output.  And the code was fully relocatable on this 8 bit processor.  It was a fun challenge.</p>
<p>I actually submitted it to Apple as a lark program.  It was submitted on the media of that time, a cassette tape.  :-)</p>
<p>Craig Peterson<br />
Apple II owner since 1978<br />
(and Apple II Plus, Apple IIgs, Macintosh 128K, 512K, iMac, Mac LC, and PCs as well)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Fikes</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-71</link>
		<dc:creator><![CDATA[Mike Fikes]]></dc:creator>
		<pubDate>Fri, 22 Jul 2011 21:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-71</guid>
		<description><![CDATA[Interestingly, Glen Bredon&#039;s assembly solution produces its result in 3:14.]]></description>
		<content:encoded><![CDATA[<p>Interestingly, Glen Bredon&#8217;s assembly solution produces its result in 3:14.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: datajerk</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-70</link>
		<dc:creator><![CDATA[datajerk]]></dc:creator>
		<pubDate>Thu, 17 Mar 2011 19:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-70</guid>
		<description><![CDATA[35x faster on my 2.13GHz MacBook Air.]]></description>
		<content:encoded><![CDATA[<p>35x faster on my 2.13GHz MacBook Air.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Ashdown</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-69</link>
		<dc:creator><![CDATA[Pete Ashdown]]></dc:creator>
		<pubDate>Thu, 17 Mar 2011 18:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-69</guid>
		<description><![CDATA[How long does it take the Apple ][ in emulation with the speed governor off? :)]]></description>
		<content:encoded><![CDATA[<p>How long does it take the Apple ][ in emulation with the speed governor off? :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Calibrator</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-68</link>
		<dc:creator><![CDATA[Calibrator]]></dc:creator>
		<pubDate>Tue, 15 Mar 2011 20:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-68</guid>
		<description><![CDATA[If using a CPU accelerator is fair game one could use an 8 MHz &quot;Zip Chip&quot; for the Apple II.
This this a) 20 year old technology and b) should result in a speedup of 7 to 8 times regular CPU speed (slightly above 1 MHz on the Apple II).
24 minutes divided by 8 would give around 3 minutes, obviously...]]></description>
		<content:encoded><![CDATA[<p>If using a CPU accelerator is fair game one could use an 8 MHz &#8220;Zip Chip&#8221; for the Apple II.<br />
This this a) 20 year old technology and b) should result in a speedup of 7 to 8 times regular CPU speed (slightly above 1 MHz on the Apple II).<br />
24 minutes divided by 8 would give around 3 minutes, obviously&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hp lover</title>
		<link>http://retrocompute.org/2011/03/14/pi-day-rematch-apple-ii-vs-hp-41c/#comment-67</link>
		<dc:creator><![CDATA[hp lover]]></dc:creator>
		<pubDate>Tue, 15 Mar 2011 15:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://jerkwerks.com/?p=378#comment-67</guid>
		<description><![CDATA[Yep, no problem. Will do.

I do think the MCODE program had to have had some problems to run at 60% of the user code speed. That just can&#039;t be right. :-)]]></description>
		<content:encoded><![CDATA[<p>Yep, no problem. Will do.</p>
<p>I do think the MCODE program had to have had some problems to run at 60% of the user code speed. That just can&#8217;t be right. :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
