<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:ent="http://www.purl.org/NET/ENT/1.0/" version="2.0">
  <channel>
    <title>Curiouser and Curiouser! on n73</title>
    <link>http://matt.blogs.it/</link>
    <description>RSS feed for topic n73</description>
    <copyright>Copyright 2008 Matt Mower. Some rights reserved.</copyright>
    <generator>Squib/0.5.0.382</generator>
    <managingEditor>self@mattmower.com</managingEditor>
    <webMaster>self@mattmower.com</webMaster>
    <language>en-gb</language>
    <item>
      <title>A recipe for frustration</title>
      <link>http://matt.blogs.it/entries/00002832.html</link>
      <pubDate>Mon, 21 Apr 2008 14:29:34 +0100</pubDate>
      <description>&lt;p&gt;I don't know if it's purely down to my Mac, or a mixture of that, bluetooth, and my N73 but I am being driven mad by constant hangs, crashes, and the need to restart.&lt;/p&gt;

&lt;p&gt;The N73 will work fine as a modem for my Mac for some time and then I will be unable to connect with "modem error" messages. Restarting the N73 occasionally cures this but usually it does not. Most often when I attempt to reconnect I will get the same error several times until I restart the Mac. Or else it will hang.&lt;/p&gt;

&lt;p&gt;Usually the hang comes in the "Connecting" bit. At this point the frontmost app window will hang but MacOSX will still be responsive. If I switch windows that window will then hang, and so on. Undearneath MacOSX is still working away but the GUI dies by inches.&lt;/p&gt;

&lt;p&gt;If I SSH in from a different machine I can kill processes and even kill the window manager. Unfortunately when it respawns it's still hung. In the end I am usually forced to cycle power.&lt;/p&gt;

&lt;p&gt;I need to be connected so I have to put up with it but it's proving to be an unreliable and extremely frustrating solution. &lt;/p&gt;</description>
      <guid isPermaLink="true">http://matt.blogs.it/entries/00002832.html</guid>
      <ent:cloud ent:href="http://matt.blogs.it/topics/">
      </ent:cloud>
    </item>
  </channel>
</rss>