How To: Create a dial-up network connection over Blueooth [with a Qtek 9100]

A co-worker inquired today about how to create a dial-up networking connection over Bluetooth with his Qtek 9100…here’s the info:

The Short Version:
After you pair the devices, open the properties on the of the Pocket PC device on your desktop BT connection.  Check the services for that device and select the Dial-up networking (DUN) service.  After you have done this, Windows will add a new modem item, then you can create a new network connection using the BT connection.

The Long Version:  (again, this assumes you have already paired your device to your desktop/laptop as well as having a data plan configured through your mobile operator)

1)  Open your BT properties and select the correct device (here, I am selecting my Qtek 9100 Windows Mobile Pocket PC); click Properties.


View BT devices

 

2) On the properties dialog, select the Services tab.  Check the DUN box and click apply.

 Select DUN service

3) Windows will now add a new modem

Windows add new hardware

4) Once Windows has added the new modem, it will assign a COM port.  At this point, you may click OK to exit the properties dialog and the BT devices dialog.

COM port assigned

 

5) Now that we have added the , we need to add a new network connection to use it.  Open your Network Connections and select ‘Create a new connection’. The wizard will open – click Next.

Start the Network Connection Wizard

6) The wizard prompts for the Network Connection Type – Select “Connect to the Internet” and click Next.

Select Internet type

7) Select “Set up my connection manually” and click Next.

Network Connection setup manual setup

8) Select “Connect using a dial-up modem”; click Next.

Network Connection Wizard - Connection type

9) We now need to select the device that this connection will use; we want to pick the Standard Modem over Bluetooth that we just added. (In this case it is modem on COM35) – Click Next.

Select Device

10) We now need to give the connection a name – I chose “T-Mobile (BT)”.  I added the “BT” to distinguish it because I also have another connection setup for T-Mobile on USB.

Connection Name

11) We now need to set the phone number to dial.  In this case we are setting up a GPRS/EDGE connection, so we enter *99#.  Click Next.

Network Connection Wizard - Phone Number

12) As a user running as non-admin, the only option I have here is “My use only”; if I were running as admin (not recommended), I could set this connection up for all users.  Click Next.

Network Connection Wizard - Connection Availability

13) It now wants us to enter account information.  If you need to enter credentials, do so and click Next.  For T-Mobile (USA), I do not need to enter any credentials, so I just click Next.

Network Connection Wizard - Account Info

14) The connection is now set up; added a shortcut to your desktop if you like.  Click Finish.

Network Connection Wizard - Complete

15) Back to the Network Connections screen we see (in the red rectangle) our new T-Mobile Bluetooth connection. Double-click it and we’ll see the connect dialog as below.  As I mentioned earlier, I do not need to enter any credentials, so I can just click Dial.

Connect to BT connection

16) When Windows connects, you should see a notification bubble.   That’s it!
BTConnected

To disconnect, you can simply right-click on the connection icon in your notification area and select ‘Disconnect” from the context menu.

-Nino

Windows Mobile 5.0 SDKs

Windows Mobile 5.0 SDK for Pocket PC
 
Windows Mobile 5.0 SDK for Smartphone
 
Please note the requirements:
  • Visual Studio 2005 Beta 2 Standard, Professional, and Team Suite Editions
  • Active Sync 4.0 Developer Beta (build 4343)
  • …so, yes, you are constrained to the spiffy new emulator until you can get your hands on a WM5 device…

    -Nino

    Windows Mobile 5.0

    In lieu of another issue of The Mobile Minute, here are a plethora of WM5 links:

    -Nino

    The Mobile Minute 92

     Lots ‘o stuff in my TMM News Bin to blog while I eagerly await my Audiovox SMT5600 (via eBay, of course).  I can hear it now… ”What took you so long?”  That answer is easy: $.

    Software / Hardware 

     Development

    Related News

    -Nino

    It’s the emulator, stupid!!!

     

    Just a quick reminder to anyone who’s been hip-deep in Whidbey/Windows Mobile 5: when you go to deploy a [legacy] VS2003/WM2003 app to WM2003 emulator, you need to pick the x86 CAB …  DOH!

    I spent twenty minutes trying to figure out why my CAB wouldn’t install on the emulator (I even re-wrote the .inf file – I got pretty handy at that after my project in D.C.)… only to have it dawn on me that I was picking the wrong CAB.  The WM2003 emulator runs an x86 version..not ARM (or ARMV4).   The only emulator that is a true ARM emulator is the one from the Windows Mobile 5.0 SDKs.  

    [sigh]…  that’s what I get for doing most of WM2003 development without the emulator [and instead deploying to the device].

    Time for dinner…and a Guinness.

    -Nino

    Fixing my CS and .Text URL redirect issues

    As some of you may have noticed, ever since I moved Community Server to the root of nino.net, I have had some outstanding URL issues.  1)my .Text redirect (forhttp://nino.net/blog/ -based URLs) has broken, and 2) all the http://nino.net/CS/blogs/nino -based URLs needed a redirect.

    I spent a little time yesterday resolving both of these with one solution.  I used a URL re-writer that I got from Dennis van der Stelt at http://bloggingabout.net/dennis/archive/2005/06/28/7408.aspx (it seems to have been started by Fritz Onion and been improved upon by several others).  I found the original link on the Community Server blog forums.  In addition to the very handy URL re-writing functionality, it also sends a permanent (HTTP 301) or temporary (HTTP 302) redirect (real swell for telling Google to update itself).  These manifest as the first item in the <add> node (note that mine have a value of “true” for sending HTTP 301’s).

    Here is the redirections section from my web.config:

        <redirections type=”Madgeek.Web.ConfigRedirections, Madgeek.RedirectModule”>
               <add permanent=“true” ignoreCase=“true” targetUrl=”^/blog/(.*).aspx??(.*)” destinationUrl=”~/blogs/nino/$1.aspx” />
               <add permanent=“true” ignoreCase=“true” targetUrl=”^/CS/(.*)” destinationUrl=”~/$1″ />
       </redirections>

    The first redirect handles all URLs coming in for my .Text blog URL (e.g. http://nino.net/blog/archive/2005/02/09/552.aspx?Pending=true  gets rewritten to http://nino.net/blogs/nino/archive/2005/02/09/552.aspx)

    The second redirect handles all URLs having /CS/ in the path (e.g. http://nino.net/CS/blogs/nino/archive/2004/01/23/172.aspx gets rewritten as http://nino.net/blogs/nino/archive/2004/01/23/172.aspx)

    I used RegexDesigner.NET from Chris Sells (I used to use The Regulator, but once I switched to running as non-admin it had issues) to verify my regex for the URL redirection along with a friendly reminder from my friend Mike L.

    -Nino

    How to hard-reset your HTC Wizard

    I had to hard-reset (not the first time) my Qtek 9100 today (I was futzing with system stuff and I zigged when I should have zagged), so I thought I would blog about it for those searching for an option other than ‘Clear Storage’. 

    Option 1:
    Start > Settings > Clear Storage (then enter in the number it requests and tap ‘YES’)

    Option 2:
    Hold down the Comm Manager button(top left) and Voice Command button(top right) buttons while performing a soft-reset (depress the reset button using the stylus); after you depress the soft-reset button, [contintue to hold the two side buttons] hold down the navigation pad for ~4 seconds until you are prompted on screen [you can release the side buttons now]. Press the Send (Talk) button (i.e. the left telephony button)  – or whichever button your system prompts you for.

    FWIW, I have seen unsubstantiated claims that Option 2 is a ‘more thorough’ hard-reset than Option 1…

    -Nino

    The Mobile Minute 83

    This issue of TMM has been shelved for two weeks while I’ve been consumed with work issues.  Last week I met Steven Pratschner, a PM on the .NET CF team, when he came to visit our project for a week and provide us some guidance (and get some constructive critcism from us). Hopefully, I’ll run into Steven in Las Vegas in May.  Thank you for your help, Steven!   I would also like to extend a large thank you to Neil Cowburn of OpenNETCF.org who gave me some assistance on a different matter for our project.

    Software / Hardware 

     Development

    -Nino

    The Mobile Minute 54

    Not too much to say today.. I think I have a touch of the flu..

    Nino