The good news is that we are currently testing our new communication protocol and it will be ready for a Beta release soon. We have been diligently working on a new communication mechanism that will work on all browsers and will avoid such things as NPAPI and Active-X and will decouple the SDK from browser specific implementations. Our existing JavaScript SDK utilizes this API.
In some situations, a full shutdown and reboot is required after all the steps have been performed for the plugin to appear in Chrome.Īs many of you know, Google is removing support for NPAPI in the Chrome browser. Go here to see if your browser has the framework installed correctly: Check Environement
In some instances, close the chrome browser then uninstall and re-install the DLS software for the plugin to appear in the plugin list: chrome://plugins/ It has been our experience that just enabling NPAPI may not be enough.
However, you can manually enable it by typing the following into the Chrome address bar and adjusting the setting: With version 42 of Chrome, Google now disables NPAPI which is required to run our plugin. We recognize that this is not a valid long term solution. It has options to add a wild card URL that will automatically use the IE Tab when it matches. This will put a web page into an IE browser tab within Chrome and will use the ActiveX plugin instead of the NPAPI version.
The same API supports all major browsers on Windows and Mac.
No new development will be done for the extension. Please note that the Firefox extension is deprecated. The Firefox extension for DYMO SDK has been updated to support Firefox 27.
KB2911106, released on, solved this issue in Windows 8.1 It can be downloaded from the below links. Microsoft has released a fix for this issue. We apologize for this inconvenience and will keep everyone updated on a fix for this issue. You may encounter scanning issues for barcodes with lots of data or 2D barcodes, though. That being said, for most barcodes, 300×300 DPI is plenty of resolution. When the “Print Quality” setting is set to “Auto” or “Barcodes and graphics”, the resolution will always be 300×600 if a barcode is present on your label.
For barcodes, we typically like to switch our printers into high resolution mode (300×600 DPI) in order to improve barcode scanning reliability. There is one side effect to making this change and that is your labels will always print at a resolution of 300×300 DPI. Navigate to the LabelWriter printer tab and change the “Print Quality” to “Text”. We are awaiting a fix from Microsoft, but in the meantime, you will need to modify a setting in DLS to workaround the issue. There is currently a bug in Windows 8.1 that causes any label with a barcode to print abnormally in DLS.