Garmin Communicator Plugin v2.7.1.0 - v.2.7.1.0 - 6.78 MB
Garmin updated its Communicator Plugin on May 12, 2009 to the 2.7.1.0 version, an upgrade from version 2.6.4.0. The Garmin Communicator Plugin is a free internet browser plugin that sends and retrieves data from Garmin GPS devices. The Garmin Communicator can send and retrieve data from any supported website.
The plugin works with IBM-compatible PCs running Windows® XP or Vista operating systems with Internet Explorer 6+ or Firefox 1.5+ Intel-based or PowerPC G3 or later Mac OS 10.4 or later with Firefox 2.0+ or Safari 2.0. It is not compatible with Windows 2000 computers and will not install and/or function properly.
Garmin’s Communicator Plugin page is located at http://www8.garmin.com/products/communicator/
After a clean install of Microsoft Windows Vista Ultimate SP1 (and subsequent Windows updates) on my Toshiba Tecra M4 tablet, I checked the device manager to see if Vista missed anything. Only one yellow exclamation point was displayed. I dug into the properties of the unknown device and it displayed the following information: unknown device – other device on Intel 82801 FBM LPC Interface Controller – 2641. Doing a search on this information pointed to about half of the notebook devices made during the last few years – nothing useful. I looked at the hardware ID of the unknown device and it displayed ACPI\IFX0101. A search on that string produced results including an Infineon TPM (Trusted Platform Module), which I knew existed on my Tecra. I browsed over to Toshiba.com, downloaded the Trusted Platform Software, and no more unknown devices in the device manager.
We ran into a problem recently in SAS Web Report Studio 3.1 where our web reports that contained graphs produced java errors while our table-only reports did not. Our platform is SAS Enterprise Business Intelligence Server 9.1.3 Service Pack 4 running Solaris 10 on Sun SPARC Servers. Our web server is Apache Tomcat 4.1.18. The error we received looked like this:
I contacted SAS tech support and they had the answer instantly. When running in a headless environment (a server that does not have a display (monitor) attached to it), Tomcat requires the following option in its startup script:
Once I added the option to the Tomcat startup script and restarted Tomcat and SAS Remote Services, no more errors and we were getting our graph output in Web Report Studio again.