<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tech Debug &#187; hardware</title>
	<atom:link href="http://techdebug.com/blog/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://techdebug.com</link>
	<description>My tech thoughts put out on the blogosphere</description>
	<lastBuildDate>Thu, 14 Jan 2010 01:42:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Snow Leopard: WWAN using Merlin XU870 ExpressCard</title>
		<link>http://techdebug.com/blog/2009/09/02/snow-leopard-wwan-using-merlin-xu870-expresscard/</link>
		<comments>http://techdebug.com/blog/2009/09/02/snow-leopard-wwan-using-merlin-xu870-expresscard/#comments</comments>
		<pubDate>Wed, 02 Sep 2009 12:20:32 +0000</pubDate>
		<dc:creator>lantrix</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[10.6]]></category>
		<category><![CDATA[WWAN]]></category>
		<category><![CDATA[snow leopard]]></category>
		<category><![CDATA[three broadband]]></category>
		<category><![CDATA[xu870]]></category>

		<guid isPermaLink="false">http://techdebug.com/?p=550</guid>
		<description><![CDATA[This is the same issue I&#8217;ve posted on a couple of forums. It&#8217;s seemed detailed enough to be a blog post, so here it is. Under 10.5.8 (Leopard) I was successfully using my Merlin XU870 ExpressCard (supplied by ISP) with Three Broadband (3) in Australia. I did not use the 3 drivers, but used the [...]]]></description>
			<content:encoded><![CDATA[<p>This is the same issue I&#8217;ve posted on a couple of forums. It&#8217;s seemed detailed enough to be a blog post, so here it is. Under 10.5.8 (Leopard) I was successfully using my Merlin XU870 ExpressCard (supplied by ISP) with Three Broadband (3) in Australia. I did not use the 3 drivers, but used the Leopard WWAN built-in to connect. There was never an issue as Leopard detected the card as a &#8220;Novatel Wireless HSDPA Modem&#8221;, and I configured the Network Advanced settings for 3 postpaid services as:</p>
<ul>
<li>Vendor: Novatel Wireless Inc.</li>
<li>Model: GSM</li>
<li>APN: 3netaccess</li>
<li>CID: 1</li>
</ul>
<p>
I installed Snow Leopard as an Upgrade (not a fresh install) after having a CCC backup and a Time machine backup in place.<br />
<br />
When I plugged in my 3 expresscard, 10.6 detects the card, initialises and populates the WWAN icon with &#8220;Telstra 3G: Not Configured&#8221;.<br />
<img src="http://s375.photobucket.com/albums/oo195/lantrix/apple/wwan01.png" alt="Screenshot 1"/><br />
It detects the card as a &#8220;Novatel Wireless HSDPA Modem&#8221;, and automatically configures the Network Advanced settings of the card, as shown:<br />
<img src="http://s375.photobucket.com/albums/oo195/lantrix/apple/wwan02.png" alt="Screenshot 2"/><br />
The question is: Why is the APN <em>telstra.datapack</em> setup as default?<br />
<br />
I am able to <b>change the APN to <em>3netaccess</em></b>, which results in a successful connection to 3:<br />
<code>Wed Sep  2 15:38:25 2009 : Initializing phone: ATE0V1&#038;F&#038;D2&#038;C1S0=0<br />
Wed Sep  2 15:38:25 2009 : Initializing PDP context: AT+CGDCONT=1,"IP","3netaccess"<br />
Wed Sep  2 15:38:25 2009 : Initializing with secondary command: AT$NWPDN=0<br />
Wed Sep  2 15:38:25 2009 : Dialing: ATD*99***1<a href="http://search.twitter.com/search?q=%23" class="tweet-hashtag">#</a><br />
Wed Sep  2 15:38:25 2009 : Waiting for connection<br />
Wed Sep  2 15:38:25 2009 : Connection established<br />
Wed Sep  2 15:38:28 2009 : Serial connection established.<br />
Wed Sep  2 15:38:28 2009 : Using interface ppp0<br />
Wed Sep  2 15:38:28 2009 : Connect: ppp0 &lt;--&gt; /dev/cu.wwan<br />
Wed Sep  2 15:38:32 2009 : Could not determine remote IP address: defaulting to 10.64.***.***<br />
Wed Sep  2 15:38:32 2009 : local  IP address 115.130.***.***<br />
Wed Sep  2 15:38:32 2009 : remote IP address 10.64.***.***<br />
Wed Sep  2 15:38:32 2009 : primary   DNS address 202.124.68.182<br />
Wed Sep  2 15:38:32 2009 : secondary DNS address 202.124.65.22</code></p>
<p>The <b>annoying thing is the WWAN menu still shows Telstra</b> when connected.<br />
<img src="http://s375.photobucket.com/albums/oo195/lantrix/apple/wwan03.png" alt="Screenshot 3"/><br />
<br />
Looking at the WWAN system file:<br />
<code>cd /System/Library/Extensions/IOSerialFamily.kext/\<br />
Contents/PlugIns/AppleWWANSupport.kext/Contents/\<br />
Resources/<br />
less countryCodes.plist</code><br />
it has only Telstra, Optus and Vodafone carriers listed. I think this could be the cause of the default APN being populated in the Advanced settings. I can&#8217;t find where the &#8220;Telstra 3G&#8221; in the WWAN menu item is coming from though.<br />
<br />
I&#8217;d appreciate if anyone can give their thoughts on how to fix this.</p>
]]></content:encoded>
			<wfw:commentRss>http://techdebug.com/blog/2009/09/02/snow-leopard-wwan-using-merlin-xu870-expresscard/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Philips VOIP321 no longer works with Skype 3.8.0.188 or later</title>
		<link>http://techdebug.com/blog/2009/01/14/philips-voip321-no-longer-works-with-skype-380188-or-later/</link>
		<comments>http://techdebug.com/blog/2009/01/14/philips-voip321-no-longer-works-with-skype-380188-or-later/#comments</comments>
		<pubDate>Tue, 13 Jan 2009 13:40:46 +0000</pubDate>
		<dc:creator>lantrix</dc:creator>
				<category><![CDATA[hardware]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[broken]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[eol]]></category>
		<category><![CDATA[philips]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[skype]]></category>
		<category><![CDATA[voip]]></category>
		<category><![CDATA[voip321]]></category>

		<guid isPermaLink="false">http://techdebug.com/?p=325</guid>
		<description><![CDATA[I&#8217;ve been having a conversation on a Skype bug reporting forum, and it came to a conclusion that the Philips VOIP321 Skype Phone is just not worth purchasing. I&#8217;m an owner of a Philips VOIP321 phone, and until December 2008 it worked fine. However the latest Skype update has put an end to product useability.
Since [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been having a conversation on a Skype bug reporting forum, and it came to a conclusion that the <a href="http://www.consumer.philips.com/consumer/en/au/consumer/cc/_productid_VOIP3211S_79_AU_CONSUMER/Internet-DECT-phone+VOIP3211S-79">Philips VOIP321 Skype Phone</a> is just not worth purchasing. I&#8217;m an owner of a Philips VOIP321 phone, and until December 2008 it worked fine. However the latest Skype update has put an end to product useability.</p>
<p><strong>Since Skype Version 3.8.0.188 (Release date: November 19, 2008) and all later versions (including Skype 4 Betas as at Jan. 2009) the software Philips supply no longer works with Skype and the VOIP321 phone.</strong></p>
<p>The latest VOIP321 <a href="http://tinyurl.com/6b2xrp" rel="nofollow">driver from their website</a> suffers the same issue, even though it states &#8220;The VOIP321 USB Phone Driver V 3.8.3 which can be downloaded from Philips web site is compatible with Skype software version from V2.0.0.x until V3.8.0.x&#8221;. This is <strong><em>plainly no longer correct</em></strong> with the latest stable release of Skype, V3.8.0.188.</p>
<p>Skype developers are <a href="https://developer.skype.com/jira/browse/SPA-599" rel="nofollow">unable to do anything about it</a> as they see it being a Philips driver problem. Phillips wont update their driver (Quoting support staff &#8220;&#8230; no more development/fixes are being incorporated into the VOIP321.EXE file&#8221;).</p>
<p><strong>The solution to getting this beast working again:</strong></p>
<ul>
<li>Uninstall Skype 3.8.0.188 (or later non-working version)</li>
<li>Visit the <a href="http://www.oldapps.com/skype.htm">Old Apps website</a> where you can (without support from Skype) download a previous version and use it.</li>
<li>I found that <em>Skype <del datetime="2009-01-17T02:34:34+00:00">3.8.0.154</del> 3.8.0.139 worked fine for me with the VOIP321 hardware under Windows XP</em></li>
<li>Reinstall the older version.</li>
<li>Launch the newly installed older version of Skype</li>
<li>Remove the VOIP321.exe application from the Skype menu: Tools > Options > Advanced > Advanced Settings > Manage other programs Access to Skype</li>
<li>Reboot your Windows Computer</li>
</ul>
<p>If you don&#8217;t own one of these yet, don&#8217;t waste your time on Philips Skype phone devices. Their driver support is lacking when Skype is updated and they <a href="http://en.wikipedia.org/wiki/End-of-life_(product)">EOL</a> their product too soon. You buy a product for a few hundred dollars and it becomes useless 12 months later. Phillips would probably rather sell you a newer bit of hardware.</p>
<p>Should they update their driver at this point I will be the first to commend them. I forgot to mention: Phillips Skype phones (where your PC is required) are Windows Only. <em>No Mac or Linux support or drivers are offered</em>.</p>
<p>My next purchase will be a wifi or wired ethernet Skype phone, and not Philips.</p>
]]></content:encoded>
			<wfw:commentRss>http://techdebug.com/blog/2009/01/14/philips-voip321-no-longer-works-with-skype-380188-or-later/feed/</wfw:commentRss>
		<slash:comments>35</slash:comments>
		</item>
		<item>
		<title>Fix for loud clicking MacBookPro trackpad</title>
		<link>http://techdebug.com/blog/2008/12/04/fix-for-loud-clicking-macbookpro-trackpad/</link>
		<comments>http://techdebug.com/blog/2008/12/04/fix-for-loud-clicking-macbookpro-trackpad/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 05:53:57 +0000</pubDate>
		<dc:creator>lantrix</dc:creator>
				<category><![CDATA[hardware]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[loud]]></category>
		<category><![CDATA[macbookpro]]></category>
		<category><![CDATA[trackpad]]></category>

		<guid isPermaLink="false">http://techdebug.com/blog/2008/12/04/fix-for-loud-clicking-macbookpro-trackpad/</guid>
		<description><![CDATA[I love the new MacBookPro, but the trackpad clicks so loud that people on public transport stare at me. I&#8217;m not the only one with the issue.
An enterprising user on the Apple Discussion forums remembers a similar problem and fix for the trackpad from earlier MacBook models. The fix in this case involves removing your [...]]]></description>
			<content:encoded><![CDATA[<p>I love the new MacBookPro, but the trackpad clicks so loud that people on public transport stare at me. I&#8217;m <a href="http://www.aibal.com/macbook-pro-late-2008-loud-click-trackpad/">not the only one</a> with the issue.</p>
<p>An enterprising user on the Apple Discussion forums <a href="http://discussions.apple.com/thread.jspa?messageID=8364951&#8364951">remembers a similar problem</a> and fix for the trackpad from earlier MacBook models. The fix in this case involves removing your battery and sticking a piece of paper between the pad and the chassis. It works, and here is my solution captured at the moment of repair:
</p>
<p><a href="http://www.flickr.com/photos/lantrix/3081704126/" title="MacBook Pro trackpad fix by lantrix, on Flickr"><img src="http://farm4.static.flickr.com/3220/3081704126_f6d58b5260_m.jpg" width="240" height="180" alt="MacBook Pro trackpad fix" /></a><br />
<em>Enjoy.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://techdebug.com/blog/2008/12/04/fix-for-loud-clicking-macbookpro-trackpad/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
