Windows CE Networking - from NDIS to TCP to SOAP to VOIP and everything in between.
Browse by Tags
All Tags »
Author: John Spaith (RSS)
Sorry, but there are no more tags available to filter with.
-
I mention here that the information about the GPSID poll driver is now included in WinCE 6. If you are an OEM implementing a GPS driver on CE6 and you're not natively spitting out NMEA but would have to generate NMEA only for GPSID to parse, I'd highly Read More...
|
-
Suppose you have some service in services(d).exe on your CE device that is so critical that you don't anyone ever unloading it. This would be a paranoid play, since most users never mess around with loading and unloading services directly. But say that Read More...
|
-
At some basic level, Windows CE's GPSID and Location Framework are doing the same thing. They're giving you the position of your device. I've had people ask me if with Location Framework if we were going to retire/deprecate/etc... GPSID. No. First, Location Read More...
|
-
In CE 6.0, one of the things we changed was naming services.exe to be servicesd.exe. I mentioned it at the end of my CE6 services.exe initial post as to why we did this. Services.exe in CE6 is just a simple command line wrapper that lets you do things Read More...
|
-
By default, whenever you use BSTRs OLE will keep the memory cached in order to aid performance. There are scenarios where you may want to disable this. First would be if you're on a device with not a lot of memory and don't want it being spent in the Read More...
|
-
The new name for Windows CE is Windows Embedded CE 6.0. Some of the marketing guys are unhappy when I call it only "Windows CE", never mind WinCE or just CE. Though I really really doubt any of you would be confused or care, I'll call out officially that Read More...
|
-
As I hinted at here , in CE 6.0 we have removed DCOM remoting due to security concerns. This is only the remoting portion. There has been some confusion on this so I want to make it clear what this means. You can still do interprocess communication on Read More...
|
-
Thanks to Seattle getting snowed in and MS borderline shutting down and me not having an emulator image built yet, this will be my first ever two blog in one day. OK, enough soon to be dated blog chattiness. Down to business. Suppose you're writing an Read More...
|
-
When rewriting services.exe for the CE 6.0 kernel , we tried to make it so that as few changes as possible were required for service writers. Unlike application BC (which is critical), there were some places in services.exe where your service may need Read More...
|
-
We're very committed on CE to creating a great development platform for location aware applications. The first piece of this was GPSID, introduced in WM5 and now in general embedded for CE 6.0. In CE 6.0, I'm pleased to announce we've added another, more Read More...
|
-
In Windows Mobile 5, we first introduced the GPS Intermediate Driver. I describe why it went into a WM release rather than general embedded here . In CE 6.0, I'm happy to announce that GPSID did make it into the product for real, as promised (or as close Read More...
|
-
I realize as I type this that there's probably 5 people in the world that actually care about this post (or most of my posts for that matter), so if you're one of the 5 I hope you really enjoy it :). In Windows Mobile 5, when we introduced GPSID (GPS Read More...
|
-
Note: This is more of a geeky article for people who want to know how stuff works under the hood in Windows CE. If you're just trying to write a service DLL there's much better guides available. In CE 6.0, services.exe was completely rewritten and renamed Read More...
|
-
If you're having problems with MSMQ on a general embedded device, you can build a debug image and setup very verbose logging in order to see what's going wrong. On a Windows Mobile device debugging MSMQ is harder and you can't get as much information Read More...
|
-
Why doesn't Windows Mobile have out of proc COM in the first place? It gets down to ROM constraints. The difference between in-proc only COM and out-of-proc COM support is in the range of 500KB - my former boss who did this work did a very good job componentizing Read More...
|
