Download Asem Port Devices Driver

Posted on by admin



The Device Install Kit download site does not provide access to all Emerson Process Management device files. Device files distributed on DeltaV and AMS Device Manager release media are not duplicated for download from this site.

  1. Download Asem Port Devices Driver Updater
  2. Download Asem Port Devices Driverpack
  3. Download Asem Port Devices Drivers
  4. Download Asem Port Devices Driver Tp-link
  5. Download Asem Port Devices Driver
-->Port

A minidriver or a miniport driver acts as half of a driver pair. Driver pairs like (miniport, port) can make driver development easier. In a driver pair, one driver handles general tasks that are common to a whole collection of devices, while the other driver handles tasks that are specific to an individual device. The drivers that handle device-specific tasks go by a variety of names, including miniport driver, miniclass driver, and minidriver.

Microsoft provides the general driver, and typically an independent hardware vendor provides the specific driver. Before you read this topic, you should understand the ideas presented in Device nodes and device stacks and I/O request packets.

Every kernel-mode driver must implement a function named DriverEntry, which gets called shortly after the driver is loaded. The DriverEntry function fills in certain members of a DRIVER_OBJECT structure with pointers to several other functions that the driver implements. For example, the DriverEntry function fills in the Unload member of the DRIVER_OBJECT structure with a pointer to the driver's Unload function, as shown in the following diagram.

  • PyFtdi aims at providing a user-space driver for popular FTDI devices, implemented in pure Python language. Suported FTDI devices include: UART and GPIO bridges. FT232R (single port, 3Mbps) FT230X/FT231X/FT234X (single port, 3Mbps) UART and multi-serial protocols (SPI, I 2 C, JTAG) bridges. FT2232C/D (dual port, clock up to 6 MHz).
  • A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows.

The MajorFunction member of the DRIVER_OBJECT structure is an array of pointers to functions that handle I/O request packets (IRPs), as shown in the following diagram. Typically the driver fills in several members of the MajorFunction array with pointers to functions (implemented by the driver) that handle various kinds of IRPs.

An IRP can be categorized according to its major function code, which is identified by a constant, such as IRP_MJ_READ, IRP_MJ_WRITE, or IRP_MJ_PNP. The constants that identify major function code serve as indices in the MajorFunction array. For example, suppose the driver implements a dispatch function to handle IRPs that have the major function code IRP_MJ_WRITE. In this case, the driver must fill in the MajorFunction[IRP_MJ_WRITE] element of the array with a pointer to the dispatch function.

Typically the driver fills in some of the elements of the MajorFunction array and leaves the remaining elements set to default values provided by the I/O manager. The following example shows how to use the !drvobj debugger extension to inspect the function pointers for the parport driver.

In the debugger output, you can see that parport.sys implements GsDriverEntry, the entry point for the driver. Agilent driver. GsDriverEntry, which was generated automatically when the driver was built, performs some initialization and then calls DriverEntry, which was implemented by the driver developer.

You can also see that the parport driver (in its DriverEntry function) provides pointers to dispatch functions for these major function codes:

  • IRP_MJ_CREATE
  • IRP_MJ_CLOSE
  • IRP_MJ_READ
  • IRP_MJ_WRITE
  • IRP_MJ_QUERY_INFORMATION
  • IRP_MJ_SET_INFORMATION
  • IRP_MJ_DEVICE_CONTROL
  • IRP_MJ_INTERNAL_DEVICE_CONTROL
  • IRP_MJ_CLEANUP
  • IRP_MJ_POWER
  • IRP_MJ_SYSTEM_CONTROL
  • IRP_MJ_PNP

The remaining elements of the MajorFunction array hold pointers to the default dispatch function nt!IopInvalidDeviceRequest.

In the debugger output, you can see that the parport driver provided function pointers for Unload and AddDevice, but did not provide a function pointer for StartIo. The AddDevice function is unusual because its function pointer is not stored in the DRIVER_OBJECT structure. Instead, it is stored in the AddDevice member of an extension to the DRIVER_OBJECT structure. The following diagram illustrates the function pointers that the parport driver provided in its DriverEntry function. The function pointers provided by parport are shaded.

Making it easier by using driver pairs

Over a period of time, as driver developers inside and outside of Microsoft gained experience with the Windows Driver Model (WDM), they realized a couple of things about dispatch functions:

  • Dispatch functions are largely boilerplate. For example, much of the code in the dispatch function for IRP_MJ_PNP is the same for all drivers. It is only a small portion of the Plug and Play (PnP) code that is specific to an individual driver that controls an individual piece of hardware.
  • Dispatch functions are complicated and difficult to get right. Implementing features like thread synchronization, IRP queuing, and IRP cancellation is challenging and requires a deep understanding of how the operating system works.

To make things easier for driver developers, Microsoft created several technology-specific driver models. At first glance, the technology-specific models seem quite different from each other, but a closer look reveals that many of them are based on this paradigm:

  • The driver is split into two pieces: one that handles the general processing and one that handles processing specific to a particular device.
  • The general piece is written by Microsoft.
  • The specific piece may be written by Microsoft or an independent hardware vendor.

Suppose that the Proseware and Contoso companies both make a toy robot that requires a WDM driver. Also suppose that Microsoft provides a General Robot Driver called GeneralRobot.sys. Proseware and Contoso can each write small drivers that handle the requirements of their specific robots. For example, Proseware could write ProsewareRobot.sys, and the pair of drivers (ProsewareRobot.sys, GeneralRobot.sys) could be combined to form a single WDM driver. Likewise, the pair of drivers (ContosoRobot.sys, GeneralRobot.sys) could combine to form a single WDM driver. In its most general form, the idea is that you can create drivers by using (specific.sys, general.sys) pairs.

Function pointers in driver pairs

In a (specific.sys, general.sys) pair, Windows loads specific.sys and calls its DriverEntry function. The DriverEntry function of specific.sys receives a pointer to a DRIVER_OBJECT structure. Normally you would expect DriverEntry to fill in several elements of the MajorFunction array with pointers to dispatch functions. Also you would expect DriverEntry to fill in the Unload member (and possibly the StartIo member) of the DRIVER_OBJECT structure and the AddDevice member of the driver object extension. However, in a driver pair model, DriverEntry does not necessarily do this. Instead the DriverEntry function of specific.sys passes the DRIVER_OBJECT structure along to an initialization function implemented by general.sys. The following code example shows how the initialization function might be called in the (ProsewareRobot.sys, GeneralRobot.sys) pair.

The initialization function in GeneralRobot.sys writes function pointers to the appropriate members of the DRIVER_OBJECT structure (and its extension) and the appropriate elements of the MajorFunction array. The idea is that when the I/O manager sends an IRP to the driver pair, the IRP goes first to a dispatch function implemented by GeneralRobot.sys. If GeneralRobot.sys can handle the IRP on its own, then the specific driver, ProsewareRobot.sys, does not have to be involved. If GeneralRobot.sys can handle some, but not all, of the IRP processing, it gets help from one of the callback functions implemented by ProsewareRobot.sys. GeneralRobot.sys receives pointers to the ProsewareRobot callbacks in the GeneralRobotInit call.

At some point after DriverEntry returns, a device stack gets constructed for the Proseware Robot device node. The device stack might look like this.

As shown in the preceding diagram, the device stack for Proseware Robot has three device objects. The top device object is a filter device object (Filter DO) associated with the filter driver AfterThought.sys. The middle device object is a functional device object (FDO) associated with the driver pair (ProsewareRobot.sys, GeneralRobot.sys). The driver pair serves as the function driver for the device stack. The bottom device object is a physical device object (PDO) associated with Pci.sys.

Notice that the driver pair occupies only one level in the device stack and is associated with only one device object: the FDO. When GeneralRobot.sys processes an IRP, it might call ProsewareRobot.sys for assistance, but that is not the same as passing the request down the device stack. The driver pair forms a single WDM driver that is at one level in the device stack. The driver pair either completes the IRP or passes it down the device stack to the PDO, which is associated with Pci.sys.

Download Asem Port Devices Driver Updater

Example of a driver pair

Suppose you have a wireless network card in your laptop computer, and by looking in Device Manager, you determine that netwlv64.sys is the driver for the network card. You can use the !drvobj debugger extension to inspect the function pointers for netwlv64.sys.

In the debugger output, you can see that netwlv64.sys implements GsDriverEntry, the entry point for the driver. GsDriverEntry, which was automatically generated when the driver was built, performs some initialization and then calls DriverEntry, which was written by the driver developer.

Computer connections centralia

In this example, netwlv64.sys implements DriverEntry, but ndis.sys implements AddDevice, Unload, and several dispatch functions. Netwlv64.sys is called an NDIS miniport driver, and ndis.sys is called the NDIS Library. Together, the two modules form an (NDIS miniport, NDIS Library) pair.

This diagram shows the device stack for the wireless network card. Notice that the driver pair (netwlv64.sys, ndis.sys) occupies only one level in the device stack and is associated with only one device object: the FDO.

Available driver pairs

The different technology-specific driver models use a variety of names for the specific and general pieces of a driver pair. In many cases, the specific portion of the pair has the prefix 'mini.' Here are some of (specific, general) pairs that are available:

  • (display miniport driver, display port driver)
  • (audio miniport driver, audio port driver)
  • (storage miniport driver, storage port driver)
  • (battery miniclass driver, battery class driver)
  • (HID minidriver, HID class driver)
  • (changer miniclass driver, changer port driver)
  • (NDIS miniport driver, NDIS library)

Note As you can see in the list, several of the models use the term class driver for the general portion of a driver pair. This kind of class driver is different from a standalone class driver and different from a class filter driver.

Port

Related topics

If your computer doesn't recognize your connected device, you might see an unknown error or a '0xE' error. If you do, follow these steps and try to connect your device again after each step:

  1. Make sure that your iOS or iPadOS device is unlocked and on the Home screen.
  2. Check that you have the latest software on your Mac or Windows PC. If you're using iTunes, make sure you have the latest version.
  3. Make sure that your device is turned on.
  4. If you see a Trust this Computer alert, unlock your device and tap Trust.
  5. Unplug all USB accessories from your computer except for your device. Try each USB port to see if one works. Then try a different Apple USB cable.*
  6. Restart your computer.
  7. Restart your device:
  8. Try connecting your device to another computer. If you have the same issue on another computer, contact Apple Support.

For more help, follow the steps below for your Mac or Windows PC.


* Learn how to connect iPad Pro (11-inch) or iPad Pro 12.9-inch (3rd generation) to your computer.

If you use a Mac

  1. Connect your iOS or iPadOS device and make sure that it's unlocked and on the Home screen.
  2. On your Mac, hold down the Option key, click the Apple menu, and choose System Information or System Report.
  3. From the list on the left, select USB.
  4. If you see your iPhone, iPad, or iPod under USB Device Tree, get the latest macOS or install the latest updates. If you don't see your device or still need help, contact Apple Support.

If you use a Windows PC

The steps differ depending on if you downloaded iTunes from the Microsoft Store or from Apple.

If you downloaded iTunes from the Microsoft Store

Follow these steps to reinstall the Apple Mobile Device USB driver:

  1. Disconnect your device from your computer.
  2. Unlock your iOS or iPadOS device and go to the Home screen. Then reconnect your device. If iTunes opens, close it.
  3. Click and hold (or right-click) the Start button, then choose Device Manager.
  4. Locate and expand the Portable Devices section.
  5. Look for your connected device (such as Apple iPhone), then right-click on the device name and choose Update driver.
  6. Select 'Search automatically for updated driver software.'
  7. After the software installs, go to Settings > Update & Security > Windows Update and verify that no other updates are available.
  8. Open iTunes.

If you downloaded iTunes from Apple

Follow these steps to reinstall the Apple Mobile Device USB driver:

  1. Disconnect your device from your computer.
  2. Unlock your iOS or iPadOS device and go to the Home screen. Then reconnect your device. If iTunes opens, close it.
  3. Press the Windows and R key on your keyboard to open the Run command.
  4. In the Run window, enter:
    %ProgramFiles%Common FilesAppleMobile Device SupportDrivers
  5. Click OK.
  6. Right-click on the usbaapl64.inf or usbaapl.inf file and choose Install.
    You might see other files that start with usbaapl64 or usbaapl. Make sure to install the file that ends in .inf. If you’re not sure which file to install, right-click a blank area in the File Explorer Window, click View, then click Details to find the correct file type. You want to install the Setup Information file.
  7. Disconnect your device from your computer, then restart your computer.
  8. Reconnect your device and open iTunes.

If your device still isn't recognized

Check Device Manager to see if the Apple Mobile Device USB driver is installed. Follow these steps to open Device Manager:

  1. Press the Windows and R key on your keyboard to open the Run command.
  2. In the Run window, enter devmgmt.msc, then click OK. Device Manager should open.
  3. Locate and expand the Universal Serial Bus controllers section.
  4. Look for the Apple Mobile Device USB driver.

Download Asem Port Devices Driverpack

If you don't see the Apple Mobile Device USB Driver or you see Unknown Device:

  • Connect your device to your computer with a different USB cable.
  • Connect your device to a different computer. If you have the same issue on another computer, contact Apple Support.

Download Asem Port Devices Drivers

If you see the Apple Mobile Device USB driver with an error symbol:

If you see , , or next to the Apple Mobile Device USB driver, follow these steps:

Download Asem Port Devices Driver

  1. Restart the Apple Mobile Device Service.
  2. Check for and resolve issues with third-party security software, then restart your computer.
  3. Try to install the usbaapl64.inf or usbaapl.inf file again.