<?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: TM Manager hacks Time Machine Back to the Future</title>
	<atom:link href="http://www.christopherprice.net/hack-released-for-time-machine-for-airport-disk-windows-sharing-86.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.christopherprice.net/hack-released-for-time-machine-for-airport-disk-windows-sharing-86.html</link>
	<description>Wireless consumer advocate Christopher Price tackles the rest of tech.</description>
	<lastBuildDate>Wed, 08 Sep 2010 22:43:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Apple Neutering AirPort Extreme to Sell Time Capsule? &#124; Christopher Price .net</title>
		<link>http://www.christopherprice.net/hack-released-for-time-machine-for-airport-disk-windows-sharing-86.html/comment-page-1#comment-767</link>
		<dc:creator>Apple Neutering AirPort Extreme to Sell Time Capsule? &#124; Christopher Price .net</dc:creator>
		<pubDate>Thu, 06 Mar 2008 06:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/2007/11/07/hack-released-for-time-machine-for-airport-disk-windows-sharing/#comment-767</guid>
		<description>[...] the hackers have continued to uncover Time Machine&#8217;s full range of support. Hacks cited previously on this blog work even better under 10.5.2. As Apple improves the code that was buggy, they still leave features [...]</description>
		<content:encoded><![CDATA[<p>[...] the hackers have continued to uncover Time Machine&#8217;s full range of support. Hacks cited previously on this blog work even better under 10.5.2. As Apple improves the code that was buggy, they still leave features [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
