Medtronic USB Devices Driver

Posted on

Medtronic Diabetes. CareLink™ Software How to Use CareLink™ Personal Software Supported Systems Create an Account Using CareLink™ Personal Software Installing and Using the New.

  1. Find information about medical products and devices that can help healthcare professionals meet their patients' needs.
  2. Medtronic Minimed CareLink USB Wireless Upload Device Medtronic Minimed CareLink USB Wireless Upload Device. Belkin wireless g plus mimo usb network adapter driver.
--- Software Downloads ---

Note:

1. Please temporarily disable Antivirus Real Time Protection or open a window for downloading to prevent from Over-Protection, causing

'Incomplete Download'. Please check downloaded file size to see if it has the same size as original on the web site.

Otherwise you may fail to Unzip and install the driver due to 'Incomplete Download'.

2. For files with rar extension, download 'RAR' Decompress SW from http://www.win-rar.com/download.html ;
For files with zip extension, download Unzip SW from http://www.winzip.com/win/en/downwz.htm ;

For files with PDF extension, download pdf reader from http://www.adobe.com/downloads/

3.Please provide basic data when inquiring support: (1) dongle serial number with the prefix, (2) year/ date purchased , (3) from where you bought, (4) Your other IR device (type/brand/model) you want to link to? (see Tech Support Form)

ACT-IRx24UN series (incl. IR224UN/424UN, IRx24UN-Li, IRx24UN-LN, IRx24UN-L+; IRx24UN-Lx-LE series)

Drivers for Mac OS, Windows (32 & 64 bit); WinCE; & Linux (Note: Shares the same driver for ACT-IR100UD family & ACT1-201)
For Windows 7/8/10 OS, Dvr installer v1.5.0 and Install Guide for ACT-IRx24UN-Lx and IRx24UN-Lx-LE (Compatible Driver & TSPack for those IR adapters which their SN# prefix starts with 'UN' or 'LI').

Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support. This can be identified by your IR adapter serial number that is not 'UN' or 'LI'. In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside). (Please See NOTE3 above for providing your basic data)

For Windows 7/8/10 OS, Dvr installer v1.12.0 and Install Guide for ACT-IRx24UN-Lx and IRx24UN-Lx-LE
(Compatible Driver & TSPack for those IR adapters which their SN# prefix starts with 'TA').

Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support. This can be identified by your IR adapter serial number. In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside). (Please See NOTE3 above for providing your basic data)

IRx24UN-Lx_Lx-LE-Manual-v1.3.4-140324.pdf General Manual - ACT-IRx24UN-Li/IRx24UN-L+/ IRx24UN-LN and ACT-IRx24UN-Lx-LE
Advanced-Uninstaller-121127.zip_File Size=18279KBThis is a Driver Remover for those users who could not uninstall the old driver from PC successfully. After running this software and complete un-installation is done, please reboot your PC. Then install the new driver. ( Source: Advance Uninstaller PRO by Innovative Solutions.)
  • For Mac OS X 10.11 El Capitan (64-bit)
  • For Mac OS X 10.10 Yosemite (64-bit)
  • For Mac OS X 10.9 Mavericks (64-bit)
  • For PL2303 H/HX/HXD/EA/RA/SA/TA/TB chip versions
  • For Prolific USB VID_067B&PID_2303 Only
  • Includes Driver Installation Manual

Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support. This can be identified by your IR adapter serial number. In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside). (Please See NOTE3 above for providing your basic data)

md_IRx24UN_H_HX_X_dmg_v1.2.1r2.zipACT-IR224UN/424UN Mac OS X Universal Binary Driver (DMG file format)
For MacOS 10.1 and above for PowerPC based Mac
For MacOS 10.4 and above for PowerPC and Intel based Mac
Supports Mac OS X 10.5 and above for PowerPC and Intel based Mac
md_IRx24UN_Mac8_9_v136b1.zipACT-IR224UN/424UN Mac OS 8 & 9 driver v1.3.6 build 1
ACT-IR224UN-Li-4Mac-Manual-v1.3.4-140324.pdfManual - for Mac Users of ACT-IR224UN-Li
Generic_IRx24UN_WinCE50_ARM_v1009.CABACT-IR224UN/424UN WinCE 5.0 Driver for ARM Standard SDK
Also for Windows Mobile 6, Windows Mobile 5, PocketPC 2003.
NOTE: Check HKEY_LOCAL_MACHINEDriversActiveUSBSER folder in registry for the COM port number.
Generic_IRx24UN_WinCE50_x86_v1009.CABACT-IR224UN/424UN WinCE 5.0 Driver for x86 Standard SDK
Also for Windows Mobile 6, Windows Mobile 5, PocketPC 2003.
NOTE: Check HKEY_LOCAL_MACHINEDriversActiveUSBSER folder in registry for the COM port number.
ld_IRx24UN_Linux_v0728.rarACT-IR224UN/424UN Linux driver for RedHat 7.3/8.0/9.0 Only.
NOTE: No need to install drivers for following:
Linux Kernel 2.4.10 and above already includes built-in drivers for PL-2303H.
Linux Kernel 2.4.31 and above already includes built-in drivers for PL-2303H, PL-2303XA/HXA and PL-2303HXD
ACT-IR224UN/IR424UN Configuration utility

Please contact [email protected] for it (Please See NOTE3for providing your basic data)

ACT1-201 ; ACT1-211
ACT1-201 Driver
Driver InstallerPlease just download from IR224UN.Actually they share the same driver.
ACT1-211 GPS Driver
ACT1-211_1414_20110314_GPS.zipGPS Driver to block Windows Mouse problem occur at 2400 bps (supports Win7 32 and 64 bit)
ACT-IR100UD-MDT
ACT-IR100UD-MDT-CD-v1.1.0-130208.zipCD for IR100UD-MDT which includes Windows driver. Please download other drivers from above IRx24UNjust in case needed. They actually share the same.
ACT-IR2000UL/IR4000US
User's Manual for Windows XP/Vista/Win7/8/10

Please contact [email protected] (Please See NOTE3 above for providing your basic data)

Driver for Windows 98/Me/2000/XP/vista/Win7/8/10 (32 & 64 bit)
Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support.
This can be identified by your IR adapter serial number. In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside).
(Please See NOTE3 above for providing your basic data)
ACT-IR2002UL/IR4002US
IR2002UL/IR4002US Manual

Please contact [email protected] (Please See NOTE3 above for providing your basic data)

IR2002UL /IR4002US Drivers
Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support.
This can be identified by your IR adapter serial number. In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside).
(Please See NOTE3 abovefor providing your basic data)
Note:If you useIrDA-OBEX, these USB-IrDA adapters support Win7/8/10-32 and 64 bit.
But, if you use IrDA-IrComm,you'll need IrComm2K ( free software from 3rd party) for all Windows O.S., including Win7-32 bit.
However,IrComm2K does Not support 64bit. then please use ACT-IR100UD/ACT-IR100UD-v2/IR100UD-v3, the Intelligent USB-IrDA adapter which is our once-for-all solution.
ACT-IR100UD/ IR120UD/ IR100UD-v2/ IR100UD-v3
ACT-IR100UD/ IR120UD/ IR100UD-v2/ IR100UD-v3 Drivers & Manuals
Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support. This can be identified by your IR adapter serial number.
In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside). (Please See NOTE3 abovefor providing your basic data)
CD for IR100UD-LPT

Please contact [email protected] (Please See NOTE3 abovefor providing your basic data)

ACT-IR100M/ IR100MP/IR100MU
ACT-IR100Mx Series (100M/100MP/100MU) User Manual
ACT-IR100MxManual -v3.2.2.1-080324.pdf

Manual for ACT-IR100M/IR100MP

ACT-IR100MU-Manual-v1.2-100108.pdfManual for ACT-IR100MU
IR82x0D/IR8250P/IR826xD

Spec for ACT-IR82x0D

Technical Spec for ACT-IR82x0D

Spec of ACT-IR8250P

Technical Spec for ACT-IR8250P

ACT-IR826xD-Technical-v1.0.0.1-120220.pdf Technical Spec for ACT-IR826xD
ACT-IR3200M
ACT-IR3200M User Guide
Please contact [email protected](Please See NOTE3 above for providing your basic data)
ACT-IR200L/IR220L/IR220L+
Windows 7/8/10 Driver
Please contact [email protected] for the driver (for some old IR adapters the IC used inside is EOL, with no driver support. This can be identified by your IR adapter serial number.
In such a case there will be no Windows 10 driver, may need to buy new IR adapter with new IC inside). (Please See NOTE3 above for providing your basic data) It is for Windows 7/8/10 IrDA driver.
Windows User Manual - for IrDA use
IR200L-IR220L&IR220L+ Manual.pdfDriver install/uninstall procedure for Windows 98/2000/XP/Vista/Win7/8/10 (32 & 64 bit)
ACTiLinkACPI_011L.zip
  1. NOTE: a. You Need Not install ACTiLinkACPI for your PC UNLESS it is really needed under some Notebook PC for IR220L+ due to below reasons.
    NOTE: b. The file we provide here is ONLY a 30-day TRIAL Version. Please BUY the Standard Version i
    f you feel it DOES Help, after the trial period expired.

  2. [What is ACPI]: In Win98SE and later Windows O.S., ACPI manager is used to save power for notebook PC. e.g., if no software using floating calculation, ACPI manager may turn off CPU. It then saves power.

  3. [What it helps]: ACPI manager also disables COM port. ACT-IR220L+ uses no external power, which gets from RS232 COM port RTS/DTR signal lines. This is to Deactivate this function, so that IR220L+ can get power and function well.

  4. Windows OS relevance : ACTiLinkACPI will not work on all OLD Windows O.S., e.g. Windows 95.

ACT-IR200L
ACT-IR200L-UsefulLink-v1.0.0-101013.pdfUseful Third Party Driver/Software Developer URL Link for ACT-IR200L
Windows 3.11 Driver
Irwin311.zip Irwin311.exe - Windows 3.11 Driver for IR200L/220L/220L+ Only
Windows 95 Driver
Irda20.zip Irda20.zip - Windows 95 Driver for IR200L/220L/220L+ Only
IrCOMM
IrComm for Windows 2000/XP/Vista/Win 7
IrComm2K.zipIrComm - to Create Virtual Port
Manual-VirtualCOMport-IrCOMM2Kdriver.pdfMicrosoft Windows 2K/XP/Vista/Win7 IrDA stack does not include IrCOMM. So, if your opposite IrDA device supports IrCOMM as a upper IrDA application protocol and wish your device exchange data using IrCOMM protocol then you can download this Third party driver and install it. Please, refer Manual for installation
ACT-IR204UN
CD Pack for ACT-IR204UN
ACT-IR204UN installation CD [Note]: Only supports up to Windows XP.
(for Windows Vista/7/8/10 and up, IR224UN is its replacement.(2nd generation)

Please contact [email protected] (Please See NOTE3 above for providing your basic data)

BLUETOOTH Dongles:
ACT-BT5100US-Air
BT5100US-Air.zip Driver Installation CD: IVT BlueSoleil (TM) 1.6.1.1 & user manual
ACT-BT5701S v2
ACT-BT5701Sv2-Manual-v2.1.1-101223.zipUser's manual
ACT-BT5711U
ACT-BT5711U-Manual-v1.0.3.1-140529.zipUser's manual
ACT-BT5800UB & BT5900US
Note-Printer_PortSetting.pdfA common Note on Printer Port Setup
OTHER OLD Dongles Solutions:
PleaseGoto DownLoads OOther old dongles solutions

[ Home Page About ACTiSYS Contact us IrDA Products Tutorials IrDA Test Center Compatibility

[ Order Price Quote Technical Support Downloads Track a Package Jobs Feedback Privacy Terms ]

ACTiSYS CORP. 921 Corporate WayFremont, CA 94539 Tel: +1-510-490-8024 Fax: +1-510-623-7268 [email protected]

©1996-2015 ACTiSYS Corporation, All Rights Reserved
--------------------------------------------------------------------------------------------------
Member of Infrared Data Association (IrDA
®) Since Its Founding Day!

-->

For certain Universal Serial Bus (USB) devices, such as devices that are accessed by only a single application, you can install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.

USB

This topic contains these sections:

Automatic installation of WinUSB without an INF file

As an OEM or independent hardware vendor (IHV), you can build your device so that the Winusb.sys gets installed automatically on Windows 8 and later versions of the operating system. Such a device is called a WinUSB device and does not require you to write a custom INF file that references in-box Winusb.inf.

When you connect a WinUSB device, the system reads device information and loads Winusb.sys automatically.

Medtronic USB devices driver

For more information, see WinUSB Device.

Installing WinUSB by specifying the system-provided device class

When you connect your device, you might notice that Windows loads Winusb.sys automatically (if the IHV has defined the device as a WinUSB Device). Otherwise follow these instructions to load the driver:

Medtronic USB Devices Driver

  1. Plug in your device to the host system.
  2. Open Device Manager and locate the device.
  3. Select and hold (or right-click) the device and select Update driver software... from the context menu.
  4. In the wizard, select Browse my computer for driver software.
  5. Select Let me pick from a list of device drivers on my computer.
  6. From the list of device classes, select Universal Serial Bus devices.
  7. The wizard displays WinUsb Device. Select it to load the driver.

If Universal Serial Bus devices does not appear in the list of device classes, then you need to install the driver by using a custom INF.The preceding procedure does not add a device interface GUID for an app (UWP app or Windows desktop app) to access the device. You must add the GUID manually by following this procedure.

  1. Load the driver as described in the preceding procedure.

  2. Generate a device interface GUID for your device, by using a tool such as guidgen.exe.

  3. Find the registry key for the device under this key:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB<VID_vvvv&PID_pppp>

  4. Under the Device Parameters key, add a String registry entry named DeviceInterfaceGUID or a Multi-String entry named DeviceInterfaceGUIDs. Set the value to the GUID you generated in step 2.

  5. Disconnect the device from the system and reconnect it to the same physical port.Note If you change the physical port then you must repeat steps 1 through 4.

Writing a custom INF for WinUSB installation

As part of the driver package, you provide an .inf file that installs Winusb.sys as the function driver for the USB device.

The following example .inf file shows WinUSB installation for most USB devices with some modifications, such as changing USB_Install in section names to an appropriate DDInstall value. You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufacture's name, the name of your signed catalog file, the correct device class, and the vendor identifier (VID) and product identifier (PID) for the device.

Also notice that the setup class is set to 'USBDevice'. Vendors can use the 'USBDevice' setup class for devices that do not belong to another class and are not USB host controllers or hubs.

If you are installing WinUSB as the function driver for one of the functions in a USB composite device, you must provide the hardware ID that is associated with the function, in the INF. You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. The hardware ID string format is 'USBVID_vvvv&PID_pppp'.

Medtronic Usb Device Driver

The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system.

Starting in Windows 10, version 1709, the Windows Driver Kit provides InfVerif.exe that you can use to test a driver INF file to make sure there are no syntax issues and the INF file is universal. We recommened that you provide a universal INF. For more information, see Using a Universal INF File.

Only include a ClassInstall32 section in a device INF file to install a new custom device setup class. INF files for devices in an installed class, whether a system-supplied device setup class or a custom class, must not include a ClassInstall32 section.

Except for device-specific values and several issues that are noted in the following list, you can use these sections and directives to install WinUSB for any USB device. These list items describe the Includes and Directives in the preceding .inf file.

  • USB_Install: The Include and Needs directives in the USB_Install section are required for installing WinUSB. You should not modify these directives.

  • USB_Install.Services: The Include directive in the USB_Install.Services section includes the system-supplied .inf for WinUSB (WinUSB.inf). This .inf file is installed by the WinUSB co-installer if it isn't already on the target system. The Needs directive specifies the section within WinUSB.inf that contains information required to install Winusb.sys as the device's function driver. You should not modify these directives.Note Because Windows XP doesn't provide WinUSB.inf, the file must either be copied to Windows XP systems by the co-installer, or you should provide a separate decorated section for Windows XP.

  • USB_Install.HW: This section is the key in the .inf file. It specifies the device interface globally unique identifier (GUID) for your device. The AddReg directive sets the specified interface GUID in a standard registry value. When Winusb.sys is loaded as the device's function driver, it reads the registry value DeviceInterfaceGUIDs key and uses the specified GUID to represent the device interface. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID.

    Note User-mode software must call SetupDiGetClassDevs to enumerate the registered device interfaces that are associated with one of the device interface classes specified under the DeviceInterfaceGUIDs key. SetupDiGetClassDevs returns the device handle for the device that the user-mode software must then pass to the WinUsb_Initialize routine to obtain a WinUSB handle for the device interface. For more info about these routines, see How to Access a USB Device by Using WinUSB Functions.

The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system. The example shows INF with WDF coinstallers.

  • USB_Install.CoInstallers: This section, which includes the referenced AddReg and CopyFiles sections, contains data and instructions to install the WinUSB and KMDF co-installers and associate them with the device. Most USB devices can use these sections and directives without modification.

  • The x86-based and x64-based versions of Windows have separate co-installers.

    Note Each co-installer has free and checked versions. Use the free version to install WinUSB on free builds of Windows, including all retail versions. Use the checked version (with the '_chk' suffix) to install WinUSB on checked builds of Windows.

Each time Winusb.sys loads, it registers a device interface that has the device interface classes that are specified in the registry under the DeviceInterfaceGUIDs key.

Device

Note If you use the redistributable WinUSB package for Windows XP or Windows Server 2003, make sure that you don't uninstall WinUSB in your uninstall packages. Other USB devices might be using WinUSB, so its binaries must remain in the shared folder.

How to create a driver package that installs Winusb.sys

To use WinUSB as the device's function driver, you create a driver package. The driver package must contain these files:

  • WinUSB co-installer (Winusbcoinstaller.dll)
  • KMDF co-installer (WdfcoinstallerXXX.dll)
  • An .inf file that installs Winusb.sys as the device's function driver. For more information, see Writing an .Inf File for WinUSB Installation.
  • A signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows starting with Vista.
Medtronic USB Devices Driver

Medtronic Usb Devices Drivers

Note Make sure that the driver package contents meet these requirements:

  • The KMDF and WinUSB co-installer files must be obtained from the same version of the Windows Driver Kit (WDK).
  • The co-installer files must be obtained from the latest version of the WDK, so that the driver supports all the latest Windows releases.
  • The contents of the driver package must be digitally signed with a Winqual release signature. For more info about how to create and test signed catalog files, see Kernel-Mode Code Signing Walkthrough on the Windows Dev Center - Hardware site.
  1. Download the Windows Driver Kit (WDK) and install it.

  2. Create a driver package folder on the machine that the USB device is connected to. For example, c:UsbDevice.

  3. Copy the WinUSB co-installer (WinusbcoinstallerX.dll) from the WinDDKBuildNumberredistwinusb folder to the driver package folder.

    The WinUSB co-installer (Winusbcoinstaller.dll) installs WinUSB on the target system, if necessary. The WDK includes three versions of the co-installer depending on the system architecture: x86-based, x64-based, and Itanium-based systems. They are all named WinusbcoinstallerX.dll and are located in the appropriate subdirectory in the WinDDKBuildNumberredistwinusb folder.

  4. Copy the KMDF co-installer (WdfcoinstallerXXX.dll) from the WinDDKBuildNumberredistwdf folder to the driver package folder.

    The KMDF co-installer (WdfcoinstallerXXX.dll) installs the correct version of KMDF on the target system, if necessary. The version of WinUSB co-installer must match the KMDF co-installer because KMDF-based client drivers, such as Winusb.sys, require the corresponding version of the KMDF framework to be installed properly on the system. For example, Winusbcoinstaller2.dll requires KMDF version 1.9, which is installed by Wdfcoinstaller01009.dll. The x86 and x64 versions of WdfcoinstallerXXX.dll are included with the WDK under the WinDDKBuildNumberredistwdf folder. The following table shows the WinUSB co-installer and the associated KMDF co-installer to use on the target system.

    Use this table to determine the WinUSB co-installer and the associated KMDF co-installer.

    WinUSB co-installerKMDF library versionKMDF co-installer
    Winusbcoinstaller.dllRequires KMDF version 1.5 or later

    Wdfcoinstaller01005.dll

    Wdfcoinstaller01007.dll

    Wdfcoinstaller01009.dll

    Winusbcoinstaller2.dllRequires KMDF version 1.9 or laterWdfcoinstaller01009.dll
    Winusbcoinstaller2.dllRequires KMDF version 1.11 or laterWdfCoInstaller01011.dll
  5. Write an .inf file that installs Winusb.sys as the function driver for the USB device.

  6. Create a signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows.

  7. Attach the USB device to your computer.

  8. Open Device Manager to install the driver. Follow the instructions on the Update Driver Software wizard and choose manual installation. You will need to provide the location of the driver package folder to complete the installation.

Related topics

WinUSB Architecture and Modules
Choosing a driver model for developing a USB client driver
How to Access a USB Device by Using WinUSB Functions
WinUSB Power Management
WinUSB Functions for Pipe Policy Modification
WinUSB Functions
WinUSB