<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx</link><description>Riffing on Raymond, once again :) Raymond's post today reminded me of an email message sent out (company wide) by one of the very senior developers on the Windows 1.0 team about 6 months before they shipped. In his email, the developer announced that</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx#407828</link><pubDate>Wed, 13 Apr 2005 15:21:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:407828</guid><dc:creator>mschaef</dc:creator><description>What kind of e-mail did the Windows 1.0 team use? I'm imagining a DOS terminal program (the original MS Access, perhaps?) and a serial link to a PDP-something running e-mail software.&lt;br&gt;&lt;br&gt;&amp;quot;So sometimes, it IS the hardware.&amp;quot;&lt;br&gt;&lt;br&gt;Yeah, just ask an embedded software developer. :-)</description></item><item><title>re: It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx#407861</link><pubDate>Wed, 13 Apr 2005 17:58:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:407861</guid><dc:creator>J Osako</dc:creator><description>It is all too easy to forget that a computer system is a *system*, and that the many parts of it - hardware and software - are interdependent. &lt;br&gt;&lt;br&gt;That having been said, it has to be added that bad memory cards - and bad individual chips - were a widespread problem in the XT/AT days, one which really wasn't solved until the advent of SIMMs. Even today bad memory is more common than is usually realized, especially since it often is intermittent and can have symptoms that seem unrelated to memory. Video memory problems can be particularly hard to track down.&lt;br&gt;&lt;br&gt;Regarding Michael Schaeffer's comment, I've been given to understand that most MS development prior to about 1989 was done in a XENIX environment, largely because it supported e-mail, FTP, source control, etc. better than the MS-DOS software of the time. XENIX was still a large part of Microsoft's long-term business strategy at the time.</description></item><item><title>re: It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx#407872</link><pubDate>Wed, 13 Apr 2005 18:51:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:407872</guid><dc:creator>LarryOsterman</dc:creator><description>J Osako's right: MS development (at least OS development) in those days was done on Xenix machines.&lt;br&gt;&lt;br&gt;Most people had an H19 terminal in their office that they used for email etc, and a serial line to download from the mainframes.</description></item><item><title>re: It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx#407978</link><pubDate>Thu, 14 Apr 2005 02:49:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:407978</guid><dc:creator>Norman Diamond</dc:creator><description>There was a time when Microsoft Basic compiler development was done on a VAX.  At around that time DEC had to replace a bunch of defective third-party memory modules that were installed by value subtracted resellers because VAXes had DEC's name on them.&lt;br&gt;&lt;br&gt;I do wish that parity (or maybe better ECC such as IBM had 35 years ago) would still be commonly used in RAM as it is just about everywhere else in PCs.  Then we'd be able to infer with a rather high accuracy whether a problem was really in RAM or in software.</description></item><item><title>re: It's the hardware, stupid!</title><link>http://blogs.msdn.com/larryosterman/archive/2005/04/12/407632.aspx#409651</link><pubDate>Tue, 19 Apr 2005 17:58:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:409651</guid><dc:creator>Jason Geffner</dc:creator><description>Seems like it's not much better today...&lt;br&gt;&lt;br&gt;&amp;quot;Why untested DRAMs are getting into more and more products&amp;quot;, 4/18/05: &lt;a rel="nofollow" target="_new" href="http://www.itmanagersjournal.com/article.pl?sid=05/04/18/194256"&gt;http://www.itmanagersjournal.com/article.pl?sid=05/04/18/194256&lt;/a&gt;</description></item></channel></rss>