<?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"
	>
<channel>
	<title>Comments on: Idiot Interfaces 67 and 68</title>
	<atom:link href="http://www.josephzitt.com/wordpress/archives/26/feed" rel="self" type="application/rss+xml" />
	<link>http://www.josephzitt.com/wordpress/archives/26</link>
	<description>The Year of Living Musically</description>
	<pubDate>Fri, 21 Nov 2008 07:19:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Bill Bowman</title>
		<link>http://www.josephzitt.com/wordpress/archives/26#comment-215</link>
		<dc:creator>Bill Bowman</dc:creator>
		<pubDate>Fri, 05 Jan 2007 21:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.josephzitt.com/wordpress/archives/26#comment-215</guid>
		<description>I once had a bluetooth on my dongle and let me tell you, that hurt like the dickens.</description>
		<content:encoded><![CDATA[<p>I once had a bluetooth on my dongle and let me tell you, that hurt like the dickens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Fischer</title>
		<link>http://www.josephzitt.com/wordpress/archives/26#comment-214</link>
		<dc:creator>Ron Fischer</dc:creator>
		<pubDate>Fri, 05 Jan 2007 20:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.josephzitt.com/wordpress/archives/26#comment-214</guid>
		<description>Recalling more details. Phone's bluetooth password is probably just configured once by you. When you discover, select &#38; pair to the phone from the PC the phone may or may not ask you to confirm depending on how bluetooth is configured.</description>
		<content:encoded><![CDATA[<p>Recalling more details. Phone&#8217;s bluetooth password is probably just configured once by you. When you discover, select &amp; pair to the phone from the PC the phone may or may not ask you to confirm depending on how bluetooth is configured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Fischer</title>
		<link>http://www.josephzitt.com/wordpress/archives/26#comment-206</link>
		<dc:creator>Ron Fischer</dc:creator>
		<pubDate>Fri, 05 Jan 2007 05:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.josephzitt.com/wordpress/archives/26#comment-206</guid>
		<description>Bluetooth was a latecomer to XP. Even today Microsoft doesn't provide a complete stack of protocols. You depend on your dongle vendor to fill the gaps. Some do it well. I think Kensington is a good brand.

Make sure Bluetooth is turned on on both devices and the phone is set to be discoverable. Ask PC to find devices. When you see phone, pair with it. Phone should pop dialog about someone wanting to pair, give password to phone and say yes. PC should then say device wants password to pair up, give it same one. After this your phone should appear in list of paired devices on me PC. Phone probably supports showing your PC its file system.

You could pair in the other direction, but I doubt a PC has service profiles the phone will find interesting. 

So remember pairing is not symmetric it's about seeing the service profiles on one device from another.  You pair to something whose services you want to use. Pairing goes: search, select device to pair with, share passwords &#38; accept on both sides.

Also check Kensington web site support.

Luck!</description>
		<content:encoded><![CDATA[<p>Bluetooth was a latecomer to XP. Even today Microsoft doesn&#8217;t provide a complete stack of protocols. You depend on your dongle vendor to fill the gaps. Some do it well. I think Kensington is a good brand.</p>
<p>Make sure Bluetooth is turned on on both devices and the phone is set to be discoverable. Ask PC to find devices. When you see phone, pair with it. Phone should pop dialog about someone wanting to pair, give password to phone and say yes. PC should then say device wants password to pair up, give it same one. After this your phone should appear in list of paired devices on me PC. Phone probably supports showing your PC its file system.</p>
<p>You could pair in the other direction, but I doubt a PC has service profiles the phone will find interesting. </p>
<p>So remember pairing is not symmetric it&#8217;s about seeing the service profiles on one device from another.  You pair to something whose services you want to use. Pairing goes: search, select device to pair with, share passwords &amp; accept on both sides.</p>
<p>Also check Kensington web site support.</p>
<p>Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ima</title>
		<link>http://www.josephzitt.com/wordpress/archives/26#comment-205</link>
		<dc:creator>ima</dc:creator>
		<pubDate>Fri, 05 Jan 2007 02:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.josephzitt.com/wordpress/archives/26#comment-205</guid>
		<description>Was John`s explanation of any help to you? 
Ima</description>
		<content:encoded><![CDATA[<p>Was John`s explanation of any help to you?<br />
Ima</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://www.josephzitt.com/wordpress/archives/26#comment-204</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Thu, 04 Jan 2007 15:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.josephzitt.com/wordpress/archives/26#comment-204</guid>
		<description>Telephone keypads were designed to be like telephone dials (which I remember, so you must too), with the 1 on the top and the 0 on the bottom.  And dials were designed that way so that dialing 1 (or rather letting go after you dialed it) would transmit one click, and dialing 0 would transmit ten clicks.  When area codes were assigned, long after the design of dials, AT&#38;T made a point of assigning low-click-count area codes to populous places:  hence New York got 212 (five clicks), L.A. got 213 (six clicks), and Chicago got 312 (also six clicks).

When push-button keypads were first being worked on, Bell Labs folks experimented with using accounting-type dial keypads, and also investigated having large buttons with no "whitespace" between them.  The latter design worked much better (it's harder for the finger to slip off a larger button), but was inexplicably rejected by the PHBs of the day.

ObTrivia: the original design of the Touch-Tone keypad allowed for a fourth column of buttons; these were never used on the public network, but were used on the DoD network to allow high-priority callers to boot lower ones from scarce trunk lines.</description>
		<content:encoded><![CDATA[<p>Telephone keypads were designed to be like telephone dials (which I remember, so you must too), with the 1 on the top and the 0 on the bottom.  And dials were designed that way so that dialing 1 (or rather letting go after you dialed it) would transmit one click, and dialing 0 would transmit ten clicks.  When area codes were assigned, long after the design of dials, AT&amp;T made a point of assigning low-click-count area codes to populous places:  hence New York got 212 (five clicks), L.A. got 213 (six clicks), and Chicago got 312 (also six clicks).</p>
<p>When push-button keypads were first being worked on, Bell Labs folks experimented with using accounting-type dial keypads, and also investigated having large buttons with no &#8220;whitespace&#8221; between them.  The latter design worked much better (it&#8217;s harder for the finger to slip off a larger button), but was inexplicably rejected by the PHBs of the day.</p>
<p>ObTrivia: the original design of the Touch-Tone keypad allowed for a fourth column of buttons; these were never used on the public network, but were used on the DoD network to allow high-priority callers to boot lower ones from scarce trunk lines.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
