View Single Post
  #42 (permalink)  
Old 07-18-2007, 01:33 PM
luv2chill's Avatar
luv2chill
Retired Staff
Offline
Location: Lawrence, KS
 
Join Date: Nov 2006
Posts: 1,524
Reputation: 143
luv2chill is keeping up the good workluv2chill is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via ICQ to luv2chill Send a message via AIM to luv2chill Send a message via MSN to luv2chill Send a message via Yahoo to luv2chill Send a message via Skype™ to luv2chill
Quote:
Originally Posted by bzo
Quote:
Originally Posted by luv2chill
bzo-- Try building in the Modem Link OEM as well as wmodem. Modem Link had some additional dlls with it and maybe one of those is needed.

I can't think of anything else at the moment.
ok, did some more tests. Like I said, if you build both the Modem Link and Wmodem OEMs into the ROM, Bluetooth DUN seems to work.
Oh did you state that somewhere? Sorry if I missed it.

Quote:
I tried copying the dll directories from the modem link oem to the wmodem oem and rebuilding the DSM. When I build a ROM like this, the bluetooth DUN profile shows available, but gives you an error when you actually try to connect. I don't know this is a oem package building error on my part or whether all the files from the modem link OEM are necessary.
Nope that was all OK to do. The problem is that you didn't include the registry entries from the Modem_Link rgu. You may not need them all but at a minimum you probably need the BTHATCI.dll port entry.

Quote:
So, I guess bottom line is, currently both the Modem Link OEM and the WModem OEM need to be included in the ROM for bluetooth DUN to work.
Hmm, well I swear bluetooth DUN worked just fine on my XP SP2 laptop without the Modem Link OEM, so maybe the files from that are only needed to make BT DUN work in certain instances.

Anyway I will figure something out. Thank you for confirming.
Reply With Quote