...using it with MS BT Dongle

Seneca, I'll have to disagree. The widcomm version 1.4.1 and up offer HID
profile support. I'm using my TDK with their 1.4.1 beta and the MS Bluetooth
mouse and keyboard worked fine
(http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't even bother
installing the MS dongle and software (a software that works only on XP?)

Some users found how to change the information file used to install widcomm
drivers with a MS dongle. It works fine, apparently (haven't done myself),
but there are problems here:

- how to source a 1.4 version set of files
- doing it without going into the gray area of property rights

The second item is interesting. In theory the drivers from one manufacturer
will work with devices from another manufacturer (providing some
configuration is changed before install), since they're all sourced from the
same company. The reason why they're "device locked" is because some
manufacturers invest time and money in testing, adapting and support
drivers. The hacks just remove this lock.

I haven't tried this technique: first because I use an original TDK and an
original Bluetake. Second because I'm happy with the current set of profiles
I have (LAN Access is the one I really use, followed by Serial for mobile
sync). Third because I didn't buy a Microsoft Bluetooth product.

No matter what is said, I think some retailers are really pushing this
product, placing unaware customers in this situation. Users should return
the product within the warranty period stating that it does not perform the
functions required. Otherwise "caveat emptor"!

--
Mauricio Freitas
Handhelds, mobile: http://www.geekzone.co.nz
Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449


"Seneca" <seneca@nospam.com> wrote in message
news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> Even if you get around the security issue, the D-Link drivers (1.4.1.6)
> don't offer the services required for the MS dongle to connect with the
> keyboard and mouse.
>
> Have a look at other threads in this forum.
>
> "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > One installed, the D-Link software askes me for a "licence.dat" file,
> saying
> > that the one I havce ca'nt be used with my dongle.
> > Is it linked to the .inf to me modified?
> > If not where could I get a working "licence.dat" file?
> >
> > Thx's
> >
> >
>
>

Mauricio, thanks for the clarification on the beta release for TDK. I read
your review on the MS desktop and was encouraged to see your initial results
using a non-MS adapter.

However, as for the original question here on the D-Link drivers, I use this
adapter and the 1.4.1.6 set does not offer the HID profile, so hacking the
security will still not provide the service for the keyboard/mouse.
Therefore, it's still up to the provider as to what profiles they wish to
offer/support even if available in Widcomm's total offering.

In the case of D-Link, the driver for HID is not included. It appears they
have decided to not support this profile in this release??


"Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
news:ity4b.447$cg.72661@news02.tsnz.net...
> Seneca, I'll have to disagree. The widcomm version 1.4.1 and up offer HID
> profile support. I'm using my TDK with their 1.4.1 beta and the MS
Bluetooth
> mouse and keyboard worked fine
> (http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't even
bother
> installing the MS dongle and software (a software that works only on XP?)
>
> Some users found how to change the information file used to install
widcomm
> drivers with a MS dongle. It works fine, apparently (haven't done myself),
> but there are problems here:
>
> - how to source a 1.4 version set of files
> - doing it without going into the gray area of property rights
>
> The second item is interesting. In theory the drivers from one
manufacturer
> will work with devices from another manufacturer (providing some
> configuration is changed before install), since they're all sourced from
the
> same company. The reason why they're "device locked" is because some
> manufacturers invest time and money in testing, adapting and support
> drivers. The hacks just remove this lock.
>
> I haven't tried this technique: first because I use an original TDK and an
> original Bluetake. Second because I'm happy with the current set of
profiles
> I have (LAN Access is the one I really use, followed by Serial for mobile
> sync). Third because I didn't buy a Microsoft Bluetooth product.
>
> No matter what is said, I think some retailers are really pushing this
> product, placing unaware customers in this situation. Users should return
> the product within the warranty period stating that it does not perform
the
> functions required. Otherwise "caveat emptor"!
>
> --
> Mauricio Freitas
> Handhelds, mobile: http://www.geekzone.co.nz
> Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
>
>
> "Seneca" <seneca@nospam.com> wrote in message
> news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> > Even if you get around the security issue, the D-Link drivers (1.4.1.6)
> > don't offer the services required for the MS dongle to connect with the
> > keyboard and mouse.
> >
> > Have a look at other threads in this forum.
> >
> > "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> > news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > > One installed, the D-Link software askes me for a "licence.dat" file,
> > saying
> > > that the one I havce ca'nt be used with my dongle.
> > > Is it linked to the .inf to me modified?
> > > If not where could I get a working "licence.dat" file?
> > >
> > > Thx's
> > >
> > >
> >
> >
>
>

Thanks Seneca. I wasn't aware of this on the DLINK release. As I said I
haven't tried the hack, er, test myself.

--
Mauricio Freitas
Handhelds, mobile: http://www.geekzone.co.nz
Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449


"Seneca" <seneca@nospam.com> wrote in message
news:uPmdnYLEjOaATs-iU-KYgw@comcast.com...
> Mauricio, thanks for the clarification on the beta release for TDK. I
read
> your review on the MS desktop and was encouraged to see your initial
results
> using a non-MS adapter.
>
> However, as for the original question here on the D-Link drivers, I use
this
> adapter and the 1.4.1.6 set does not offer the HID profile, so hacking the
> security will still not provide the service for the keyboard/mouse.
> Therefore, it's still up to the provider as to what profiles they wish to
> offer/support even if available in Widcomm's total offering.
>
> In the case of D-Link, the driver for HID is not included. It appears
they
> have decided to not support this profile in this release??
>
>
> "Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
> news:ity4b.447$cg.72661@news02.tsnz.net...
> > Seneca, I'll have to disagree. The widcomm version 1.4.1 and up offer
HID
> > profile support. I'm using my TDK with their 1.4.1 beta and the MS
> Bluetooth
> > mouse and keyboard worked fine
> > (http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't even
> bother
> > installing the MS dongle and software (a software that works only on
XP?)
> >
> > Some users found how to change the information file used to install
> widcomm
> > drivers with a MS dongle. It works fine, apparently (haven't done
myself),
> > but there are problems here:
> >
> > - how to source a 1.4 version set of files
> > - doing it without going into the gray area of property rights
> >
> > The second item is interesting. In theory the drivers from one
> manufacturer
> > will work with devices from another manufacturer (providing some
> > configuration is changed before install), since they're all sourced from
> the
> > same company. The reason why they're "device locked" is because some
> > manufacturers invest time and money in testing, adapting and support
> > drivers. The hacks just remove this lock.
> >
> > I haven't tried this technique: first because I use an original TDK and
an
> > original Bluetake. Second because I'm happy with the current set of
> profiles
> > I have (LAN Access is the one I really use, followed by Serial for
mobile
> > sync). Third because I didn't buy a Microsoft Bluetooth product.
> >
> > No matter what is said, I think some retailers are really pushing this
> > product, placing unaware customers in this situation. Users should
return
> > the product within the warranty period stating that it does not perform
> the
> > functions required. Otherwise "caveat emptor"!
> >
> > --
> > Mauricio Freitas
> > Handhelds, mobile: http://www.geekzone.co.nz
> > Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
> >
> >
> > "Seneca" <seneca@nospam.com> wrote in message
> > news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> > > Even if you get around the security issue, the D-Link drivers
(1.4.1.6)
> > > don't offer the services required for the MS dongle to connect with
the
> > > keyboard and mouse.
> > >
> > > Have a look at other threads in this forum.
> > >
> > > "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> > > news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > > > One installed, the D-Link software askes me for a "licence.dat"
file,
> > > saying
> > > > that the one I havce ca'nt be used with my dongle.
> > > > Is it linked to the .inf to me modified?
> > > > If not where could I get a working "licence.dat" file?
> > > >
> > > > Thx's
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Mauricio,

Well, I stand corrected. While working in my advanced configurations today,
I came across the HID under the client applications tab. At first this
didn't make sense that a corresponding service wasn't in my local services
tab.

Then, it hit me. I was in the old mind set of services and applications
having coinciding names and my pc providing the service to a remote device.
However, in the case of HID and HCRP, my pc is USING the service provided by
the remote device!!

So, of course, in My Bluetooth Neighborhood, I won't see this service with
my local services until I've configured a shortcut.

So, my guess is that there's a good chance the D-Link's adapter may be a
solution for a PAN with the MS keyboard/mouse, printer, mobile, etc. Next
step is a volunteer to try??
"Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
newsTA4b.483$cg.75134@news02.tsnz.net...
> Thanks Seneca. I wasn't aware of this on the DLINK release. As I said I
> haven't tried the hack, er, test myself.
>
> --
> Mauricio Freitas
> Handhelds, mobile: http://www.geekzone.co.nz
> Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
>
>
> "Seneca" <seneca@nospam.com> wrote in message
> news:uPmdnYLEjOaATs-iU-KYgw@comcast.com...
> > Mauricio, thanks for the clarification on the beta release for TDK. I
> read
> > your review on the MS desktop and was encouraged to see your initial
> results
> > using a non-MS adapter.
> >
> > However, as for the original question here on the D-Link drivers, I use
> this
> > adapter and the 1.4.1.6 set does not offer the HID profile, so hacking
the
> > security will still not provide the service for the keyboard/mouse.
> > Therefore, it's still up to the provider as to what profiles they wish
to
> > offer/support even if available in Widcomm's total offering.
> >
> > In the case of D-Link, the driver for HID is not included. It appears
> they
> > have decided to not support this profile in this release??
> >
> >
> > "Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
> > news:ity4b.447$cg.72661@news02.tsnz.net...
> > > Seneca, I'll have to disagree. The widcomm version 1.4.1 and up offer
> HID
> > > profile support. I'm using my TDK with their 1.4.1 beta and the MS
> > Bluetooth
> > > mouse and keyboard worked fine
> > > (http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't even
> > bother
> > > installing the MS dongle and software (a software that works only on
> XP?)
> > >
> > > Some users found how to change the information file used to install
> > widcomm
> > > drivers with a MS dongle. It works fine, apparently (haven't done
> myself),
> > > but there are problems here:
> > >
> > > - how to source a 1.4 version set of files
> > > - doing it without going into the gray area of property rights
> > >
> > > The second item is interesting. In theory the drivers from one
> > manufacturer
> > > will work with devices from another manufacturer (providing some
> > > configuration is changed before install), since they're all sourced
from
> > the
> > > same company. The reason why they're "device locked" is because some
> > > manufacturers invest time and money in testing, adapting and support
> > > drivers. The hacks just remove this lock.
> > >
> > > I haven't tried this technique: first because I use an original TDK
and
> an
> > > original Bluetake. Second because I'm happy with the current set of
> > profiles
> > > I have (LAN Access is the one I really use, followed by Serial for
> mobile
> > > sync). Third because I didn't buy a Microsoft Bluetooth product.
> > >
> > > No matter what is said, I think some retailers are really pushing this
> > > product, placing unaware customers in this situation. Users should
> return
> > > the product within the warranty period stating that it does not
perform
> > the
> > > functions required. Otherwise "caveat emptor"!
> > >
> > > --
> > > Mauricio Freitas
> > > Handhelds, mobile: http://www.geekzone.co.nz
> > > Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
> > >
> > >
> > > "Seneca" <seneca@nospam.com> wrote in message
> > > news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> > > > Even if you get around the security issue, the D-Link drivers
> (1.4.1.6)
> > > > don't offer the services required for the MS dongle to connect with
> the
> > > > keyboard and mouse.
> > > >
> > > > Have a look at other threads in this forum.
> > > >
> > > > "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> > > > news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > > > > One installed, the D-Link software askes me for a "licence.dat"
> file,
> > > > saying
> > > > > that the one I havce ca'nt be used with my dongle.
> > > > > Is it linked to the .inf to me modified?
> > > > > If not where could I get a working "licence.dat" file?
> > > > >
> > > > > Thx's
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Seneca, I read about this today. Coincidence?

Anyway, some folks tried and reported here:
http://www.geekzone.co.nz/forums.asp...=8&TopicId=393

--
Mauricio Freitas
Handhelds, mobile: http://www.geekzone.co.nz
Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449


"Seneca" <seneca@nospam.com> wrote in message
news:RZWcnYT6KYEOvcmiXTWJiw@comcast.com...
> Mauricio,
>
> Well, I stand corrected. While working in my advanced configurations
today,
> I came across the HID under the client applications tab. At first this
> didn't make sense that a corresponding service wasn't in my local services
> tab.
>
> Then, it hit me. I was in the old mind set of services and applications
> having coinciding names and my pc providing the service to a remote
device.
> However, in the case of HID and HCRP, my pc is USING the service provided
by
> the remote device!!
>
> So, of course, in My Bluetooth Neighborhood, I won't see this service with
> my local services until I've configured a shortcut.
>
> So, my guess is that there's a good chance the D-Link's adapter may be a
> solution for a PAN with the MS keyboard/mouse, printer, mobile, etc. Next
> step is a volunteer to try??
> "Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
> newsTA4b.483$cg.75134@news02.tsnz.net...
> > Thanks Seneca. I wasn't aware of this on the DLINK release. As I said I
> > haven't tried the hack, er, test myself.
> >
> > --
> > Mauricio Freitas
> > Handhelds, mobile: http://www.geekzone.co.nz
> > Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
> >
> >
> > "Seneca" <seneca@nospam.com> wrote in message
> > news:uPmdnYLEjOaATs-iU-KYgw@comcast.com...
> > > Mauricio, thanks for the clarification on the beta release for TDK. I
> > read
> > > your review on the MS desktop and was encouraged to see your initial
> > results
> > > using a non-MS adapter.
> > >
> > > However, as for the original question here on the D-Link drivers, I
use
> > this
> > > adapter and the 1.4.1.6 set does not offer the HID profile, so hacking
> the
> > > security will still not provide the service for the keyboard/mouse.
> > > Therefore, it's still up to the provider as to what profiles they wish
> to
> > > offer/support even if available in Widcomm's total offering.
> > >
> > > In the case of D-Link, the driver for HID is not included. It appears
> > they
> > > have decided to not support this profile in this release??
> > >
> > >
> > > "Mauricio Freitas" <dr.emailposter@nowhere.invalid> wrote in message
> > > news:ity4b.447$cg.72661@news02.tsnz.net...
> > > > Seneca, I'll have to disagree. The widcomm version 1.4.1 and up
offer
> > HID
> > > > profile support. I'm using my TDK with their 1.4.1 beta and the MS
> > > Bluetooth
> > > > mouse and keyboard worked fine
> > > > (http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't
even
> > > bother
> > > > installing the MS dongle and software (a software that works only on
> > XP?)
> > > >
> > > > Some users found how to change the information file used to install
> > > widcomm
> > > > drivers with a MS dongle. It works fine, apparently (haven't done
> > myself),
> > > > but there are problems here:
> > > >
> > > > - how to source a 1.4 version set of files
> > > > - doing it without going into the gray area of property rights
> > > >
> > > > The second item is interesting. In theory the drivers from one
> > > manufacturer
> > > > will work with devices from another manufacturer (providing some
> > > > configuration is changed before install), since they're all sourced
> from
> > > the
> > > > same company. The reason why they're "device locked" is because some
> > > > manufacturers invest time and money in testing, adapting and support
> > > > drivers. The hacks just remove this lock.
> > > >
> > > > I haven't tried this technique: first because I use an original TDK
> and
> > an
> > > > original Bluetake. Second because I'm happy with the current set of
> > > profiles
> > > > I have (LAN Access is the one I really use, followed by Serial for
> > mobile
> > > > sync). Third because I didn't buy a Microsoft Bluetooth product.
> > > >
> > > > No matter what is said, I think some retailers are really pushing
this
> > > > product, placing unaware customers in this situation. Users should
> > return
> > > > the product within the warranty period stating that it does not
> perform
> > > the
> > > > functions required. Otherwise "caveat emptor"!
> > > >
> > > > --
> > > > Mauricio Freitas
> > > > Handhelds, mobile: http://www.geekzone.co.nz
> > > > Bluetooth guides:
http://www.geekzone.co.nz/content.asp?contentid=449
> > > >
> > > >
> > > > "Seneca" <seneca@nospam.com> wrote in message
> > > > news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> > > > > Even if you get around the security issue, the D-Link drivers
> > (1.4.1.6)
> > > > > don't offer the services required for the MS dongle to connect
with
> > the
> > > > > keyboard and mouse.
> > > > >
> > > > > Have a look at other threads in this forum.
> > > > >
> > > > > "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> > > > > news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > > > > > One installed, the D-Link software askes me for a "licence.dat"
> > file,
> > > > > saying
> > > > > > that the one I havce ca'nt be used with my dongle.
> > > > > > Is it linked to the .inf to me modified?
> > > > > > If not where could I get a working "licence.dat" file?
> > > > > >
> > > > > > Thx's
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

And I don't agree too, at
http://forum.gsmhosting.com/vbb/show...430#post448430
I found a way to make my dongle work on W2K and I managed to port thye
solution to WinXP. (with Dell-Widcomm 1.4.1.4 stack)

Now: My Keyboard, my mouse and my phone do work perfecly under windows XP.

Under Windows 2K : my phone is ok. But as my w2k config is at my working
place, I didn't tried the BT mouse and KB. (not sure it is worth testing it,
as the XP BT Patch is required for Bluetooth Intellipoint/Type to install)

But I'm actually working on a note describing all the problem that I had to
face and how did I pass throught them.

GrH

"Mauricio Freitas" <dr.emailposter@nowhere.invalid> a écrit dans le message
de news: ity4b.447$cg.72661@news02.tsnz.net...
> Seneca, I'll have to disagree. The widcomm version 1.4.1 and up offer HID
> profile support. I'm using my TDK with their 1.4.1 beta and the MS
Bluetooth
> mouse and keyboard worked fine
> (http://www.geekzone.co.nz/content.asp?contentid=1008). I didn't even
bother
> installing the MS dongle and software (a software that works only on XP?)
>
> Some users found how to change the information file used to install
widcomm
> drivers with a MS dongle. It works fine, apparently (haven't done myself),
> but there are problems here:
>
> - how to source a 1.4 version set of files
> - doing it without going into the gray area of property rights
>
> The second item is interesting. In theory the drivers from one
manufacturer
> will work with devices from another manufacturer (providing some
> configuration is changed before install), since they're all sourced from
the
> same company. The reason why they're "device locked" is because some
> manufacturers invest time and money in testing, adapting and support
> drivers. The hacks just remove this lock.
>
> I haven't tried this technique: first because I use an original TDK and an
> original Bluetake. Second because I'm happy with the current set of
profiles
> I have (LAN Access is the one I really use, followed by Serial for mobile
> sync). Third because I didn't buy a Microsoft Bluetooth product.
>
> No matter what is said, I think some retailers are really pushing this
> product, placing unaware customers in this situation. Users should return
> the product within the warranty period stating that it does not perform
the
> functions required. Otherwise "caveat emptor"!
>
> --
> Mauricio Freitas
> Handhelds, mobile: http://www.geekzone.co.nz
> Bluetooth guides: http://www.geekzone.co.nz/content.asp?contentid=449
>
>
> "Seneca" <seneca@nospam.com> wrote in message
> news:nMmdnSHLcvi2Ms-iU-KYuA@comcast.com...
> > Even if you get around the security issue, the D-Link drivers (1.4.1.6)
> > don't offer the services required for the MS dongle to connect with the
> > keyboard and mouse.
> >
> > Have a look at other threads in this forum.
> >
> > "GreuuH" <nospam@slaporte.cjb.net> wrote in message
> > news:bitlql$mun$1@news-reader2.wanadoo.fr...
> > > One installed, the D-Link software askes me for a "licence.dat" file,
> > saying
> > > that the one I havce ca'nt be used with my dongle.
> > > Is it linked to the .inf to me modified?
> > > If not where could I get a working "licence.dat" file?
> > >
> > > Thx's
> > >
> > >
> >
> >
>
>