Results 1 to 19 of 19
  1.    #1  
    I've spent hours trying (and researching) the Error 633 problem when trying to use DUN on my Sprint 650, and I'm hoping that better minds than mine can figure this out.

    DUN works, but only intermittently. I have followed the steps provided by shadowmite, varoomba and others (PCS off, soft reset, DUN off and on again, etc.), but the problem persists. The most frustrating part is that it connects occasionally. On those rare occurences, if I disconnect and try to reconnect right away, I get the "modem is already in use or not configured properly." Both devices are paired, and I can HotSync via the cradle or Bluetooth without any problem whatsoever.

    I would greatly appreciate any suggestions.
  2. #2  
  3. #3  
    I would suggest you turn of the bluetooth hotsync and leave it off. Then delete all instances of the BT pairing on your PC and your Treo, then repair them. That is what eventually got me out of error 633 hell.
    Photography Politics Technology Music Photoshop
    VOXEFX
  4. #4  
    I was having the same problem. Were you using Shadowmite Patched BtManager before the upgrade? I was. I had the hacked file in place and did the upgrade and was getting constant 633 errors. I just went back and installed the unhacked BtManager exactly according to Shadowmite's direction on installing the hacked version. As soon as the original file was installed - everything worked perfectly.

    I can only guess that on my 650 shadowmite's hack was in someway conflicting with the Sprint 1.12 release with respect to DUN.

    Good luck!
  5. #5  
    Quote Originally Posted by rtrider
    I've spent hours trying (and researching) the Error 633

    I would greatly appreciate any suggestions.
    Here's an extensive list of errors and possible solutions:

    http://discussion.treocentral.com/sh...t=Error+%23633
    -->BtDUN pre- and post- SprintPCS update 1.12 paired to PC and PPC.
    Darth_Maul -- a dark attacker, trained in the Jedi arts.
  6.    #6  
    Quote Originally Posted by stormer
    I was having the same problem. Were you using Shadowmite Patched BtManager before the upgrade?
    stormer,
    No, I have never used any of shadowmite's patches, although maybe I would be better off if I had. Maybe I should try installing the unhacked BT manager. Can I find it, and instructions, on shadowmite's site?

    Quote Originally Posted by pda_jedi
    Here's an extensive list of errors and possible solutions:

    http://discussion.treocentral.com/s...ht=Error+%23633
    pda_jedi,
    Thanks for the link. I've been there, and have tried all the suggested fixes with no success. As I said, my biggest frustration is that DUN works fine occasionally, and I can't duplicate the circumstances that cause it to fail. But I'm stubborn enough to just keep trying, for now, anyway.
  7. #7  
    You're not alone rtrider... I've got the same problem. Works fine on my Macs...yet with good old reliable Windows, I experience the same crap you do. Tried it on more than once PC too.

    Deleted the pairings. Re created them. Reset the Treo. Rebooted the PCs...nothing.
  8.    #8  
    Quote Originally Posted by Bill Gamble
    Bill,
    Good call! I just downloaded and installed pdanet and it works fine! I know that DUN should be functional now on the 650 without any additional expense, but I have already incurred more than $30 worth of effort and frustration, so this is a relief. Thanks for the suggestion.
  9. #9  
    Error 633 implies a problem between the operating system and the virtual port. With Bluetooth, it usually means that some program has taken control of the virtual device before your modem connection. In my case, it was Hotsync camping out the Bluetooth serial port.

    In contrast, if you get a 692 error, it means that the operating system cannot connect to the Bluetooth device itself. This happens, for example, when I forget to insert my USB Adaptor before trying to use it.
  10. #10  
    Quote Originally Posted by rtrider
    Bill,
    Good call! I just downloaded and installed pdanet and it works fine! I know that DUN should be functional now on the 650 without any additional expense, but I have already incurred more than $30 worth of effort and frustration, so this is a relief. Thanks for the suggestion.
    You're welcome. I have to admit, I was also loath to pay for an app to do this, but it makes things so simple...it just works. :-)
    V > Vx > m505 > m515 > T/T > T3 > TC > 650 > 680
    <script type="text/javascript" src="http://download.skype.com/share/skypebuttons/js/skypeCheck.js"></script>
    <a href="skype:wwgamble?call"><img src="http://mystatus.skype.com/balloon/wwgamble" style="border: none;" width="150" height="60" alt="My Skype status" /></a>
  11. JoeSam's Avatar
    Posts
    88 Posts
    Global Posts
    89 Global Posts
    #11  
    Same problem here - Error 633. I am not even running HotSync on this machine! In fact, I don't have any hardware using a serial connection, so there's nothing that could potentially be conflicting with the BT serial connection. This is really more trouble than it's worth. I've waisted way too much time getting this thing to go.

    BTW, I'm using the Lanso dongle from Treocentral Store. I get this problem whether using the packaged software or using XPSP2's configuration when Lanso is uninstalled. Absolutely no connection to the BT serial port.
  12. #12  
    ((( BUMP )))
    Anyone know how to fix this shwag?

    It works fine on my Mac, but that's not a laptop. Stupid Windows...
  13. #13  
    If it helps any, I have the exact same problem. My Treo DUN works perfectly from my iBook but only on occasion it connects from my XP laptop without an error 633.

    Another thing, XP bluetooth never remembers my Treo as a trusted device. I have to pair with a passcode EVERY time, and then pair again once the dial begins.
  14. #14  
    Quote Originally Posted by probablybill
    Another thing, XP bluetooth never remembers my Treo as a trusted device. I have to pair with a passcode EVERY time, and then pair again once the dial begins.
    Arg. My XP laptop does this - I was just trying to see if I could get DUN to worok at all, and it wanted to pair everytime I blinked.
  15. #15  
    Guys, I managed to conquer the Error 633 on my Windows XP laptop...

    To get DUN to work, I had to do the following;

    1) Turn OFF the Treo's Auto Answer for Bluetooth Headsets (Under Prefs: Handsfree).
    2) IMPORTANT: Turn OFF Hotsync Manager on the laptop (From the System Tray).
    3) Remove any other Bluetooth services that the lap top associates with the Treo.
    4) Disable the Wi-Fi radio on the laptop.
    5) Soft reset the Treo, and make sure the phone is turned on after reboot.
    6) Enable Bluetooth Dial-Up Networking on the Treo.
    7) Establish a Bluetooth connection (pairing) between the laptop and Treo.
    8) Start the DUN service on the Laptop.

    Here is my tech info;

    Cingular Branded Treo 650 (Never used Hacked DUN)
    Laptop Modem Setting - Bluetooth Modem (COM6)
    Bluetooth Modem Phone Number: *99***1#
    User Name: WAP@CINGULARGPRS.COM
    Password: CINGULAR1
    CompUSA USB Bluetooth Adapter (Dongle)
    Laptop: Dell Insiron 9100
    OS: MS Windows XP Home Edition (Service Pack 1)

    If you have a non-cingular Treo, then the user name and password information
    you need for your particular phone can probably be found on Shadowmite's site
    (see resource list below). There is some warning about problems with XP SP2
    on the MyTreo.net resource that might help if you are running SP2.

    I'm not sure which steps (from #1-8) that I did are absolutely critical,
    except #2. It was the last change in the setup routine that I made
    which made the dredded Error 633 go away. Using those steps, I was
    able to connect, disconnect, make phone calls, use my BT headset and
    then reconnect several times with no sign of the error. I pieced this
    setup routine together from several resources (including this thread);

    RESOURCE LIST;
    http:/www.palm.com/us/support/handbooks/treo/Treo650_GSM_DUN_UG.pdf
    http://shadowmite.com/HowToDUN.html
    http://mytreo.net/archives/2005/08/b...e_treo_650.php

    When it did come up, the reported connection speed was 115.2 Kbps,
    which is about 2x dialup. (Is that fast enough to be called broadband?)

    I hope this is usefull.

    Alan
    Last edited by a_bcd@msn.com; 12/19/2005 at 02:30 PM.
  16. #16  
    I can't get this to work with PDANet, and I am at my wits end.

    If it's a Cingular-locked Treo 650 (like mine), will it even do anything over a BT connection? I try to use PDANet over a Bluetooth connection for DUN, and it refuses to connect.

    "Modem is busy".

    Bah...
    Unlocked 750v: Voice / Data
    Blackberry 7130c: Private Line
    Motorola v60g T-Mo: Business Voice
    Also HTC TyTN factory; Palm LifeDrive & TX
    7 year Cingular/PacBell veteran.
  17. #17  
    This may be a little late in coming, but having just upgraded to the TREO 650, I've only just encountered the error 633 hassle when trying to use my phone as a modem. I'm using the DBT-120 adapter. Both the software on the installation CD that came with the device and the software available on the website allowed Windows XP to use generic bluetooth drivers. Turns out I needed to download an updated driver from the site that was specific to my DBT-120 device. After installing the new driver I was able to use my TREO as a bluetooth modem with no problem and no error 633!
  18. #18  
    Microsoft bluetooth stack could be a problem. The Widcomm bletooth stack seems to be more reliable in my case.
  19. #19  
    I don't have any more answers, but thought I'd share my results. I posted them in this thread:

    http://discussion.treocentral.com/sh....php?p=1114058
    PalmIII -> PalmV -> Sprint Treo650 -> Treo755P -> Pre

    "Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway."

    --Andrew Tanenbaum

Posting Permissions