View Danny Meeks’ profile on LinkedIn, the world’s largest professional community. Danny has 1 job listed on their profile. See the complete profile on LinkedIn and discover Danny’s. Launch SeeMore and allow WIndows to again recognize your USB probe (s) and install the second and final USB probe driver. Note: Windows will install the above drivers for each USB port that has a probe attached. Once this second driver is installed for each USB port that has a probe attached, SeeMore will load and you can begin to image! View a list of all installed printers and print drivers in Windows 7. Whenever you are about to print a document or picture in Windows 7, the 'Print' dialog appears, giving you a choice of which printer or print driver to use to print that particular file. Drivers for windows xp: Interson USB Firmware Downloader.Use the links on this page to download the latest version of CDC Serial drivers. All drivers available for download have been scanned by antivirus program.buffalo ts3400d nas firmware 1 50 ckdqw Windows 8 downloads. Note: The software provided in the following download links are for Simpli Series array probes only. Please contact Interson Customer Support for software request for other ultrasound probes. Minimum System Requirements. Computer Operating System – Windows 7, 10; Minimum processor – 2.5 GHz (or 1.6 GHz if i5) Minimum RAM – 4 GB; USB 2.0 port.

Next:14.3 Windows CE DriverProgram Up:14. Distributing Your Driver Previous:14.1 Getting a ValidContents
  • All references to wdreg in this section can bereplaced with wdreg_gui, which offers the samefunctionality as wdreg but displays GUI messages insteadof console-mode messages.
  • If you have renamed the WinDriver kernel module(windrvr6.sys), as explained in section 15.2, replace the relevant windrvr6references with the name of your driver, and replace references to theWinDriverredist directory with the path to the directory that containsyour modified installation files. For example, when using the generatedDriverWizard renamed driver files for your driver project, as explainedin section 15.2.1, you can replace references tothe WinDriverredist directory with references to the generatedxxx_installationredist directory (wherexxx is the name of your generated driver project).
  • If you have created new INF and/or catalog files for your driver,replace the references to the original WinDriver INF files and/or to catalog file with the names of your newfiles (see information in sections 15.2.1 and 15.3.2 regardingrenaming of the original files).
  • If you wish to distribute drivers for both 32-bit and 64-bit targetplatforms, you must prepare a separate driver installation package foreach platform. The required files for each package are located within theWinDriver installation directory for the respective platform.

Distributing the driver you created is a multi-step process. First, create adistribution package that includes all the files required for the installationof the driver on the target computer. Second, install the driver on the targetmachine. This involves installing windrvr6.sys andwindrvr6.inf,installing the specific INF file for your device (for Plug-and-Play hardware - PCI/PCI Express/PCMCIA), and installing your KernelPlugIn driver (if you have created one).Finally, you need to install and execute the hardware control application thatyou developed with WinDriver. These steps can be performed usingwdreg utility.


Drivers Interstate Compact

This section refers to distribution of *.sys files. Startingfrom WinDriver version 6.21 *.vxd drivers are no longer supported.

14.2.1 Preparing the Distribution Package

Your distribution package should include the following files:

  • Your hardware control application/DLL.
  • windrvr6.sys.Get this file from the WinDriverredist directory inthe WinDriver package.
  • windrvr6.inf.Get this file from the WinDriverredist directory inthe WinDriver package.
  • this file from the WinDriverredist directory inthe WinDriver package.
  • wdapi1010.dll (for distribution of32-bit binaries to 32-bit target platforms or for distribution of 64-bitbinaries to 64-bit platforms) or wdapi1010_32.dll(for distribution of 32-bit binaries to 64-bit platforms [A.2]).Get this file from the WinDriverredist directory inthe WinDriver package.
  • difxapi.dll (required by thewdreg.exe utility [13.2.2]).
    Get this file from the WinDriverutil directory in theWinDriver package.
  • An INF file for your device (required for Plug-and-Play devices, such as PCI and PCMCIA).
    You can generate this file with the DriverWizard, as explained insection 4.2.
  • Your Kernel PlugIn driver - <KP driver name>.sys -if you have created such a driver.

14.2.2 Installing Your Driver on the Target Computer

Driver installation on Windows requires administrator privileges.

Follow the instructions below in the order specified to properly install yourdriver on the target computer:

  • Preliminary Steps:
    • To successfully install your driver, make sure that there are no open handles tothe WinDriver service (windrvr6.sys or your renamed driver [15.2]), and that there are no connected and enabledPlug-and-Play devices that are registered with this service. This is relevant, forexample, when upgrading the version of the driver (for WinDriverv6.0.0 and above; earlier versions used a different module name).If the service is being used, attempts to install the new driverusing wdreg will fail.
      You can disable or uninstall connected devices from the DeviceManager (Properties Disable / Uninstall) or usingwdreg, or otherwise physically disconnect thedevice(s) from the PC.
    • On Windows 2000, remove any INF file(s) previouslyinstalled for yourPlug-and-Playdevice (such as files created with an earlier version of WinDriver)from the %windir%inf directory before installingthe new INF file that you created for the device. This will preventWindows from automatically detecting and installing an obsoletefile. You can search the INF directory for the device's vendor IDand device/product ID to locate the file(s) associated with thedevice.
  • Install WinDriver's kernel module:
    1. Copy windrvr6.sys,windrvr6.inf and wd1010.catto the same directory.


      NOTE contains the driver'sAuthenticode digital signature. To maintain the signature'svalidity this file must be found in the same installation directoryas the windrvr6.inf file. If you select todistribute the catalog and INF files in different directories, ormake any changes to these files or to any other files referred toby the catalog file (such as windrvr6.sys), youwill need to do either of the following:
      • Create a new catalog file and re-sign the driver usingthis file.
      • Comment-out or remove the following line in thewindrvr6.inf file:
        and do not include the catalog file in your driverdistribution. However, note that this option invalidates thedriver's digital signature.
      For more information regarding driver digital signing andcertification and the signing of your WinDriver-based driver, referto section 15.3 of the manual.

    2. Use the utility wdreg to install WinDriver'skernel module on the target computer:
      wdreg -inf <path to windrvr6.inf> install

      For example, if windrvr6.inf andwindrvr6.sys are in the d:MyDevice directory on the target computer, the command shouldbe:
      wdreg -inf d:MyDevicewindrvr6.inf install

      You can find the executable of wdreg in theWinDriver package under the WinDriverutildirectory. For a general description of this utility and itsusage, please refer to Chapter 13.


      • wdreg is dependent on thedifxapi.dll DLL.
      • wdreg is an interactive utility. If itfails, it will display a message instructing the user how toovercome the problem. In some cases the user may be asked toreboot the computer.


      When distributing your driver, take care not to overwrite a newerversion of windrvr6.sys with an older version ofthe file in Windows drivers directory (%windir%system32drivers). You should configure your installationprogram (if you are using one) or your INF file so that theinstaller automatically compares the time stamp on these two filesand does not overwrite a newer version with an older one.

  • Install the INF file for your device (registering yourPlug-and-Play device with windrvr6.sys):

    Run the utility wdreg with the install command toautomatically install the INF file and update Windows Device Manager:
    wdreg -inf <path to your INF file> install

    You can also use the wdreg utility's preinstallcommand to pre-install an INF file for a device that is not currentlyconnected to the PC:
    wdreg -inf <path to your INF file> preinstall


    On Windows 2000, if another INF file was previously installedfor the device, which registered the device to work with thePlug-and-Play driver used in earlier versions of WinDriver remove anyINF file(s) for the device from the %windir%infdirectory before installing the new INF file that you created. This willprevent Windows from automatically detecting and installing an obsoletefile. You can search the INF directory for the device's vendor ID anddevice/product ID to locate the file(s) associated with the device.

  • Install your Kernel PlugIn driver: If you have created aKernel PlugIn driver, install it by following the instructions insection 14.2.3.
  • Install wdapi1010.dll:
    If your hardware control application/DLL useswdapi1010.dll (as is the case for the sample andgenerated DriverWizard WinDriver projects), copy this DLL to the target's%windir%system32 directory.If you are distributing a 32-bit application/DLL to a target 64-bitplatform [A.2], renamewdapi1010_32.dll in your distribution package towdapi1010.dll, and copy the renamed file to thetarget's %windir%sysWOW64 directory.


    If you attempt to write a 32-bit installation program that installs a64-bit program, and therefore copies the 64-bitwdapi1010.dll DLL to the%windir%system32 directory, you may find that thefile is actually copied to the 32-bit%windir%sysWOW64 directory. The reason for this isthat Windows x64 platforms translate references to 64-bit directoriesfrom 32-bit commands into references to 32-bit directories. You can avoidthe problem by using 64-bit commands to perform the necessaryinstallation steps from your 32-bit installation program. Thesystem64.exe program, provided in theWinDriverredist directory of the Windows x64 WinDriver distributions,enables you to do this.

  • Install your hardware control application/DLL: Copy yourhardware control application/DLL to the target and run it!

Drivers Intervention Programs In Ohio

14.2.3 Installing Your Kernel PlugIn on the Target Computer

Driver installation on Windows requires administrator privileges.

Drivers Intervention Program Cleveland Ohio


If you have created a Kernel PlugIn driver, follow the additionalinstructions below:

  1. Copy your Kernel PlugIn driver (<KP driver name>.sys) to Windows drivers directory on the targetcomputer (%windir%system32drivers).
  2. Use the utility wdreg to add your Kernel PlugIndriver to the list of device drivers Windows loads on boot. Use thefollowing installation command:

    To install a SYS Kernel PlugIn Driver:
    wdreg -name <Your driver name, without the *.sysextension> install

    You can find the executable of wdreg in the WinDriverpackage under the WinDriverutil directory. For ageneral description of this utility and its usage, please refer toChapter 13 (see specificallysection 13.2.4 for Kernel PlugIn installation).

Next:14.3 Windows CE Driver Up:14. Distributing Your DriverDrivers Previous:14.1 Getting a ValidContents