Shawns Next Attack on 3.5 BT PAN/DUN

sfaure03 · #1 (**permalink**) 02-25-2007, 01:03 PM

Ok.. I think i have patched us down to 3 remaining items on 3.5

1. BT/PAN <-- What I'm gonna try and tackle
2. HelpScreens
3. Modem.lnk doesnt work.

I've posted what I see to be the issue on the Modem link in another thread. Figure we'll get feedback and a simple solution to it quickly so i'm just gonna wait for that feedback.

On the Help screens I think we need to get another ROM that has the missing help screens and extract them. Saw others hunting that, I will await and look for that feedback.

On the BT/DUN I dont see any active threads or work to resolve, so i figured I'd step up to the bar and take a look. Now, I dont use this "feature" so i dont even know where to start and what the problem is. I'm looking for responses here that show what effort has been done and what the responses/errors detected are, hopefully saving me hours of crawling the threads. So this thread I'd like to keep to those with input on the BT PAN/DUN topic and issues, teach me what it does, what doesnt work, and I'll see if I can get us a fix for that.

You're help appreciated, and I'll see what I can do to help resolve this.

Sogarth · #2 (**permalink**) 02-25-2007, 02:45 PM

Well, as stated before, I've got AKU 3.5 help files from another of Helmi's kitchens, but at this point, I'm waiting until we have a source control system to check them into....

**colonel** · #3 (**permalink**) 02-25-2007, 03:12 PM

Shawn, there is a thread called Bluetooth DUN\PAN issues. Anyway, I have been tinkering with this, but I do not have a BT laptop or dongle to play with. However, I can post the registry dumps from the Wizard WM6 rom. Only thing is, though, I do not know if it was ever confirmed to work on the Wizard rom. I might have a chance to do some checking over at xda to see if anyone has confirmed that it works.

Honestly, I think that this may be the best place to start. If we can confirm that it is working in a 3.x rom, then we can really move forward. However, confirming functionality in any rom is a real help. Plus, this avoids any issues that may arise later from just tinkering and just "getting it to work".

sfaure03 · #4 (**permalink**) 02-26-2007, 01:05 PM

Sogarth: could you post the other kitchens?

bmtbandit · #5 (**permalink**) 02-26-2007, 03:19 PM

I got the Wireless Modem Link to work by copying the OEM from the Orignal Helmi_C 3.3 Kitchen

finster869 · #6 (**permalink**) 02-26-2007, 05:27 PM

Quote:

Originally Posted by bmtbandit

I got the Wireless Modem Link to work by copying the OEM from the Orignal Helmi_C 3.3 Kitchen

Does the program work?

bmtbandit · #7 (**permalink**) 02-26-2007, 05:39 PM

It starts up. I have not yet tried tethering.

finster869 · #8 (**permalink**) 02-26-2007, 05:42 PM

Quote:

Originally Posted by bmtbandit

It starts up. I have not yet tried tethering.

Actually, the modem link error is a different problem than to what you are referring. Wireless modem works fine. There is a dead modem link that refers to a file starting with the letter "a" (can't recall the name offhand) that isn't working properly. It is a separate program.

ashortnacy · #9 (**permalink**) 03-01-2007, 08:54 AM

Did some work this week on the Widcomm stack, older DUN and newer PAN. Finally broke down and started hacking this thing from pand on the linux side. It reported the service as 'GN' from the Widcomm stack instead of NAP. I got so far with this and started getting a 'Connection Refused (111)' error. I remembered that I get this sometimes with my VNC connectivity to Winders so I checked into it on the WMobile side and noticed this article:

http://www.pocketpcthoughts.com/foru...c.php?p=422973

For one this guys seems knowledgeable and it seems this may be a simple connectivity issue.

I started thinking I would want some sort of reverse proxy or other facade to protect me from the bad ol' internet because mine is always on. Same holds true for running Bluetooth at the mall, I wouldn't want to get hacked and become victim to one of these local 'virus' outbreaks I've heard about in Asia with these phones. SARS for your PDA is not kewl.

So I'm continuing to look into this IP connectivity issue and the DMZ he talks about with the original stack which does support NAP best I can tell. Seems my headsets didn't work as well with Widcomm and even though I could get the PAN to show up in my Winders XP Bluetooth app it wouldn't connect. Same problem? You would think Microshaft would know better but then who am I kidding?

Another thing is this app IntShrUI.exe Seems that link has moved around in Colonel's and Helmi's builds so running the EXE from the Windows folder works and apparently according to the article above MUST be enabled to support PAN. Well I can start it and it does work for USB but tried to start the dial up #777 connection for PAN and chokes.

Does anyone know anything about the 'firewall' for lack of a better term, on these WMobile PDAa?

ashortnacy · #10 (**permalink**) 03-01-2007, 09:28 AM

I've got an old D-Link BT USB dongle if you want it Colonel. It's tiny so I can mail it to you in a padded envelope. I'll never use it again as all my pc's have BT now that need it. It runs off standard p&p winders drivers.

you can send me your addy @

allen.shortnacy@oracle.com