<?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: Preservation, Conservation, Restoration: What&#8217;s the Difference?</title>
	<atom:link href="http://www.computerhistory.org/atchm/preservation-conservation-restoration-whats-the-difference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerhistory.org/atchm/preservation-conservation-restoration-whats-the-difference/</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Fri, 10 May 2013 18:58:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Karen Kroslowitz</title>
		<link>http://www.computerhistory.org/atchm/preservation-conservation-restoration-whats-the-difference/#comment-39</link>
		<dc:creator>Karen Kroslowitz</dc:creator>
		<pubDate>Mon, 29 Oct 2012 15:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerhistory.org/atchm/?p=1417#comment-39</guid>
		<description>Thanks for your comments, Lyle. It&#039;s great to have volunteers like you who are both conscientious about your work and willing to learn about the many facets and impact that restoration projects can have on artifacts - and audiences.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Lyle. It&#8217;s great to have volunteers like you who are both conscientious about your work and willing to learn about the many facets and impact that restoration projects can have on artifacts &#8211; and audiences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lbickley</title>
		<link>http://www.computerhistory.org/atchm/preservation-conservation-restoration-whats-the-difference/#comment-38</link>
		<dc:creator>lbickley</dc:creator>
		<pubDate>Sun, 28 Oct 2012 00:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerhistory.org/atchm/?p=1417#comment-38</guid>
		<description>A close friend of mine also bought, restored and collected clocks. Since I&#039;m a collector who acquires vintage computers and restores them - we had a lot in common! It made for great conversations.

Your points, Karen, on preservation, conservation, and restoration are well made. 

It also seems to me there are several &quot;classes&quot; or &quot;levels&quot; of restoration. Some examples:

Get it working
--------------
When I restore a piece of vintage test equipment, my goal is typically to get it running so I can put it to work. For example, I recently acquired several vintage Wilson hard drive testers. If one was not working properly, I replaced parts using vintage or modern components. My goal was not to have/show a tester as a historical object, but rather to use it as a working tool.

Restoration - maintain it&#039;s vintage status
------------------------------------------
In this case, a restoration must only use modules, peripherals and parts which are age and configuration appropriate. For instance, I acquired a DEC PDP 11/34 and restored it carefully. When it could pass all diagnostics, I upgraded it with cache memory, additional RAM memory, added two RL02 cartridge disks, and a third party SCSI controller. All the boards and peripherals used were age appropriate to the 11/34; i.e., one could have expected to see an 11/34 in the seventies with this configuration.

Restoration - of a historical artifact
---------------------------------------
This is the most demanding level of restoration. We vintage computer collectors rarely restore to this level. The goal is to restore a system with as little change to the artifact as possible. This means using replacement parts which are the same type and vintage as those one is replacing and insuring that any changes made can be reversed.

Those of us who had the privilege of restoring the CHM&#039;s PDP-1 did so at this level.

The entire restoration process was carefully defined by the Restoration Team. We studied the history, uses and architecture of the PDP-1. We discussed the alternative restoration processes by the hour.

Recognizing we were dealing with a rare artifact, we created a restoration process which insured to the best of our ability that we would not have an event which could damage the system in any way.

We also initiated a system log in which every action we took and changes to our process were logged in detail.

A critical element in our restoration process was that every part which was replaced was put into a plastic bag with a tag identifying its origin module&#039;s location. The replacement part was identified on the module with a &quot;dot&quot; of red nail polish. By doing so, we were able to insure that all our &quot;changes&quot; were reversible.

If the PDP-1 Team had merely had the charter to &quot;get the PDP-1 working&quot; we could have done so a LOT more quickly.

However, the process we used insured that the PDP-1 not only &quot;worked&quot;, but maintained its status as an accurate historical artifact.

I am a strong advocate of future CHM restorations and agree with the CHM&#039;s strategy of being &quot;dedicated to collecting and preserving at least one unaltered example of the major technological advances of the Information Age&quot;.

While some may see this as too restrictive, from a practical perspective it&#039;s actually quite broad. Restoration of historical artifacts is very doable - but a necessarily careful and sometimes time consuming process.</description>
		<content:encoded><![CDATA[<p>A close friend of mine also bought, restored and collected clocks. Since I&#8217;m a collector who acquires vintage computers and restores them &#8211; we had a lot in common! It made for great conversations.</p>
<p>Your points, Karen, on preservation, conservation, and restoration are well made. </p>
<p>It also seems to me there are several &#8220;classes&#8221; or &#8220;levels&#8221; of restoration. Some examples:</p>
<p>Get it working<br />
&#8212;&#8212;&#8212;&#8212;&#8211;<br />
When I restore a piece of vintage test equipment, my goal is typically to get it running so I can put it to work. For example, I recently acquired several vintage Wilson hard drive testers. If one was not working properly, I replaced parts using vintage or modern components. My goal was not to have/show a tester as a historical object, but rather to use it as a working tool.</p>
<p>Restoration &#8211; maintain it&#8217;s vintage status<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
In this case, a restoration must only use modules, peripherals and parts which are age and configuration appropriate. For instance, I acquired a DEC PDP 11/34 and restored it carefully. When it could pass all diagnostics, I upgraded it with cache memory, additional RAM memory, added two RL02 cartridge disks, and a third party SCSI controller. All the boards and peripherals used were age appropriate to the 11/34; i.e., one could have expected to see an 11/34 in the seventies with this configuration.</p>
<p>Restoration &#8211; of a historical artifact<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
This is the most demanding level of restoration. We vintage computer collectors rarely restore to this level. The goal is to restore a system with as little change to the artifact as possible. This means using replacement parts which are the same type and vintage as those one is replacing and insuring that any changes made can be reversed.</p>
<p>Those of us who had the privilege of restoring the CHM&#8217;s PDP-1 did so at this level.</p>
<p>The entire restoration process was carefully defined by the Restoration Team. We studied the history, uses and architecture of the PDP-1. We discussed the alternative restoration processes by the hour.</p>
<p>Recognizing we were dealing with a rare artifact, we created a restoration process which insured to the best of our ability that we would not have an event which could damage the system in any way.</p>
<p>We also initiated a system log in which every action we took and changes to our process were logged in detail.</p>
<p>A critical element in our restoration process was that every part which was replaced was put into a plastic bag with a tag identifying its origin module&#8217;s location. The replacement part was identified on the module with a &#8220;dot&#8221; of red nail polish. By doing so, we were able to insure that all our &#8220;changes&#8221; were reversible.</p>
<p>If the PDP-1 Team had merely had the charter to &#8220;get the PDP-1 working&#8221; we could have done so a LOT more quickly.</p>
<p>However, the process we used insured that the PDP-1 not only &#8220;worked&#8221;, but maintained its status as an accurate historical artifact.</p>
<p>I am a strong advocate of future CHM restorations and agree with the CHM&#8217;s strategy of being &#8220;dedicated to collecting and preserving at least one unaltered example of the major technological advances of the Information Age&#8221;.</p>
<p>While some may see this as too restrictive, from a practical perspective it&#8217;s actually quite broad. Restoration of historical artifacts is very doable &#8211; but a necessarily careful and sometimes time consuming process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.computerhistory.org @ 2013-06-06 16:28:29 by W3 Total Cache --