<?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 for codelaide software</title>
	<atom:link href="http://codelaide.com/blog/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://codelaide.com/blog</link>
	<description>we &#60;3 macs, too</description>
	<lastBuildDate>Thu, 10 Dec 2009 12:11:13 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Lighthouse is Leopard-ready by georg</title>
		<link>http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/comment-page-1/#comment-14126</link>
		<dc:creator>georg</dc:creator>
		<pubDate>Thu, 10 Dec 2009 12:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/#comment-14126</guid>
		<description>Could you please send an email to support@codelaide.com - I can help you more efficiently this way, since the blog isn&#039;t really built to handle support requests.

That being said, the problem could very well be caused by the DVD drive firmware flashing. The error message you are getting is generated by OS X, not by Lighthouse. In fact, OS X refuses to launch Lighthouse at all, so provided that no program tinkered with the Lighthouse application itself, something within OS X must have changed.</description>
		<content:encoded><![CDATA[<p>Could you please send an email to <a href="mailto:support@codelaide.com">support@codelaide.com</a> &#8211; I can help you more efficiently this way, since the blog isn&#8217;t really built to handle support requests.</p>
<p>That being said, the problem could very well be caused by the DVD drive firmware flashing. The error message you are getting is generated by OS X, not by Lighthouse. In fact, OS X refuses to launch Lighthouse at all, so provided that no program tinkered with the Lighthouse application itself, something within OS X must have changed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lighthouse is Leopard-ready by Astonished</title>
		<link>http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/comment-page-1/#comment-14109</link>
		<dc:creator>Astonished</dc:creator>
		<pubDate>Tue, 08 Dec 2009 22:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/#comment-14109</guid>
		<description>My Lighthouse (v1.2.7) just suddenly stopped working; clicking on the app brings the message &quot;You can&#039;t open the application &#039;Lighthouse&#039; because it is not supported on this architecture&quot;. 

I&#039;m running a plain Mac with Leopard, nothing fancy at all. The only modification I&#039;ve made is to - I think - flash the firmware on the DVD drive, for which I installed Windows under VMWare Fusion. But that surely should have no effect on Lighthouse.</description>
		<content:encoded><![CDATA[<p>My Lighthouse (v1.2.7) just suddenly stopped working; clicking on the app brings the message &#8220;You can&#8217;t open the application &#8216;Lighthouse&#8217; because it is not supported on this architecture&#8221;. </p>
<p>I&#8217;m running a plain Mac with Leopard, nothing fancy at all. The only modification I&#8217;ve made is to &#8211; I think &#8211; flash the firmware on the DVD drive, for which I installed Windows under VMWare Fusion. But that surely should have no effect on Lighthouse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on News on the 7.2.1 Airport Extreme Issue by georg</title>
		<link>http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/comment-page-1/#comment-2790</link>
		<dc:creator>georg</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/#comment-2790</guid>
		<description>Yeah, it&#039;s pretty annoying, but maybe the airport team has been kept busy with time capsule? anyways, I&#039;ve reported the bug a long time ago, so I&#039;m still crossing my fingers that it will be fixed through a firmware upgrade eventually.</description>
		<content:encoded><![CDATA[<p>Yeah, it&#8217;s pretty annoying, but maybe the airport team has been kept busy with time capsule? anyways, I&#8217;ve reported the bug a long time ago, so I&#8217;m still crossing my fingers that it will be fixed through a firmware upgrade eventually.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on News on the 7.2.1 Airport Extreme Issue by David Rice</title>
		<link>http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/comment-page-1/#comment-2789</link>
		<dc:creator>David Rice</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/#comment-2789</guid>
		<description>Hey, this is damn annoying. I&#039;ve been having this problem too and have verified it to be the same NAT/PMP reasons. Downgrading to 7.2 is a good interim measure, when the NAT/PMP server dies it will restart again instead of lying on the floor. 7.1.1 is no longer available from the Apple website.

I love when I phone Apple and the claim that such bugs do not exist and want to replace my Airport Express. Dudes it&#039;s a firmware issue.</description>
		<content:encoded><![CDATA[<p>Hey, this is damn annoying. I&#8217;ve been having this problem too and have verified it to be the same NAT/PMP reasons. Downgrading to 7.2 is a good interim measure, when the NAT/PMP server dies it will restart again instead of lying on the floor. 7.1.1 is no longer available from the Apple website.</p>
<p>I love when I phone Apple and the claim that such bugs do not exist and want to replace my Airport Express. Dudes it&#8217;s a firmware issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lighthouse is Leopard-ready by georg</title>
		<link>http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/comment-page-1/#comment-2269</link>
		<dc:creator>georg</dc:creator>
		<pubDate>Wed, 21 Nov 2007 21:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/#comment-2269</guid>
		<description>It&#039;s possible that this works, but you still definitely need to have a .mac account. According to this &lt;a href=&quot;http://docs.info.apple.com/article.html?artnum=307024&quot; rel=&quot;nofollow&quot;&gt;technical note&lt;/a&gt;, Back to my Mac uses UDP port 4500 for the sharing features, so I&#039;d suggest to create and run a Lighthouse profile on the Mac you want to connect to that forwards port 4500 (enter this for both the private and public port). Choose &quot;UDP&quot; or &quot;Both&quot; as the type. According to this &lt;a href=&quot;http://discussions.apple.com/thread.jspa?threadID=1225637&quot; rel=&quot;nofollow&quot;&gt;article&lt;/a&gt;, UDP port 500 is also used, so you might want to add this as well. Running this profile on the Mac you want to connect *to* then might solve your BTMM issues.

However, note that BTMM is actually a pretty complex, dynamic service, so if you have more than one Mac in your home network that you want to use BTMM on, it&#039;s very well possible that it configures a different port than 4500 for one of these Macs. I couldn&#039;t find a definitive guide on which ports need to be forwarded for BTMM (which configures itself automatically on supported routers), but this info might help. Please let me know if you have success with such a profile.</description>
		<content:encoded><![CDATA[<p>It&#8217;s possible that this works, but you still definitely need to have a .mac account. According to this <a href="http://docs.info.apple.com/article.html?artnum=307024" rel="nofollow">technical note</a>, Back to my Mac uses UDP port 4500 for the sharing features, so I&#8217;d suggest to create and run a Lighthouse profile on the Mac you want to connect to that forwards port 4500 (enter this for both the private and public port). Choose &#8220;UDP&#8221; or &#8220;Both&#8221; as the type. According to this <a href="http://discussions.apple.com/thread.jspa?threadID=1225637" rel="nofollow">article</a>, UDP port 500 is also used, so you might want to add this as well. Running this profile on the Mac you want to connect *to* then might solve your BTMM issues.</p>
<p>However, note that BTMM is actually a pretty complex, dynamic service, so if you have more than one Mac in your home network that you want to use BTMM on, it&#8217;s very well possible that it configures a different port than 4500 for one of these Macs. I couldn&#8217;t find a definitive guide on which ports need to be forwarded for BTMM (which configures itself automatically on supported routers), but this info might help. Please let me know if you have success with such a profile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lighthouse is Leopard-ready by Hans</title>
		<link>http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/comment-page-1/#comment-2267</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Wed, 21 Nov 2007 18:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/11/18/lighthouse-is-leopard-ready/#comment-2267</guid>
		<description>Is there anything I can configure for getting the Back to my mac functionality working?</description>
		<content:encoded><![CDATA[<p>Is there anything I can configure for getting the Back to my mac functionality working?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on News on the 7.2.1 Airport Extreme Issue by codelaide software &#187; Lighthouse 1.2.2</title>
		<link>http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/comment-page-1/#comment-1966</link>
		<dc:creator>codelaide software &#187; Lighthouse 1.2.2</dc:creator>
		<pubDate>Sun, 23 Sep 2007 21:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/09/21/news-on-the-721-airport-extreme-issue/#comment-1966</guid>
		<description>[...] 1.2.2 finally delivers a workaround for the stability problems introduced by the 7.2.1 firmware upgrade for the 802.11n Apple Airport Extreme base [...]</description>
		<content:encoded><![CDATA[<p>[...] 1.2.2 finally delivers a workaround for the stability problems introduced by the 7.2.1 firmware upgrade for the 802.11n Apple Airport Extreme base [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please don&#8217;t upgrade your Airport Extreme to 7.2.1 by codelaide software &#187; News on the 7.2.1 Airport Extreme Issue</title>
		<link>http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/comment-page-1/#comment-1937</link>
		<dc:creator>codelaide software &#187; News on the 7.2.1 Airport Extreme Issue</dc:creator>
		<pubDate>Fri, 21 Sep 2007 20:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/#comment-1937</guid>
		<description>[...] back from our vacation and have started investigating the issue that prevents Lighthouse from working on n-enabled Airport Extreme base stations after the recent [...]</description>
		<content:encoded><![CDATA[<p>[...] back from our vacation and have started investigating the issue that prevents Lighthouse from working on n-enabled Airport Extreme base stations after the recent [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please don&#8217;t upgrade your Airport Extreme to 7.2.1 by James</title>
		<link>http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/comment-page-1/#comment-1903</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 19 Sep 2007 02:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/#comment-1903</guid>
		<description>I didn&#039;t realize it was that easy!!!  I just uploaded a previous firmware (7.1.1) and it looks like I&#039;m back in business. Thanks!!</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t realize it was that easy!!!  I just uploaded a previous firmware (7.1.1) and it looks like I&#8217;m back in business. Thanks!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please don&#8217;t upgrade your Airport Extreme to 7.2.1 by georg</title>
		<link>http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/comment-page-1/#comment-1874</link>
		<dc:creator>georg</dc:creator>
		<pubDate>Sat, 15 Sep 2007 16:39:28 +0000</pubDate>
		<guid isPermaLink="false">http://codelaide.com/blog/2007/08/30/please-dont-upgrade-your-airport-extreme-to-721/#comment-1874</guid>
		<description>I&#039;m still investigating, but it currently looks as if the NAT/PMP service is completely unavailable on Fast Ethernet pre-n Airport Extremes after the 7.2.1 installation (though it works fine on Gigabit Ethernet ones, indicating that this is clearly a firmware bug introduced by Apple).

Since the NAT/PMP service is not available &lt;em&gt;at all&lt;/em&gt; on the affected routers after installing 7.2.1, a workaround is not possible. I&#039;m still waiting for some diagnostic info to confirm this, but I&#039;d greatly suggest downgrading to a previous version in the meantime, since a workaround will probably not be possible and we&#039;ll have to wait for Apple to fix the issue in the next firmware upgrade after 7.2.1.

It&#039;s not exactly &quot;screwing around&quot; either, just select the base station in &quot;Airport Utility&quot;, click &quot;Manual Setup&quot;, then select &quot;Upload Firmware...&quot; from the &quot;Base Station&quot; menu in the menu bar. Finally, select a previous version and hit the &quot;OK&quot; button.

Downgrading the firmware is &lt;em&gt;not&lt;/em&gt; a hack, it&#039;s a supported feature of &quot;Airport Utility&quot;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still investigating, but it currently looks as if the NAT/PMP service is completely unavailable on Fast Ethernet pre-n Airport Extremes after the 7.2.1 installation (though it works fine on Gigabit Ethernet ones, indicating that this is clearly a firmware bug introduced by Apple).</p>
<p>Since the NAT/PMP service is not available <em>at all</em> on the affected routers after installing 7.2.1, a workaround is not possible. I&#8217;m still waiting for some diagnostic info to confirm this, but I&#8217;d greatly suggest downgrading to a previous version in the meantime, since a workaround will probably not be possible and we&#8217;ll have to wait for Apple to fix the issue in the next firmware upgrade after 7.2.1.</p>
<p>It&#8217;s not exactly &#8220;screwing around&#8221; either, just select the base station in &#8220;Airport Utility&#8221;, click &#8220;Manual Setup&#8221;, then select &#8220;Upload Firmware&#8230;&#8221; from the &#8220;Base Station&#8221; menu in the menu bar. Finally, select a previous version and hit the &#8220;OK&#8221; button.</p>
<p>Downgrading the firmware is <em>not</em> a hack, it&#8217;s a supported feature of &#8220;Airport Utility&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.855 seconds -->
<!-- Cached page served by WP-Cache -->
