<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Fifteen Classic PC Design Mistakes</title>
	<atom:link href="http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/</link>
	<description>Reviews, News, and Opinion About Personal Technology by Harry McCracken &#38; Friends</description>
	<lastBuildDate>Sat, 21 Nov 2009 10:59:01 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: carfan</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-28599</link>
		<dc:creator>carfan</dc:creator>
		<pubDate>Sat, 24 Oct 2009 03:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-28599</guid>
		<description>Steve Job&#039;s insistence on fanless computers sounds similar to Soichiro Honda&#039;s insistence on air-cooled engines in the 60s.  The Honda engineers had to build an air-cooled formula-one racing engine!  Without water, cooling was never enough, so they bored a hole in the clunk case to let air in.  But, then the engine spilled oil from the hole, so they installed a centrifugal separator at the whole to separate oil from air.  A formula-one car with such an engine actually ran in a race (or the qualifying session of it)!</description>
		<content:encoded><![CDATA[<p>Steve Job&#8217;s insistence on fanless computers sounds similar to Soichiro Honda&#8217;s insistence on air-cooled engines in the 60s.  The Honda engineers had to build an air-cooled formula-one racing engine!  Without water, cooling was never enough, so they bored a hole in the clunk case to let air in.  But, then the engine spilled oil from the hole, so they installed a centrifugal separator at the whole to separate oil from air.  A formula-one car with such an engine actually ran in a race (or the qualifying session of it)!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barc</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-28017</link>
		<dc:creator>Barc</dc:creator>
		<pubDate>Thu, 15 Oct 2009 22:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-28017</guid>
		<description>When I started here at my current employer 20+ years ago, they had just got started with personal computers.  Just not PCs.  Since they were already using a Burroughs mainframe, they used the Burroughs B26, then B28, machines, mentioned by Scott Marlowe above.  Burroughs supplied (though I don&#039;t know if they charged for) mainframe emulator software.  This architecture used what the article calls &quot;sidecar expansion&quot;.  Burroughs called the extensions &quot;slices&quot;.  A brother-in-law in the CG Reserve reported seeing a room full of metal shelving at his base whereon each machine was augmented with slices to the limit of the shelf length (file servers?  Never found out).  (We never had any that large here.)  They ran on CTOS (Convergent Technology OS) until Burroughs acquired Convergent.  After that, they just changed the name to BTOS.  

The text-based system, lacking a mouse, had an interesting feature in the word processor.  (To be fair, I never really used any other text-based word processor; by the time we moved to PCs, they were GUI.  I imagine other WPs worked similarly.)  To copy a block of text, you moved the cursor with the arrow keys to the beginning of the text, pressed a key (I think it was a soft key) to &quot;mark&quot; the starting point, then moved the cursor to the end and pressed another key to &quot;bound&quot; your selection.  Then you could copy the highlighted selection.</description>
		<content:encoded><![CDATA[<p>When I started here at my current employer 20+ years ago, they had just got started with personal computers.  Just not PCs.  Since they were already using a Burroughs mainframe, they used the Burroughs B26, then B28, machines, mentioned by Scott Marlowe above.  Burroughs supplied (though I don&#8217;t know if they charged for) mainframe emulator software.  This architecture used what the article calls &#8220;sidecar expansion&#8221;.  Burroughs called the extensions &#8220;slices&#8221;.  A brother-in-law in the CG Reserve reported seeing a room full of metal shelving at his base whereon each machine was augmented with slices to the limit of the shelf length (file servers?  Never found out).  (We never had any that large here.)  They ran on CTOS (Convergent Technology OS) until Burroughs acquired Convergent.  After that, they just changed the name to BTOS.  </p>
<p>The text-based system, lacking a mouse, had an interesting feature in the word processor.  (To be fair, I never really used any other text-based word processor; by the time we moved to PCs, they were GUI.  I imagine other WPs worked similarly.)  To copy a block of text, you moved the cursor with the arrow keys to the beginning of the text, pressed a key (I think it was a soft key) to &#8220;mark&#8221; the starting point, then moved the cursor to the end and pressed another key to &#8220;bound&#8221; your selection.  Then you could copy the highlighted selection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Cassara</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-27085</link>
		<dc:creator>Joe Cassara</dc:creator>
		<pubDate>Thu, 01 Oct 2009 03:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-27085</guid>
		<description>#16: Commodore PET 2001 chicklet keyboard: Even a genius like Chuck Peddle is allowed to goof-up now and then.</description>
		<content:encoded><![CDATA[<p>#16: Commodore PET 2001 chicklet keyboard: Even a genius like Chuck Peddle is allowed to goof-up now and then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enrique</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-24225</link>
		<dc:creator>Enrique</dc:creator>
		<pubDate>Sun, 23 Aug 2009 09:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-24225</guid>
		<description>For those who want to know why the 1541 drive was sooo slow with the C-64, here&#039;s an old post from the guru Jim Brain.

http://www.geocities.com/rmelick/6522f.txt

&gt;  We early PET/CBM freaks knew, from playing music, that there was
&gt;  something wrong with the 6522&#039;s shift register...

So it was a bug in the VIA 6522 shift register which caused the data transfer to be handled in software rather than hardware, slowing down all the system.</description>
		<content:encoded><![CDATA[<p>For those who want to know why the 1541 drive was sooo slow with the C-64, here&#8217;s an old post from the guru Jim Brain.</p>
<p><a href="http://www.geocities.com/rmelick/6522f.txt" rel="nofollow">http://www.geocities.com/rmelick/6522f.txt</a></p>
<p>&gt;  We early PET/CBM freaks knew, from playing music, that there was<br />
&gt;  something wrong with the 6522&#8217;s shift register&#8230;</p>
<p>So it was a bug in the VIA 6522 shift register which caused the data transfer to be handled in software rather than hardware, slowing down all the system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fallos en el diseño de computadoras &#124; IdentidadGeek</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-23982</link>
		<dc:creator>Fallos en el diseño de computadoras &#124; IdentidadGeek</dc:creator>
		<pubDate>Fri, 21 Aug 2009 05:37:21 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-23982</guid>
		<description>[...] Tecnologizer, 15 classic PC Design Mistakes AKPC_IDS += [...]</description>
		<content:encoded><![CDATA[<p>[...] Tecnologizer, 15 classic PC Design Mistakes AKPC_IDS += [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: samuel</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-15/#comment-21486</link>
		<dc:creator>samuel</dc:creator>
		<pubDate>Wed, 22 Jul 2009 18:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-21486</guid>
		<description>dVmvK5 odfBxZakGhH3v96M2Qsk</description>
		<content:encoded><![CDATA[<p>dVmvK5 odfBxZakGhH3v96M2Qsk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Algunos Errores de diseño en ordenadores clásicos &#124; CyberHades</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-14/#comment-20873</link>
		<dc:creator>Algunos Errores de diseño en ordenadores clásicos &#124; CyberHades</dc:creator>
		<pubDate>Tue, 14 Jul 2009 15:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-20873</guid>
		<description>[...] Technologizer [...]</description>
		<content:encoded><![CDATA[<p>[...] Technologizer [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: user</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-14/#comment-20753</link>
		<dc:creator>user</dc:creator>
		<pubDate>Sun, 12 Jul 2009 06:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-20753</guid>
		<description>For a modern one, a graphic card: EVGA Geforce 8600 GTS. It adjusted the fan speed in accordance with the temperature, but for some reason reason it would slow down when it would heat up, causing it to run at 85 C and feel blistering hot to the touch. Using software to control the fan would fix this, or installing an aftermarket cooler. 

Blue &amp; White Power Mac G3, early G4 - Had a cooling system that made no sense. Big fan blows in through the side of the case hitting the expansion cards, CPU got indirect air because it really didn&#039;t get that hot. Only problem was the hot air had no where to go (the power supply fan wasn&#039;t enough), so this bad design caused turbulence, resulting in had been an exhaust fan on top of the unit.

What else.. I have a Compaq Deskpro that won&#039;t boot unless it has a Compaq CDROM drive installed, but other than that it&#039;s a reliable solid computer.</description>
		<content:encoded><![CDATA[<p>For a modern one, a graphic card: EVGA Geforce 8600 GTS. It adjusted the fan speed in accordance with the temperature, but for some reason reason it would slow down when it would heat up, causing it to run at 85 C and feel blistering hot to the touch. Using software to control the fan would fix this, or installing an aftermarket cooler. </p>
<p>Blue &amp; White Power Mac G3, early G4 &#8211; Had a cooling system that made no sense. Big fan blows in through the side of the case hitting the expansion cards, CPU got indirect air because it really didn&#8217;t get that hot. Only problem was the hot air had no where to go (the power supply fan wasn&#8217;t enough), so this bad design caused turbulence, resulting in had been an exhaust fan on top of the unit.</p>
<p>What else.. I have a Compaq Deskpro that won&#8217;t boot unless it has a Compaq CDROM drive installed, but other than that it&#8217;s a reliable solid computer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dholm.com &#187; Blog Archive &#187; Tumblelog 090706</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-14/#comment-20326</link>
		<dc:creator>dholm.com &#187; Blog Archive &#187; Tumblelog 090706</dc:creator>
		<pubDate>Mon, 06 Jul 2009 09:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-20326</guid>
		<description>[...] Fifteen Classic PC Design Mistakes, Technologizer has made a great list of the ten worst PC design mistakes. [...]</description>
		<content:encoded><![CDATA[<p>[...] Fifteen Classic PC Design Mistakes, Technologizer has made a great list of the ten worst PC design mistakes. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Lajko</title>
		<link>http://technologizer.com/2009/06/14/fifteen-classic-pc-design-mistakes/comment-page-14/#comment-19794</link>
		<dc:creator>Patrick Lajko</dc:creator>
		<pubDate>Mon, 29 Jun 2009 18:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://technologizer.com/?p=12983#comment-19794</guid>
		<description>I had forgotten about the mistake in the CGA colors of the PC: cyan, magenta and yellow --- not red, blue and green. They used printing colors rather than video colors. So you could never get real color images or graphics. They improved with the alternate color set: red, yellow and blue. Still not right as these are the colors for mixing paint (remember grade school and mixing colors with watercolors?). How could all the IBM brains not know the difference between CMY and RGB?</description>
		<content:encoded><![CDATA[<p>I had forgotten about the mistake in the CGA colors of the PC: cyan, magenta and yellow &#8212; not red, blue and green. They used printing colors rather than video colors. So you could never get real color images or graphics. They improved with the alternate color set: red, yellow and blue. Still not right as these are the colors for mixing paint (remember grade school and mixing colors with watercolors?). How could all the IBM brains not know the difference between CMY and RGB?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
