Re: MS / widcomm bluetooth programming
- From: gregsco@xxxxxxxxxxxxxxxxxxxx (Greg Scott [MS])
- Date: Tue, 26 Apr 2005 16:40:47 GMT
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 There is a lot of info on MSDN. The following page actually shows you how to register the virtual COM port with BT (most devices have some UI to do this). So you probably won't need to call RegisterDevice as described here:
\par
\par http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50concomportemulationfacility.asp
\par
\par Here are some links to the general purpose APIs for using COM ports (this will be applicable for both MS & Widcomm stacks):
\par
\par http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceobjst/html/cerefCreateFile.asp
\par
\par http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceobjst/html/cerefreadfile.asp
\par
\par http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceobjst/html/cerefwritefile.asp
\par
\par If you install Windows CE Platform Builder (evaluation edition) you can find some samples here:
\par
\par public\\common\\oak\\drivers\\bluetooth\\sample
\par public\\common\\sdk\\samples\\bluetooth
\par
\par Good luck!
\par
\par Greg Scott
\par Software Design Engineer, Windows CE
\par Microsoft Corporation
\par _____________________________________________________________
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par _____________________________________________________________
\par
\par \pard\li720 --------------------
\par From: "dave" <dave@xxxxxxxxxxxxxxxxxxxx>
\par Newsgroups: microsoft.public.pocketpc.developer.networking
\par Subject: Re: MS / widcomm bluetooth programming
\par Date: Mon, 25 Apr 2005 09:59:40 +0100
\par Lines: 64
\par Message-ID: <d4ic2r$gdp$1$8302bc10@xxxxxxxxxxxxxxxx>
\par References: <B524A998-0CA8-41AF-A494-B4E76F0192E0@xxxxxxxxxxxxx> <6tGJ3rpRFHA.12764@xxxxxxxxxxxxxxxxxxxxx>
\par NNTP-Posting-Host: parystec.demon.co.uk
\par X-Trace: news.demon.co.uk 1114420125 16825 80.176.87.116 (25 Apr 2005 09:08:45 GMT)
\par X-Complaints-To: abuse@xxxxxxxxx
\par NNTP-Posting-Date: Mon, 25 Apr 2005 09:08:45 +0000 (UTC)
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
\par X-Priority: 3
\par X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
\par X-MSMail-Priority: Normal
\par Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed.icl.net!newsfeed.fjserv.net!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
\par Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.pocketpc.developer.networking:1281
\par X-Tomcat-NG: microsoft.public.pocketpc.developer.networking
\par
\par Hi Greg,
\par
\par Can you point us at more info on using "virtual com ports (Serial Port
\par Profile)" ?
\par
\par bye
\par Dave
\par
\par "Greg Scott [MS]" <gregsco@xxxxxxxxxxxxxxxxxxxx> wrote in message
\par news:6tGJ3rpRFHA.12764@xxxxxxxxxxxxxxxxxxxxxxxx
\par > Microsoft and Widcomm have completely different SDKs. If you are creating
\par > a simple enough application you might be able to get away with just using
\par > virtual COM ports (Serial Port Profile). Virtual COM ports use standard
\par > Windows CE APIs which wrap Microsoft and Widcomm BT stacks.
\par >
\par > I hope this helps.
\par >
\par > Greg Scott
\par > Software Design Engineer, Windows CE
\par > Microsoft Corporation
\par > _____________________________________________________________
\par > This posting is provided "AS IS" with no warranties, and confers no
\par rights.
\par > _____________________________________________________________
\par >
\par > --------------------
\par > Thread-Topic: MS / widcomm bluetooth programming
\par > thread-index: AcVFtm3PpBU9KVMQTGOvX2dvIU97pg==
\par > X-WBNR-Posting-Host: 217.15.96.17
\par > From: "=?Utf-8?B?S2V2aW4gQnVzdXR0aWw=?="
\par > <KevinBusuttil@xxxxxxxxxxxxxxxxxxxxxxxxx>
\par > Subject: MS / widcomm bluetooth programming
\par > Date: Wed, 20 Apr 2005 07:37:07 -0700
\par > Lines: 9
\par > Message-ID: <B524A998-0CA8-41AF-A494-B4E76F0192E0@xxxxxxxxxxxxx>
\par > MIME-Version: 1.0
\par > Content-Type: text/plain;
\par > charset="Utf-8"
\par > Content-Transfer-Encoding: 7bit
\par > X-Newsreader: Microsoft CDO for Windows 2000
\par > Content-Class: urn:content-classes:message
\par > Importance: normal
\par > Priority: normal
\par > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > Newsgroups: microsoft.public.pocketpc.developer.networking
\par > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > Xref: TK2MSFTNGXA02.phx.gbl
\par > microsoft.public.pocketpc.developer.networking:4224
\par > X-Tomcat-NG: microsoft.public.pocketpc.developer.networking
\par >
\par > Hi I'm rather new to Bluetooth programming.
\par >
\par > Is there a way to make one program using VC++ CE 4.2 that works both with
\par > Widcomm and Microsoft Bluetooth stack? Does programming with OBEX or
\par Serial
\par > Connectivity works?
\par >
\par > I couldn't find a simple up-to-date answer of this issue on the internet.
\par >
\par > Please help
\par >
\par
\par
\par \pard
\par
\par }
- References:
- MS / widcomm bluetooth programming
- From: Kevin Busuttil
- RE: MS / widcomm bluetooth programming
- From: Greg Scott [MS]
- Re: MS / widcomm bluetooth programming
- From: dave
- MS / widcomm bluetooth programming
- Prev by Date:
Re: MS / widcomm bluetooth programming - Next by Date:
OK, I'm embarrassed - s/b easy - connecting to SQL server - Previous by thread:
Re: MS / widcomm bluetooth programming - Next by thread:
does socket.Receive() block waiting for data? - Index(es):