<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for promethh</title><link>http://disqus.com/by/promethh/</link><description></description><atom:link href="http://disqus.com/promethh/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 12 Dec 2008 16:43:29 -0000</lastBuildDate><item><title>Re: Modacom KWD-U2000, The First Mac Friendly USB WiMAX Modem</title><link>http://www.wimaxian.com/2008/12/12/modacom-kwd-u2000-the-first-mac-friendly-usb-wimax-modem/#comment-4374170</link><description>&lt;p&gt;At $70 USD, it would be worth one of us getting to test to see if the Modacom KWD-U2000 would work with the Clear/XOHM network.  Do you know which frequency the KT WiMAX operates on?  Hoping it's not 3.5GHz or 2.4Ghz.  Clear/XOHM here in the US is at 2.5GHz.&lt;/p&gt;&lt;p&gt;I'm assuming the KT WiBro connection manager is just searching for any WiMAX signal and displaying it.  I wonder if it'll detect our "XOHM" signal here and display it, or if they hardcoded their connection manager to search only for their WiMAX SSID?  I doubt our existing ZTE drivers and connection manager would work with the Modacom KWD-U2000.&lt;/p&gt;&lt;p&gt;Perhaps we should ask SVinge at Sprint/WiMAX? =)&lt;br&gt;&lt;a href="http://twitter.com/svinge" rel="nofollow noopener" target="_blank" title="http://twitter.com/svinge"&gt;http://twitter.com/svinge&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">promethh</dc:creator><pubDate>Fri, 12 Dec 2008 16:43:29 -0000</pubDate></item><item><title>Re: Ken Caught XOHM in DC and Virginia</title><link>http://www.wimaxian.com/2008/11/24/ken-caught-xohm-in-dc-and-virginia/#comment-4009723</link><description>&lt;p&gt;How to see coverage in DC and northern VA:&lt;br&gt;&lt;a href="http://www.latheofdreams.com/?p=561" rel="nofollow noopener" target="_blank" title="http://www.latheofdreams.com/?p=561"&gt;http://www.latheofdreams.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;How to check coverage here in Washington, DC, and northern VA:&lt;br&gt;&lt;a href="http://www.xohm.com/apps/coverage-tracker/" rel="nofollow noopener" target="_blank" title="http://www.xohm.com/apps/coverage-tracker/"&gt;www.xohm.com/apps/coverage-tracker/&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Address:   1 Columbus Circle&lt;br&gt;City:      Washington&lt;br&gt;State:     District of Columbia&lt;br&gt;ZIP Code:  20002&lt;/p&gt;&lt;p&gt;Show coverage for:&lt;br&gt;[x] Mobile Devices&lt;br&gt;[ ] Modems&lt;/p&gt;&lt;p&gt;...from there, you can zoom in/out, scroll around.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">promethh</dc:creator><pubDate>Tue, 25 Nov 2008 13:59:59 -0000</pubDate></item><item><title>Re: Ken Caught XOHM in DC and Virginia</title><link>http://www.wimaxian.com/2008/11/24/ken-caught-xohm-in-dc-and-virginia/#comment-4003452</link><description>&lt;p&gt;Thanks, bermandt. Despite the fact that metro DC hasn’t yet been officially deployed, I find I can connect to XOHM from Capital Hill to Sterling, VA, and places in-between. Coverage is spotty, but it’s not yet fully deployed, so I expect it to improve.&lt;/p&gt;&lt;p&gt;I posted again this morning about my WiMAX experience on the VRE as I rode from Burke Center, VA, to Union Station, DC:&lt;br&gt;&lt;a href="http://www.latheofdreams.com/?p=556" rel="nofollow noopener" target="_blank" title="http://www.latheofdreams.com/?p=556"&gt;http://www.latheofdreams.co...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">promethh</dc:creator><pubDate>Tue, 25 Nov 2008 07:21:12 -0000</pubDate></item></channel></rss>