lanestill.blogg.se

1. #Microsoft streets and trips 2011 problems driver#
2. #Microsoft streets and trips 2011 problems software#
3. #Microsoft streets and trips 2011 problems code#

It would even allow the AutoRoute 2013 software to work as advertised.Īddendum: Well, Microsoft hasn’t bothered to write a software shim, or updated their Streets & Trips or AutoRoute software at this time of writing (December 2013), but at least two third parties have developed shims:Īddendum 25 February 2014: If you’re looking for a map application that has maps held on your Tablet, and which will work directly with the GNSS sensor in the ThinkPad Tablet 2, then the good news is that Nokia has released its HERE Maps App for all Windows 8.1 devices. That would enable us to carry on using our legacy Windows navigation software on Windows 8 tablets with GPS receivers.

#Microsoft streets and trips 2011 problems code#

Now what would be really useful is for someone in Microsoft to code a software shim that would connect a virtual COM port to a Location Provider Driver. The left hand of Microsoft clearly has no clue what the right hand is doing.

Janet, please tell that to your fellow developers in Microsoft, not us, the poor users of this stuff.

#Microsoft streets and trips 2011 problems driver#

You can use the Location API and a Location Provider Driver to get NMEA strings, instead of using a virtual COM port. Open mouth, change feet.Ī further irony is given by the fact that when this issue was raised in a Microsoft forum, Janet Schneider, a Microsoft employee, blithely writes that However, the AutoRoute team has completely forgotten to use the new interfaces for GPS sensors that may be present in Windows 8 devices. What I find truly ironic about this is that Microsoft trumpets the fact that AutoRoute 2013 now has support for the Touch features of Windows 8: As you can see, AutoRoute 2013 expects to find GPS data arriving via a COM port, and complains that it can’t find the GPS receiver: I downloaded a trial version and installed it on my Lenovo ThinkPad Tablet 2, which has a Broadcom GNSS Gelocation Sensor in it. Here for example is the very latest version of Microsoft’s AutoRoute 2013. So, as you might expect, traditional Windows navigation software, which has been written expecting to find GPS data coming in via traditional COM port interfaces, won’t see the new generation of GPS receivers being built directly into PC hardware running Windows 8.Īnd so it is.

The point being that this means that there is a new set of interfaces for developers to use, and they are different from the traditional COM port interfaces. In the development of Windows 8, support for a variety of sensors, including GPS, was built into the operating system, and exposed by a new set of APIs. These days, they are “virtual” ports set up over a Bluetooth or USB connection. In the old days, these were physical RS232 ports. Instead, external devices such as GPS Data Loggers were used to provide GPS data, and interfaced to Windows software applications via Windows COM (communications) ports. Now the thing is that until very recently, PCs did not have GPS hardware built into them. I had noticed some reports that people weren’t able to get their navigation software to interface with the GPS sensor built in to some Windows 8 tablets. I see that I’ve used the phrase “open mouth, change feet” a number of times in the life of this blog to describe the continuing ability of Microsoft to snatch defeat from the jaws of victory.