Step-four Ges.m.b.h USB Devices Driver



If there is more than one USB/DOT4 port available, select the USB/DOT4 port with the highest port number. To see the full port name, widen the ports row in the Properties dialog box by placing the cursor over the vertical line between Port and Description, and then click and hold the mouse button.Move the mouse to the right until the port name is visible. The Strike Industries Slide Adapter Plate (SAP) allows you to use a GEN3 slide on a GEN4 frame properly. A GLOCK™ factory or aftermarket GEN3 slide will fit and function on a GEN4 frame, but there are a few issues to address. USB-to-Serial Cable Converter. Software File Name: Title: Version: Publish Date: Manual: Notesusb2ser102: USB-to-Serial Cable Software Driver: 1.02:: Supported by Windows® 7, Windows® 8.1 and Windows® 10. Hello, Would you like us to contact you regarding USB.

You must have the following software components in order to start developing Android applications for ConnectCore 6:

If you already have Android Studio 2.0 or later in your computer, you can skip the first two installation steps.

Step-four Ges.m.b.h Usb Devices Driver Updater

Ges.m.b.h

1. Java SE Development Kit 7 (JDK 7)

Before you set up Android Studio, be sure you have installed JDK 7 or later. The Java Runtime Environment (JRE) alone is not sufficient.

For Linux users:

We recommend the Java OpenJDK-7 package. Depending on your distribution, you can install this package in two ways:

  • For Debian and Ubuntu distributions, issue this command:
  • For Fedora, Oracle Linux and Red Hat Enterprise Linux, issue this command:

For Windows users:

  1. Check if you already have JDK 7 or later installed on your computer. If you do, you can skip this step.
    How to check if you have JDK installed and which version
    1. Open a terminal and type the following:
    2. The version should be 7 or later. Java SE version strings have the form:

    • 1.x

    • 1.x.0

    • 1.x.0_u

    In these examples, x is the product version number and u is the update version number. For example, an installed JDK update 60 (JDK 7u60) returns:

  2. If the JDK is not installed or the version is not 7 or later:
    1. Download the Java SE Development Kit 7 at www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
    2. Once the download is complete, run the executable file and follow the on-screen instructions to finish the installation process.

2. Android Studio

Android Studio provides everything you need to start developing apps for Android. Digi Embedded for Android has been validated with Android Studio 2.2.3, although newer versions should also work.

To download and install Android Studio on your computer:

  1. Download Android Studio at http://developer.android.com/sdk/index.html.
  2. Follow the steps for installing Android Studio at https://developer.android.com/sdk/installing/index.html?pkg=studio.

3. Digi Extensions for Android Studio

To download and install the Digi Extensions on your Android Studio:

  1. Open Android Studio.
  2. Open the Android Studio Settings dialog by doing one of the following:
    • Select Configure > Settings on the Welcome screen.
    • Select File > Settings from the menu.
  3. Select Plugins from the tree on the left of the Settings dialog.

Note You can also access the Plugins dialog from the Welcome screen. Click Configure on the Quick Start panel and then click Plugins.

  1. Click Browse repositories at the bottom of the page.
  2. In the Browse Repositories dialog, select Digi Extensions for Android Studio from the list on the left. You can use the search box to look for the plugin.
  3. Click Install plugin on the right panel.
  4. A dialog is displayed asking whether you would like to download and install the plugin Digi Extensions for Android Studio. Click Yes.

    A dialog displays the progress of the download process.

  5. Once the download process finishes, click Close in the Browse Repositories dialog.
  6. Click OK to close the Plugins dialog.
  7. When a message appears asking you to restart, click Restart to activate the plugin.

4. SDK Add-on for ConnectCore 6

You are now ready to start developing Android applications. The Get started section provides an initial tutorial, while the Application development section gives you everything you need to start using the Digi APIX for Android extensions to create more advanced apps.

  1. On the Android Studio Welcome screen, click Configure on the Quick Start panel and then click SDK Manager.
  2. Click the Launch Standalone SDK Manager link at the bottom of the list. The SDK Manager dialog opens.

  3. Click Deselect All to uncheck any previously selected package from the list.

  4. Select Tools > Manage Add-on Sites from the main menu of the application.

    A new configuration window opens.

  5. Select the User Defined Sites tab and click the New button to add a new add-on site.
  6. Enter the following URL for the new add-on site: http://ftp1.digi.com/support/android/sdk_addon/addon.xml
  7. Click OK and then close the Add-on Sites configuration dialog. A new package named SDK Add-On for ConnectCore 6 appears under Android 5.1.1 (API 22).
  8. Select the new package and click Install 1 package.
  9. Accept the License Agreement and click Install.
  10. Once installation is complete, close the SDK Manager.
  11. Restart Android Studio.

You are now ready to develop Android applications using the Digi APIX for Android.

5. Google USB driver

You need the Google USB Driver for Windows if you want to perform adb (Android Debug Bridge) debugging with your ConnectCore device.

  1. Download the Google USB driver at http://developer.android.com/sdk/win-usb.html.
  2. Once you have downloaded the USB driver, perform the following instructions to install it, based on your Windows version:
Windows 7 or later

To install the Google USB driver on Windows 7 or later for the first time:

  1. Unzip the downloaded file.
  2. Connect your Android-powered device to your computer's USB port.
  3. Right-click on Computer from your desktop or Windows Explorer, and select Manage.
  4. Select Device Manager in the left pane of the Computer Management window.
  5. Locate and expand Other device in the right pane.
  6. Right-click the device name and select Update Driver Software to launch the Update Driver Software wizard.
  7. Select Browse my computer for driver software and click Next.
  8. Click Browse and locate the USB driver folder, called usb_driver, which appears after you decompress the downloaded file.
  9. Click Next to install the driver.
Windows Vista

To install the Google USB driver on Windows Vista for the first time:

  1. Unzip the downloaded file.
  2. Connect your Android-powered device to your computer's USB port. Windows detects the device and launches the Found New Hardware wizard.
  3. Select Locate and install driver software.
  4. Select Don't search online.
  5. Select I don't have the disk. Show me other options.
  6. Select Browse my computer for driver software.
  7. Click Browse and locate the USB driver folder, called usb_driver, which appears after you decompress the downloaded file.
  8. Click Next. Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
  9. When Vista asks if you'd like to install the Google ADB Interface device, click Install to install the driver.

In a hurry and just want the script, click here.


If you're here, then you must have a driver and App-V conundrum. Perhaps you have sequenced scanner software but you still need to find a delivery method to get the driver injected? Maybe it’s a label maker, a noise measurement tool, a 3d printer, timing equipment - the list goes on.

You’re in the right place. I've written a script which will work with App-V to inject and remove the drivers as part of the DeploymentConfig. It will also handle drivers where the certificate is not known in the Trusted Root Certification Authorities.

The script was written with the following in mind.


·Scalable.

·Reusable.

Step-four Ges.m.b.h Usb Devices Driver Vga

·Low administrative overhead.

A Quick Guide On Drivers

First, some knowledge on drivers, driver signing and how it all works together. After much research I've found drivers fall into three categories.


·Signed and certificate chain is recognised in the Trusted Root Certification Authorities.
These will silently install with DPIsnt.

·Signed, but certificate chain is not recognised by Trusted Root Certification Authorities.
These will throw a prompt when you try to install them with DPIsnt.

·Unsigned or signed but has been modified, the certificate may or may not be recognised by the Trusted Root Certification Authorities.
These will throw an ugly warning which you cannot get around easily.

You can work around the second bullet point, but to work around the third bullet point is either impossible or a lot of work depending on your desired outcome. If this is your problem, then read 'Sign your unsigned drivers - Damn It' for more information, as this script will not help.


At this point I recommend reading the sections below from 'Practical Windows Code and Driver Signing' - it will give you a decent insight into driver signing.

·Anatomy of a signature

·Signature requirements, specifically the section TRCA requirements for it to look good.

·Installing a driver package

·Driver package installation in Windows Vista and 7



Important information: The .cat file contains a cryptographic hash of all the files, if you modify any of the files it will break the hash. eg, editing of the .inf file.




All About The Manage-Drivers.ps1 Script

The script can be found hereon my GitHub Gist.

https://gist.github.com/rileyz/464175e3bb96f1b67dfc



The script can perform the following functions.

  • Inject drivers.
  • Inject drivers and hide Programs and Features entry.
  • Import certificate into Trust Publishers store pre driver injection.
  • Remove drivers.
  • Remove certificate from Trust Publishers store post driver removal.
  • All the above with Logging.


There are a number inbuilt script variables that can be changed as per requirements, they are as follows.

$LogFile, change this to your desired log location. Default is %Windows%Temp

$DPInst32, name of DPInst 32bit executable.

$DPInst64, name of DPIsnt 64bit executable.

Step-four Ges.m.b.h USB Devices Driver

$WithThisErrorCode, set to 0 to gracefully exit or set to 1 to fatally exit.

It’s important to note that if you plan to use $WithThisErrorCode to fatally exit, it needs to be used in conjunction with the DeploymentConfig xml attribute <Wait RollbackOnError='true' Timeout='30'/>.

The script has two mandatory parameters which are as follows.

-DriverSource a token, UNC or relative path to driver source.

-LogName the name for the log file.

The script has two optional parameters which are as follows.

-HideARP, this switch will not add entry to Programs and Features.

-Remove, this switch will remove the driver package from the Driver Store.


If your certificate chain is not recognised by Trusted Root Certification Authorities then you need to add a certificate to the Trusted Publishers certificate store. This functionality has been built into the script, just prefix the certificate with “TrustedPublishers” and store it at the base directory with the drivers.


To make use of the script, the DeploymentConfig will need to be edited. The script is launched via PowerShell in ExecutionPolicy ByPass mode, passing the required arguments to the script to locate the drivers and name the log file.



To inject drivers, where the drivers are located on the VFS.


To inject drivers, where the drivers are located in a zip archive.


To inject drivers and hide the Program and Features entry.


To remove a driver, where the drivers are located on the VFS.


To remove drivers, where the drivers are located in a zip archive.


Step By Step Guide

Best to do the steps below in a virtual environment as it’s easy to step back to a clean snapshot for testing.


Remember, always do a standard vendor install to ensure the software/drivers work as required.

Step-four Ges.m.b.h Usb Devices Driver Adapter


I'm assuming intelligence on the reader’s part to fill in the gaps.

  1. On a clean machine inject the drivers manually using DPInst.
    If you get prompted “Would you like to install this device software?” then check the “Always trust software from…” check-box and click install.
    Open the DPIsnt log to double check it installed ok. Returning with code 0x100 means DPInst injected one driver, 0x200 means two drivers injected and so on.
  2. If you received the “Would you like to install this device software?” prompt, it means the certificate chain was not recognised in the Trusted Root Certification Authorities. Hopefully you checked the box “Always trust software from…” as we now need to export the certificate from the certificate store.
    In a nutshell you need to start MMC -> Certificates -> This Computer -> Trusted Publishers -> export the certificate.
    If you’re a bit unsure then have a look at the two links below for more detailed information, no point reinventing the wheel.
    http://it.peikkoluola.net/2013/12/16/windows-cant-verity-the-publisher-of-this-driver-software-bat
    http://www.myangrydome.com/?p=1744
  3. After the above steps one and two you should have similar files below ready for the App-V package, to either add during sequencing or afterwards during finalisation of the App-V package.
  4. Time to sequence your application and add the files to the VFS or scripts collateral folder depending on your desired implementation.
    You should have something similar below after you have sequenced the application.
    1. VFS implementation.
    2. Scripts collateral implementation.
  5. It’s now time to edit the DeploymentConfig.xml, the implementation you chose in step four will determine the PowerShell arguments you need to pass to the script.

6. Test your App-V package, and don’t forget to enable package scripts.


  • Where do I get DPInst?
    You can get DPInst from the Windows Driver Kit (WDK).


Step-four Ges.m.b.h Usb Devices Drivers

Compatible With App-V Versions
If the version has not been mentioned, then it has not been tested against that version.
Most likely will be OK, just has not been formally tested.

  • App-V 5 SP2 - OK
  • App-V 5 SP2 HF4 - OK
  • App-V 5 SP3 - OK
  • App-V 5.1 - OK
  • App-V Windows 10 (all versions with no known issues currently 27/11/2019)


Compatible With Windows Installer

Just tested this out recently on a Windows Installer package, I had a requirement to add the certificate to Trusted Publishers as that was stopping the driver injection. It works but it not intended for this kind of application.



Edit Log

29/01/2015: Initial release.

24/02/2015: Spelling errors fixed.

10/04/2015: Added App-V target version testing.

17/06/2015: Confirmed script works on SP3.

13/11/2015: Confirmed script works on MSI packages.

*Seen issues with zip extraction on Windows 7, recommend folder path for source.

19/04/2016: Confirmed script works on 5.1.
Caveats, bug found when running script with ScriptRunner.exe.
Test case = Windows 10 64-bit, App-V 5.1.
Script detects 64-bit system as 32-bit, thus uses incorrect DPInst architecture.
The root cause is ScriptRunning.exe being 32-bit, thus running a 32-bit PowerShell session.

16/05/2016: Script has been bugfixed to detect o/s architecture correctly when launched with ScriptRunning.exe.

03/05/2017: Bug found: Script does not unpack zip file from UNC path reference location, ie MyServerMyDriver.zip.

This is an unusual/low risk bug as normally the zip source is stored with the package itself.

27/11/2019: Updated App-V Support.