Jungo windriver для windows 10

Купите у нас рекламу ! Your advertising could be here ! E-mail для связи:

Уважаемые пользователи портала 2BakSa.WS и форума NoWa.cc ! Рады Вам сообщить, что у нас открылся Torrent трекер >> BRODIM.COM . Приглашаем вас принять участие в обмене полезной информацией, и ждем от вас поддержки в создании новых раздач.

Спасибо за поддержку!

WinDriver — семейство программных продуктов для быстрого создания высокопроизводительных, высококачественных драйверов устро-йств для работы в пользовательском режиме. Не требуется знаний DDK или уровня разработки ядра. Преимущетсва WinDriver: значительно облегчает и сокращает цикл разработки драйвера, разработка в режиме пользователя — выполнение в режиме ядра, не требуется знаний внутренней структуры ОС или ядра, не требуется знаний DDK, — оптимальная производительность, высокая надежность — поддержка кросс-платформ и множества ОС.

WinDriver™ USB for Windows automates and simplifies the development of user mode Windows device drivers for USB. No DDK knowledge or kernel level programming required.

WinDriver for Windows Desktop Supported Platforms

Windows 10 / Windows 8 / Windows 8 x64 / Windows 7 / Windows 7 x64 / Server 2008 / Server 2008 x64, 32 bit or 64 bit (x64: AMD64 and Intel EM64T) processor

WinDriver for WinCE Supported Platforms

• An x86 / MIPS / ARM Windows CE 4.x–7.0 (.NET) target platform
• WinCE 2013 — WEC 2013 8.0 for x86 and ARM
• For Windows CE 4.x–6.0 — Microsoft Embedded Visual C++ with a corresponding target SDK, or Microsoft Platform Builder with a corresponding BSP (Board Support Package) for the target platform; also required for Windows Mobile 6.0 — Microsoft Visual Studio (MSDEV) .NET 2005

WinDriver for Linux Supported Platforms

• x86 32-bit, x86 64-bit (x86_64: AMD64).
• Supported Linux kernel (including embedded Linux):
  • For x86 32-bit architectures:Linux kernel 2.6-5.10.3
  • For x86 64-bit architectures: Linux kernel 2.6-5.10.3
  • PCI / PCIe
• Any 32-bit or 64-bit development environment (depending on your target platform) supporting C.

Jungo’s professional services unit provides a complete Windows Hardware Certification (aka WHQL) submission service for WinDriver customers.

How to Install WinDriver

Below you will find instructions for , , and .

Installation Instructions for Windows

• Any x86 32-bit or 64-bit (x64: AMD64 or Intel EM64T) processor.
• Any compiler or development environment supporting C or .NET
• Windows XP requires at least SP2.

Installation

1. 1. Run the WinDriver installation — WD .EXE (for example, WD1460.EXE) — and follow the installation instructions.
   2. At the end of the installation, you may be prompted to reboot your computer.

• • The WinDriver installation defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard code generation — it determines the default directory for saving your generated code and is used in the include paths of the generated project/make files. This variable is also used from the sample Kernel PlugIn projects and makefiles.
  • If the installation fails with an ERROR_FILE_NOT_FOUND error, inspect the Windows registry to see if the RunOnce key exists in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion . This registry key is required by Windows Plug-and-Play in order to properly install drivers using INF files. If the RunOnce key is missing, create it; then try installing the INF file again.

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo Connectivity, follow these steps:

3.Start DriverWizard: Start | Programs | WinDriver | DriverWizard.

4. Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo Connectivity.

5. Click the Activate License button.

6. To register source code you developed during the evaluation period —

• • For USB, refer to the documentation of WDU_Init() in the .
  • For PCI, refer to the documentation of WDC_DriverOpen() in the .When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the .

Installation Instructions for Windows CE

System Requirements

• • An x86 or ARM target platform running Windows CE (a.k.a. Windows Embedded Compact) 4.x–8.x (including Windows Mobile)
    OR
    a MIPS target platform running Windows CE 4.x–7.x (including Windows Mobile)

• • Windows 10/8.1/Server 2016/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP host development platform.

IDE:

• For Windows Embedded CE 6.x: Microsoft Visual Studio 2005/2008 with a corresponding target SDK or with the Windows CE 6.0 plugin.
• For Windows CE 4.x–5.x (including Windows Mobile):
  • Microsoft eMbedded Visual C++ or Microsoft Visual Studio 2005/2008 with a corresponding target SDK
  • Microsoft Platform Builder with a corresponding Board Support Package (BSP) for the target platform

• For Windows Embedded CE 7.x: Microsoft Visual Studio 2008 with the Windows Embedded Compact 7 plugin
• For Windows Embedded CE 8.x: Microsoft Visual Studio 2012 or higher with the Application Builder for Windows Embedded Compact 2013 plugin

Installation

Installing WinDriver CE when Building New CE-based Platforms

• • The following instructions apply to platform developers who build Windows CE kernel images using Windows CE Platform Builder or using MS Visual Studio 2005/2008 with the appropriate Windows CE 6.0 plugin. The instructions use the notation “Windows CE IDE” to refer to either of these platforms.
  • We recommend that you read Microsoft’s documentation and understand the Windows CE and device driver integration procedure before you perform the installation.
  Modify the project registry file — WinDriver\samples\wince_install\project_wd.reg — to add an entry for your target device.

  Integrate the driver into your platform:

  1. Run the Windows CE IDE and open your platform.
  2. Select Open Build Release Directory from the Build menu.
  3. Copy the WinDriver CE kernel file — WinDriver\redist\ \windrvr1460.dll — to the %_FLATRELEASEDIR% subdirectory on the target development platform (should be the current directory in the new command window).
  4. Append the contents of WinDriver\samples\wince_install\project_wd.reg to the %_FLATRELEASEDIR%\project.reg registry file.
  5. Copy the contents of the WinDriver\samples\wince_install\project_wd.bib file to the FILES section of the binary image builder file — %_FLATRELEASEDIR%\project.bib. Then uncomment the line that matches the target platform (see the “TODO” comments in the copied text).

  Installing WinDriver CE when Developing Applications for CE Computers

  The following instructions apply to driver developers who do not build the Windows CE kernel, but only download their drivers, built using MS eMbedded Visual C++or MS Visual Studio 2005/2008 to a ready-made Windows CE platform.

  1. 1. Run the WinDriver installation — WD CE.EXE (for example, WD1460CE.EXE) — on your host Windows PC, and complete the installation.
     2. Copy WinDriver’s kernel module — windrvr1460.dll — from the WinDriver\redist\WINCE\ directory on the Windows host development PC to the Windows directory on your target Windows CE platform
     3. Add WinDriver to the list of device drivers Windows CE loads on boot:
        • • Modify the registry according to the entries documented in the file WinDriver\samples\wince_install\project_wd.reg. This can be done using the Windows CE Pocket Registry Editor on the hand-held CE computer, or by using the Remote CE Registry Editor Tool supplied with MS eMbedded Visual C++ or MS Visual Studio 2005/2008. Note that in order to use the Remote CE Registry Editor tool you will need to have Windows CE Services installed on your Windows host platform.
  2. On many versions of Windows CE, the operating system’s security scheme prevents the loading of unsigned drivers at boot time, therefore the WinDriver kernel module has to be reloaded after boot. To load WinDriver on the target Windows CE platform every time the OS is started, copy the WinDriver\redist\Windows_Mobile_5_ARMV4I\wdreg.exe utility to the Windows\StartUp\ directory on the target PC.
  3. Restart your target CE computer. The WinDriver CE kernel will automatically load. You will have to do a warm reset rather than just suspend/resume (use the reset or power button on your target CE computer).
  4. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see the for an explanation on how to check your installation).

  Windows CE Installation Note:

  The WinDriver installation on the host Windows PC defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard code generation — it determines the default directory for saving your generated code, and is used in the include paths of the generated project/make files.

  Note that if you install the WinDriver Windows toolkit on the same host PC, the installation will override the value of the WD_BASEDIR variable from the Windows CE installation.

  Installation Instructions for Linux

  System Requirements
  

  • • Any of the following processor architectures, with a 2.6.x or higher Linux kernel:
      • 32-bit x86
      • 64-bit x86 AMD64 or Intel EM64T (x86_64)
      • PowerPC 32-bit or 64-bit (PCI only)
    • A GCC compiler
      The version of the GCC compiler should match the compiler version used for building the running Linux kernel.
    • Any 32-bit or 64-bit development environment (depending on your target configuration) supporting C for user mode
    • On your development PC: glibc2.3.x
    • libstdc++.so.6 and libpng12.so.0 — required for running GUI WinDriver applications (e.g., DriverWizard; Debug Monitor)

    Preparing the System for Installation

    In Linux, kernel modules must be compiled with the same header files that the kernel itself was compiled with. Since WinDriver installs the kernel modules, it must compile with the header files of the Linux kernel during the installation process.

    Therefore, before you install WinDriver for Linux, verify that the Linux source code and the file version.h are installed on your machine:

    Install Linux kernel source code:

  • If you have yet to install Linux, install it, including the kernel source code, by following the instructions for your Linux distribution.
  • If Linux is already installed on your machine, check whether the Linux source code was installed. You can do this by looking for ‘linux’ in the /usr/src directory. If the source code is not installed, either install it, or reinstall Linux with the source code, by following the instructions for your Linux distribution.

  Install version.h:

  The file version.h is created when you first compile the Linux kernel source code. Some distributions provide a compiled kernel without the file version.h. Look under /usr/src/linux/include/linux/ to see whether you have this file. If you do not, follow these steps:

  1. Become super user:
     $ su
  2. Change directory to the Linux source directory:
     # cd /usr/src/linux
  3. Type
     # make xconfig
  4. Save the configuration by choosing Save and Exit.
  5. Type
     # make dep
  6. Exit super user mode:
     # exit

  To run GUI WinDriver applications (e.g., DriverWizard; Debug Monitor) you must also have version 6.0 of the libstdc++ library — libstdc++.so.6 — and version 12.0 of the libpng library — libpng12.so.0. If you do not have these files, install the relevant packages for your Linux distribution (e.g., libstdc++6 and libpng12-0).

  Before proceeding with the installation, you must also make sure that you have a ‘linux’ symbolic link. If you do not, create one by typing
  /usr/src$ ln -s linux
  For example, for the Linux 3.0 kernel type
  /usr/src$ ln -s linux-3.0/ linux

  Installation

  On your development Linux machine, change directory to your preferred installation directory, for example to your home directory:
  $ cd

  /WD1460LN.tgz

  1. Change directory to your WinDriver redist/ directory (the tar automatically creates a WinDriver/ directory):
     $ cd /redist/
  2. Install WinDriver:
     1. 1. For USB:
           /redist$ ./configure
           For PCI:
           /redist$./configure —disable-usb-support

        The configuration script creates a makefile based on the running kernel. You may select to use another installed kernel source, by executing the script with the —with-kernel-source=

        is the full path to the kernel source directory — e.g., /usr/src/linux.

     2. If the Linux kernel version is 2.6.26 or higher, the configuration script generates makefiles that use kbuild to compile the kernel modules. You can force the use of kbuild on earlier versions of Linux, by executing the configuration script with the —enable-kbuild flag.

For a full list of the configuration script options, use the —help option:
./configure —help

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo Connectivity, follow these steps:

/wizard/wdwizard

Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo Connectivity.

Click the Activate License button.

To register source code you developed during the evaluation period —

• For USB, refer to the documentation of WDU_Init() in the .

• For PCI, refer to the documentation of WDC_DriverOpen() in the .When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the .

For security reasons the WinDriver installation script does not automatically perform the steps of changing the permissions on /dev/windrvr1460 and the DriverWizard executable (wdwizard).

Online Support Center for customer/evaluator: Secured Support Center (can’t access? use the non-secured version). For general inquiries: email [email protected] .

WinDriver Tutorials